Terminal Services rejecting sessions on a server

Terminal Services rejecting sessions on a server

Terminal Services recently began rejecting Terminal Services sessions on one of our servers. We have a very small IT dept. (3 admins) and none of us made any changes on that server. We have uninstalled and reinstalled several times but to no avail. It continues to reject our sessions. The server is able to be administered through vnc. In Terminal Server Manager, it says that the RDP TCP connection on port (65539) is down. If you reset it, it is still down but the port increments by one. I've been working on this for over a week. Any suggestions would be greatly appreciated.

    Requires Free Membership to View

    When you register, you’ll also receive targeted alerts from my team of editorial writers and independent industry experts with the latest news, tips, and advice to help you do your job more efficiently and effectively. Our goal is to keep you informed on the hottest topics and biggest challenges faced by IT professionals today working with desktop virtualization technology.

    Margie Semilof, Editorial Director

    By submitting your registration information to SearchVirtualDesktop.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchVirtualDesktop.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

Just for future reference, it's helpful to include the error message--Terminal Services has many error messages and they all mean something different. One possibility is that you're using DHCP for the terminal server and the server lost its lease. See if you can connect directly using the server's IP address instead of its name.

This was first published in January 2004