Win 2008 R2 DHCP Servers - BAD_ADDRESS

My 2 DC's in another site (since replacement of a firewall) are giving outr all IP's in the scope.

I also noticed that the autoconfig option on the Local VM NICs were also picking up a 169 IP and losing connectivity with the LAN, but also showed its original static IP as an auto configured IP...

So i found a fix (for now) to get the 2x DC's up but disabling DHCP client service and other settings for the local DC's.  Fine, but i still am getting BAD_ADDRESSES in the DHCP servers.

Ideas, before i go back and replace the firewall?

Thanks
LVL 1
CHI-LTDAsked:
Who is Participating?
 
eeRootConnect With a Mentor Commented:
Since this happened right after a firewall was replaced, I would suspect the new firewall has its DHCP server enabled.  But you may need to check the whole network for rouge DHCP servers, and enable conflict detection as well.

How to find rogue DHCP servers.
How to enable Conflict Detection

Also, try extending the DHCP lease time to several days, so clients only need to refresh their IP address once a week or so.
0
 
CHI-LTDAuthor Commented:
Its having the same affect on my other 2008 R2 servers.  But 2008 is fine...
0
 
CHI-LTDAuthor Commented:
0
What Kind of Coding Program is Right for You?

There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.

 
Steve KnightConnect With a Mentor IT ConsultancyCommented:
if you havent already turn on the conflict detection in properties of dhcp server.

for one client, what does ipconfig /all say it gets its address from?  you say it got an apipa address but had static address before - do you mean alternative address setting?

steve
0
 
Steve KnightConnect With a Mentor IT ConsultancyCommented:
also is firewall sending dhcp requests through dhcp helper / relay setting to your other site so that is replying and allocating that subnet.

i presume if both servers are doing dhcp that you have non overlapping ranges, or ratherscope is full range and exclude the other servers ranges?
0
 
CHI-LTDAuthor Commented:
Yes, scopes were fine, as was the LAN itself.
Cause was to do with this http://social.technet.microsoft.com/Forums/windowsserver/en-US/07a26080-5b37-410d-85c7-e131cc678efe/vista-and-windows-7-client-not-getting-ip-fom-dhcp-server - at the bottom of th page...
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.