logon batch does not execute after adding a second Domain Contlr.

[roloexe]

I am having quite an issue right now since I just implemented a second domain controller on my domain. The 2nd AD setup went off like a charm. I used the wizard to do it and had no problems. I saw both controllers on the network and both databases look identical. No issues came up yesterday with any of my users. But when I came in this morning only half of my users were able to login properly using my logon batch and the other half were not mapped to any network drives. So what I did to temporarily resolve the issue was to shut down the new controller and everyone was able to logon with no problem. Does anyone have any ideas why that would happen? Thanks for any help.

 

[GlenJohnson]

Did you check the event logs for errors? Glen A. Johnson
Johnson Computer Consulting
MCP W2K
glen@johnsoncomputers.us

Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884
"Doubt is not a pleasant condition, but certainty is an absurd one."
Voltaire -born Francois-Marie Arouet- (1694-1778); French writer.

 

[tahoe2]

When you add a DC to your domain, it uses default user info until it gets a chance to replicate. Like if you tried to log on as Administrator, your password wouldn't work until the DC's are synchronized, you would have to leave the password blank. Could be caused by a faulty network connection or other network problems.

To synchronize a specific backup domain controller with the primary domain controller, follow these steps:

Select the backup domain controller in the Server Manager main window.
Choose Synchronize with Primary Domain Controller from the Computer menu. You will see a message that the process may take several minutes to complete. Click the OK button to proceed.


You should check the event log of the primary and backup domain controller to make sure that the replication process succeeded.

Hope this helps.

Corie

 

[jacare]

check the NETLOGON share of each server. if they differ, you have replication issues.

 

[whateva]

I have identical problems running on our NT 4.0 domain. Our network connections seem to foil many replication attempts between our domain controllers. Whenever I make changes to our logon scripts, I manually copy the scripts to the same location on our BDCs. For example, on NT, the logon scripts are stored in C:/winnt/system32/repl/import. There is also an export folder listed in the REPL folder. domain replication is supposed to copy the contents of the repl/export folder to the repl/import folders on each of the DCs. So, save the scripts in c:/winnt/system32/repl/export, and then copy and paste a copy of the script to c:/winnt/system32/repl/export on the same DC. Then, to push the script to the other DC, click START--RUN. Then, as long as you have admin rights on the remote DC, type in \\REMOTESERVERNAMEHERE\C$\WINNT\SYSTEM32\REPL\IMPORT That should open the import folder on the remote DC, paste the same script in there. Taa Daa!!! Now people should get the script when they login. Make certain your users aren't closing the scripts before they have a chance to execute either. Hope this helps.