I am trying to restore a Toshiba Portege M200 lap top with no dvd by booting via PXE/Tftps.
I get a connection to the Tftp server, but it falls over when it tries to send the pxelinux.0 file, with an error of
PXE-T04 Illegal FTP on the client
then
PXE-E036 Error recieved from ftp server
It then quits.
TFTPD reports
Rcvd DHCP Discover Msg for IP 0.0.0.0, Mac 00:16:17:60:D5:C9 [19/01 17:13:26.143]
DHCP: proposed address 192.168.1.10 [19/01 17:13:27.655]
4332 Request 2 not processed [19/01 17:13:27.756]
Rcvd DHCP Rqst Msg for IP 0.0.0.0, Mac 00:16:17:60:D5:C9 [19/01 17:13:27.996]
Previously allocated address 192.168.1.10 acked [19/01 17:13:29.498]
Connection received from 192.168.1.10 on port 2070 [19/01 17:13:29.558]
Read request for file <pxelinux.0>. Mode octet [19/01 17:13:29.558]
OACK: <blksize=1456,> [19/01 17:13:29.558]
Using local port 4302 [19/01 17:13:29.568]
4332 Request 2 not processed [19/01 17:13:29.608]
Connection received from 192.168.1.10 on port 2071 [19/01 17:13:31.611]
Unexpected request 4 from peer [19/01 17:13:31.611]
Returning EBADOP to Peer [19/01 17:13:31.611]
I have tried this with tftpd version 2.5 and 2.7, two pxelinux.0 files (from syslinux 2.2 and 3.0) and also an HP dx2200 desk top. All have the same problem.
The failure starts as it loads the pxelinux.0 file. If I rename the pxelinux.0 it tftpd reports a file not found error, so it is finding the file.
Any suggetsions?
PXE booting error from server
Started by
MartinHow
, Jan 20 2009 10:42 AM
4 replies to this topic
#1
Posted 20 January 2009 - 10:42 AM
#2
Posted 16 February 2009 - 06:34 AM
Did you make a pxelinux.cfg directory with a default file with the loading options in it?
And what settings are you using within tftpd32? I have this working with tftpd32 v3.25 and pxelinux (syslinux) v3.73.
here is my pxelinux.cfg\default file:
I am using the PLoP Boot Loader to boot a bootable USB key with no BIOS emulation to load other OS's/tools on my USB key.
And what settings are you using within tftpd32? I have this working with tftpd32 v3.25 and pxelinux (syslinux) v3.73.
here is my pxelinux.cfg\default file:
label plp menu label PLoP Boot Loader kernel plpbt label pqmagic menu label Partition Magic 8 kernel memdisk initrd=images\pm8.imz label m86 menu label MemTest86+ kernel memtest\memtest.x86 label DOS menu label MS-DOS kernel memdisk initrd=images\msdosboot.imz
I am using the PLoP Boot Loader to boot a bootable USB key with no BIOS emulation to load other OS's/tools on my USB key.
#3
Posted 07 April 2009 - 01:49 PM
The IP range you use is the same that most ADSL routers normally use. If there's another DHCP server on your network (ie PC with internet sharing or ADSL router with DHCP enabled) it maybe interferring with your TFTPD32.
If this is not the case make sure to use pxelinux.0 from a latest or known working syslinux package (v3.72 works for me perfectly) and also latest or known working TFTPD32 (v3.26 works ok, found quite a few problems with v3.32).
If you never succeded pxe-booting your laptop before it may have a broken PXE stack (network adapter firmware) which is very unlikely but possible. So you might want to give another PC a go and see if that one can PXE boot ok.
If this is not the case make sure to use pxelinux.0 from a latest or known working syslinux package (v3.72 works for me perfectly) and also latest or known working TFTPD32 (v3.26 works ok, found quite a few problems with v3.32).
If you never succeded pxe-booting your laptop before it may have a broken PXE stack (network adapter firmware) which is very unlikely but possible. So you might want to give another PC a go and see if that one can PXE boot ok.
#4
Posted 06 September 2011 - 08:59 AM
Hey,
Late on this but we've got this issue at our local school.
Advisory: HP Compaq dx2200 May Hang During Remote Image Deployment, HP support document ID: c00746649
So that takes the DX2200 out of the "can do" basket. I think the Lithuanian guy is right about the broken NIC firmware, just coincidence that both pieces of kit won't fly.
Your config is probably good. (who knows... not me.)
Late-late-late with advice... I know... but you guys helped me out recently so a drive by on this ... and stuff..
cheers.
Late on this but we've got this issue at our local school.
Advisory: HP Compaq dx2200 May Hang During Remote Image Deployment, HP support document ID: c00746649
So that takes the DX2200 out of the "can do" basket. I think the Lithuanian guy is right about the broken NIC firmware, just coincidence that both pieces of kit won't fly.
Your config is probably good. (who knows... not me.)
Late-late-late with advice... I know... but you guys helped me out recently so a drive by on this ... and stuff..
cheers.
#5
Posted 06 September 2011 - 10:38 AM
Advisory: HP Compaq dx2200 May Hang During Remote Image Deployment, HP support document ID: c00746649
It's this one:
http://h20000.www2.h...=reg_R1002_USEN
Basically it is a BIOS firmware update.
ftp://ftp.compaq.com...500/sp33387.exe
SP33387
Good to know.
Though unlikely to be of any practical use to peeps having a "Toshiba Portege M200 lap top".
Just like a new, improved carburetor for a Volkswagen Golf GTI 1987 won't be of real use for a FIAT 124 Spider.
Wonko
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users