Discussion Locked

Net Use - Anyone ever seen this vodoo.

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

I have a share that for the life of me will not map to a drive letter. Here is what is being done.

NET USE T: \\ensler_ho3\transfer

All other net use commands in the script work except this one. When the login script runs I get this message.
System error 53: Network path not found
for more information type: net helpmsg 2250 at prompt.

(This share has been moved to 3 different servers. Same error message every time.

After login if I go to a command shell and type NET USE T: \\ensler_ho3\transfer IT WORKS!

Any ideas, tricks, or solutions greatly appreciated.

15 replies

by ravi

Did you try "Net Use t: /Delete" and then map the share with "net use t: \\ensler_ho3\transfer"

by rindi1

during login, a drive gets mapped to the login path of your server, in your case probably drive T:. After login, that drive is released again and therefore available again. This means that if you use login scripts to map drives, drive T: won't be available. If you want to map this drive once windows is up and running, T is available again and therefore you can map that drive by hand. Try mapping to another drive letter or play around with your lastdrive setting in config.sys (set it to highr than T).

by gary sharp

The underscore is not recomended in machine neames, as it will not list in DNS. assuming the other answers are wrong, and you do not have t: mapped already, try using the ip address of the server instead of the name, in case DNS is handling the lookup and failing it. - eg:

net use t: \\172.1.5.67\transfer

cheers

g

by gary sharp

The underscore is not recomended in machine neames, as it will not list in DNS. assuming the other answers are wrong, and you do not have t: mapped already, try using the ip address of the server instead of the name, in case DNS is handling the lookup and failing it. - eg:

net use t: \\172.1.5.67\transfer

cheers

g

by joe hardstaff

A few things to try:
1: Try using a different drive letter during logon (elimate whether the problem is server or workstation based if it maps using a different drive letter the problem is user / workstation)

Check out the following Technet article PSS ID Number: Q137565 This explains the process involved, and also some solutions. This is a known problem that was resolved by NT4 Service Pack4.

Also, take a look at PSS ID Number: Q161431

If your server is using TCP/IP, try replacing the netbios name (ensler_ho3) with the IP address of the server.

Hope this helps.

This discussion is closed to new replies.