Hopsnbaer
asked on
Map network drive from dos, error 53: the computer name specified in network path cannot be located
OK, I am trying to use a dos boot disk to map to a shared directory on an xp box
auto exec.bat
path=a:\net
a:\net\net start
net use z: \\computer\directory
It logs on to domain fine, when net use runs I get "error 53: The computer name specified in the network path cannot be located."
when I map to the drive from gui in 98 or command promopt from GUI it works fine.
net bios to tcp/ip is enabled on XP machine
The problem is intermitant we have got it to work before
auto exec.bat
path=a:\net
a:\net\net start
net use z: \\computer\directory
It logs on to domain fine, when net use runs I get "error 53: The computer name specified in the network path cannot be located."
when I map to the drive from gui in 98 or command promopt from GUI it works fine.
net bios to tcp/ip is enabled on XP machine
The problem is intermitant we have got it to work before
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
tmwsiy
you dont have the XP firewall enabled do you?
Hopsnbaer:
This old question needs to be finalized -- accept an answer, split points, or get a refund. For information on your options, please click here-> http:/help/closing.jsp#1
EXPERTS:
Post your closing recommendations! No comment means you don't care.
This old question needs to be finalized -- accept an answer, split points, or get a refund. For information on your options, please click here-> http:/help/closing.jsp#1
EXPERTS:
Post your closing recommendations! No comment means you don't care.
No comment has been added lately, so it's time to clean up this TA.
I will leave the following recommendation for this question in the Cleanup topic area:
Split: TheAmigo {http:#8351957} & bkinsey {http:#8352256}
Please leave any comments here within the next seven days.
PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!
Julian Crawford
EE Cleanup Volunteer
I will leave the following recommendation for this question in the Cleanup topic area:
Split: TheAmigo {http:#8351957} & bkinsey {http:#8352256}
Please leave any comments here within the next seven days.
PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!
Julian Crawford
EE Cleanup Volunteer
Sounds like a name resolution issue.
IP addresses are not valid when used with the dos client. Quick work around is to create a "lmhosts" on the boot disk. Same location on the disk as the network files, etc
lmhosts:
======
aaa.bbb.ccc.ddd servername
aaa.bbb.ccc.ddd dc_name #PRE #DOM:domain
======
Last line is optional. Dos Client seems to know where Wins and DNS is if the domain is validating username and passsword.
IP addresses are not valid when used with the dos client. Quick work around is to create a "lmhosts" on the boot disk. Same location on the disk as the network files, etc
lmhosts:
======
aaa.bbb.ccc.ddd servername
aaa.bbb.ccc.ddd dc_name #PRE #DOM:domain
======
Last line is optional. Dos Client seems to know where Wins and DNS is if the domain is validating username and passsword.