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

DHCP question




Can anyone think of why a Winbox would stop sending it's hardware address when it's time to renew its lease? When the machine is first turned on, it requests an IP correctly. I can see its hardware address in the log files, and DHCP will hand out an IP, no problem. But later in the day, sometimes within an hour, but more often than not when the lease expires and the machine comes back to renew, this is what I see:

dhcpd: DHCPINFORM from 192.168.1.139 via eth1
dhcpd: DHCPACK to 192.168.1.139 (<no client hardware address>) via eth1
dhcpd: DHCPINFORM from 192.168.1.139 via eth1
dhcpd: DHCPACK to 192.168.1.139 (<no client hardware address>) via eth1
dhcpd: DHCPINFORM from 192.168.1.139 via eth1
dhcpd: DHCPACK to 192.168.1.139 (<no client hardware address>) via eth1

...and that happens for a few seconds then it stops. Rebooting the Winbox will cause it to send its hardware address again, only to stop when it's time for renewing again.


Here's another that did The Right Thing (TM) to begin with, but then failed shortly thereafter:

10:47:22 dhcpd: DHCPDISCOVER from 00:08:74:bd:06:b6 via eth1
10:47:23 dhcpd: DHCPOFFER on 192.168.1.117 to 00:08:74:bd:06:b6 (MedusaGorgon) via eth1 10:47:23 dhcpd: Added new forward map from medusa.example.com to 192.168.1.117 10:47:23 dhcpd: added reverse map from 117.1.168.192.in-addr.arpa. to medusa.example.com 10:47:23 dhcpd: DHCPREQUEST for 192.168.1.117 (192.168.1.1) from 00:08:74:bd:06:b6 (MedusaGorgon) via eth1 10:47:23 dhcpd: DHCPACK on 192.168.1.117 to 00:08:74:bd:06:b6 (MedusaGorgon) via eth1

11:00:30 dhcpd: DHCPINFORM from 192.168.1.117 via eth1
11:00:30 dhcpd: DHCPACK to 192.168.1.117 (<no client hardware address>) via eth1
11:00:30 dhcpd: DHCPINFORM from 192.168.1.117 via eth1
11:00:30 dhcpd: DHCPACK to 192.168.1.117 (<no client hardware address>) via eth1
11:00:30 dhcpd: DHCPINFORM from 192.168.1.117 via eth1
11:00:30 dhcpd: DHCPACK to 192.168.1.117 (<no client hardware address>) via eth1


The machines exhibiting this behavior are all Winblows systems, Win2K & WinXP (Home and Pro)

So, is this a hardware problem with that machine, or is Winblows itself acting up?

--
W | It's not a bug - it's an undocumented feature.
 +--------------------------------------------------------------------
 Ashley M. Kirchner <mailto:ashley pcraft com>   .   303.442.6410 x130
 IT Director / SysAdmin / Websmith             .     800.441.3873 x130
 Photo Craft Imaging                       .     3550 Arapahoe Ave. #6
http://www.pcraft.com ..... . . . Boulder, CO 80303, U.S.A.
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]