Registered member login:
Register Now
Altirigos » Deployment Solution » Network - PXE, DHCP, NICs, Multicasting » PXE Boot / System Error 53 or 1231 upon Map to Express share

» Current Poll
Vista?
Staying on XP until Windows 7 - 71.83%
102 Votes
Already on Vista - 10.56%
15 Votes
Planning an upgrade to Vista soon - 10.56%
15 Votes
Other (please explain) - 7.04%
10 Votes
Total Votes: 142
You may not vote on this poll.
» Stats
Members: 6,845
Threads: 9,784
Posts: 47,849
Top Poster: Nick (4,800)
Welcome our newest member, suresh
» Online Users: 40
5 members and 35 guests
eleets2, ipetit@technip.com, ittcs, klaasdm, suresh
Most users online at once 294, 06-30-2007 at 01:24 PM.
» January 2009
S M T W T F S
28293031 1 2 3
4 5 6 7 8 9 10
11 12 13 14 15 16 17
18 19 20 21 22 23 24
25 26 27 28 29 30 31
Reply
Old 11-11-2008, 11:43 AM   #1 (permalink)
 
Status: Junior Altiris Admin
Join Date: 06-08-2005
Location: NYC
Age: 25
Posts: 18


PXE Boot / System Error 53 or 1231 upon Map to Express share

Hey all,

When performing a PXE boot using a newly-created WinPE 2.1 menu item, I receive "System error 53 The network path was not found" OR ""System error 1231 has occurred. The network location cannot be reached."

However, if I manually type NET USE Y: \\server\share with username/pw credentials, immediately afterwards, it maps fine....

The wpeinit.log says the following (this from a Lenovo T41):

- Installing device pci\ven8086&dev101e\... X:\Windows\INF\oem14.inf succeeded.
- Spent 5138ms installing network drivers
- QueryAdapterStatus: no adapters operational
- Spent 0ms confirming network initialization; status 0x003d0001
- STATUS: SUCCESS (0x003d0001)

It seems as though the NIC doesn't have enough time to initialize (shrug). Has anyone seen this before?

It doesn't seem to be hardware-specific as it's occurred on two different Lenovo model laptops (T41, T400), an HP desktop and a Virtual Machine configured to use an Intel e1000 NIC.

I recently upgraded from DS6.8 to DS 6.9 SP1 (w/ Hotfixes).

I have two PXE boot menu items -- one from Windows PE 1.6 and the other Windows PE 2.1.

The 1.6, which is what we've been using in the past, still works with no problem. I'd like to begin using 2.1 for better compatibility / easy of maintainence.
Kai Mallea is offline   Reply With Quote
Old 11-11-2008, 03:04 PM   #2 (permalink)
 
Status: Junior Altiris Admin
Join Date: 06-08-2005
Location: NYC
Age: 25
Posts: 18


Okay, so I modified the mapdrv.bat in the boot.wim and added a wait command:

await 15 "Waiting for %d seconds..."

Looks like that fixes that:

Mapping network drives...
Waiting for d seconds...
The command completed successfully.

Deployment share mapped to Y:

Starting Agent...
Locating Agent..
Searching Deployment Share for Agent...
> 6.8.378 .. "Y:\Agents\Aclient\altiris-dagent-*.x86.exe"
> 6.9.355 .. "Y:\Agents\Aclient\altiris-dagent-*.x86.exe"
> Highest ver=6.9.355
> Hhighest file=Y:\Agents\AClient\altiris-dagent-6.9.355.x86.exe
Copying agent 6.9.355 from Deployment Share at Y:\agents\aclient...
Starting Remote Agent X:\dagent\dagent.exe...
Launching dagent [d]...

Calling custom actions...

Startup complete.

HOWEVER, now the DAgent just sits there saying "Client Record Updated." Doesn't show up in DS. If I boot up 1.6, it comes up fine. Grrr. If it's not one thing it's another! I have all public hotfixes applied.
Kai Mallea is offline   Reply With Quote
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On

Powered by vBadvanced CMPS v3.0 RC2

All times are GMT -4. The time now is 09:13 AM.


Powered by vBulletin® Version 3.7.4
Copyright ©2000 - 2009, Jelsoft Enterprises Ltd.
SEO by vBSEO 3.2.0
vB.Sponsors
Altirigos