Terminal Server and roaming profile question, in the Terminal Services forum on BrianMadden.com

Good day to you all.

The company I work for has a Windows 2003 Terminal Server environment with 11 Dell 1955 Blade servers. In the past I've successfully been able to restore and rebuild the systems without any difficulty but today I've come across a small problem that I was hoping the members here might be able to help with at this time.

After rebuilding a server to train someone else on how this is done, I now find that the terminal server refuses to load roaming profiles. A search of Event Viewer after a reboot showed this ominous message (along with others but I'm trying to tackle them one at a time):

This computer was not able to set up a secure session with a domain controller in domain MGA due to the following:
---
EventID 5719:

This computer was not able to setup a secure session with the domain controller.

There are currently no logon servers available to service the logon request.
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.

ADDITIONAL INFO
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
---


I find this difficult to believe though because (a) I did rejoin the server to the domain and (b) I see the server listed in Active directory users and computers.

If any help or guidance could be provided I'd appreciate it.

are you restoring/rebuilding it using a image? did you try set it to workgroup then reboot then make it member of the domain again. also check if the systemtime is alright.