I have a windows 2003 server (standard) providing DHCP/DNS/Wins services to a small network with a IP address of 192.168.1.50
internal user IP range is 192.168.1.100 to 192.168.1.150, with each machine being assigned a fixed DHCP IP based on MAC Address.
A Linksys router acts as the default gateway with DHCP being disabled on it (the W2k3 DHCP server passes the default gateway/DNS/Wins to the DHCP clients)
Sometimes, a machine will loose its fixed DHCP address and will be assigned something like 192.168.1.2; but the DNS/WINS will be correct and point to 192.168.1.50)
Usually there will be no record of this in the DHCP log (sometimes I’ll see the client machine making quite a few requests later on for the 192.168.1.2 and then get assigned the correct IP).
Its like the DHCP service hickups and looses track?
Any one else seen anything similar, and know of why, and if there’s something that can be done.
Aside: I think its alternate DHCP server, or a Windows 2003 Standard issue. I also baby sit a similarly configured Windows 2003 SB server which doesn’t assign screwy IP addresses (theres a dlink as the default gateway).. Its the fact that the DNS, and wins information is correct which makes me think its something to do with the Windows 2003 server
Thanks
Paul