?
Solved

Remote Desktop disconnecting after 30 minutes

Posted on 2008-10-23
9
Medium Priority
?
4,888 Views
Last Modified: 2013-11-21
I'm having problems with my Remote Desktop - it is disconnecting users after 30 minutes or so.  I don't have the exact message, but it was not specific.

Our primary server hosts the Remote Web Workplace under Windows Small Business Server 2003.  User can log in there and connect to the company's application server.  

The application server is running Windows Terminal Services (Windows Server 2003) and hosts several applications.

This has worked well in the past, but recently my remote users have been complaining that they are getting disconnect.  This seems to happen after about 30 minutes of use.

I've checked the setting on the Terminal Services Configuration and it is not set to automatically disconnect users (set to "Never").

Any ideas on the solution or at least how to troubleshoot?
0
Comment
Question by:ReeseWatt
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
9 Comments
 
LVL 1

Expert Comment

by:vodka7
ID: 22787237
Go into the GPO editor (gpedit.msc) and goto Computer Config, Admin Templates, Windows Components, Term Services, and check settings for Keep-Alive Connections, Auto reconnection and the settings in the Sessions folder.
0
 
LVL 18

Expert Comment

by:sk_raja_raja
ID: 22787248
1.On the server
Go to Start
Administrative tools
Terminal Services Configuration
In the RH pane select connections
Right click on the defult RDP, properties
Select the session tab
Set the idle session limit to what you require.
The server will leave the session open up to this set limit

2.Do you have GPO for this ?
0
 
LVL 77

Expert Comment

by:Rob Williams
ID: 22787559
The remote desktop session is controlled by numerous session limits, such as time limits for disconnected sessions, active sessions, idle sessions, and action upon reaching the time limit. All of these can be set in 6 locations. You should likely check all to see if one or more is affecting the host/domain PC's. Numbers 1 and 5 are the most likely location for any set limits.
1)      Domain group policy Computer configuration | Administrative templates | Windows components | Terminal Services | Sessions |....
2)      Domain group policy User configuration | Administrative templates | Windows components | Terminal Services | Sessions |....
3)      Local computer policy Computer configuration | Administrative templates | Windows components | Terminal Services | Sessions |....
4)      Local computer policy User configuration | Administrative templates | Windows components | Terminal Services | Sessions |....
5)      Users profile in Active Directory. See: Active Directory Users and Computers | User profile | Sessions
6)      If a terminal server, see also: on the terminal server, Terminal Services Configuration console | Connections | right click on RDP-Tcp in the right hand window and choose properties | Sessions |&.
0
Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

 

Author Comment

by:ReeseWatt
ID: 22787620
vodka7,
None of the GPO's were configured for Terminal Services.

ski_raja_raja,
Terminal Services configuration is okay - the sessions are not automatcially disconnected.

Couple additional bits of info:
It was working well (with a few glitches) for a year or so.  Also, after the users are disconnected, they often have trouble re-connecting again.
0
 

Author Comment

by:ReeseWatt
ID: 22787783
RobWill,
All of GPO objects are set to "not configured".  Also, the Terminal Services Configuration is set to override the user settings and is set to "Never" disconnect.

I doubt it's disconnecting at exactly 30 minutes.  For the most part, users just say, "Hey, I got disconnected."  Just one user said it had been about 30 minutes.

But the other problem is that they can't reconnect right away.  They wait awhile and then are able to connect.

I'm having that problem right now.  When I remote to a PC in another town, and then use IE to connect back to our web, this is what happens:
1) I can log in and connect to Remote Web Workplace
2) I get the menu and choose "Connect to your Company's Application Sharing Server"
3) Nothing happens, until I get this message:
VBScript: Remote Desktop Disconnected
"The client could not connect to the remote computer.  Remote connections might not be enabled or the remote computer might be too busy to accept new connections..."

There are no connections currently enabled, so it's not too busy.  

In summary, it seems to be connection problem between our primary server, which hosts the Remote Web Workplace, and the Application Server, which is hosting Terminal Services.



0
 
LVL 77

Expert Comment

by:Rob Williams
ID: 22787831
Can you connect successfully using RWW to the SBS or another PC?
If so verify in DNS that the Host record is correct and not duplicated for the terminal server.
Also make sure in the TS network adapter configuration it points only to the SBS for DNS, and the ISP's DNS is not present even as an alternative.

What do you have for an Internet connection? Might it be PPPoE?
0
 

Author Comment

by:ReeseWatt
ID: 22788253
RobWill,
No, I can't connect to other PC's using RWW.

So, that makes me think I've been focusing on the wrong server.  Maybe the problem is with the server that is hosting the RWW and not with the server hosting the TS.

Our internet connection is a T1 line via Nuvox.
0
 

Author Comment

by:ReeseWatt
ID: 22788687
More info on this problem.  This works:

1) I sit down at the primary server (running SBS)
2) Open Internet Explorer
3) Goto the Remote Web Workplace website using the internal address
4) Connect to other PC's and the application server.

But when I try to do the same thing from an external website, I can't complete step 4
0
 

Accepted Solution

by:
ReeseWatt earned 0 total points
ID: 22790107
Well, it's working now.  I think the problem was with my firewall. Essentially, I just rebooted it and the remote desktop started working again.
0

Featured Post

Office 365 Training for Admins - 7 Day Trial

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

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

I’m often asked about newer and larger USB drives connected to SBS2008 and 2011 failing Windows Server Backup vs the older USB drives not failing. As disk space continues to grow and drive technology change SBS2008 and some SBS2011 end up with the f…
Issue: One Windows 2008 R2 64bit server on the network unable to connect to a buffalo Device (Linkstation) with firmware version 1.56. There are a total of four servers on the network this being one of them. Troubleshooting Steps: Connect via h…
Two types of users will appreciate AOMEI Backupper Pro: 1 - Those with PCIe drives (and haven't found cloning software that works on them). 2 - Those who want a fast clone of their boot drive (no re-boots needed) and it can clone your drive wh…
In this video, Percona Solution Engineer Rick Golba discuss how (and why) you implement high availability in a database environment. To discuss how Percona Consulting can help with your design and architecture needs for your database and infrastr…

762 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