5 replies
by blackcurrant
Hi
Sounds like the XP machines are not able to connect to the domain controller at logon. Because each user cannot be verified, they are not being allowed access to the mapped drive.
I would check your DNS settings on the XP machines and make sure that the DNS server address, hostname, gateway and domain name are correct. I would also check your DNS event log on the domain controller, and check it is starting up OK.
Is the domain controller on all the time or are you starting it up at the same time as the XP machines. If the latter, then you should be aware that servers take much longer to start up, hence the percieved delay in logging on.
Good luck
This article might be helpful:
http://support.microsoft.com/default.aspx?scid=kb;en-us;831998
The problem appears to be with the Fast Optimization logon. I hope this helps your situation.
I was having the exact same problem. Running WinXP SP2, and using a logon script from a Windows Server 2003 machine to map 2 network drives. They don't show up in Windows Explorer but I can see them if I do a "net use" in a command prompt. seekingjustice, your solution worked for me.
Just open gpedit.msc, navigate to: "User Configuration\Administrative Templates\System\Scripts\Run logon scripts synchronously" and enable that policy. My client machine acted all crazy after the first reboot (execute disable bit killed Windows Explorer and MS Outlook crashed too, wtf!) but after second reboot all is well and I've got my drives!
This problem has been driving me crazy for months. Thank you thank you thank you!!!
by tdnewk
by ichambas
We had this issue lately and got help with this procedure. Run the following command on each XP machines:
regsvr32 vbscript.dll
It's also recommended you run GPUPDATE or the SECEDIT command for Windows 2000 machines to refresh any GPO's from the domain.
I hope this helps.
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending