Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Shutting down secondary DC/DNS server causing name resolution issues


  • Please log in to reply
4 replies to this topic

#1 Wasisnt

Wasisnt

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:01:55 AM

Posted 14 October 2010 - 11:14 AM

We have a 2003 Server domain and I added a 2008 DC and did all the forest/domain prep etc beforehand. The 2008 DC has all the FSMO roles as well and is running DHCP.

The 2008 DC uses .68 and the 2003 DC uses .34. The DNS server addresses setup in DHCP to hand out are .68 first and .34 second. They are the only 2 DCs running.

If I shut down the 2003 DC then many but not all people cant access the file server by name until I turn it back on. It says something like there are no login servers available.

For the people who can access the file server I check their IP settings and .68 is their primary DNS server.

Any ideas?

BC AdBot (Login to Remove)

 


#2 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:08:55 AM

Posted 14 October 2010 - 01:27 PM

Check the settings on the boxes, and have them do ipconfig /flushdns via command prompt via start then run cmd. or have them restart their computers.

#3 Wasisnt

Wasisnt
  • Topic Starter

  • Members
  • 7 posts
  • OFFLINE
  •  
  • Local time:01:55 AM

Posted 14 October 2010 - 02:06 PM

I'm thinking its something to do with letting it take its time so all the clients can catch up. I'm going to shut the DC down on Friday at 5 and see if there are issues Monday morning. I get in at 6 so I can test stuff out before everyone gets here. Its hard to do it during business hours since it affects so many people and my phone starts ringing off the hook. The main goal is to get rid of this DC for good and add another 2008 DC once I know everything will work without it.

#4 techextreme

techextreme

    Bleepin Tech


  • Members
  • 2,125 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Pittsburgh, PA
  • Local time:04:55 AM

Posted 02 December 2010 - 01:27 PM

Did you move the DHCP server from your 2003 box to your 2008 box?

If you did, did you shutdown the DHCP Server on the 2003 box?

If you shutdown the DHCP server on your 2003 box and you're still receiving the "No Login Server is available" message on your desktops, you may also want to try:
  • Click Start then Run
  • Type "cmd" ( minus the quotes )
  • In the command prompt window, type ipconfig /release and press enter
  • Next type ipconfig /renew and press enter

This will force the desktops to renew their IP addresses from your 2008 DHCP server and allow your desktops to login.

I would also recommend removing the DNS server entry from the DHCP Scope options for your 2003 Server.

Hope this helps,
Techextreme

"Admire those who attempt great things, even though they fail."

-- Seneca

#5 chromebuster

chromebuster

  • Members
  • 899 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:the crazy city of Boston, In the North East reaches of New England
  • Local time:04:55 AM

Posted 12 December 2010 - 09:45 PM

Sounds good to me. If I were you, I'd get rid of the older domain controller as quickly as possible. and just curious, but how big is your network? I ask since I have a contact from England who says that if you don't need two machines doing the same thing, don't use two since the more machines you have, the more issues you'll be prone to plus the more monitoring you need to do. So you should ask yourself, do I really need that second domain controller? If the answer is no, sell it to someone who can use it for geeky stuff or something LOL. Good luck.

Chromebuster

The AccessCop Network is just me and my crew. 

Some call me The Queen of Cambridge





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users