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

Timeouts, error 10054's, can't connect to Console nor GhostCast Server!

Created: 15 Apr 2009 • Updated: 21 May 2010 | 8 comments
This issue has been solved. See solution.

Howdy,

recently got the GSS 2.5 suite, and now in progress of learning to use it. I'm familiar with ghostcasting using the server on one server, and then casting the images down to the destination laptops, running the client.
What I'm now trying to learn, is using console to do this through PXE. So far I've installed the suite and the 3com boot services. After this I created the image package using a guide on these forums.
The client pc I'm using to test this is a Lenovo T400. I can get it to boot WinPE just fine, but then it hangs in polling the ghost server. 3Com PXE server log is filling with error 10054's, and the TFTP log is having quite a few timeouts.

Here's a piece of the PXE log:

15.4.2009 13:14 - Program started
15.4.2009 13:14 - Data file: C:\TFTPBOOT\BOOTPTAB (15.4.2009 12:21)
15.4.2009 13:14 - Data read: 1 hosts, 1 templates
15.4.2009 13:14 - Server started
15.4.2009 13:14 - Proxy: [001C259EA61B] (TESTI)
15.4.2009 13:14 - Proxy: [001C259EA61B] (TESTI)
15.4.2009 13:14 - PXE: [001C259EA61B] (TESTI)
** Receive error 10054 **
15.4.2009 13:14 - PXE: [001C259EA61B] (TESTI)
15.4.2009 13:14 - PXE: [001C259EA61B] (TESTI)
** Receive error 10054 **
15.4.2009 13:14 - PXE: [001C259EA61B] (TESTI)
** Receive error 10054 **
15.4.2009 13:14 - PXE: [001C259EA61B] (TESTI)
** Receive error 10054 **
15.4.2009 13:14 - PXE: [001C259EA61B] (TESTI)
** Receive error 10054 **
15.4.2009 13:14 - PXE: [001C259EA61B] (TESTI)
** Receive error 10054 **
15.4.2009 13:14 - PXE: [001C259EA61B] (TESTI)
** Receive error 10054 **
15.4.2009 13:14 - PXE: [001C259EA61B] (TESTI)
** Receive error 10054 **
** Receive error 10054 **
15.4.2009 13:20 - Proxy: [001C259EA61B] (TESTI)
15.4.2009 13:20 - Proxy: [001C259EA61B] (TESTI)
15.4.2009 13:20 - PXE: [001C259EA61B] (TESTI)
** Receive error 10054 **
15.4.2009 13:20 - PXE: [001C259EA61B] (TESTI)
15.4.2009 13:20 - PXE: [001C259EA61B] (TESTI)
** Receive error 10054 **
15.4.2009 13:20 - PXE: [001C259EA61B] (TESTI)
** Receive error 10054 **
15.4.2009 13:20 - PXE: [001C259EA61B] (TESTI)
** Receive error 10054 **
15.4.2009 13:20 - PXE: [001C259EA61B] (TESTI)
** Receive error 10054 **
15.4.2009 13:20 - PXE: [001C259EA61B] (TESTI)
** Receive error 10054 **
15.4.2009 13:20 - PXE: [001C259EA61B] (TESTI)
** Receive error 10054 **
15.4.2009 13:20 - PXE: [001C259EA61B] (TESTI)
** Receive error 10054 **
** Receive error 10054 **
15.4.2009 13:32 - Proxy: [001C259EA61B] (TESTI)
15.4.2009 13:32 - Proxy: [001C259EA61B] (TESTI)
15.4.2009 13:32 - PXE: [001C259EA61B] (TESTI)
** Receive error 10054 **
15.4.2009 13:32 - PXE: [001C259EA61B] (TESTI)
15.4.2009 13:32 - PXE: [001C259EA61B] (TESTI)
** Receive error 10054 **
15.4.2009 13:32 - PXE: [001C259EA61B] (TESTI)
** Receive error 10054 **
15.4.2009 13:32 - PXE: [001C259EA61B] (TESTI)
** Receive error 10054 **
15.4.2009 13:32 - PXE: [001C259EA61B] (TESTI)
** Receive error 10054 **
15.4.2009 13:32 - PXE: [001C259EA61B] (TESTI)
** Receive error 10054 **
15.4.2009 13:32 - PXE: [001C259EA61B] (TESTI)
** Receive error 10054 **
15.4.2009 13:32 - PXE: [001C259EA61B] (TESTI)
** Receive error 10054 **
** Receive error 10054 **

And here some of the TFTP's log file:

