Discussion Locked

Clients not logging on to BDC's

0 helpful
21 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We've got three sites here running NT 4.0 Server. Site A has the PDC and one BDC, B has a BDC and C has a BDC. All of our clients are Windows 9x TCP/IP with DHCP using WINS. Problem is users at all 3 sites log into the PDC (local or over the WAN) instead of logging into the BDC's. We can't run SETPRFDC since these are 9x clients and SETPRFDC on works on NT. We've tried LMHOSTS files, but the #PRE #DOM isn't forcing the 9x clients to logon to the BDC's. I can tell this because we're running ScriptLogic and it shows the users logon server in the log and when they login. In addition, Mark Minasi of NT Magazine has an article where he states "Unfortunately, LMHOSTS can't force Windows 98 or Win95 workstations to log on to a particular domaincontroller" http://www.winntmag.com/Articles/Index.cfm?ArticleID=4802&pg=1. We're running WINS without any problems. We can do name resolution fine, the master browsers at each site is the domain controller, domain master browser is the PDC. Everything else looks good. Any suggestions?

21 replies

by Former member

I have a quick suggestion: Change the 'node type' on one of the remote site's PC to B-node. This will force the PC to look locally for the master browser. Do this as a test and let me know. If this doesn't work, I'll post another comment, but pleasedon't reject until finished. Try hacking the registry to change the node type...thanks...

by Former member

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..

by Former member

Oops! I meant M-node, not H-node...

by Former member

If it's still at Hybrid, Then the reg entry didn't work. Go into your DHCP server, under DHCP options, add a SCOPE option the one labled "046 WINS/NBT Node type" and give it a value of 0x4. Let me know. I will also email this solution..

by Former member

BTW, H-node queries the WINS server firtst, then broadcasts. I want you to broadcast first, then WINS.

by Former member

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 goodfth

I assume your using NT's DHCP server. If that is the case, you can change the node type of all your clients by setting the WINS/NBT DHCP option 046 to 0x8. This will make all DHCP clients H-Type NBT nodes. I would also install a local pull WINS server on the BDC's. This would ensure that the nodes will use the local BDC for authentication since the nearest authenticator will be the BDC. The WINS hex type should be 1ch for the PDC and 1bh for the BDC's.

by ryans5050

Q: We're running WINS and it's currently set via DHCP and sets the clients to H-node. I put one of the remote workstations to B-node via the registry entry and it's still going to the PDC for logon. It seemed weird also, even though I set the reg to force it to B-node, running WINIPCFG still showed it as HYBRID. I'm thinking I might disable DHCP on a remote PC and go static just to test. Any other ideas?

by frank.peeters

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 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

The next thing to do then is to setup DHCP on each site and have it dish out the primary/secondary WINS servers to all clients local to each BDC/PDC.

by jarrettc

If all your nodes, regardless of site are having to go to the PDC for IP distribution it will cache that route and use it for NETLOGON services as well.

by ryans5050

Just an update on this since I've seen alot of suggestions on WINS. We've had WINS installed on each of the BDC's at the remote sites (B and C) and it's installed on the PDC at the primary site (A). WINS is configured so that the Site A WINS has Sites B and C as push/pull partners and the Sites B and C has Site A as a push/pull partner. So we're using WINS already and it's at all three sites.

by subbz

In the properties of network neighbourhood, you have a page for Access Control. In this page make the system have user-level access and specify your BDC's NetBIOS name in the box provided. This should make the client logon to your domain, authenticated by the server specified (BDC) instead of looking for the PDC. This should solve your problem.

This discussion is closed to new replies.