Mapped network drives do not appear in WIndows explorer
Hello everybody,
On my PC (Windows XP SP2) I have a number of network drives which are mapped by the logon script.
Although correctly mapped, all these drivers do not appear in Windows explorer. I can access them with the UNC name
On my PC (Windows XP SP2) I have a number of network drives which are mapped by the logon script.
Although correctly mapped, all these drivers do not appear in Windows explorer. I can access them with the UNC name
Do they appear when you open my computer?
ASKER
No they don't
For clarification wouldn't the issue be that you mapped drives aren't showing up period? Have you tried mapping one through Windows?
ASKER
The mapped drive letters (apart from the homedrive P:) don't appear in Windows Explorer.
If I click on 'Tools\Disconnect Network Drive...' all of them appear (because they are all correctly mapped).
If I disconnect one and manually map it, it work and it shows up on the WIndows explorer, but when I logoff and logon back again it does not show.
I'm using a regular account with no privileges. If I give myself administrator rights, then all the drives show up.
If I click on 'Tools\Disconnect Network Drive...' all of them appear (because they are all correctly mapped).
If I disconnect one and manually map it, it work and it shows up on the WIndows explorer, but when I logoff and logon back again it does not show.
I'm using a regular account with no privileges. If I give myself administrator rights, then all the drives show up.
kindly check if you have any policies set on local computer or group policy from the server for the normal users, which is preventing to view this mapped drives and some of the other items from mycomputer.
If you open a command prompt and type Driveletter: and press enter, are you able to change to any of the mapped letters?
If you enter in the command window prompt C:\>PushD "\\ServerName\ShareName" and press enter does the prompt change to a new drive letter? (Should be the first available letter reading from Z to A)
PopD closes the temporary mapping.
If PushD & PopD work then your scripted mappings are not working properly even if the command is correctly written. In which case posting the "mapping" script may help us determine where it is failing. Another check that can be performed is if you can run the script that maps the drives after you login. If your drives appea then it is a timing problem with when your script executes.
Cheers
If you enter in the command window prompt C:\>PushD "\\ServerName\ShareName" and press enter does the prompt change to a new drive letter? (Should be the first available letter reading from Z to A)
PopD closes the temporary mapping.
If PushD & PopD work then your scripted mappings are not working properly even if the command is correctly written. In which case posting the "mapping" script may help us determine where it is failing. Another check that can be performed is if you can run the script that maps the drives after you login. If your drives appea then it is a timing problem with when your script executes.
Cheers
ASKER
Yogalingam:
There is not such a policy
Krompton:
Yes, if I open the command prompt I am able to change to any of the mapped letters.
Yes, the PushD command does change to a new drive letter (Z: which is the first available)
Here is the logon script (by the way it is the same for all the workstations in the domain and on the other machines it works fine).
If Exist Q:\Nul NET USE Q: /DELETE
Net Use Q: \\Quetzal\Q-Drive /Persistent:NO
If Exist S:\Nul NET USE S: /DELETE
Net Use S: \\Shedar\S-Drive /Persistent:NO
If Exist U:\Nul NET USE U: /DELETE
Net Use U: \\Shedar\U-Drive /Persistent:NO
If Exist V:\Nul NET USE V: /DELETE
Net Use V: \\Vesta\V-Drive /Persistent:NO
Running the logon scripts afterwards makes the driver appear
There is not such a policy
Krompton:
Yes, if I open the command prompt I am able to change to any of the mapped letters.
Yes, the PushD command does change to a new drive letter (Z: which is the first available)
Here is the logon script (by the way it is the same for all the workstations in the domain and on the other machines it works fine).
If Exist Q:\Nul NET USE Q: /DELETE
Net Use Q: \\Quetzal\Q-Drive /Persistent:NO
If Exist S:\Nul NET USE S: /DELETE
Net Use S: \\Shedar\S-Drive /Persistent:NO
If Exist U:\Nul NET USE U: /DELETE
Net Use U: \\Shedar\U-Drive /Persistent:NO
If Exist V:\Nul NET USE V: /DELETE
Net Use V: \\Vesta\V-Drive /Persistent:NO
Running the logon scripts afterwards makes the driver appear
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hey Hey msartoris,
Which part fixed this problem...the registry entry or switching to a VB script?
We use a VBS script already...but on random TS servers the drives fail to map.
Thanks,
Which part fixed this problem...the registry entry or switching to a VB script?
We use a VBS script already...but on random TS servers the drives fail to map.
Thanks,
ASKER
If I remember properly, it was the VB script. I must admit, that it still happens, from time to time; we just tell our users to logoff and the log on , the mapped drives noermally reappear.
Shizzle...thanks a lot for posting back...I really appreciate it.
Have a good one!!!
Have a good one!!!