RE: RWW users disconnected from Remote Desktop



Hello Herman,

Thank you for posting back and keeping us updated!

Thanks a lot for your very detail information reply!

Based on my research, this issue can be occurred if you run a backup
program or antivirus scan while remote users are connected to the network,
Remote Web Workplace remote desktop sessions may be disconnected. If this
occurs, the error message "An Internal Error has occurred" appears, and
users are returned to the Remote Web Workplace computer selection page or
log on page. At this point, users can log back on to the remote computer
and resume work.

If this is the case, you may need to call PSS to obtain the hotfix 821438:

821438 FIX: Antivirus Programs May Cause Some Web Applications to Restart
Unexpectedly
http://support.microsoft.com/?id=821438

if the issue persists, please help to gather following information:

1. Do you have a server that might be offline at the present time? The RWW
will go through all your servers to determine their capabilities (TS
support for example), if one is showing in active directory but it cannot
be contacted then the RWW will timeout and take additional time.

You can try set the registry value AppTS to 0
(HKLM\Software\Microsoft\SmallBusinessServer\RemoteUserPortal\KWLinks) and
see if it helps.

2. Please try the steps included in the KB 323497 on the problematic
Windows XP clients and see if the issue still occurs:

323497 "The RDP Protocol Component "DATA ENCRYPTION" Detected an Error..."
error message
http://support.microsoft.com/?id=323497

3. Were problematic clients joined domain through
http://sbsserver/connectcomputer?

Please take your time to perform the steps above and collect the
information for us to troubleshoot your issue. I am looking forward to
hearing from you!

Best regards,

Brandy Nee

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: RWW users disconnected from Remote Desktop
>thread-index: AcXvgVQhTGtpJ4jsTWumpae+wDlr3g==
>X-WBNR-Posting-Host: 70.162.164.128
>From: "=?Utf-8?B?Q1NIZXJtYW4=?=" <CSHerman@xxxxxxxxxxxxxxxxxxxxxxxxx>
>References: <E23EC434-13B1-4225-9219-4E5C42D94420@xxxxxxxxxxxxx>
<pBUuQUf2FHA.2904@xxxxxxxxxxxxxxxxxxxxx>
>Subject: RE: RWW users disconnected from Remote Desktop
>Date: Tue, 22 Nov 2005 08:25:19 -0800
>Lines: 80
>Message-ID: <C0898A9F-A3C6-443E-B0FC-5F4FC51D8FEC@xxxxxxxxxxxxx>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 8bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:224639
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>Good day all, and thank you, Brandy, for your reply. Note that I
>accidentally started two threads related to this same issue, but since I
>received different replies to each thread I am posting this response back
to
>both threads on the theory that I am twice as likely to come up with a
>solution :)
>
>This issue was put on the back burner for a few weeks but now I am back to
>it. The basic description is every user utilizing remote desktop via RWW
is
>disconnected at random intervals between 10 and 30 minutes with the error
>message:
>
>VBScript: Remote Desktop Disconnected
>An internal error has occurred.
>
>This occurs when users are actively using the remote desktop session, not
as
>in a timeout situation when they leave the session idle for too long.
Some
>users have even been disconnected while in the middle of typing a sentence.
>
>After the user is disconnected from remote desktop, they are taken all the
>way back out to the RWW login screen where they must login again; not back
to
>the â??Connect to Client Desktopsâ?? screen. This leads me to think that
the
>issue is likely related to IIS?
>
>In addition to the troubleshooting steps I mentioned in my previous
posting
>(please review as I am not recapping here), I have tried/observed the
>following:
>
>1. Connecting to RWW from inside the LAN and using remote desktop to
>another LAN workstation produces the same issue as when users are
connecting
>to RWW from the internet.
>
>2. I have replaced the NIC card with a PCI Intel PRO/100 S adapter and
the
>issue still occurs.
>
>3. The issue occurs when using remote desktop via RWW to connect to any
>client workstation or the server itself.
>
>4. Using remote desktop without RWW to any client workstation or the
server
>results in no issues; the user can work without disconnection for any
period
>of time.
>
>5. I have run and re-run CEICW many times.
>
>6. I performed a â??clean bootâ?? on the server, disabling all
non-Microsoft
>services and startup entries via MSCONFIG and the issue still occurs. As
far
>as I can tell there are no applications or services that may interfere
with
>port 4125 on the server.
>
>7. RRAS is not configured or started on this server so I would not expect
>that it is causing problems.
>
>8. The issue occurs while using RWW from workstations using Win XP SP1,
>SP2, and Win2000 Pro, IE 6 with and without the pop-up blocking tool so a
>pop-up blocker is not causing the issue.
>
>9. RWW worked perfectly for months on an old server , but that server
kept
>having unrelated problems locking up all of the time. The old server was
>replaced with new hardware, we loaded SBS 2003 on the new server and
>replicated AD/moved Exchange mailboxes from the old server to preserve the
>domain context. This is when the problems with RWW started to occur.
>
>10. Although this may or may not be related, during Windows setup on the
>new server we got errors related to Sharepoint configuration. Currently
>Sharepoint does not work (http://companyweb results in â??Page cannot be
>displayedâ?? and there is no Companyweb site listed in IIS). This office
does
>not use Sharepoint so this specific issue does not need to be resolved but
I
>thought it might provides clues to the RWW issue.
>
>11. I tried using the PortQry utility to troubleshoot this issue but am
not
>sure exactly how I am supposed to test. If I query port 4125 on the
server
>when no one is connected via RWW it returns â??NOT_LISTENINGâ??. If
someone is
>connected via RWW the query tells me â??ESTABLISHEDâ?? and I logged the
port
>activity to disk but all that gets logged is, when the disconnection
occurs,
>the query tool reflects that port 4125 is back to the disconnected state.
If
>I was supposed to use PortQry to determine if another application is
>interfering on port 4125 I think I have established that this is not the
case.
>
>Thank you for any assistance with this issue you can provide, my goal is
to
>figure this one out before the end of the year. Please let me know if any
>further information is needed.
>

.



Relevant Pages

  • RE: RWW users disconnected
    ... The basic description is every user utilizing remote desktop via RWW is ... Using remote desktop without RWW to any client workstation or the server ... the user can work without disconnection for any period ...
    (microsoft.public.windows.server.sbs)
  • RE: RWW and Remote Desktop
    ... cannot connect to the remote desktop sessions through the site. ... desktop connection in RWW site, the TCP port 4125 is required. ... connect to the clients'' desktop through RWW, the SBS server works as a RDP ... if the ISA 2004 version which has installed in the server box ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Connected on VPN - NOW what?
    ... able to connect to our server and login as the administrator. ... I think my PIX firewall is blocking access using RWW. ... "connect to my computer at work" Remote Desktop option. ... That said, if you also get a dedicated TS box on your network, you will ...
    (microsoft.public.windows.server.sbs)
  • RE: RWW users disconnected from Remote Desktop
    ... The basic description is every user utilizing remote desktop via RWW is ... Using remote desktop without RWW to any client workstation or the server ... the user can work without disconnection for any period ...
    (microsoft.public.windows.server.sbs)
  • Re: RWW works with IP but not FQDN
    ... if I go to http://servername/remote at the server and log ... In another response GG states" "Did you declare FQDN on rule of RWW? ... I'm trying to connect from a client not running windows firewall that is ... but neither Remote Server Access or Remote Desktop ...
    (microsoft.public.windows.server.sbs)