RE: Problems connecting through RWW
- From: v-crinal@xxxxxxxxxxxxxxxxxxxx ("Crina Li")
- Date: Mon, 27 Mar 2006 05:23:47 GMT
Hi,
Thank you for posting in SBS newsgroup.
I am sorry for the delayed response due to weekend. Please understand that
the newsgroups are staffed weekdays by Microsoft Support professionals to
answer your systems and applications questions. Your understanding is
greatly appreciated!
From the description, do you mean you can access RWW from internal andexternal network now and the issue to be: If you try to connect to client
computer by using ''Connect to my computer at work'' feature from client
computer, the connection is denied with the error message?
VBScript: Remote Desktop Disconnected.
The client could not connect to the remote computer. Remote connections
might not be enabled or the computer might be too busy to accept new
connections. It is also possible that network problems are preventing your
connection. Please try connecting again later. If the problem continues to
occur, contact your administrator.
As I know, the error message "VBScript: Remote Desktop Disconnected..."
indicates a socket has been closed. We may try the following steps: [Note:
the troubleshooting steps may be too long, thanks for your patient and time]
1. Can you RDP to SBS or other computers directly through click Start and
Accessories and Communications and Remote Desktop Connection?
2. In Internet Explorer on the workstation you are connecting from, go to
Tools, Internet Options, then click on the Privacy tab, remove the check
for Block pop-ups.
3. Double check if you have selected Allow users to connect remotely to
this computer on the Remote tab of properties of My Computer on SBS server
and the computer you want to connect to.
4. This issue can also occur if you are connecting from an Internet
computer and your router does not have incoming TCP port 4125 opened. If
this is the case, all connections from LAN computers should work. I suggest
you check to make sure the incoming TCP port 4125 is opened on your router
or hardware firewall. For more information regarding a similar issue, see:
828053 ISA Server prevents connection to a remote desktop when you connect
http://support.microsoft.com/?id=828053
886209 Users cannot connect to remote desktops by using the Windows Small
http://support.microsoft.com/?id=886209
5. Modify the RWW trusted timeout regkey to a value greater than the max
values of the IIS and ASP.NET timeouts, you will need to increase the IIS
and ASP.NET timeouts. Otherwise, you will be timed out of those features
before RWW, leading to some weird behavior. To do it as following:
Remote Web Workplace timeout:
===========================
The time out values (in minutes) are configurable in the registry, at:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\RemoteUserPortal\P
ublicTimeOut
REG_DWORD: 20 (Default)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\RemoteUserPortal\T
rustedTimeOut
REG_DWORD: 60 (Default)
The PublicTimeOut is used when the user checks the box for "I'm using a
public or shared computer" on the RWW logon page. The TrustedTimeOut is
used when the user unchecks this checkbox.
ASP.NET timeout:
==============
Edit the C:\inetpub\remote\web.config file.
Look for line:
<forms name="RemotePortalAuth" loginurl="logon.aspx" protection="All"
path="/" timeout="120" />
timeout = value in minutes of your largest timeout value. The default
timeout in SBS 2003 is 120 minutes.
IIS timeout:
=========
Server Management | Advanced Management | Internet Information Server
|%Server Name% | Web Sites | Default Web Site | right click Remote and
choose Properties | Virtual Directory tab | Configuration button | Options
tab | Session timeout.
The Default Session timeout in SBS 2003 is 120 minutes.
Close and reopen IE.
6. You may check if the following CLSIDs has been added to the Add-on List
for RWW to work on external clients:
{F414C260-6AC0-11CF-B6D1-00AA00BBBB58} - Javascript
{B54F3741-5B07-11cf-A4B0-00AA004A55E8} - VBScript
{7584C670-2274-4EFB-B00B-D6AABA6D3850} - Microsoft RDP Client Control
(redist)
You may find them on GP policy:
1) Click Run, and then input gpedit.msc.
2) Local Computer Policy >Computer Configuration > Administrative Templates
Windows Components > Internet Explorer > Security Features > Add-onManagement.
You may also refer to the following KB article:
883256 How to manage Internet Explorer add-ons in Windows XP Service Pack 2
http://support.microsoft.com/?id=883256
If it does not work, please try to rerun CEICW as following:
1. Expand Standard Management | To Do List.
2. Click Connect to the Internet in the right pane.
3. Navigate the wizard to Firewall and then select Enable firewall.
4. Click Next twice and then select Allow access to the following web site
services from the internet.
5. Make sure OWA, RWW be selected and click Next.
6. Click Create a new Web services certificate (input your FQDN as the web
server certificate) and then click Next.
7. Following the wizard to finish it.
Please also refer to the following KB article:
825763 How to configure Internet access in Windows Small Business Server
2003
http://support.microsoft.com/?id=825763
If the problem still persists, would you please help me collect the
following information?
1. Please try to telnet the SBS server's TCP port 4125 to see if this gets
connected properly.
2. Does the situation occur on LAN client or remote client?
3. Can you connect to client computer via RWW from SBS?
Please do not hesitate to let me know if you have any questions or concerns
regarding the issue.
Thanks for your time and I look forward to your reply.
Best regards,
Crina Li (MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Thread-Topic: Problems connecting through RWW
| From: =?Utf-8?B?VGVjaCBQYXJ0cw==?= <TechParts@xxxxxxxxxxxxxxxxxxxxxxxxx>
| Subject: Problems connecting through RWW
| Date: Sun, 26 Mar 2006 14:50:56 -0800
|| Newsgroups: microsoft.public.windows.server.sbs
||
| After the intial setup of SBS 2003, I cant access any computers including
the
| server through RWW. The server is shown in the list of computers to
connect
| to, but when i click connect it gives this error message "The client
coul
| not connect ot the remote computer. Remote connections might not be
enabled
| or the computer might be to busy to accept connections." I logged onto
RWW
| as the administrator. Ports 3389, 444, 443, and 4125 are forwarded to
the
| server. There are no firewalls involved. The server and all my
computers
| have remote desktop enabled in the system properties.
|
| *once again* I cant connect to any computers using RWW after the intial
SBS
| 2003 setup.
|
| Thanks,
| Tech Parts Corp
|
.
- Prev by Date: Re: Problems connecting through RWW
- Next by Date: MAPI call error Exchange Server **we don't use it***
- Previous by thread: Re: Problems connecting through RWW
- Next by thread: RE: OWA GUI
- Index(es):
Relevant Pages
|