Hi All

I am having a problem remote booting client machines using LTSP 3.05.  The server is a 
RH 7.3 box without much on it, and LTSP was installed from RPM.  

I have tried two clients with boot rom on the nic, and etherboot from a 
floppy.  The DHCP server responds to the client, the client gets the correct IP 
address, and knows which server to find the kernel on.  The client sends 
through a tftp request for the correct kernel file to the server.

Here is where things are breaking down and I am stuck  The server __appears__ 
to start chucking packets at the client the client doesn't seem to see them  
it just periodically initiates a new tftp session on the server.  After 5 tries, the 
client gives up with a timeout error.  I can manually tftp to the 
server from another linux machine, and get the kernel file.  I can't ping the 
client from the server while it it trying to tftp, but at that level I am not 
sure if the client should respond to a ping?

I have removed ipchains from the LTSP server, modifed hosts.allow to let tftp 
through to the client.  I must have missed something simple

Any help appreciated

Cheers
Robert

---
Robert Fraser                   
Infrastructure Manager                    
Canterbury District Health Board         ph   +64 3 364 1467
Christchurch, New Zealand                mob  +64 27 226 5708



**********************************************************************
** This email and attachments have been scanned for content and viruses 
and is believed to be clean **

This email or attachments may contain confidential or legally 
privileged information intended for the sole use of the addressee(s). 
Any use, redistribution, disclosure, or reproduction of this message, 
except as intended, is prohibited. If you received this email in error, 
please notify the sender and remove all copies of the message, 
including any attachments. Any views or opinions expressed in this 
email (unless otherwise stated) may not represent those of Canterbury 
District Health Board
**********************************************************************

Reply via email to