Discussion Locked

BDC Rebuild problems

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

I had a BDC called Company_BDC that went belly and had to be rebuilt from scratch. I removed Company_BDC from the domain on the PDC and then proceeded to rebuild the machine. It rebuilt fine I called it Company_BDC again added it during the install,the SAM's synced no problem and I thought all was well. I could logon and all looked fine. My network users when logging in were hitting the Company_BDC now but not able to athenticate to the domain ? I am able to sync the domain but anyone who is served the logon from Company_BDC cannot authenticate. I need some help in understanding why and being able to correct this. I have for now disabled the Net Logon service and temporarily restored some sanity to my network.

Thanks,
Jamie

3 replies

by mphoffar

If I'm remembering correctly, the sams will not exist on the that machine until you promote Company_BDC to the primary and then demote it back to a backup and until that exists on that machine, it'll give you headaches trying to authenticate people.

Mark

by jpotter

The answer is wrong and inaccurate.

Backup Domain controllers get a read only copy of the SAM when the machine is first configured. This is why a BDC must be on the network to be initially configured, it then gets the RO copy from the PDC.

Thanks Anyway,

by rcc

The previous answer si not correct, as you may already kno, you do not need to rotate the DC's in order to get a copy of the SAM...On the other hand, as an exercise, it may pay to try that to see if any inconsistencies get cleared out.
If you useWINS, look in there for any type of records that may cauze problems to your BDC (i.e.: static, old BDC name not released...)
Verify user permissions (log on from the network rights in the user manager for domains (advanced)). Verify that the logonservice is working properly. Enable login auditing and look in the Security log to see what is the error when you clients attempt to login. Try loging in localy as a domain user on the BDC.
One think I found on one of my domains at one stage was that I had to ask the BDC to sync because it was jsut not doing it if I'd asked the PDC to sync the whole domain. I found out later that some WINS records caused problems...Have a look at the NETWORK BROWSING services and status as well (there are some tools in the reskit you can use this for).
Does the machine has the same name as the old one? What type of name resolution are you using (DNS, WINS, NetBIOS broadcast)? Are you using DHCP at all?
I hope some of this questions will broaden the chances to get your net back together...
Regards,
Radu

This discussion is closed to new replies.