We have a two site domain (same domain – just two sites – two subnets).
Site one contained two domain controllers Sever1 (FSMO) and Server2.
Server2 was also an Exchange server (before my time), and File server.
Site two has one domain controller, PLT2SRV1.
All have Windows Server 2003 SP2 installed.
We had a Domain controller on site one die (Server2)
The server has been rebuilt and renamed as Exchange1. Exchange1 is now a member server, with Exchange 2003 installed, and still functioning as a File server.
I have logon batch files set up on domain controllers (sysvol). They are basic mapping of drives to groups of users, and clock syncing with FSMO domain controller.
Here is an example of batch files:
NET USE * /DELETE /Y
net use K: \\SERVER1\Database$ /y
net use G: \\exchange1\Finance$ /y
net use Q: \\exchange1\Quality$ /y
net time /setsntp: Server1
net time \\Server1 /set /yes
These have work fine for years. When you log on, you might see a quick flash of the DOS window and your drives were mapped and good to go. Now after the server melt down and rebuild. They work fine for two weeks and now when you logon, the DOS window stays up, and it tries to map drives but gives a few lines of “Continuing will cancel the connections.”, and "The command completed successfully” (one for each drive mapping).
Then ends with an “Enter the user name for ‘Server2’: (see enclosed).
Most users get there drives mapped, but a few don’t and all the users have to close out the DOS window
Sounds kind of like a permissions thing, but why after all these years and still yet two weeks after rebuild, before it started doing this?
I don’t want no user name or passwords for the users from logon scripts (just logon with the username and passwords). No user actions.
Experts have any ideas?
I am beside myself on what to do next.
Thanks in Advance!