Windows Forum

Ask something
Discussion Locked

Wins is acting funky

0 helpful
10 replies

by bgreenwood10

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

I have a network that is broken up into two subnets, each at a different location. I have a PDC on one and a BDC on the other. The PDC is acting as the WINS server.

On the PDC side in network neighborhood, I can see everything on it's subnet but only the BDC on the other side and vice-versa for the other side. The funny thing is, is that when I reboot the BDC, both sides can see everything but after about fifteen minutes they can only see their respective subnets through network neighborhood.

At one point this was working fine. The only thing that has changed is that I reconfigured the network to allow for more hosts on each subnet. As soon as I did that I ran into this problem.

10 replies

by Former member

It's got a lot to do with netbios resolution and the order of resolution, which depends on which Netbios nodetypes you workstations are using. I can't remember the order for each nodetype, but an example would be: Cache, broadcasts, WINS, LMHOSTS, ..etc. You can force your workstation to resolve using the WINS server first by changing the node type to P-node.

Another solution would be to install a WINS pull service on the BDC...

by Former member

It's got a lot to do with netbios resolution and the order of resolution, which depends on which Netbios nodetypes you workstations are using. I can't remember the order for each nodetype, but an example would be: Cache, broadcasts, WINS, LMHOSTS, ..etc. You can force your workstation to resolve using the WINS server first by changing the node type to P-node.

Another solution would be to install a WINS pull service on the BDC...

by Former member

It's got a lot to do with netbios resolution and the order of resolution, which depends on which Netbios nodetypes you workstations are using. I can't remember the order for each nodetype, but an example would be: Cache, broadcasts, WINS, LMHOSTS, ..etc. You can force your workstation to resolve using the WINS server first by changing the node type to P-node.

Another solution would be to install a WINS pull service on the BDC...

by bgreenwood10

Both the P/H-node hit the WINS server first. The only difference between the P and H node, (I am using H), is that the P-Node does not do a broadcast if the name is not in the WINS database. It goes straight to an LMHOSTS file. Using DHCP, I do not want to keep an up to date LMHOST file for every machine.

The WINS server has all of the entries for both sides in it's database. I can ping either side by computer name with success from any computer. I just can't see the other side subnet from network neighborhood.

If you can revoke your answer I will not grade it.

This discussion is closed to new replies.