Discussion Locked

NETLOGON error

0 helpful
12 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I recently renamed a BDC "LN03" to "LN01" which was the name of the PDC. When renaming the PDC offline to "LNS01" I got a warning about losing logon info. I proceeded as I had already renamed the BDC. After this logon info like Domain and Privilage was not available to the Logon script. However, users appeared to logon properly except for the drive mappings being incorrect. I then restored the WINNT directory and registry to the PDC (now "LNS01"). Everything appears normal except. 1. Users get an Error 2455 at logon but the rest of the logon proceeds fine. 2. The BDC also gets a NETLOGON error with "Access Denied". Again the rest of the logon appears normal. How do I get reed of these error messages?

12 replies

by robshan

It is hard to say exactly what is wrong, however I would suspect a synchronisation problem between the PDC and BDC. Microsoft knowledgebase article Q153719 steps you through the resolution of the problem.

by bkubai

The event viewer reports success,but when users logon through the BDC their info is not found. Privilage dependent drive mappings don't process. All is fine if they use the PDC.

by viperian

Promote the other BDC to PDC, demote the PDC to a BDC. After this, synchronise the entire domain. Wait some time (depends on how large the domain is)to let the sync do its work. Then stop the netlogon service on the demoted PDC. Try logon with a client. If this works. Start the logon service again on the demoted PDC. Promote the BDC (demoted PDC) an demote the new PDC.

Good Luck.

by bkubai

The event viewer reports success after using Rob's suggestion,but when users logon through the BDC their info is not found. Privilage dependent drive mappings don't process. All is fine if they use the PDC.

by viperian

What you also can do is, to get a workstation, make it a BDC of the domain, promote this machine to pdc. Check the eventlogs on all domain controllers wether they accept it. Otherwise you have some machines running in a other domain (because of the SID's) but with the same name. Take the original PDC offline. Remove the computer account from the domain. Sync the domain. Then make a new computeraccount for the former PDC in this domain a put the former PDC back online.

Good luck

by calves

I can't tell you what's wrong, but I can tell you that I learned long ago:
DCs do not like to have name and domain info changed on them. I seen it happen before, but I never seen a fix. Perhaps in the registry...

Good luck!

by mmohammed

Did you change the domain name on all the workstaions to match with the new one? May be this will help...

by guy

I agree with calves. Do not rename Domain controllers.

So, the only way out is to reverse all the renaming. THEN Promote the BDC that you want to be the PDC.

by bkubai

The event viewer reports success after using Robs suggestion,but when users logon through the BDC their info is not found. Privilage dependent drive mappings don't process. All is fine if they use the PDC.

This discussion is closed to new replies.