Re: Son of Re: [K12OSN] x86 thin client apparently ignoring

Tom La Bone (labone@ifx.net)
Thu, 23 Jan 2003 20:50:15 -0500

Messages sorted by: [ date ][ subject ][ author ]
Next message: Shawn Powers "Re: [K12OSN] Onboard S3 Trio64V+"
Previous message: Terrell Prude', Jr. "Re: Son of Re: [K12OSN] x86 thin client apparently ignoring DHCPOFFER"

I don't have access to another server -- all of this is going on in my 
study at home.  I am trying to experiment with the LTSP setup to in an 
effort to see if could be used at our K-8 school computer lab.  As a side 
note, I am curious why the Gateway and Vaio were offered different IP 
addresses when they were each the only client on the network when they 
tried to boot.

At 08:38 PM 1/23/2003 -0500, you wrote:
>Hmmm...I had a similar problem and tested it with an alternate DHCP server 
>(in my case, a Cisco router).  This may sound like heresy, but solely as a 
>troubleshooting technique (i. e. not a production solution!), would it be 
>possible for you to set up, say, an NT Server with the MS DHCP server, 
>just to see if it's the thin client itself or the ISC DHCP daemon?
>
>--TP
>
>Tom La Bone wrote:
>
>>All of this message did not get to you last time, so I will try again.
>>
>>I have a 1GHz Micron server running LTSP V3.0 connected by a crossover 
>>cable to a 233 MHz Gateway client.  I booted the Gateway with a ROM 
>>floppy and it successfully boots and runs as a thin client.  This is 
>>really cool.  The relevant parts of /var/log/messages for this are
>>
>>Jan 22 21:37:14 Bootle dhcpd: DHCPDISCOVER from 00:a0:cc:64:8b:dd via eth0
>>Jan 22 21:37:15 Bootle dhcpd: DHCPOFFER on 192.168.0.253 to 
>>00:a0:cc:64:8b:dd via eth0
>>Jan 22 21:37:15 Bootle dhcpd: DHCPREQUEST for 192.168.0.253 
>>(192.168.0.254) from 00:a0:cc:64:8b:dd via eth0
>>Jan 22 21:37:15 Bootle dhcpd: DHCPACK on 192.168.0.253 to 
>>00:a0:cc:64:8b:dd via eth0
>>Jan 22 21:37:20 Bootle dhcpd: DHCPDISCOVER from 00:a0:cc:64:8b:dd via eth0
>>Jan 22 21:37:20 Bootle dhcpd: DHCPOFFER on 192.168.0.253 to 
>>00:a0:cc:64:8b:dd via eth0
>>Jan 22 21:37:22 Bootle dhcpd: DHCPREQUEST for 192.168.0.253 
>>(192.168.0.254) from 00:a0:cc:64:8b:dd via eth0
>>Jan 22 21:37:22 Bootle dhcpd: DHCPACK on 192.168.0.253 to 
>>00:a0:cc:64:8b:dd via eth0
>>
>>I then rebooted the Micron and attached a VAIO notebook with the 
>>crossover cable.  The VAIO shows the following (as best I could copy it) 
>>while it tries to boot from its floppy:
>>
>>.000021.0000 done
>>ROM segment 0x0800 length 0x4000 reloc 0x9400
>>A20 enabled via bios
>>Etherboot 5.0.8 (GPL) Tagged ELF for [EEPRO100]
>>Boot from (N)etwork or from (L)ocal? N
>>Probing...[EEPRO100]Found Intel EthernetExpressPro100 82562EM ROM address 
>>0x0000
>>Ethernet addr: 08:00:46:13:88:29
>>Searching for server (DHCP)..
>>
>>Then it freezes and goes no further.  The relevant part of 
>>/var/log/messages for the VAIO are
>>
>>Jan 22 21:49:13 Bootle dhcpd: DHCPDISCOVER from 08:00:46:13:88:29 via eth0
>>Jan 22 21:49:14 Bootle dhcpd: DHCPOFFER on 192.168.0.252 to 
>>08:00:46:13:88:29 via eth0
>>
>>Any ideas what is going wrong here?  Thanks for the help.
>>
>>Tom La Bone
>>labone@ifx.net
>>
>>
>>
>>
>>
>>
>>_______________________________________________
>>K12OSN mailing list
>>K12OSN@redhat.com
>>https://listman.redhat.com/mailman/listinfo/k12osn
>>For more info see 
>
>
>
>
>
>_______________________________________________
>K12OSN mailing list
>K12OSN@redhat.com
>https://listman.redhat.com/mailman/listinfo/k12osn
>For more info see 





_______________________________________________
K12OSN mailing list
K12OSN@redhat.com
https://listman.redhat.com/mailman/listinfo/k12osn
For more info see

Next message: Shawn Powers "Re: [K12OSN] Onboard S3 Trio64V+"
Previous message: Terrell Prude', Jr. "Re: Son of Re: [K12OSN] x86 thin client apparently ignoring DHCPOFFER"