Logon script works, kinda....

Skilldibop · 29 Mar 2006 at 12:04

We run a server 2003 Active directory domain. The logon script maps drives in the normal way. There are 2 drives that map using a specific, generic username and password. for some reason one terminal (XP SP2) doesn't like it. The drive re-maps but remains in the state: Disconnected network drive. Opening the drive reconnects it but it prompts for password, which means unless they enter that password they can't get mail.
Also the PC doesn't adopt the domain's group policy for the desktop and theme.

We had a few glitches with logon scripts mapping this mail drive in 2000Pro but not on any XP workstations. What the hell is going on on this one bad apple??

Sp00n · 29 Mar 2006 at 13:09

Where is the policy applied? Domain level? OU level?

Richard Slater · 29 Mar 2006 at 13:58

Have a check of the event log, see if there are any messages about Group Policy processing being aborted because the computer could not identify the name of the domain controller.

This is usualy caused by the network driver taking too long to start up, and Group Policy throwing in the towel after a couple of seconds, there is a reg hack to fix that if it is that problem.

Skilldibop · 30 Mar 2006 at 09:42

The group policy is at domain level and the fact it doesn't apply is a minor issue i just thought the two might be related. The real issue is the network drive that restores but doesn't reconnect when the others do. I know there were credentials issues in NT4 (this was what we upgraded from) to do with caching the initial credentials and not updating the cached files. But the W: drive for the blood results lookup program works fine.
Thought that's mapping to a 2003 box, the mail is on an NT server because 2003's crap and won't do Novell gateway services.
You reckon that could be it??
If so deleting the drive and re mapping it with the same credentials supplied in the logon script should solve it.
Still open to other suggestions though.