Domain Link to remote Server

[hungrybeaver]

Hoping someone here can give me a hand quickly while I continue to work at it. Scenario:

A server 2003 box at a remote branch, on our HQ domain.
I am able to ping it with IP and hostname.
I am able to browse to it.
I am able to RDP into it.

The server has been in operation for 2 weeks. For some unknown reason I am unable to log into the server as a domain user. I can only log into the server as a local user. This was working with domain accounts previously!! Now when I log in as a domain user I get the error:

http://i.imgur.com/KRJ7m.png


Any help is appreciated!

[Demon7]

Do they have a domain controller at that site, and is is up? Can you log into any other machines with domain credentials?(pref. one that has not cached the credentials.)
check that the server is joined to the domain. If not, that's your problem :)
The account that you are attempting to log in with, does it have admin rights or RDP permissions?

Seen the message now...
could be a number of things...
1st. Check the time of the server and confirm that it is right (and date)
2nd. Make sure no ip conflicts.

[hungrybeaver]

Managed to find a workaround here: http://social.technet.microsoft.com/Forums/en-us/winserverTS/thread/40b18122-4071-49db-a553-93c1d0935f4b and can now login. However the server is still unable to contact the domain.

Any ideas?

[hungrybeaver]

Do they have a domain controller at that site, and is is up? Can you log into any other machines with domain credentials?(pref. one that has not cached the credentials.)
check that the server is joined to the domain. If not, that's your problem :)
The account that you are attempting to log in with, does it have admin rights or RDP permissions?

The strange thing is that it was working a few days ago perfectly. Now the server cannot see the Domain controller. I've sorted the login problem, but have found that this server cannot view the Active Directory.

This server is part of the domain yet I am unable to see the domain, but I can log in still :confused:. I think it may need to be restarted.. but the issue still remains.

[Demon7]

Have you checked the time.. cause I had the same issue in the past.. just a time problem.

[Anthro]

Did you possibly replace the machine with a new pc, and kept the same machine name ?
If yes, then remove the PC from AD, then re-add it

[hungrybeaver]

Time, date etc are correct. Its a replacement server but uses a different name. It replaced a server that wasn't on the domain.

I restarted the server and it is now working correctly. It seems like when the connection is lost and comes back, the connection to the DC is not restored. Next step is to now find a way to get the server to re-establish its connection to the DC.

[bubbatentoe]

check event viewer on the member server.
You'll see a ""The trust relationship between this workstation and primary domain failed, blah blah blah"

Remove the suspect from domain via RDP, reboot it. add it to the domain again, reboot it.

I've seen this happen many times when people don't reboot the PC/server after joining the domain. (happens when it's a production system that's "busy")

It seems the initial domain trust relationship is only valid for X hours.
if the system is not restarted after joining the domain then the trust fails and it needs to be removed form the domain and joined again.
tedious.