4/15/09 13:20 - TFTP Read C:\TFTPBOOT\\Boot\BCD from 10.51.3.138
4/15/09 13:20 - TFTP Read C:\TFTPBOOT\\Boot\Fonts\wgl4_boot.ttf from 10.51.3.138
4/15/09 13:20 - TFTP Read C:\TFTPBOOT\\hiberfil.sys from 10.51.3.138
4/15/09 13:20 - TFTP Read C:\TFTPBOOT\\Boot\BCD from 10.51.3.138 Done
4/15/09 13:20 - TFTP Read C:\TFTPBOOT\\Boot\Fonts\wgl4_boot.ttf from 10.51.3.138 Abort
4/15/09 13:20 - TFTP Read C:\TFTPBOOT\\hiberfil.sys from 10.51.3.138 Abort
4/15/09 13:20 - TFTP Read C:\TFTPBOOT\\boot\testi.wim from 10.51.3.138
4/15/09 13:20 - TFTP Read C:\TFTPBOOT\\boot\boot.sdi from 10.51.3.138
4/15/09 13:20 - TFTP Read C:\TFTPBOOT\\boot\boot.sdi from 10.51.3.138
4/15/09 13:20 - TFTP Read C:\TFTPBOOT\\boot\testi.wim from 10.51.3.138
4/15/09 13:20 - TFTP Read C:\TFTPBOOT\\boot\boot.sdi from 10.51.3.138 Done
4/15/09 13:21 - TFTP Read C:\TFTPBOOT\\boot\testi.wim from 10.51.3.138 Done
4/15/09 13:21 - TFTP Read C:\TFTPBOOT\\Boot\Fonts\wgl4_boot.ttf from 10.51.3.138
4/15/09 13:21 - TFTP Read C:\TFTPBOOT\\Boot\Fonts\wgl4_boot.ttf from 10.51.3.138 Abort
4/15/09 13:25 - TFTP Read C:\TFTPBOOT\\boot\pxeboot.n12 from 10.51.3.138 TimeOut
4/15/09 13:25 - TFTP Read C:\TFTPBOOT\\Boot\BCD from 10.51.3.138 TimeOut
4/15/09 13:25 - TFTP Read C:\TFTPBOOT\\boot\testi.wim from 10.51.3.138 TimeOut
4/15/09 13:25 - TFTP Read C:\TFTPBOOT\\boot\boot.sdi from 10.51.3.138 TimeOut
4/15/09 13:32 - TFTP Read C:\TFTPBOOT\\boot\pxeboot.n12 from 10.51.1.141
4/15/09 13:32 - TFTP Read C:\TFTPBOOT\\boot\pxeboot.n12 from 10.51.1.141
4/15/09 13:32 - TFTP Read C:\TFTPBOOT\\boot\bootmgr.exe from 10.51.1.141
4/15/09 13:32 - TFTP Read C:\TFTPBOOT\\boot\pxeboot.n12 from 10.51.1.141 Done
4/15/09 13:32 - TFTP Read C:\TFTPBOOT\\boot\bootmgr.exe from 10.51.1.141 Done
4/15/09 13:32 - TFTP Read C:\TFTPBOOT\\Boot\Fonts\wgl4_boot.ttf from 10.51.1.141
4/15/09 13:32 - TFTP Read C:\TFTPBOOT\\Boot\Fonts\wgl4_boot.ttf from 10.51.1.141 Abort
4/15/09 13:32 - TFTP Read C:\TFTPBOOT\\boot\boot.ini from 10.51.1.141
4/15/09 13:32 - TFTP Read C:\TFTPBOOT\\boot\boot.ini from 10.51.1.141 Abort
4/15/09 13:32 - TFTP Read C:\TFTPBOOT\\Boot\BCD from 10.51.1.141
4/15/09 13:32 - TFTP Read C:\TFTPBOOT\\Boot\BCD from 10.51.1.141
4/15/09 13:32 - TFTP Read C:\TFTPBOOT\\Boot\Fonts\wgl4_boot.ttf from 10.51.1.141
4/15/09 13:32 - TFTP Read C:\TFTPBOOT\\hiberfil.sys from 10.51.1.141
4/15/09 13:32 - TFTP Read C:\TFTPBOOT\\boot\testi.wim from 10.51.1.141
4/15/09 13:32 - TFTP Read C:\TFTPBOOT\\boot\boot.sdi from 10.51.1.141
4/15/09 13:32 - TFTP Read C:\TFTPBOOT\\boot\boot.sdi from 10.51.1.141
4/15/09 13:32 - TFTP Read C:\TFTPBOOT\\Boot\BCD from 10.51.1.141 Done
4/15/09 13:32 - TFTP Read C:\TFTPBOOT\\Boot\Fonts\wgl4_boot.ttf from 10.51.1.141 Abort
4/15/09 13:32 - TFTP Read C:\TFTPBOOT\\hiberfil.sys from 10.51.1.141 Abort
4/15/09 13:32 - TFTP Read C:\TFTPBOOT\\boot\testi.wim from 10.51.1.141
4/15/09 13:32 - TFTP Read C:\TFTPBOOT\\boot\boot.sdi from 10.51.1.141 Done
4/15/09 13:32 - TFTP Read C:\TFTPBOOT\\boot\testi.wim from 10.51.1.141 Done
4/15/09 13:32 - TFTP Read C:\TFTPBOOT\\Boot\Fonts\wgl4_boot.ttf from 10.51.1.141
4/15/09 13:32 - TFTP Read C:\TFTPBOOT\\Boot\Fonts\wgl4_boot.ttf from 10.51.1.141 Abort
4/15/09 13:37 - TFTP Read C:\TFTPBOOT\\boot\pxeboot.n12 from 10.51.1.141 TimeOut
4/15/09 13:37 - TFTP Read C:\TFTPBOOT\\Boot\BCD from 10.51.1.141 TimeOut
4/15/09 13:37 - TFTP Read C:\TFTPBOOT\\boot\testi.wim from 10.51.1.141 TimeOut
4/15/09 13:37 - TFTP Read C:\TFTPBOOT\\boot\boot.sdi from 10.51.1.141 TimeOut

