SBS2003 DHCP server detects itself

i have an SBS server that is responsible for DHCP on my network. Every few hours the DHCP service shuts down stating that it has detected another dhcp server on the network. the problem is the DHCP server it is detecting is itself.
this SBS has 2 NIc cards

card 1 192.168.27.134, 255.255.255.224, 192.168.27.129
card 2 192.168.16.10, 255.255.255.0, (no gateway)

the error message states that SBS has encountered another server on this netowrk with ip address 192.168.16.10.

any ideas on how to fix this from the server side, without touching the actual network?
LVL 18
Sanga CollinsSystems AdminAsked:
Who is Participating?
 
Rob WilliamsConnect With a Mentor Commented:
Though it would not be enabled with a wizard, RRAS (Routing and Remote Access) has an option to install NAT/basic firewall. Within it's configuration it can set up a DHCP server for NAT clients which can cause the DHCP server to shut down. If RRAS is enabled try locating the RRAS service in the service management console and stopping the service to see if this cures the problem. If so RRAS will have to be re-configured.
0
 
craigothyConnect With a Mentor Commented:
Check your bindings within DHCP.  Launch the DHCP administration console.  Right click on the DHCP server in question and click "properties".  Click the "Advanced" tab and then click the "Bindings" button.  Make sure the inactive nic is not checked and the active nic is checked.  Hope this helps.
0
 
Sanga CollinsSystems AdminAuthor Commented:
the server is bound to the 192.168.16.10 address on NIC#2, but not to the 192.168.27.134 address. should it be bound to both interfaces or just the one that it is servicing?
0
Cloud Class® Course: Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

 
craigothyCommented:
It should only be bound to the network segment that it is servicing.
0
 
Sanga CollinsSystems AdminAuthor Commented:
it was bound to just the one interface (same as network it was serving)
0
 
Rob WilliamsCommented:
Are you certain DHCP has not been enabled on a local router?
0
 
Sanga CollinsSystems AdminAuthor Commented:
dhcp is not enabled on the local router (actually a juniper firewall) i also blocked all traffic from the second NIC card from reaching the first NIC card using a policy in the firewall. sadly the result is the same. every few hours the dhcp server service shuts itsefl off saying that it has it has detected another server on the network, which happens to be itself
0
 
Sanga CollinsSystems AdminAuthor Commented:
i stopped the RRAS service and should have more info by tomorrow morning whether it worked or not. This server is occasionally used as a VPN gateway into our network for my boss, and it looks like RRas is a part of that setup. hopefully my boss wont need to connect while he is on a week long business trip!
0
 
Rob WilliamsCommented:
If you want to leave RRAS enabled you can locate the specific problem. I didn't have a RRAS server handy earlier. The problem, if it exists, is the DHCP allocator. This can be located and disabled by going to: RRAS console | expand the server name | expand IP routing | if present/installed right click on NAT and choose properties | Address assignment | un-check automatically assign IP addresses using DHCP allocator.
I can't think of anything on SBS this would be used for. It can be used when doing Internet Conection Sharing without SBS.
0
 
Sanga CollinsSystems AdminAuthor Commented:
i tried with RRAS disbaled, as well as with the dhcp allocator disabled (it was already disabled by default) and the problem persists. i think im just going to disbale the dhcp server entirelly and just let the juniper firewall handle the dhcp services from here on out.
0
 
Rob WilliamsCommented:
The only other possibility I can think of is to use a packet analyzer like Wireshark, filter for DHCP offers, and see if any are coming from another source.
http://www.wireshark.org/
0
 
Sanga CollinsSystems AdminAuthor Commented:
ill give this a shot before throwing in the towel. id rather fix the problem than just find a quick band aid (which happens alot at the company i work for, i think we have more band aid than actual infrastructure).

ill post the results later this evening or early tomorow
0
 
Rob WilliamsCommented:
Great. Good luck with it.
I agree the band-aids pile up and then end up being the problem down the road.
0
 
Sanga CollinsSystems AdminAuthor Commented:
i finally resolved the problem by removing dhcp options 66 and 68 which were configured for a now defunct pxe boot server. im not sure why this started causing the problem, but since i removed the settings earlier this week, the problem has since stopeed
0
 
Rob WilliamsCommented:
Interesting.
Good to know, and thank you for reporting your findings. Likely option 68 that was the problem.
--Rob
0
 
Sanga CollinsSystems AdminAuthor Commented:
just to clarify for all, it was actually option 66 and 67 that i used,not option 68. i was also able to determine that i had missed some steps when configuring windows to point to a secondary serve for pxe boot services. in addtion to the DHCP options, RRAS needed to be configured as weel which i totally neglected.

thanks to all for your contributions
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.