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

Unable to map a network drive with a Windows PE boot disk

Created: 26 Oct 2009 • Updated: 26 Oct 2009 • 4 comments
Randall Newnham's picture
+3 3 Votes
Login to vote

This is either due to a lack of network drivers, or due to the drive mapping command, net use, executing too early in the boot sequence.

First, you must verify that you have networking capabilities in the boot environment. To do this, boot with your existing Windows PE boot disk , then choose Quit to exit Ghost. At the command prompt, type the following, then click Enter:


If an IP address is present, and is not, then you have networking capabilities. If this is not the case, you will need to add the appropriate network driver according to these instructions:

How to add drivers to DeployAnywhere or WinPE.

If you have networking capabilities but still cannot map a drive, it is likely that the net use command is executing too quickly. To resolve this, recreate your boot disk as normal, but with the following exception on the page titled "Symantec Ghost Boot Wizard - Review" page in the Ghost Boot Wizard:

1. Click the Start Editing button in the lower right-hand corner of the window.

2. Click on the line just above the line starting with "net use".

3. Type the following:


4. Click Stop Editing.

5. Click Next to complete the wizard and create the boot media.

This should work to resolve it if the issue is with timing.

Comments 4 CommentsJump to latest comment

AnthonyTWC's picture

The ping command worked perfectly for our Dell D630's.

But for some reason, it's back to the same problem with our new E6320's. All drivers and IP address have been verified and the script works when you type it in after the error. So it's back to the script loading too soon.
Any suggestions?

Login to vote
EdT's picture

Delay the script loading, or put some delays into the beginning of the script if the script is loading OK but executing the commands before the machine is ready.

If specified (-w switch), PING will wait for a number of milliseconds between two pings before giving a time-out. For example:

PING -n 1 -w 60000 >NUL

will delay execution of the next command by 60 seconds, provided is not a valid IP address

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

Login to vote
AnthonyTWC's picture

actually, what I have done were 2 tests.

I did a double ping command to give it more time, but that didnt seem to work.

I then used  the pause command and waited like, 5 second or so after the ping was complete. That seemed to work.

However, that is not fully automated to me lol I want ZERO key presses :)

I will give your idea a shot now.

Login to vote
AnthonyTWC's picture

Ok, for some reason your way wasnt working,(dont ask me why, it just seemed like it wasnt even pinging) but I took a variation of it and it seemed to do the trick.

ping -n 20 did the trick. Thanks for pointing me in the right direction!

Login to vote