Question Locked

Startup Script Fails to Map Drive.... WTF?

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hello all,

I've got a startup script that fails to map a drive. I get system error 53 - network path not found. I added ping tests to that server by host name in the batch file, and pings fine. When I change the host name to IP, it attempts to map, but prompts for authentication.

The path exists as I can execute the batch file manually & it executes perfectly...just not on startup! It's a very basic batch file to map a drive, copy files, and then delete the mapped drive.

NET USE x: \\\

x:\

NET USE x: /DELETE

WTF? Can anyone help? This should work, but it's frickin' not!!!!

We have AD 2003.

Thanks!

3 replies

by jacemg

Whenever you run the batch file manually you're logged in with your saved credentials and passwords. Attempt to run this script manually on under another username on that machine to assess if this is true.

by dumphrey

the script is in the wrong location? So users do not have the correct permissions to access the script?

Any errors of failure notifications?
EDIT: Reread your post, I would have to agree its authentication issues. You may need to add a username and password to the script, or allow the user needing to run the script permissiosn to the share.

This discussion is closed to new replies.