21 replies
For Netbios resolution problems, see:
http://support.microsoft.com/support/kb/articles/Q160/1/77.ASP
I'm thinking you're using a WINS server, that registers your DCs, but is located at the PDC site. The WINS sees the PDC as the nearest controller.
If it works to use B-node, then change it to H-node and go with that, do another test. You can them dessiminate this NodeType using your DHCP server if you have one..
However, if you can change one workstaion to static IP, this would work as well, then the reg entry should work too, as long as you created the NodeType key. This method would obviously be preferred, since you're not affecting other clients.
M-node should work, though you may want to try B-node first to be sure. Then, if all else fails, install a pull WINS server at the remote site.
by ryans5050
by goodfth
by ryans5050
by ryans5050
Clients should find the BDC's regardless of their node type. At best, changing the node type would cure the symptoms but not the real problem, which seems to be related to name resolution.
Using the WINS administrator, check your WINS server for the domain's 1Ch record. It should contain the IP addresses of all domain controllers. If it doesn't have the BDC's address(es), something went wrong during name registration. This could be caused by:
1) the BDC's having a bad or missing WINS server configured in their TCP/IP configuration.
2) a static 1Ch record on the WINS server. Static entries take precedence over dynamic name registrations so any BDC's name registrations are discarded. Solve this either by removing the static entry and rebooting PDC and BDC's, or by editing the static record. In the latter case, you have to manually maintain the record each time BDC addresses are changed or added.
by ryans5050
by jarrettc
With three sites, guessing that they are WAN's I would suggest having seperate WINS (And even DHCP) servers on each BDC. This will free up alot of morning and evening (log on and log off traffic) between the sites freeing up bandwidth, speeding up user response on their local and remote access and allowing the BDC's to be completely independant of the PDC incase of link failure between sites. When setting up the WINS servers just create push/pull partners in any regards that you need.
Currently the site I'm at we have 4 WAN's and each has a WINS server with a push/pull partner to the main WINS server with it pushing/pulling to all of them. This created a central point for all changes to converge and to be distributed.
This also made all the nodes under that WINS/DHCP server dependant on the BDC and therefore they do not look to the PDC during logon.
by jarrettc
by jarrettc
by jarrettc
by ryans5050
by ryans5050
by subbz
by ryans5050
by ryans5050
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending