DHCP, Some Leases have wrong Subnet Mask, causing IP address conflicts
We have been having a weird set of issues come up recently. We have several subnets that we are getting reports of IP address conflicts errors from end users. We are assigning addresses via DHCP. The addresses (hardware, and IP) that are being listed as being in conflict are usually not the same. I initialy thought this could be a dhcp server issue, so I changed one subnet with issues to a different DHCP server with a differant scope of addresses. No change the issue still exists. Then errors started occuring on a subnet in a remote location, running a totally differant setup for dhcp(The main site uses Microsoft's DHCP Server propagating dhcp traffic across a Cisco 6509 Switch's subnets with helper addresses setup, and the remote site with a single subnet with a Cisco 4006 switch, and running DHCP Server on the 1750 Cisco Router at that location) Finally I found one lead but am not sure what it means. We just got in a new Fluke Optiview Network analyser, and I put it on each subnet with issues. The Optiview shows that on each subnnet about 6 PC's have the wrong subnet mask, It should be a class C subnet mask but is coming up as class A or B. I verified that these PC's were not set with static IP addresses, and if you release and renew the ip address manually the correct mask appears, but within a couple days the incorect mask reappears. The only thing in common with these computers seems to be that they are running Windows 98, they are all of several differant brands, and also are running several differant brands of Network cards (3Com, integrated Dell, and Aopen) My thoughts are that since the subnet masks are not right the dhcp servers cannot tell that the IP addresses they are assigning are in use and they reassign the same address. Any ideas? Am I even on the right track here?
Re: DHCP, Some Leases have wrong Subnet Mask, causing IP address
I could only venture some educated guesses but there may be a rogue DCHP server on the local subnet (to the PC sending the DHCP request) or that your DHCP server scopes are overlapping. If multiple DHCP servers can issue addresses for that subnet, make sure both scopes do not overlap each other and that the proper mask is configured in the scope settings. In most DHCP implementations, DHCP servers do not sychronize their databases so they will be unaware of other DHCP servers. Also you will need to make sure that your Win98 machines have the latest IP stack from Microsoft (usually contained in the latest MSDUN update).
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...