G
Guest
I am on an NT 4 domain with 3 W2K and 1 W2K3 Terminal Servers (We will be
upgrading to AD shortly). Our license server is W2K3 server. Each terminal
server has the termservice/parameters registry key pointing directly to the
W2K3 license server. Most of our users communicate to these servers through
RDP sessions across a private WAN.
This has happened twice already and I have no idea as to why: Users in
remote subnets are unable to connect to 1 or more of the Terminal servers.
The logon screen does not even appear. They generally get a ‘connection
timeout error’. Users who have already connected earlier in the day remain
logged on and do not experience any issues. I can, however, successfully log
on from any client on the local subnet.
There are no event log errors on the client machine, terminal server, or
license server. We have plenty of available TS Licenses. The only way I have
been able to resolve this issue is a complete uninstall/reinstall of Terminal
Services on the problem servers.
Any ideas?
Thanks
upgrading to AD shortly). Our license server is W2K3 server. Each terminal
server has the termservice/parameters registry key pointing directly to the
W2K3 license server. Most of our users communicate to these servers through
RDP sessions across a private WAN.
This has happened twice already and I have no idea as to why: Users in
remote subnets are unable to connect to 1 or more of the Terminal servers.
The logon screen does not even appear. They generally get a ‘connection
timeout error’. Users who have already connected earlier in the day remain
logged on and do not experience any issues. I can, however, successfully log
on from any client on the local subnet.
There are no event log errors on the client machine, terminal server, or
license server. We have plenty of available TS Licenses. The only way I have
been able to resolve this issue is a complete uninstall/reinstall of Terminal
Services on the problem servers.
Any ideas?
Thanks