-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Kanwar Ranbir Sandhu Sent: Tuesday, January 16, 2007 2:28 PM To: CentOS mailing list Subject: [CentOS] dhcpd errors
Hello Everyone,
I'm running a dhcp server on CentOS 4.4. It's providing IPs and remote booting for a number of thin clients.
I've recently had problems rebooting a few thin clients. Here is the error I've been seeing:
Jan 16 14:16:45 at01 dhcpd: DHCPRELEASE from 00:40:63:e5:71:4f specified requested-address. Jan 16 14:16:45 at01 dhcpd: DHCPRELEASE of 10.1.1.150 from 00:40:63:e5:71:4f via eth0 (not found)
Depending on the thin client, the MAC and the IP changes. Otherwise, the errors are all the same.
The effect on the thin client end is that it doesn't get an IP, and so it doesn't boot. The usual remedy is to unplug/plug-in the cat5 cable at the thin client, or to move the thin client to another network drop.
This has me thinking there's a problem with the cat5 cabling (the office is going through a major renovation). But, I'm not 100% that is the case. It could be a problem with the dhcp server.
I don't have easy access to that office - it's remote, and I'm only out there once every few months. It's why I want to make sure it's not a software problem first.
At the moment I have no clue what's going on. My searching with google hasn't turned up anything useful.
I'd appreciate any comments/suggestions.
If you are using Cisco switches make sure that you have "spanning-tree portfast" set for each PC/thinclient port, otherwise the spanning-tree protocol negotiation phase might step on the DHCP offers.
-Ross
______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.