Windows Forum

Ask something
Discussion Locked

Server 2003 hangs - Terminal Licensing

0 helpful
3 replies

by mark_lt

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have added a 2003 server into my NT4 doamin, a temp PDC was used to be upgraded to 2003 AD, apart from some small issues, the 1st biggy was that my 2000 terminal server now refused to run the Terminal License server as there was the AD 2003 present. I installed the terminal license server, activated it, and after reboot, the server now takes over 45 mins to log in, and will not now shut down. This has happened two times now with a clean install each time.

3 replies

by shmaltz

In my experience the reason for long logons has to do with DNS.
In the networking tab make sure that at least one DNS server is correctly configured, and that this DNS server is a DNS server for you AD Domain.
If Windows doesn't have a network connection for whatever reason (unplugged cable, NIC that is not properley installed, etc.) then windows will take very long to start. Login in safe mode and make sure DNS is configured correctly.
Any Event IDs?
You don't mention which Server takes long to reboot, the TS or the Win2k3 AD DC?

by mark_lt

Well, it was DNS, in a manner, we had installed the MS PRoxy Client on the server, and this made the AD search via our external DNS rather than its on as config in network settings.

This discussion is closed to new replies.