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

Login to server without domain controller available

Here is my question..

The person that use to run these servers at this company had a test VM network setup that was on a different subnet from the production servers. This allowed a software company to make database and programming changes without affecting the production servers.

I need to clone one of the production servers for the test environment. This server that I am cloning had been cloned before for the test environment, so I am basically just getting rid of that one and putting in a newer version in the test environment. The clone and everything goes well, but after the server is cloned and put on the test network, I cannot login to the domain account due to the domain controller being unavailable.

I could login to the older server that was on the test network no problem, but for some reason I can't on the newer one I just put in. I've copied the same IP settings and everything but have hit a bit of a wall on this.

I know I can logon locally to the server, but I would rather have the same logins as the previous server.

Is there somethign I am missing here?

The user accounts that I am trying to login to on this server had already been logged into while it was on the domain, so I figured I would be able to login once it was moved to the test environment, but I can't.

Any ideas?
2 Solutions
Is your DNS configuration working correctly? If you run a nslookup test the correct DNS server must resolve the domain name and IP address if you query it
Sikhumbuzo NtsadaSenior IT TechnicianCommented:
If that server is not a domain controler, then go ahead and log in locally, once logged on re-add it to the domain if there is, if not then add it to some workgroup.
Is the server now on a different subnet?
Can you ping the DC's IP address?
Perhaps the default gateway is different?
themightydudeAuthor Commented:
Sorry for the late reply..I once again was a bit of an idiot.

Didn't think to check the DC server that was put on the test network..just had to reboot that server and all is well.

Thanks guys.
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