I have thought about that, so I connected the cable that was going to eth1 of the server that was not working to eth1 of one of my other servers. All thin clients booted up therefore I can conclude that something blew up in the motherboard.
Thanks to everyone that tried to help
On Wed, Mar 4, 2009 at 6:18 PM, David Groos <email@example.com> wrote:
I offer this story, quite uncertain of its utility, nonetheless...* My thin clients were working well last summer, then I replaced the switch with a new switch... and could get only 1 or often none of the thin clients to boot--couldn't connect to a DHCP server.* Several people tried to find the problem with the new switch, and it wasn't until a systems engineer looked at it that he was able to properly configure it so that during the PXE booting, the thin client could get it's IP address.* I seem to recall him saying it was something about the spanning tree protocol though don't remember if that was just one of the things he checked or if that were the issue... Good luck :-)
On Wed, Mar 4, 2009 at 5:03 PM, Nicolas Roussi <firstname.lastname@example.org> wrote:
I have formatted yet again the server and this time I installed 8.04 i386 thinking that this will resolve the issue since I have another on the LAN that works perfectly. After the 3rd client boots up I get the same thing No DHCP or no proxyDHCP offers received. Could it be that the network card or the motherboard blew something?
On Tue, Mar 3, 2009 at 9:31 PM, Nicolas Roussi <email@example.com> wrote:
I am guessing that it is. I recently configured a bind9 server on the network which is also the LDAP server but I disabled bind9. These are the files on the server that is not working. I have included hosts, hostname, interfaces, dhcpd.conf, ifconfig -a and resolv.conf. I am really puzzled about this. The help is greatly appreciated.