Link to home
Start Free TrialLog in
Avatar of Hobson Beeman
Hobson Beeman

asked on

IP addresses issued are different from DHCP range assigned

I have a LAN with about 20 PCs (DHCP assigned) and a domain controller (static IP). The LAN has been relatively stable, but lately for some reason the PCs are starting to get assigned an IP address different (10.0.1.x) from what the DHCP server range is assigned to use (192.168.0.100-199). I have had the Comcast router changed out thinking it may be the problem, however it did not resolve the issue. There are also 2 Apple Express APs that provide wireless access to 192.160.0.x and one that provides guest access to a 192.168.1.1, 255.255.255.128 network. All the APS appear to be working properly. I am not sure why this occurring and have not seen any errors about more than one DHCP server on the network. Any suggestions would be most welcomed regarding where to start or a resolution. - Thx HBee
Avatar of Member_2_406981
Member_2_406981

boot an affected machine with a knoppix dvd start wireshark and let the machine do some dhcp requests and see what happens.

from which mac address he will get what dhcp replys,

would be most effective way to see whats going on.
Avatar of Dave Baldwin
The default IP range for Comcast routers is 10.0.1.x.  At least it has been for the ones that I have had.
Make sure to login into the Comcast router and disable the DHCP portion.

The issue you seem to have might be related t o where the Comcast cable is plugged into
Given you have two conflicting IPs , look at the network layout setup you expect versus how it is setup.

Internet <=> Comcast router <=> do you have an internal router <=> switch <=> LAN?
you can run ipconfig /all to see what the ip of the dhcp server is. then look at your arp cache to get the mac. look in the forwarding table of the switch and track down the switch port to identify the host.
i had the same issue. If you want to use your own IP range, make sure you disable bridge mode on the Comcast router
Actually, if you do want to use your own IP, you need to enable bridge mode on comcast. I.e. the comcast router's functionality will only make sure to terminate the docsis connection with ethernet being passed to the router behind it.
In bridge mode, the comcast device will function as an adapter no routing/DHCP IP assignment from it..
Avatar of Hobson Beeman

ASKER

There is no internal router other than the Comcast equipment. Oddly, the older SMC was the original DOCIS 2.0 modem that was in use when the problem began and has always been in the router mode. The fact that the PCs were pulling a 10.0.1.x IP led me to believe it was the modem/router since this is default Comcast IP address range. They replaced it with a Netgear 3000 series DOCIS 3.0  and it was also set up in the router mode (no bridge mode setup), however the problem remained. I did run an ipconfig/all and looked at the MAC of the DHCP server, it does not match the Comcast Netgear 3000. I'll have to look into the knoppix DVD, not familiar with it. I'm kinda doubting the Comcast equipment is at fault, but haven't ruled it out.
Login into the Comcast router on IP 10.0.0.1 and change the settings reconfiguring its IP LAN range to match what you have configured and you would need to reboot the Comcast device after the changes.
ASKER CERTIFIED SOLUTION
Avatar of vivigatt
vivigatt
Flag of France image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Vivigatt, thanks for the url and info, I will certainly give this a try to see if it reveals anything and keep everyone posted.
The problem was accidentally created by myself. I had set up an Apple Express access point and had set it up to use NAT+DHCP to create a different subnet (10.0.1.x) for guest users. This was the same default range as the Comcast router. Turns out that after some investigation that the Apple was trying to do DHCP on the Ethernet connection? I disconnected it and all was back to normal. I then set it up in test environment and it worked as it should offering the 10.0.1.x addresses to the WiFi side.