Everything on my network works fine. Logon scripts run on the new Windows XP Pro machines (we have an NT4 domain). But, one of my administrator guys mapped a network drive on a couple of PCs as his account (he was a local admin on the machines) and now it seems every other normal user who logs on to these two machines doesn't get their login script drives mapped. It seems to be because the %systemroot% variable is not working properly. The PCs are not seeing "net use" as an allowable command. I have to type c:\windows\system32\net use... " to make it work. If I change %systemroot%\system32 to c:\windows\system32 in the environment variables, then it will work without having to go to c:\windows\system32 first. What causes this? It only seems to be after as administrator maps a drive with the "map network drive" tool on the tools menu of explorer.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
%systemroot% problem - logon script fails to map drives
- Thread starter Rearview
- Start date
- Thread starter
- #2
We seem to have fixed our own problem... It seems if we just open the path variable in the little built in editor, change it, and save it.... Then, change it back and save it, (like add a space to the end, save, remove the space, sava again) after restarting the PC it all works as normal. This is the strangest thing...
I am not completely certain, but investigate:
1. Is the MAPROOTOFF variable assigned in the environment?
2. If you Start, Run, CMD and then type SET does it show the path fully expanded? And what does it report for the value of MapRoot? See if the macro expansion fails, or if MapRoot is not pointing at C:\Windows in a CMD session. If the macro explansion is failing, then:
3. You may have run out of environment space. To increase the amount of RAM reserved from the environment go to System Properties, Advanced, Environmental Variables and click on Comspec. Edit the line to add the " /e:2048"
ComSpec = <drive:\windir>\system32\cmd.exe /e:2048
You may need to increase 2048 even higher, the limit is 32768 bytes.
4. Last thought, make certain net.exe is not in the path of the share your friend created on the machines. You may be getting an Access Denied message.
1. Is the MAPROOTOFF variable assigned in the environment?
2. If you Start, Run, CMD and then type SET does it show the path fully expanded? And what does it report for the value of MapRoot? See if the macro expansion fails, or if MapRoot is not pointing at C:\Windows in a CMD session. If the macro explansion is failing, then:
3. You may have run out of environment space. To increase the amount of RAM reserved from the environment go to System Properties, Advanced, Environmental Variables and click on Comspec. Edit the line to add the " /e:2048"
ComSpec = <drive:\windir>\system32\cmd.exe /e:2048
You may need to increase 2048 even higher, the limit is 32768 bytes.
4. Last thought, make certain net.exe is not in the path of the share your friend created on the machines. You may be getting an Access Denied message.
- Status
Similar threads
