Workgroup/Share issues - Invisible folders

[Guest]

Hello,

I'm having a very strange problem with 2 PC's setup for workgroup networking
(ie. not on a domain). I am able to bonnect to \\computername\share\ and
browse, but certain folders are invisible. However, if I leave this window
open and connect to the same computer via IP rather than name (ie.
\\10.200.1.20\share\) the folders become visible (in both explorer windows).
Anyone have an idea on this?

Here is the setup:

- 2 PC's (1 desktop, 1 laptop)
- both are running XP Pro SP2 (w/ all subsequent patches to date)
- Both have the Windows Firewall enabled
- both have run through the "Network Setup Wizard"
- File/Printer sharing enabled
- File sharing ports allowed through FW (via exceptions)
- both have NetBIOS over TCP/IP enabled in the networking-WINS tab.

Any help with this annoyance would be greatly appreciated.

 

[Chuck]

Hello,

I'm having a very strange problem with 2 PC's setup for workgroup networking
(ie. not on a domain). I am able to bonnect to \\computername\share\ and
browse, but certain folders are invisible. However, if I leave this window
open and connect to the same computer via IP rather than name (ie.
\\10.200.1.20\share\) the folders become visible (in both explorer windows).
Anyone have an idea on this?

Here is the setup:

- 2 PC's (1 desktop, 1 laptop)
- both are running XP Pro SP2 (w/ all subsequent patches to date)
- Both have the Windows Firewall enabled
- both have run through the "Network Setup Wizard"
- File/Printer sharing enabled
- File sharing ports allowed through FW (via exceptions)
- both have NetBIOS over TCP/IP enabled in the networking-WINS tab.

Any help with this annoyance would be greatly appreciated.

Can see some folders but not others. Sounds familiar. Check your Windows
Update history - is KB885250 in your list as applied?
<http://groups.google.com/group/micr...b&q=885250&qt_g=1&searchnow=Search+this+group>

 

[Guest]

Thanks Chuck!
I removed KB885250 on both machines - so far so good...

 

[Chuck]

Thanks Chuck!
I removed KB885250 on both machines - so far so good...

Thanks for the update!