Problem seeing all machines in a workgroup

[Mr Thanks]

On my network I have 1 workgroup containing mostly w2k pro
machines with a couple of NT servers, a couple of w2k
servers and a couple of w2k3 servers.

The network contains a DNS server and WINS server. All
machines have static IP addresses.

If on any machine, I go to 'My Network Places' and access
the Workgroup I can only see those machines which have the
same default gateway as the machine I am on.
E.g. if I'm on a machine with IP address 10.1.10.20,
subnet mask 255.255.255.0, default gateway 10.1.10.1 then
I can only see machines with IP addresses that start
10.1.10.
I see the same machines in 'Computers Near Me'.

All machines have the following network protocols
installed: Client for Microsoft Network, File and Printer
Sharing for Microsoft Networks, TCP/IP. The Computer
Browser service is running on all machines. All machines
have the correct IP addresses for the DNS and WINS. I can
ping and map drives to all machines, regardless of whether
I can see them in the Workgroup or not.

So the question comes in 2 parts...
1. Is it normal behaviour to only be able to see machines
with the same default gateway as you in the Workgroup? If
not, what could cause this.

2. Sometimes when a machine is booted up and connects to
the network, you cannot access the workgroup. The message
is 'Workgroup is not accessible. Network path not found'
but I can still ping and map drives to all machines. What
could the cause of this be?

When this happens I have left the machine for up to 3
hours before trying again, with the same results.

If I reboot and try again then normally I can access the
Workgroup straight away. This happens occasionally on most
machines and not just on the same troublesome machine.

This isn't really causing any problems because everyone
can access everything they need to on the network, its
just frustrating not knowing what it could be and whether
it is a symptom of something else.

 

[Richard G. Harper]

In regard to question #1, that's the general purpose of subnetting
computers. Only the computers in the same subnet (10.1.10.x, 255.255.255.0)
will see each other. If you want all computers to be visible then you need
to alter your subnet or their addresses so that they will all appear. For
example, if you were to change the netmask to 255.255.240.0 then you could
see all computers in the range 10.1.1.x - 10.1.31.x as one subnet.

In regard to question #2, this is entirely normal in a workgroup
environment. With no domain controller to hold the master browser list (all
the available PCs in a workgroup) there will be an election process to
determine who will hold the master browser list. If computers are shut down
and started up frequently the election process will likely keep happening
and disrupting browsing. As your workgroup and network are performing
correctly even when browsing is unavailable you don't really need to worry
about it.

 

[Mr Thanks]

Thanks, your answer was at just the sort of technical
level I was after.

I'm off to read up on subnetting.

 

[Richard G. Harper]

Glad I was able to help.

 

[Richard G. Harper]

Slight correction ... the range should, of course, be 10.101.0.x -
10.101.31.x for a netmask of 255.255.240.0 - not enough coffee as I typed
that one. ;-(

--
Richard G. Harper [MVP Win9x] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

In regard to question #1, that's the general purpose of subnetting
computers. Only the computers in the same subnet (10.1.10.x,
255.255.255.0) will see each other. If you want all computers to be
visible then you need to alter your subnet or their addresses so that they
will all appear. For example, if you were to change the netmask to
255.255.240.0 then you could see all computers in the range 10.1.1.x -
10.1.31.x as one subnet.

In regard to question #2, this is entirely normal in a workgroup
environment. With no domain controller to hold the master browser list
(all the available PCs in a workgroup) there will be an election process
to determine who will hold the master browser list. If computers are shut
down and started up frequently the election process will likely keep
happening and disrupting browsing. As your workgroup and network are
performing correctly even when browsing is unavailable you don't really
need to worry about it.

--
Richard G. Harper [MVP Win9x] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

On my network I have 1 workgroup containing mostly w2k pro
machines with a couple of NT servers, a couple of w2k
servers and a couple of w2k3 servers.

The network contains a DNS server and WINS server. All
machines have static IP addresses.

If on any machine, I go to 'My Network Places' and access
the Workgroup I can only see those machines which have the
same default gateway as the machine I am on.
E.g. if I'm on a machine with IP address 10.1.10.20,
subnet mask 255.255.255.0, default gateway 10.1.10.1 then
I can only see machines with IP addresses that start
10.1.10.
I see the same machines in 'Computers Near Me'.

All machines have the following network protocols
installed: Client for Microsoft Network, File and Printer
Sharing for Microsoft Networks, TCP/IP. The Computer
Browser service is running on all machines. All machines
have the correct IP addresses for the DNS and WINS. I can
ping and map drives to all machines, regardless of whether
I can see them in the Workgroup or not.

So the question comes in 2 parts...
1. Is it normal behaviour to only be able to see machines
with the same default gateway as you in the Workgroup? If
not, what could cause this.

2. Sometimes when a machine is booted up and connects to
the network, you cannot access the workgroup. The message
is 'Workgroup is not accessible. Network path not found'
but I can still ping and map drives to all machines. What
could the cause of this be?

When this happens I have left the machine for up to 3
hours before trying again, with the same results.

If I reboot and try again then normally I can access the
Workgroup straight away. This happens occasionally on most
machines and not just on the same troublesome machine.

This isn't really causing any problems because everyone
can access everything they need to on the network, its
just frustrating not knowing what it could be and whether
it is a symptom of something else.