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







HopsnbaerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

TheAmigoCommented:
I think you have to install NetBEUI on the XP box so that your dos boot floppy can see it.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
bkinseyCommented:
Hm, could be name resolution, I guess.  What do you do for resolution in your network?  To test, try net use \\ipaddress\directory instead of \\computername\directory.  If it works, I'd say you've found the problem.
tmwsiyCommented:
you dont have the XP firewall enabled do you?
Get Blueprints for Increased Customer Retention

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

CleanupPingCommented:
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.
juliancrawfordCommented:
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
GreenclockCommented:
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.  

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Networking

From novice to tech pro — start learning today.