R
Rik
Our old Windows Server 2003 terminal server is at end of life. It was also
our Terminal Server License server.
We installed a new Windows Server 2003 terminal server, and configured a new
Terminal Server License server on this new system. Activating the Terminal
Server Licensing server and the TS CAL's worked fine. We also deactivated
the old terminal server license server.
When the old server is down and we startup Terminal Server Licensing on the
new server, the new server is still looking for the old server (Finding
servers... is taking about half a minute).
When a client computer tries to connect to the new server, the same timeout
occurs before the user can logon to the new terminal server. Once connected,
everything goes fine.
Both problems doesn't occur when the old server is running.
What to do so the new server doesn't search for the old one anymore?
Greetings,
Rik
our Terminal Server License server.
We installed a new Windows Server 2003 terminal server, and configured a new
Terminal Server License server on this new system. Activating the Terminal
Server Licensing server and the TS CAL's worked fine. We also deactivated
the old terminal server license server.
When the old server is down and we startup Terminal Server Licensing on the
new server, the new server is still looking for the old server (Finding
servers... is taking about half a minute).
When a client computer tries to connect to the new server, the same timeout
occurs before the user can logon to the new terminal server. Once connected,
everything goes fine.
Both problems doesn't occur when the old server is running.
What to do so the new server doesn't search for the old one anymore?
Greetings,
Rik