[x]
Posted via EE Mobile

Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

Question
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

6.4

Users in remote offices cannot connect to Terminal Server sporadically

Asked by sherryfitzgroup in Remote Desktop/Terminal Services, Windows 2003 Server

Tags: Microsoft, Terminal Server, Server 2003

Hi,

We have two 2003 Terminal Servers. Different users are directed to a different TS. Every few days, users in remote offices cannot connect to their Terminal server. It times out with the message ' The remote connection has times out.' The user can ping the server ok, but when they try to RDP in they get this message. I point them to the other server, which works fine.
Users based in the head office never have any problems connecting to either server. The remote offices are connected to our WAN.

I have ruled out:
-the TS profile, as it logs on ok to the other Terminal Server
-the RDP client, as it logs on ok to the other server
-network problem, as I can ping the server no problem
-MTU settings on the office router, as it logs on ok to the other server
-Firewall on the server, as it's disabled

Anyone got any ideas on this? Help is greatly appreciated.
 
Related Solutions
Keywords: Users in remote offices cannot connec…
 
Loading Advertisement...
 
[+][-]06/20/08 12:34 PM, ID: 21834223Accepted Solution

View this solution now by starting your 30-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

About this solution

Zones: Remote Desktop/Terminal Services, Windows 2003 Server
Tags: Microsoft, Terminal Server, Server 2003
Sign Up Now!
Solution Provided By: sherryfitzgroup
Participating Experts: 0
Solution Grade: A
 
 
Loading Advertisement...
20091021-EE-VQP-81 / EE_QW_2_20070628