Solved

Trouble staying connected with terminal services via RWW

Posted on 2013-01-30
14
1,075 Views
Last Modified: 2013-11-21
We have a SBS 2008 service in the office. I work from home and connect to the domain workstations via Remote Web Workplace. I'm having several problems, but I'll see if I can deal with these one-by-one. First, my sessions time out all the time if I am not actually typing on the remote session. The timeout duration seems to vary, sometimes it seems like a minute or so, sometimes it seems to go 20 minutes or more. It does seem to time out quicker if the remote session screen is occluded by a local window.

How can I fix this to NEVER timeout?

I came across advice in this blog http://terminal.servebeer.com/php/flaky_connections.php to create a registry DWORD KeepAliveEnable in HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server, and set it to 1. This blog was not dated and did not specify to which OS versions the advice applied. Digging deeper in the blog and links seemed to discuss WIN2000 and WINNT, old stuff. Nevertheless I tried this, but it didn't do anything. So, I removed the DWORD just in case it would end up doing bad things.

Please help solve. This is driving me crazy!
0
Comment
Question by:jmarkfoley
  • 9
  • 2
14 Comments
 
LVL 78

Expert Comment

by:David Johnson, CD, MVP
Comment Utility
Remote Desktop settings set on the server has the option of disconnecting idle sessions after a set period and closing sessions if they have been disconnected for a set period.. check with your administrator.
0
 
LVL 1

Author Comment

by:jmarkfoley
Comment Utility
I am the administrator. Are you sure this is part of Remote Desktop settings? I thought this had to do with Terminal Services. I'll check the remote desktop settings and see if that helps.
0
 
LVL 1

Author Comment

by:jmarkfoley
Comment Utility
Interestingly, On Server 2008, the 'Remote Settings' >Remote tab has the "Allow Remote Assistance connections to this computer' greyed out, but I can still use RWW to access this computer. On WIN7 workstations, the 'Allow remote assistance ...' is checked, and under 'Advanced', the 'Invitations' timeout is set to 6 hours. So, I don't think this is a Remote access issue per se.


The message I get at the client (remote) end is: "VBScript Remote Desktop Disconnected. / An internal error has occured (error 50331657). For more information, please contact your network administrator or Microft Product Support."

I have not found much helpful on the web about this error.
0
 
LVL 78

Expert Comment

by:David Johnson, CD, MVP
Comment Utility
0
 
LVL 1

Author Comment

by:jmarkfoley
Comment Utility
ve3ofa: Thanks for the feedback. I saw that link in my searches, but I didn't see anything related  to my problem. Issue #2 is for VBScript Error: 50331676 which has to do with not being able to connect at all, which is not my case. My error is 50331657. Am I missing something? Which error did you have in mind for my issue?
0
 
LVL 14

Expert Comment

by:BlueCompute
Comment Utility
Are you ever seeing this notification?
http://blogs.technet.com/b/sbs/archive/2006/07/25/443383.aspx#_Toc41042000

The "remote assistance" settings are completely irrelevant. They relate to a different technology entirely. The "terminal services" registry settings on the server are also not relevant here, unless it's the actual server you're loading the desktop of - if it's the client desktops then it's the TS Proxy and RWW settings that are relevant - have a look here:

http://blogs.technet.com/b/sbs/archive/2009/06/15/how-to-configure-the-rww-timeout.aspx

The default should never be anything like as low as 1 minute though, and you should be warned. If you forward the Remote Desktop port to one of the client computers, and connect without going through the remote web workplace, does the connection still behave in the same way?
0
Shouldn't all users have the same email signature?

You wouldn't let your users design their own business cards, would you? So, why do you let them design their own email signatures? Think of the damage they could be doing to your brand reputation! Choose the easy way to manage set up and add email signatures for all users.

 
LVL 1

Author Comment

by:jmarkfoley
Comment Utility
> Are you ever seeing this notification?

Wow, there are lots of screens on that link that I've never seen. When I connect to RWW I first get this login page:

