Deployment Solution

 View Only
  • 1.  PXE failing to map network drives

    Posted Jun 03, 2009 10:42 AM
    We have just upgraded to DS 6.9 sp2 and we are having issues with getting PXE to work. I have a Dell Latitude D620 set to image. I connects to the Deployment server and authenticates correctly. Just after authenticating it fails to map network drives. The error message I am getting is

    'Computer name specifies in the path could not be found'   'Mapping networl drives failed.'

    We have the PXE server and DS installed on the same server. I checked the lmhosts file in the bootdisk creator and our server and it's ip address are entered correctly.

    Does anyone have any ideas?


  • 2.  RE: PXE failing to map network drives

    Posted Jun 03, 2009 10:50 AM
    What preboot, MS-DOS, FreeDOS, Linux or WinPE?  If it is DOS, you may find some useful information on this forum:

    https://www-secure.symantec.com/connect/forums/error-53-computer-name-specified-network-path-cannot-be-located


  • 3.  RE: PXE failing to map network drives

    Posted Jun 03, 2009 10:51 AM
    Sorry I forgot to mention. Preboot is DOS.


  • 4.  RE: PXE failing to map network drives

    Posted Jun 03, 2009 10:08 PM
    Are you sure the appropriate network driver is being loaded?  I've noticed that it may appear to be fine, other than the mapping errors, however, it never really checks in to the DS server.

    Also, if your password has more than 8 characters that could also cause a problem.  I would also try to map via the IP address instead of the name to ensure it's not a name resolution problem (i.e. \\192.168.1.1\express).

    Hope that helps at least a little bit.


  • 5.  RE: PXE failing to map network drives

    Posted Jun 04, 2009 07:31 PM
    Did you change the Network adapter type:

    did you make sure that you selected "Use Intel UNDI driver for PXE" step 3 of 12 when configuring your DOS PXE configuration?


  • 6.  RE: PXE failing to map network drives

    Posted Jun 05, 2009 12:24 AM
    I would try reducing the amount of characters you had in the password this has resolved that particular issue for us. 8 characters or less as bhawver mentioned.