Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 401
  • Last Modified:

Moved logonserver, lost domain

I removed my backup server (server02) from the subnet it was serving to repair a bad disk. The workstations on that subnet show logonserver=server02 , and the only available server is server01 on a different subnet. How do I get the workstations to find the main server in the interim? When logging on , they now complain the the domain is not found. Server01 is found in dns, and the alternate dns server is specified as server01. Before I installed this backup server, all machines on the subnet used the main server by default.
0
HilltownHealthCenter
Asked:
HilltownHealthCenter
  • 4
  • 2
  • 2
  • +1
2 Solutions
 
dphantomCommented:
Your workstations need to be on the same subnet as the DC or have a route defined to that DC.  Yours, evidently does not.  That is why when you removed the DC, those users could no longer find the domain.  Fix that and you should be fine.  Do you have multiple sites set up in AD Sites and Services?
0
 
Darius GhassemCommented:
You should have the clients pointing to the Server01 for primary DNS. If the second DC wasn't demoted correctly then AD will still read that a DC is still within the subnet. Second go in DNS delete any records for the DC that is down.
0
 
HilltownHealthCenterAuthor Commented:
I moved the backup server into the default site and deleted the alternate site. It still can't find the domain on login.
0
Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

 
HilltownHealthCenterAuthor Commented:
I also changed both subnet properties to use the same site (default-first-site).
sites.jpg
0
 
dphantomCommented:
How exactly did you remove server02 and how did you put it back.  You said a bad disk.  Does this mean you had to reinstall the OS, or just shut down the server to replace a hard drive in a mirror or raid 5?
0
 
javiersantanaCommented:
Change the srv records in DNS so the new dc has the lower priority.
0
 
HilltownHealthCenterAuthor Commented:
I found the problem. Somehow, dns on the workstation I was trying to log into was pointing wrong.
0
 
Darius GhassemCommented:
That is why I said to make sure you DNS was pointing to Server01 it is a common mistake or look over.
0
 
HilltownHealthCenterAuthor Commented:
I changed the remote subnet dhcp params to point to the server01 for dns.
I rebuilt the server02 RAID (data drive, not the boot partition) and moved it into the primary (server01) server room, and changed its ip to a local ip, so that I can restore the data in the high-speed local environment from the primary DC (remote subnet is over T1).

But I would like to know exactly what the proper steps to pulling the server out of the remote subnet to run temporarily on the master subnet should have been, to avoid the problems I had (or any other problems)?

Is there any problem having both servers running temporarily in the local (master) subnet?
0
 
javiersantanaCommented:
as long as both subnets have static routes pointing to each other, there isn't any more configuration that needs to be done. Once you first setup the domains, the srv records in DNS prioritize the domain controllers. As long as the client machines can access a DNS server for that domain everything should go smoothly.

make sure to always have a primary and secondary dns server on your network and assign those server ip address to the client machines on your network.

Also to answer your question. The only problem i could see is that you might have unnecessary broadcast traffic on that subnet.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 4
  • 2
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now