Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

TS client not working

Posted on 2009-04-01
3
Medium Priority
?
757 Views
Last Modified: 2013-12-05
Hi,

Need help with this one, since im not experienced on terminal services much. Just recently came across an odd issue. We have a Windows 2003 domain with all DCS 2003, but still some existing 2000 member servers. One of these servers is an application server having terminal services installed on it. Our terminal services licensing server is one of the DCs and seems to be working fine. Since 3 days, few of the application users cannot connect to the application server getting the error that 'terminal services has ended the connection' when they use termincal services client from their windows 2000/XP workstations. The funny thing is that it works when i give them admin privileges.

Any clues? I have to add that the only major change that happened before three was that we rebuilt our Certificate Authority server. It was on one of the DCs and we uninstalled and reinstalled again there.

So where do i start? Check the application server? Check the terminal services licensing server? Check certificate authority server?

Thanks in advance for the help.
0
Comment
Question by:dxbit
  • 2
3 Comments
 
LVL 4

Expert Comment

by:NDSSI
ID: 24037501
Have you checked that users are member of Remote Desktop Users localy on the 2000 server.

/AJ
0
 

Author Comment

by:dxbit
ID: 24128504
Sorry for the late reply. Surprisingly for those users, its working now and just this week it stopped working for another batch of users.
Yes, those users have permissions on the terminal services security tab. The funny thing is, my username even as administrator cannot connect to those application servers from those particular user's workstations terminal services client. Terminal services client works for other servers that are installed in remote administration mode, but not for those two servers which are installed in application mode.
I did a packet capture and am attaching a snapshot of that to this post. It seems the server (192.168.128.57) is sending a RST connection to the client (10.1.203.51).
Another weird thing is that when i did a packet capture on the server and did a filter for that client IP, i did not find any packets from it or to it.
Help!!!

tserror.JPG
0
 

Accepted Solution

by:
dxbit earned 0 total points
ID: 24857695
I found somewhere on the internet that you have to make sure that the terminal server is defined in the active directory sites and services on your domain as well as the certificate server is defined on the application server and if not to edit the registry and put it there manually. It worked when i did these steps.
0

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Problem Description: Actually I found the below issue with some customers after migration from SMS 2003 to SCCM 2007 and epically if they change site code, some clients may appear in the console with old site code, plus old sites still appearing …
The question has been asked on multiple occasions as to how best to do printing in a remote desktop or terminal services environment.   It seems that this particular question has plagued several people and most especially as Terminal Services, as…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an anti-spam), the admin…
Loops Section Overview

927 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question