• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 944
  • Last Modified:

DHCP server problems

I am running DHCP on a 2k3 server. It's been fine until recently. In the last month, I've had issues where clients get an IP address, but can't ping or connect to the DC (also my DHCP).
They are able to ping any other server on the network.
After much research, I've discovered that my DHCP server has an issue, as this now is happening to multiple PCs everyday.  

I have attached a picture of a snapshot of my DHCP.  I have IP's that list "bad_address", and others that are blank.  I'm not sure if any of these are causing the problem, but it doesn't look good.  I'm assuming instead of trying to figure out what is corrupt, it might be easier to just move the DHCP server to another server, right?

So does anyone know of any good websites that have step by step instructions on how to do this?
0
Dan
Asked:
Dan
3 Solutions
 
DanNetwork EngineerAuthor Commented:
Here's the attachement.
DHCP.jpg
0
 
DanNetwork EngineerAuthor Commented:
I just had a user call me and tell me that her PC said there's a duplicate IP on the network, but when I checked, her IP is only listed once in DHCP.
0
 
DanNetwork EngineerAuthor Commented:
After doing some googling, I was thinking to just migrate the entire database over to the the 2008 server, but if the database is corrupt, then I think I would be moving the issue over to the new server.  It would be nice though to just move everything over, instead of creating all scopes from scratch.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
CompProbSolvCommented:
Is the DHCP configuration too complicated to reconfigure on the other server manually?
0
 
DanNetwork EngineerAuthor Commented:
Well, kind of.  I have 4 scopes, but that's not the problem, I have a Siemens phone system, an when the vender installed it, they entered a special code of characteres into the DHCP server to make it work. I  have no idea what that code is.  But I was thinking, since it's exporting the database in a .txt document, I wonder if that moves the corruption to the new server or not?
0
 
Andrew DavisManagerCommented:
have you checked for existence of a secondary DHCP?

Can you post a ipconfig /all from a good machine and also a bad machine?

Have you tried doing an ipconfig /registerdns to a bad machine?

Cheers.
Andrew
0
 
Krzysztof PytkoSenior Active Directory EngineerCommented:
Looks like something is issuing DHCP leases too (another DHCP server?)
Try to investigate if there is any
http://blogs.technet.com/b/teamdhcp/archive/2009/07/03/rogue-dhcp-server-detection.aspx

additionally, please enable on your DHCP server, IP conflict detection attempt and used IPs won't be issued. DHCP database would be rebuilt
http://www.windowsitpro.com/article/dhcp2/how-can-i-enable-conflict-detection-on-my-dhcp-server-

and see if it is working properly then

Regards,
Krzysztof
0
 
DanNetwork EngineerAuthor Commented:
I am on windows 2003, so it doesn't have the optoin for IP conflict detection.

What gives you the impression that something else is issuing DHCP leases?
0
 
Krzysztof PytkoSenior Active Directory EngineerCommented:
Yes you have :) Open DHCP Management console and select server name. Click on it right mouse button and choose "Properties". Udener "Advanced" tab set up 2-3 in section "Conflict detection attempt"

Should work fine. If you wish, you may also rebuild DHCP database by replacing current with empty one. If you're interested, please let me know

Krzysztof
0
 
DanNetwork EngineerAuthor Commented:
Yes, I guess I don't mind rebuilding it, but the only problem is with my Siemens VoIP phone system, there's special characters they entered when they installed it and I don't know what they are.  Do you have instructions on how to build it step by step, I think I alreayd have an article on this.
0
 
Krzysztof PytkoSenior Active Directory EngineerCommented:
Please follow a post from EE in which I helped with
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_27818325.html

This is about broken DHCP database but it also applies in your case.

Krzysztof
0
 
DanNetwork EngineerAuthor Commented:
I ran the subnet and rogue program and it didn't detect any rogue dhcp servers.

my main DHCP server is 192.168.100.50

Then my 192.168.100.81 should be my backup server.

Then it still shows 192.168.100.88 and 192.168.100.89 as "AD authorized MS DHCP servers", and I'm not sure why, as those are decommissioned and not in production anymore, they are disposed of.  How do I deauthorize them from my domain, as I don't physically have those servers anymore.  Can they be causing this problem?
dhcprogue.jpg
0
 
Krzysztof PytkoSenior Active Directory EngineerCommented:
Probably not if they have no valid scopes. However, you can clean this up using Active Directory Sites and Services console. But this is sensitive action and you can break something by wrong action. I have no access to test environment to provide you complete guide at this moment, sorry

If you could wait until morning (it's late here, I will check that and prepare guide for you)

Krzysztof
0
 
DanNetwork EngineerAuthor Commented:
sure, I won't do anything now anyways, so I will wait until Monday morning.
0
 
Krzysztof PytkoSenior Active Directory EngineerCommented:
OK, so to remove DHCP servers which are no longer authorized but still appears on the list, you need to follow below steps:

1) Open Active Directory Sites and Services console
2) Select root node in the console "Active Directory Sites and Services"
3) In "View" menu select "Show Services Node"
4) Now, you should see new node in the console. Expand "Services" node
5) Select "NetServices" node and go to the right pane
6) Search for DHCP server names and/or their IP addresses (if they are present)
7) You can select them with control key but I would suggest to remove them one by one (just in case :) )
8) Click right mouse button on an entry to remove and choose "Delete"
9) Click "Yes" to confirm

after these steps. "ghost" DHCP should disappear. And you can set up simply conflict detection and rebuild DHCP database

Krzysztof
0
 
DanNetwork EngineerAuthor Commented:
Thanks, I deleted them, but there's an entry for DhcpRoot.  There's no IP address for it, so not sure what that's for, I'm assuming I don't want to delete that, right?

Also, I'm getting ready to add a new DC, DHCP server, etc... what are the proper steps to add a new DC server, with DHCP, DNS, etc.., Then I will want to decommission my current DC, dhcp, dns, but I will still need to use the server in production, just not for DHCP and DNS.  What do you recomend?

Back to my original post, any idea's what's causing that problem, could it be that my DHCP server is corrupt? If it is, is it not wise to export and import the configuration to my new server?
0
 
DanNetwork EngineerAuthor Commented:
Now I have a bigger problem, as of 10 minutes ago, I have devices that are not getting an ip address from my server.  They get a random 169.254.228.x Ip address.  I have plenty IP addres in my DHCP server, as I saw that theres about 50% free.

Not sure what to do?  How do I fix this?
0
 
DanNetwork EngineerAuthor Commented:
Nevermind my last post, the server was not handing out IPs because it was not authorized.
I have no idea how it got dauthorized.
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.

Join & Write a Comment

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now