P
PJinCanada
I am having the same problem as a couple of other posters. Seems that on the
weekend 3 of my customers who have Win2K Terminal Servers can only have one
person logged in at a time.
I've focused on one of these customers to try to solve the problem. Here's
what I've seen so far:
1. Trying to RDP into the box from a remote site or the LAN, could not
connect.
2. Had user reset the listener from the console.
3. After reset, I could connect remotely, but nobody else could either
remotely or on the LAN.
4. During connection attempts, no event is generated in the logs.
5. During connection attempts, the computer connection icon in the Terminal
Services Manager appears with no description, then disappears after some
time-out.
6. During connection attempts from a remote site (NAT through a router),
the remote user receives (from a Vista PC), the following: " This computer
can't connect to the remote computer. Try connecting again. If the problem
continues, contact the owner of the remote computer or your network
administrator"
7. During connection attempts from the LAN, the user recieves (from a WinXP
PC)"Remote desktop disconnected. The client could not establish a connection
to the remote computer. The most likely causes for this error are: 1.
Remote connections might not be enabled at the remote computer. 2. The
maximum number of connections was exceeded at the remote computer. 3. A
network error occured while establishing the connection."
I restarted the server and found an error 17 in the event log describing a
corrupted Licensing file.
Per MS support article, I removed Terminal Server Licensing, rebooted,
re-installed TS Licensing, re-activated the License server and re-installed
the licenses.
Still having the problem.
Help!!!!
Paul
weekend 3 of my customers who have Win2K Terminal Servers can only have one
person logged in at a time.
I've focused on one of these customers to try to solve the problem. Here's
what I've seen so far:
1. Trying to RDP into the box from a remote site or the LAN, could not
connect.
2. Had user reset the listener from the console.
3. After reset, I could connect remotely, but nobody else could either
remotely or on the LAN.
4. During connection attempts, no event is generated in the logs.
5. During connection attempts, the computer connection icon in the Terminal
Services Manager appears with no description, then disappears after some
time-out.
6. During connection attempts from a remote site (NAT through a router),
the remote user receives (from a Vista PC), the following: " This computer
can't connect to the remote computer. Try connecting again. If the problem
continues, contact the owner of the remote computer or your network
administrator"
7. During connection attempts from the LAN, the user recieves (from a WinXP
PC)"Remote desktop disconnected. The client could not establish a connection
to the remote computer. The most likely causes for this error are: 1.
Remote connections might not be enabled at the remote computer. 2. The
maximum number of connections was exceeded at the remote computer. 3. A
network error occured while establishing the connection."
I restarted the server and found an error 17 in the event log describing a
corrupted Licensing file.
Per MS support article, I removed Terminal Server Licensing, rebooted,
re-installed TS Licensing, re-activated the License server and re-installed
the licenses.
Still having the problem.
Help!!!!
Paul