Windows Forum·65,705 discussions

192sub only see’s its own servers

Locked

WE have 12 servers, on a class c network( 204). We recently created a subnet (192) . The 192 subnet only see’s servers on the 192 subnet in the network neighbourhood but can ping and connect to all servers on both the 204 and the 192 subnet. I do not know how to get the clients (nt/98) on the 192 subnet to see all servers (204& 192 subnets). Note only users on 192 have this problem all users on the 204 subnet can see all in network neighbourhood on both subnets.

Topic

192sub only see’s its own servers

In reply to 192sub only see’s its own servers

are you pinging by IP address? or by computer name? if you can ping by ip but not by name, then it’s a WINS issue. test to see if this is true by using a LMHOSTS file.

192sub only see’s its own servers

In reply to 192sub only see’s its own servers

The question was auto-closed by TechRepublic

192sub only see’s its own servers

In reply to 192sub only see’s its own servers

Sounds to me like you have your WINS server on the 204 subnet, with the clients from the 192 subnet not registering with WINS. Check your WINS database to see if all systems have registered. You say that all can be seen in NN. All systems? Or all Servers? If all servers, check to make sure clients all have WINS server configured in TCP properties.
As the previous poster says, you can always back the whole name resolution thing up with a well configured LMHOSTS file. Just put #PRE entries for all servers and copy the file as LMHOSTS to the system32\drivers\etc folder on all systems. (Works faster, too, with less network traffic….no name resolution traffic)

Good luck,

Ian

192sub only see’s its own servers

In reply to 192sub only see’s its own servers

The question was auto-closed by TechRepublic

192sub only see’s its own servers

In reply to 192sub only see’s its own servers

This question was auto closed due to inactivity

[Author]

Replies