Set up a debug mode on the script, when you are in that mode (say an environment variable is set to something), the logon script will run visible and slowly with a pause between each step and echo everything. Alternatively set up a whole debug script. That way you can see the errors that it is popping if any.
 
Without detailed info this is a difficult one to troubleshoot over the list. The issue could be due to the logic in the script itself if it is choosing what to map or it could be issues with the machine or the machine's ability to connect to other machines.
 
   joe


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Parker
Sent: Friday, May 21, 2004 8:10 AM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] Slow or non existent drive mappings

Greets to all on this beautifully gloomy Friday!
 
We have a small (100 users) Win2K AD. Fully patched, Spacked etc.
 
I have one XP user who's network drive mappings do not show up consistently.  Sometimes partial, other none at all.  if the user logs out and logs back in, (Sometimes more than once) They will map properly.
 
Anyone seen this?
 
The mapping is done via a logon script on the AD server.
 
Thanks in advance.
 
John Parker, MCSE
IS Admin.
Senior Technical Specialist
Alpha Display Systems.
Alpha Video

Reply via email to