Discussion Locked

nethood browser/multiple subnet issue

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a network utilizing two subnets 192.168.67.* & 192.168.65.*
(NT4 domain)
The PDC, WINS, and DNS servers are all on the .67.
The problem is workstations on the 65 segment have problems 'seeing' machines on the 67, until i physically add them to the lmhosts/hosts files.
They can ping etc.. just not browse or resolve by machine name.
I moved the BDC to the 65 segment in order to correct any login script problems.
The network *looks* right and connectivity works fine once the lmhosts/hosts files are updated..
There are no problems with the 67 machines browseing anything on the 65.
any ideas?

7 replies

by mpdcsup

Not wanting to make any assumptions, I have a few questions:

Are all of the machines domain members of a single domain and does each machine have the proper WINS server address in its IP configuration?

You can't ping by hostname without entries in each machine's host file -- you're not running DNS?

You *should* be able to add a single item in the lmhosts file that will point out the domain controller (and browse master) -- this is what WINS is supposed to do, so if it works by setting an entry in lmhosts, the problem lies with WINS (like hosts is a static, local alternative to DNS).

The lmhosts setting goes like this:

192.168.67.16 servername #PRE DOM:domainname

Another question: Has the BDC always been on .65? If so, (and if the browsing has never worked) you might have a situation where the PDC and BDC each believe they are the domain master browser -- check and make sure the BDC has the proper WINS address in its IP configuration.

Finally, if you're still having trouble, and if your two subnets are on the same physical segment put the PDC on the .65 subnet too (on both) by adding a second IP address to the existing NIC -- as a plus this will also alleviate the routing overhead of packets to and from the PDC and the .65 subnet.

by gbworld

The problem is that the computers on .65 are not resolving the DNS server. They are also not resolving WINS (lmhosts), but you have not said anything about a WINS server.

Note that the BDC will not solve the DNS problems. The BDC will solve machines logging onto the domain, which you have not stated is a problem.

The most likely problem here is that you are not setting up the gateway between the networks properly. Perhaps you have an Internet gateway and have only set that one up, I am not sure. If you are using DHCP, you will have to specify all gateways this network can use.

The router you have chosen to segment your network with can have a profound effect on your network, esp. with DHCP.

My suggestions:

1. Run an ipconfig /all (winipcfg on 9x/ME) and find out if the gateway between the segments is resolving. You also want to check to make sure the DNS server(s) show up in ipconfig.

a) You may simply have to add another gateway.

b) You may just have to add the DNS server.

If this is all windows, a WINS server could help, but there are pluses and minuses to this approach.

If you are using DHCP, make sure you have it on both segments and make sure that they are talking. If not, you may need a DHCP relay agent.

Also, check and make sure the BDC is talking to the PDC. This will help you identify where the problem is coming from.

Gregory A. Beamer
MCP: +I, SE, SD, DBA

by Former member

You need a WINS server and hybrid or p-node clients, or you need the router to pass broadcasts..

This discussion is closed to new replies.