RWW Login
After logging in, I get this page:

RWW screen.
From the 'Connect to Computer' block (middle, blue) I can expand a list of possible workstations by clicking on "Show List". When I select a computer I then get a login form for that computer:

RWW connect to workstation
None of these screens seems to show options regarding connection speed. I never get that nice timeout warning shown in your link.

I will try using the "How to Configure the RWW Timeout" instructions specified in your 2nd link and get back to you on the results. However, this will have to be tomorrow as it is 1:00 AM here and I don't intend to stay up for the several hours I plan on setting the timeout to.

Thanks for your response.
0
 
LVL 1

Author Comment

by:jmarkfoley
Comment Utility
OK, I've run some tests. I configured the domain server to specify a 2 hour timeout according to this instructions in your 2nd link. My results:

Connecting to a server 2008 computer configured to have a 1 hour "screen saver", the remote session reverted to the login screen after 1 hour. It's kind of noteworthy that it doesn't actually go to the screen saver image, but goes to the (local to that host) login screen. After another 7 minutes I got the timeout message. So, this system stayed connected for 1 hour and 7 minutes.

Connecting to a XP workstation with a screen saver set to 20 minutes - after 20 minutes I got the login screen, as above. After another 31 minutes I got the timeout. Connection time 51 minutes.

Connecting to a WIN7 workstation with a screen saver set to 20 minutes - after 20 minutes I got the login screen, as above. After another 37 minutes I got the timeout. Connection time 54 minutes.

None of these connections stayed up for the 2 hours I specified in the IIS manager. Should I have rebooted the domain server? Restarted the IIS service? I didn't do that.
0
 
LVL 1

Author Comment

by:jmarkfoley
Comment Utility
Your 1st link: http://blogs.technet.com/b/sbs/archive/2009/06/15/how-to-configure-the-rww-timeout.aspx, method I, "To change the client time-out setting for Remote Web Workplace"  has the instruction to option the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\RemoteUserPortal. It also says that if RemoteUserPortal doesn't exist to create it. Well, that key does not exist on my computer, but neither does SmallBusinessServer. Do you suppose it would be OK to go ahead and create SmallBusinessServer?
0
 
LVL 1

Author Comment

by:jmarkfoley
Comment Utility
OK, I went ahead and made the client time-out change by adding the SmallBuinessServer\RemoteUserPortal key to my workstation registry. I opened a new browser window and connected to RWW.

On the remote XP system I connected to, I got the screen saver (not the login screen) in 20 minutes. 41 minutes after connecting I got the disconnect message.

So, none of these suggested settings are doing anything to fix the problem. I still disconnect between 41 and 54 minutes. Here is the exact message I get on my remote WIN7 client:

Remote Desktop Disconnect
0
 
LVL 1

Accepted Solution

by:
jmarkfoley earned 0 total points
Comment Utility
This question is a bit old. Ttime to close it. I think I've figured out the main problem. It was my D-Link router. For a completely unrelated reason and for my own amusement, I decided to make a Linux based wireless router. (if anybody is interested in the howto on that: http://www.experts-exchange.com/Networking/Linux_Networking/Q_28162388.html). After replacing the D-link, all the problems discussed in this issue went away. Additional problems I didn't post: WINscp would lose connection on almost every file I tried to transfer and I would have to re-login. Sometimes, I'd have to do that more than once per transfer. Mapping remote folders using Windows was next to useless. I could open/read the files, but never save them. These features worked fine with my XP computer and I upgraded to WIN7 at about the same time I got the new D-link, so I wasn't sure whether it was a WIN7 issue or a router issues. With new new linux router, all these additional problems (WINscp, mapping ...) have disappeared.  So, apparently it was the router all along!
0
 
LVL 1

Author Closing Comment

by:jmarkfoley
Comment Utility
I figured out the problem.
0

Featured Post

What Security Threats Are You Missing?

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

Join & Write a Comment

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…
Know what services you can and cannot, should and should not combine on your server.
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…
Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…

771 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

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now