Windows Forum

Ask something
Discussion Locked

Can't browse network

0 helpful
14 replies

by bv2

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a fileserver running Windows 2003 Server, and 20-30 workstations running XP Pro. I have mapped network drives that are completely accessible. My problem is that I cannot browse the workgroup. At the Run prompt, I can type in the UNC location (\\server1) and view the contents, but I can't browse to it through My Network Places. I always get an error telling me my workgroup is not accessible and I need to contact my system administrator. It's not causing any problems for users, but I can't figure out why I can't browse...

14 replies

by lmon

Mosre than likely you have a firewall issue which is not configured correctly. Something Zone Alarm, Noron's Anti-Virus script blocking service or password validation. start by ther.

by bv2

Nope - problem only occurs on the XP machines, and there is no firewall between the server and the workstations. Password validation isn't an issue because I can access the workgroups through UNC notation, but not through browsing.

by lmayeda

I had a similar problem when setting up a new XP on an existing LAN. It turned out that there is a Internet Connection Firewall paramenter in the LAN, Properties, Advanced which by default is set to "protect my computer and network by limiting or preventing access to this computer from the internet". Uncheck this box and you should be able to browse the XP. Hope this works for you.

by bv2

I appreciate the link, but is there a direct correlation? Are you telling me that Windows 2000 Server is too old to connect via TCP/IP to XP - especially given the fact my erred post said Windows 2003 Server, which would mean a year old OS can't talk TCP/IP?

by mikex

Right click my computer=>Properties=>Network identification tab=>properties button=>change (as i suspect there must be a workgroup settings on) the workgroup option to a domain and type your domain name there=>you'll be asked for user name and password and domain to login properly (WARNING - this will change your user profile, so all of your settings can be lost and you'll need to start like a new user)

by vryce

Sorry about the previous answer being ambiguous, I didn't notice your correction to Server 2000. So I thought the problem might have been netBEUI not being installed on server 2k3.

All I can suggest are:
Make sure the workgroup names all match, and
the Knowledge Base article: 285035

Hope it helps.

by bv2

Thanks, Vryce, but no dice (purely unintentional rhyme). The workstations are configured to use NetBIOS setting from the DHCP server and I have also tried the setting of enable netbios over tcp/ip with nil results. The exact error is "'WORKGROUP' is not accessible. You might not have permission to access this network resource. Contact the administrator of this server to find out if you have access permissions. The network path was not found."

This discussion is closed to new replies.