IP Address Conflict
I Have a sbs 2003 sevrer running in my workshop (In a computer shop) every so often the dhcp server (running on the sbs2003 box) will give a customers computer the same ip address as the server and throw everything to hell. We need to plug the customers machines in for wds use and for basic internet etc. I've already set a reservation for the server in DHCP but it still seems to do it randomly. Any ideas?
Krzysztof Pytko
Could you tell me please what is your DHCP scope's configuration, please?
ASKER
Sorry iSiek, what details exactly are you needing? Does the attached screen shot help or do you need me to burrow down a bit?
dhcp.JPG
dhcp.JPG
Have you tried just creating an exclusion for the server IP address in DHCP and assigning the IP address statically on the server?
See: http://technet.microsoft.com/en-us/library/cc754537%28WS.10%29.aspx
See: http://technet.microsoft.com/en-us/library/cc754537%28WS.10%29.aspx
Are you sure you don't have another device that sometimes comes online and starts handing out IP addresses?
Frankly, I'd change the scope so it couldn't give out the server's IP address.
Frankly, I'd change the scope so it couldn't give out the server's IP address.
I would always use static addresses for servers and exclusions for those addresses in dhcp as long as doing so is feasible i.e. there are not too many servers and they are all accessible. That way the servers are not reliant on dhcp to get a correctly assigned IP address.
ASKER
There's only the one server, it's statically assigned to 192.168.1.2. Is an exclusion the same as a reservation? I've just realised the scope starts at 192.168.1.1 i've just changed it to 192.168.1.3. Will this stop it happening again?
No an exclusion is not the same as a reservation. See http://www.windowsnetworking.com/kbase/WindowsTips/Windows2003/AdminTips/Network/DHCPReservationsandExclusions.html
By changing the scope you have effectively excluded the first two IP addresses anyway. That should stop DHCP leasing those addresses.
By changing the scope you have effectively excluded the first two IP addresses anyway. That should stop DHCP leasing those addresses.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
It might be worth using dhcploc from the command line to check for any rogue dhcp servers. See http://www.windowsnetworking.com/kbase/WindowsTips/Windows2000/AdminTips/DHCPandDNS/UsingtheDHCPLOCUtility.html
There shouldn't be one online NOW, but maybe someone brings in a VM or a linksys router needs a periodic reset - if there were one on the network now, SBS would show the SBS DHCP server as shutdown.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Haev you checked your router if it is assigning IP address as well?
ASKER
Dhcp on the router is switched off. Is the problem with 192.168.1.x just that alot of devices may already have the an ip address from that range statically assigned?
ASKER
Turned out to be a bit of a messy question, thanks for the help folks