• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 234
  • Last Modified:

Terminal services problem

I have two of my domain controllers which will not allow me to connect via the terminal services client. I get a message saying "The terminal server has ended the connection" via Windows and a "Connection reset by peer" message via RDP on Linux.

All DC's are in Remote Administration mode. Browsing the system logs I see an Event ID generated from TermServices that states: "Attempt to send a message to a disconnected communication port." Event ID 55. I can connect to both servers via Terminal Services Manager and they don't show and open sessions. I've reset the sessions anyway. I've ran a port scan against both machines and they show 3389 as open and listening, the service is also running.

Thanks!
0
mbeaven
Asked:
mbeaven
  • 5
  • 4
  • 3
1 Solution
 
map000Commented:
try a newer version of rdp on that Linux system
by the way, 2k or 2k3 servers?
0
 
map000Commented:
sorry, I realized it's the 2k forum :(
0
 
mbeavenAuthor Commented:
Windows 2000 servers. RDP is version 5.
0
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

 
map000Commented:
i'm not very familiar with the latests versions; but I've did it many times in the past (connecting from linux systems on TS)
0
 
KaliKoderCommented:
Hello mbeaven,

Can you double check if the DCs are running in remote administration mode ? If they are, then the account you are trying to connect using, is this a Administrator account ? Remote Administration mode would only allow two sessions, and they need to be coming from administrative accounts. Please check that you are not already maxed out on the two connections, if you are then you need to go to Terminal Services Manager and close those two sessions, and then try a  new one. You can also use the command line to close those sessions, please see article below:

How to reset the Windows 2000 Terminal Server Client Session:
http://www.jsiinc.com/SUBK/tip5200/rh5209.htm

If for some reason you are not running in the remote administration mode, then if 90 days have elapsed, you would not be connect.
http://www.winnetmag.com/Article/ArticleID/19784/19784.html

Please check the following: "Event ID 52 When You Start Terminal Services"
http://support.microsoft.com/default.aspx?scid=kb;en-us;258021&sd=tech

Also make sure you are running the latest version of RDP software to connect to your terminal server, some RDP sessions require that you use this, because it provides encryption over the wholse session, which the older versions did not. The latest client for this is available from:
http://www.microsoft.com/windowsxp/downloads/tools/rdclientdl.mspx

Thanks and Good Luck!




0
 
mbeavenAuthor Commented:
Thanks for the reply KaliKoder, I do know for a fact they are running in remote administration mode. Also I'm connecting with an Administrator account. As I remarked earlier there are no visable sessions either in terminal services manager or via the command line.

I don't believe the Event ID 52 applies to remote administration mode and at any rate I've restarted the services previously and can clearly see the termsrv process running in process viewer. I'm using the latest version of RDP in Windows XP. I've also tried from other clients and servers and no luck. It is only affecting these 2 servers. I can and have been accessing all the other 2000 servers. Thanks!
0
 
KaliKoderCommented:
Thanks for providing those answers mbeaven. Event ID 55 in most cases is a File System error. Can you perform a chkdsk /f on your two DCs if possible, this would unfortunately need a reboot, hopefully you have other DCs in place and this one can be brought down for about 5-10 mins. Chkdsk /f is worth it...

Event ID: 55
Source: NTFS
Description: The file system structure on disk is corrupt and unusable.
Please run the chkdsk utility on the volume "Drive_letter:"

thanks
0
 
mbeavenAuthor Commented:
KaliKoder, I've checked the event id on the Microsoft site and you are correct if the source is NTFS but the source is TermServices and the description states: Attempt to send a message to a disconnected communication port. Thanks.
0
 
KaliKoderCommented:
mbeaven.. have you tried uninstalling and reinstalling terminal services ? I know its a far thing to try, but might work out. If downtime is not a big issue, I would still try those two things, 1. chkdsk and 2. reinstall of term services
0
 
KaliKoderCommented:
Another thing would be to redo SP4 as well.
0
 
mbeavenAuthor Commented:
Unfortunately downtime is an issue for these 2 servers, they're in field offices where the users access them at all hours. I will see what I can work out with the holiday approaching.
0
 
KaliKoderCommented:
Reinstalling the Terminal Services would have solved this problem, according to Microsoft, especially if there were no Network related issues. Application of SP4 would have also helped for sure.
0

Featured Post

Prep for the ITIL® Foundation Certification Exam

December’s Course of the Month is now available! Enroll to learn ITIL® Foundation best practices for delivering IT services effectively and efficiently.

  • 5
  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now