A
Andy Siegel
I have a user that this just started happening on her Windows XP Pro (SP3)
machine. She has administrative rights on the computer. When she goes to
Start | Run and types in CMD (or command), a DOS window opens up pointing to
her Active Directory assigned drive letter U:\. If she tries a ping, telnet,
ipconfig, or just about any other command other than "dir", the command fails
saying that it's not a recognized command. Even if she changes to c:\, she
gets the same thing. In the title bar of the window, it shows
C:\Windows\System32\CMD.exe. However, if she just browses to
C:\Windows\System32\command.com or cmd.exe, the commands work fine. The
title in the window show the same path, but the only way to make it work is
to drill all the way down to the system32 folder to launch the command window.
Has anyone seen this? How can I restore this functionality?
Andy Siegel
Dover, DE
machine. She has administrative rights on the computer. When she goes to
Start | Run and types in CMD (or command), a DOS window opens up pointing to
her Active Directory assigned drive letter U:\. If she tries a ping, telnet,
ipconfig, or just about any other command other than "dir", the command fails
saying that it's not a recognized command. Even if she changes to c:\, she
gets the same thing. In the title bar of the window, it shows
C:\Windows\System32\CMD.exe. However, if she just browses to
C:\Windows\System32\command.com or cmd.exe, the commands work fine. The
title in the window show the same path, but the only way to make it work is
to drill all the way down to the system32 folder to launch the command window.
Has anyone seen this? How can I restore this functionality?
Andy Siegel
Dover, DE