Some PCs not showing up in Workgroup

[cscsonline]

A client of mine has a server running W2K Server with SP4 and has 6 PCs as clients in a Workgroup.
All the client PCs are running WXP SP2 and have AVG Internet Security on them. The firewall allows all network traffic from 192.168.0.1 to 192.168.0.100.

The server sees three of the PCs but will not see the other three and likewise none of the client machines seen on the server can see the other three that are not showing on the server.

The bizarre thing was that two of these unseen PCs showed up on the network briefly but don't anymore.

Can anyone suggest why this might be and how I can get all the PCs to show up on the server.I have run the wizard in WXP several times.

 

[GrimR]

Lets eliminate the following
I take the server has no AD running, and all computers have IP Addresses [not conflicting].
All have same subnet mask?
All computer browser services have started?
All have the same workgroup name?
Can all ping each other?

 

[GrimR]

Clients for MS Installed?
File and Print sharing selected?
Netbios over tcp/ip checked?

 

[itsp1965]

First try running the Browser service only on the server and disable it on the workstations. It's possible that there are browser elections that are hindering the browsing process

 

[cscsonline]

Each PC has its own IP address - no conflicts.
All have the same Workgroup name.
They can ping each other.
File and Print sharing is selected.
I'm uncertain about Netbios over TCP/IP being checked.
I'm not sure about the Browser service. How do I disable it on on the workstations?
I'll check on my next visit.
Thanks for the feedback so far.

 

[kmcferrin]

The "workgroup" functionality that you are describing relies on NetBIOS in order to identify systems. Each PC regularly broadcasts data about itself on the network, and that's how the discovery happens. Within the network there will be a "master browser" that maintains the browse lists for the various machines on the network (these lists include what resources are available). As machines do NetBIOS broadcasts they list what resources are available over NetBIOS (usually file shares) and the Master Browser collects the data and maintains the lists. If anything is blocking NetBIOS traffic this process will be broken. If your PCs cannot see the master browser, then this process will be broken. In the event that the PC cannot locate the master browser, it will send a broadcast to force an election of a new master browser. There are a number of rules that the election process follows, but in the end a new master browser will be selected. If your PC cannot see any other PCs on the network then it will win the election. So if you have 7 PCs and 1 server all firewalled off from each other, you could have 8 different systems that see themselves as a master browser, and none of them will be able to see resources from the other ones.

Assuming that all of your PCs are on the same network, you would want to make sure that NetBIOS over TCP/IP is running AND that your software firewalls are not blocking NetBIOS broadcasts (which they usually do).

 

[MoLaker]

I might add to kmcferrin's statement that commonly network switches/routers can be set to NOT pass netbios. With some, this is the default setting and with some, this can be set by individual port. If other measures don't resolve the problem, check out your network.

"Retired Programmer", that is. So, please be patient.

 

[GrimR]

cscsonline, if you running networks these are very standard things you should be checking. NetBIOS over TCPIP has been explained by kmcferrin, but just to add to this, the default is Use NetBIOS from DHCP server, but seems as your running a Workgroup you don't have a DHCP server.

kmcferrin nice explanation on the whole browser thing I had to do 2 x MCSE's MCSA MCDBA etc to learn all this.

And based on kmcferrin if a computer wins an election then the 3 new computers may only see each other.
To overcome this you could read up on registry browser elections. Try some google.

And lastly you should still be able to map drives by \\computerName\shareName

 

[kmcferrin]

Good point about the default NetBIOS over TCP/IP settings. If you're using a the firewall device for DHCP then I you may not be getting the correct node type settings.

 

[xmsre]

SOunds like you are having issues registering netbios names with the master browser via broadcasts. Why don't you implement WINS instead?

 

[cscsonline]

I shall revisit my client on Friday and will report back. Thanks for all the feedback.

 

[mikey61]

You need to make sure AVG allows File and Printer sharing, AVG disables this by default. I just ran into this myself on a server and that was the cause. A good 1st place to look.