Hello there, I suceeded in setting up WDS with PXELinux. Now I'm trying to point the primary tftp server with pxechain.com to a second tftp server. Actually it will just load the specified kernel, which is given through APPEND. After that the tftp client just freezes. Do I need to start with another tftp? The actual used tftp (and DHCP) server comes from Win2008 R2 Server. (Using Syslinux 4.02 package) Any help would be appreciated. Thanks, Alex
--On Wednesday, September 08, 2010 11:38:15 PM +0200 Alexander <erazoramg at freenet.de> wrote:> Hello there, > > I suceeded in setting up WDS with PXELinux. > Now I'm trying to point the primary tftp server with pxechain.com to a > second tftp server. Actually it will just load the specified kernel, which > is given through APPEND. After that the tftp client just freezes. > Do I need to start with another tftp? The actual used tftp (and DHCP) > server comes from Win2008 R2 Server. > (Using Syslinux 4.02 package) > > Any help would be appreciated.You haven't told us anything about the configuration that leads to the problem. Please send a copy of your PXELINUX config file along with a description of which server is which, where the files are, and exactly what happens when you try to chain to the second server (what output do you get? especially, what are the last lines before it freezes?). -- Jeffrey T. Hutzelman (N3NHS) <jhutz+ at cmu.edu> Carnegie Mellon University - Pittsburgh, PA
On Wed, Sep 8, 2010 at 17:38, Alexander <erazoramg at freenet.de> wrote:> Hello there, > > I suceeded in setting up WDS with PXELinux. > Now I'm trying to point the primary tftp server with pxechain.com to a > second tftp server. Actually it will just load the specified kernel, which > is given through APPEND. After that the tftp client just freezes. > Do I need to start with another tftp? The actual used tftp (and DHCP) server > comes from Win2008 R2 Server. > (Using Syslinux 4.02 package) > > Any help would be appreciated. > > Thanks, Alexpxechain.com is supposed to be used to load another pxe program, like a copy of PXELINUX, off of another server. It might be freezing if you're passing it a normal kernel (like the Linux kernel). It should accept another PXE program. If 192.168.0.3 is the new TFTP, 'APPEND 192.168.0.3::pxelinux.0' should work (assuming that's the name of the file, of course). Is this what you're already doing? -- -Gene