Browser Not showing Subnets

[dfren]

Hello, and Thanks

We are experiencing problems with our Browser service. When we go to "Network Places" on a W/2000 Pro machine we get the following error.
""MyDomainName" is not accessible""
"The list of Servers for this workgroup is not currently available"

Now if we go to the Server and look in "Network Places" I can see the Local Computers, but not any in the "two" other subnets. Everything else seems to be working fine i.e. DNS, DHCP, & WINS.
The W/2000 Server is a File & Print Server which is also running AD, DNS, DHCP, & WINS as stated above. I've experienced symptoms like some of the subnets dropping off previously, but never with the error message as above.

This problem appeared after the removal & reinstall of a trial version of Server Protect which we are currently reviewing as our AntiVirus software. The W/2000 Server is the "Normal Server" in this software, and a W/2000 Pro. machine is the "Information Server" as the W/2000 Server does not have internet access, and cannot receive updates. This was all previously working fine, and I'm thinking something didn't go right with the Uninstall.
This is not a major issue, but an inconvienance as I cannot quickly verify what computers are connected to the Network. I can ping computers without problem, and nothing seems to be wrong with the Network in general.

I need a place to start....

Thanks in advance for your time...

 

[ShackDaddy]

I'd start by checking WINS. Everything I know about the subject suggests that your browsing infrastructure is crippled, and WINS would be the hub of it. Make sure that each of your subnets has a browsemaster record in the WINS database. If there are three, then clients should be able to browse between the three subnets. Also compare the LanManServer\Parameters registry key on your server with the same key on another Win2k file server in your network. It could be that the security software changed some settings that might have crippled browsing.

ShackDaddy

 

[tosberg]

We had a similar problem. We had to enable the "Use netbios setting from the DHCP server" Or the "Enable netbios over TCP/IP" setting. Get to this by right clicking on My Network Places->Properties->Local Area Connection->Internet Protocol (TCP/IP)->Properties->Advanced->WINS (tab). Enable one or the other as either one checked solved our problem.