I tried disabling the timeout, but for some reason it still occurs.

Eagerly waiting for a solution ;)

Comments 8 CommentsJump to latest comment

Krish Jayaratne's picture

Hi,

Did the client boot to WinPE? Once it is boot to WinPE, the PXE operation is completed. There should not be such logs in the PXE log, but if it is booting to WinPE and start 'polling for <server name>" it is a different issue.
If you get that message, by any chance does it use the local host IP (127.0.0.1)?

Krish 

jraines-123's picture

I am having the same problem with my installation of 3COM Boot Services.  The laptop I am trying to image (HP 2730p tablet) boots the PXE image just fine and gets me to the main Ghost screen.  However, when I attempt to connect to a GhostCast session, the local IP address of the tablet is 127.0.0.1 (even though the DHCP server states that it received a valid IP address).  Naturally, every attempt to connect to the session fails.

Any ideas?

J.L.'s picture

Hello,

like I said, the client booted to WinPE, and the log file was from the PXE software running on the server, not from the client itself. Running IPCONFIG  on the client shows nothing either.
Read a few posts about this thing, and thought it'd be the NIC drivers, but one of your employees wrote that the drivers for the T400 are built in already in WinPE. And trying to add them manually from the "Edit" menu in Ghost Boot Wizard tell me that it can't find the drivers in the location I specified. Made even sure the drivers were for vista.

The weird thing is, I took another laptop, Fujitsu S2110, and loaded up a WinPE-512 with all possible drivers in it. And what do you know, no errors, no timeouts, works like a charm. Pulling images from it atm. Thought the T400 might have a faulty NIC, but it's ok when connecting to web or ghosting using the a dvd with the boot package in it.

Atleast I know that I didn't completely screw this up, but would like to get the Lenovo's working too, as there's many in our company.

Joona

EDIT: The Lenovo T400 has a Intel 82567 Gigabit Ethernet Controller in it ;)

J.L.'s picture

Also noticed, that the T400 is warning that MBR.BIN could not be created. Running the server on a VM, which I'm controlling from another Fujisu laptop using Remote Desktop Connection.

Thanks,

Joona

Krish Jayaratne's picture

Hi Joona,

Cannot create mbr.bin is not an error when boot from PXE.

If you get nothing when run ipconfig, it is a sure sign of not having the NIC driver loaded (Could be a faulty NIC but more likely a wrong driver). For Intel chips, there is lot of updates so the default drivers we have may not be compatible with this model. GBW requires the unpacked drivers to add to WinPE. If it cannot find any drivers, most likely  it is an exe file rather than  an unpacked driver. I think you can extract drivers from EXE  if you run with the switch -X (i'm not sure about  this though). Could you try extracting them to a folder and then adding?

If you still have problems, could you please post the link to the driver for me to give a try?

Krish

J.L.'s picture

Hello again,

Think this is the correct driver. Indeed an .exe, and I running it extracts the contents to a folder (C:\DRIVERS\Vista\ETHERNET\PRO1000\Win32), which is what I selected @ the boot wizard, but it told me it can't find any drivers. Tried downloading them from Intel's site too, but same results.

Thank ye,

Joona
 

Krish Jayaratne's picture

Hi Joona,

I just downloaded that driver and it worked without an issue. Could you please check the folder and see if you get .inf and .sys files there? At what point did GBW complained that it could not find the driver?

Krish

SOLUTION
J.L.'s picture

Aww, I feel like an idiot...
Just tried it myself with the driver I linked, seems like I only tried the driver @Intel's site the first time, and not the one I just linked. The log still get's few 10054's when using the T400 as a client, but I can control it with Ghost Console just fine.
Thanks for trying to help anyway, probably wouldn't downloaded these drivers if you hadn't asked :)

Joona