Re: [Ltsp-discuss] running dhcpd on port 67 \n ERROR! dhcpd failed!

2006-07-30 Thread Darryl Palmer
On 7/25/06, RP <[EMAIL PROTECTED]> wrote: Did I say I was using a hub?  Don't twist this around.  The problemsexisted UNTIL the SWITCH was put into place. Do a Google search for 'collision' and 'duplex' and you'll find that thesymptoms I was seeing are common when two network devices wind up usingd

Re: [Ltsp-discuss] running dhcpd on port 67 \n ERROR! dhcpd failed!

2006-07-25 Thread RP
Peter Billson wrote: > RP wrote: > > D-Link's "collision" light would sometimes go berserk. > >Collision light? On a switch? Sounds like a hub. Using a hub with > LTSP will almost certainly cause you some grief. > Did I say I was using a hub? Don't twist this around. The problems existe

Re: [Ltsp-discuss] running dhcpd on port 67 \n ERROR! dhcpd failed!

2006-07-25 Thread Peter Billson
RP wrote: > D-Link's "collision" light would sometimes go berserk. Collision light? On a switch? Sounds like a hub. Using a hub with LTSP will almost certainly cause you some grief. Hubs/switches will compensate for many network ills, including poor wiring but putting a switch/hub at eac

Re: [Ltsp-discuss] running dhcpd on port 67 \n ERROR! dhcpd failed!

2006-07-24 Thread RP
Robert Bottomley wrote: > I did find a work around that works for me: I noticed if I hooked the > LTSP client up to a cheap D-Link 5-port switch and then into our > network, no more problem. I bought a bunch of D-Link switches and put > one on each client that was having the problem. It seems to

Re: [Ltsp-discuss] running dhcpd on port 67 \n ERROR! dhcpd failed!

2006-07-24 Thread Robert Bottomley
Mikhail Pokidko wrote: > PXE boot works. It gets the IP address over DHCP, retrieves the kernel > over TFTP, and starts booting it. > And then after loading NIC module (e100) it starts to launch dhcpd > > > > Running dhcpd on port 67 > Input: imPS2/2 Generic Wheel Mouse as /class/input/input1 >

Re: [Ltsp-discuss] running dhcpd on port 67 \n ERROR! dhcpd failed!

2006-07-24 Thread Mikhail Pokidko
hm, unfortunately it doesn`t make any difference: # less /etc/dhcp/dhcpd.conf | grep option-12 option option-128 code 128 = string; option option-129 code 129 = text; option option-128 e4:45:74:68:00:00; option option-129 "NIC=e100"; it still freezes at trying to start dhcpd @ client I`ve trye

[Ltsp-discuss] running dhcpd on port 67 \n ERROR! dhcpd failed!

2006-07-24 Thread Mikhail Pokidko
PXE boot works. It gets the IP address over DHCP, retrieves the kernel over TFTP, and starts booting it. And then after loading NIC module (e100) it starts to launch dhcpd Running dhcpd on port 67 Input: imPS2/2 Generic Wheel Mouse as /class/input/input1 ERROR! dhcpd failed! Can someone give t