[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Son of Re: [K12OSN] x86 thin client apparently ignoringDHCPOFFER from LTSP



I tried to set up a very simple network: the computers are connected with a crossover cable -- there is no hub. I tested the setup with the Mircon/Gateway, and things worked fine. So , I assume that the cable and server ethernet card is OK. When I went to the Micron/Vaio, it did not work. I can't readily change the ethernet card in the Vaio (it is a laptop). I can move the ethernet card in the server, so I will give that a try. Keep shooting ideas at me.

Tom
labone ifx net


At 11:46 AM 1/24/2003 -0500, you wrote:
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.

It could be a bad ethernet cable, or even a bad port on your switch or
hub.  Ethernet cables use two different pairs of wires for transmit vs
receive.  Your client is transmitting OK (the server sees the dhcp
request and makes an offer) but the client doesn't receive the offer.

It could also be a bad ethernet card in the client, or it could be that
the ethernet card is plugged into a bad slot.

So I'd try these steps:
Try a different ethernet cable for the client.
Try a different ethernet cable for the server.
Try a different port on the switch/hub.
Move the client's ethernet card to a different slot.
Try a different ethernet card in the client.


-- Jim Thomas Principal Applications Engineer Bittware, Inc jthomas bittware com http://www.bittware.com (703) 779-7770 I'm a man. But I can change. If I have to. I guess. - Red Green



_______________________________________________
K12OSN mailing list
K12OSN redhat com
https://listman.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>







[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]