Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Unable to Map network drive and unable to start network properly

Updated: 22 May 2010 | 4 comments
Suren's picture
0 0 Votes
Login to vote

I'm trying to image a client. I was able to do this until yesterday morning. We were doing this for last 1.5 years.

From yesterday afternoon I'm getting following error

Unable to map network drive
Unable to start network properly.

Here are the steps that come to a failure :

1. start the altiris imaging job
2. machine reboots
3. PXE boots off of the network and starts pulling down the DOS bootdisk
4. Computername changes
5. Initializes TCP/IP via DHCP
6. Establishes network Connection
7. Authenticates Connection
8. The Command completed Successfully
9. Mapping Network Drive
10. The Command completed Successfully
11. Deployment Share mapped to F:
12. Unable to map Network Drive
13. Unable to Start Network Properly
14. Reboots in 5 Seconds

I restarted the server and checked the event viewer and no errors.

If any one have any idea why this is happening.

Thanks

Comments

Palvaran's picture
16
Oct
2009
0 Votes 0
Login to vote

Hey Suren, It sounds like

Hey Suren,

It sounds like permissions.  Did you verify that the eXpress share of the network share  you are trying to use has the user still added in the membership and security settings?

Systems Administrator
Rice University

Remember, "The happiness of your life, depends on the quality of your thoughts."

Suren's picture
16
Oct
2009
0 Votes 0
Login to vote

Thanks Palvaran, I verified

Thanks Palvaran,

I verified the share permissions. Nothing changed.

bhawver's picture
16
Oct
2009
0 Votes 0
Login to vote

Couple of things to check

In my experience with DOS, this happens due to one of the two following reasons.

1.  Password gets changed or is longer than 8 characters.

2.  NIC drivers are not correct.

I would regenerate your PXE boot image and see if that corrects your problem first and foremost, then check the account that PXE is utilizing for the network share.  Lastly, if the network driver isn't correct, recreate your PXE image and make sure that you have the correct NIC drivers selected.

Brian Hawver
Systems Engineer
Yaskawa America, Inc.

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.

Suren's picture
19
Oct
2009
0 Votes 0
Login to vote

I fixed the issue. It was an

I fixed the issue. It was an error on autoexe.bat file. It didn't run the rdeploy.exe file.