Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
I have a Windows 2000 Domain controller and a Windows 2000 Member server acting as a Terminal server. The W2K Domain controller is a Terminal services license server. Remote users login to the Terminal server using TS Cleint with their domain account over the internet (Frac T-1). There are more than enough liceses installed for Terminal services clients. If the client is idle for more than 5 mins it times out and an error message appears "the terminal server has ended the connection". I checked all the settings for the terminal server session timeout etc. There are no errors in the event logs either. This used to work before SP3 and other updates were installed . I did not archive the previous Service pack. How do I go back to Service pack2 ? and also any other suggesstions to keep the clients sessions alive ? I tried all workaround and still no luck with this. The hardware we use has no issues its all name brands Cisco, Compaq etc. The internet connection is stable too.
Any help will be greatly appreciated.

Well, if you didn't archive SP2, then you can't go back. First thing I'd try is use the Windows XP Remote Desktop client (basically XPs Terminal Services client), which you can download from Microsoft.
And I'm assuming you checked the client sessiong timeouts on the terminal server as well as any sort of group policies that may be flowing down and affecting your users.What happens if you remotely connect to the TS server from within the building? Does it time out then? Or only coming through your outside line?

Yes all the settings are fine. we have a Windows 2000 machine with TS Client inside the Network which does'nt time out . Only the connections coming through the internet timeout say after 3-4 mins of idle time and get that error message. we have also tested the T-1's and the Routers and they are properly configured. It used to work before with SP2. These problems started recently .
I also tried using XP RDP client and still have the same problem. There are no group policies setup. If the machine is not idle we dont get disconnected from the Terminal server. The idle time is set to never .
Thanks for your response. Any other Ideas ?

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |