Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

DS 6.9 SP6 - DOS PXE cannot map F:

Created: 07 May 2014 | 4 comments

I have a new installation of Altiris DS 6.9 SP6 running on Windows Server 2008 R2.  Linux and WinPE PXE works fine.  However DOS fails to map the F: drive giving a net use Error 53: The computer name specified in the network path cannot be located.

I know the DOS image is getting an IP address as I can manually map our old eXpress share on a 2003 server.  I'm thinking there is a difference between 2003 R2 and 2008 R2 that's stopping this connection.

Thank you for any help.

Operating Systems:

Comments 4 CommentsJump to latest comment

andykn101's picture

My old notes say that an error 53 when mapping can be caused by name resolution problems, try using an LMHosts file in your DOS image, or that Ports 137 (UDP), 138 (UPD) and 139 (TCP) need opening, maybe on the 2008 R2 server.
 

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

Thomas Baird's picture

Another option is to check DNS for short and long name resolution.  From another system, try pinging based on short name, and based on long / FQDN and see if it works.  If not, then you've some holes in your DNS configuration.  Granted, the LMHosts can make up for it, but then again...

You CAN change the F drive mapping to use IP or ... whatever.  Just go into BootWiz and modify it to work.

MOST of the time, this is a DNS issue as Andy said.

Thomas Baird
Enthusiast for making things better!

 

andykn101's picture

I don't think you can map a drive by IP address in DOS.
 

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

Thomas Baird's picture

Uh - are you sure you can't?  Test it.  I do it all the time, but granted it has been ages since I've even attempted to actually use true MSDos.  The  net use statement though should easily support direct IP drive mapping.  All you do is:

net use * \\192.168.0.15\share

And it shouldl prompt for user name and whatever.  That said, they'll still need to figure out DNS to ensure OTHER things in the environment don't fail.  It just starts here, but there are other places it ends up affecting later.

Thomas Baird
Enthusiast for making things better!