There is one machine in our organization that will not map one of my network drives. This script has worked on dozens of other machines, but not this one. I do have local admin rights. Does anyone know why this is happening?
Seriously though, what happens if you try to use the same command that's in the logon script from a command prompt to map the drive? What error do you get?
Post your script so we know how you are trying to do it. Is is a vbscript or a bat file? Are you disconnecting the drive letter first? Are you mapping using the ",True" if this is vbscript?
It sounds as if the XP SP2 machine has the firewall turned on.. what you need to do is open up the Firewall Exceptions list and enable File & Print Sharing in the exceptions.
Unless you do so, this will deny all file and print sharing.
I am about 100% sure that the firewall is off because other logon scripts are running and mapping other drives. Yes, I am sure that there is not a drive letter conflict. The drive is being mapped to B:, our computers do not have floppy drives.
No, you can map to both A and B if the computer does not have a floppy assigned to either letter. I was able to run the script from the command prompt from the offending computer. I logged onto a machine in the next cubical and the script ran sucessfully. Maybe, I should check the BIOS to see if something needs to be changed there.
Yes Lolyd it ran when I opened up the command prompt and typed \\server\xx.bat. The output was the command completed succesfully. I then opened my computer and there was B: maped.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.