Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

Our DC was having issues so we built a new server to replace it. It's running 2003 (same as previous DC). I ran DCpromo and transferred roles to the new DC. Now Users are having issues connecting to the internet (169.254). Also I did not set up DHCP. This backup DC will be replaced within the next few weeks. Any help is appreciated.

share|improve this question
1  
1. What issues was the old DC having? 2. Is the old DC still on the network/domain? 3. Did the old DC run DHCP? You say 169.254 - I take it you mean the clients aren't getting a DHCP address? –  Dan Apr 18 '12 at 14:29
    
Why did you not install DHCP? –  tombull89 Apr 18 '12 at 14:30
    
I wanted to install DHCP but was told not to by my boss. He said that it shouldn't be an issue, which I believe it is. The reason we are getting rid of the old one is because it was freezing consistently. The old DC is still connected and it did run DHCP –  Mike Apr 18 '12 at 14:33
    
Thanks for the quick response! –  Mike Apr 18 '12 at 14:34
2  
@Mike To be clear, is the old DC still running DHCP? Either way, yes, DHCP is the root cause of your issue but you need to ensure you don't end up with two DHCP servers on the same network. Either fix whatever s wrong with your old DHCP server, or remove the role and recreate it all on the new server. –  Dan Apr 18 '12 at 14:37

4 Answers 4

You did not install DHCP, and the client's are getting a default ARPA IP because you don't have DHCP running.

Install DHCP.

share|improve this answer

You need to enable DHCP on your new server and ensure your old one is no longer a DHCP server.

share|improve this answer

I'm going to say installing DHCP would be a good step - this is why your clients are getting this type of IP address.

share|improve this answer
    
Because I can not answer: –  Mike Apr 18 '12 at 14:59

Yeah, you need DHCP, it's what provides your clients with an IP-address. Also, make sure you put your new DC server as prim DNS.

share|improve this answer
    
So The issue was the DHCP server was saying that it wasn't Authorized on the older server. I went to Authorize the service it said that it was already authorized. I restarted the service and DHCP came back up. Had clients do a Ipconfig release/renew. Thanks for all your help and quick responses. –  Mike Apr 18 '12 at 15:00

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.