RE: Remote Web Workplace Connect to client computer error

The system can use the built in XP Remote desktop connection to connect fine.
It only happens using the RWW connect t o client computers. Once you choose a
computer from the list you recieve a small dialog box that says an invalid
server name was encountered. There is no more information. All other remote
PC'c can connect only this one remote PC cannot. This system gets the same
error when trying to connect to a different SBS server's RWW clients desktops
at another location also. So it is in the workstation. I thought I saw a tech
note on how to remove the active x RWW downloads to the remote system so at
the next logon attempt it will be re-downloaded. I would think this would be
the easiest thing to try. But I cannot find the article again. This did work
on this system before. but the user says nothing has changed.

thank you

Bob

Brandy Nee [MSFT]"" wrote:

> Dear Customer,
>
> Thank you for posting to the SBS Newsgroup.
>
> I understand that from one of client workstations, you cannot RDP in RWW.
> If I have misunderstood your issue, please let me know.
>
> Due to lack of information, I need your help to gather following
> information for detail research.
>
> 1. What is the exact error message shown to you? Please type the error
> message word by word to the Newsgroup. We need the exact error information
> for accurate research.
>
> 2. Does this issue occur from LAN or the Internet?
>
> 3. On the problematic client workstation, go to Start -> Run "mstsc"
> (without quotation marks), can you directly RDP to SBS Server and any other
> client workstations?
>
> 4. When did the issue occur? Could you RDP in RWW before? Did you make any
> changes on the client workstation and SBS Server, recently?
>
> 5. In the RWW page, click "Connect to Client Desktops" -> Click "Optional
> Settings". What are the boxes you have checked?
>
> ==============
>
> For your additional information:
>
> When you try to connect to client desktops or server desktops from RWW, the
> SBS server tells the clients to initialize a connection on port 4125. If
> the connection is establishes the server will deliver the terminal service
> connection to the destination computer on the normal Terminal Service port
> 3389. This is a by-design in RWW.
>
> Please make sure the incoming TCP port 4125 is opened on your router or
> hardware firewall (forward traffic on port 4125 to the SBS server). For
> more information regarding a similar issue which is caused by ISA, see:
>
> 828053 ISA Server prevents connection to a remote desktop when you connect
> http://support.microsoft.com/?id=828053
>
> If you already opened the port 4125 however the issue still occurs, the
> issue can occur if certain process running on the SBS server has assumed
> the port 4125. For detailed information, please take a look at the
> following KB article:
>
> 886209 Users cannot connect to remote desktops by using the Windows Small
> http://support.microsoft.com/?id=886209
>
> Please take your time to perform the steps above and collect the
> information for us to troubleshoot your issue. If anything is unclear,
> please feel free to let me know. 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: Remote Web Workplace Connect to client computer error
> >thread-index: AcXqDo32RwgU0VS3Sn+Q6fk3q05feQ==
> >X-WBNR-Posting-Host: 70.88.217.137
> >From: "=?Utf-8?B?Qm9naWUyMjI=?=" <Bogie222@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >Subject: Remote Web Workplace Connect to client computer error
> >Date: Tue, 15 Nov 2005 10:01:08 -0800
> >Lines: 6
> >Message-ID: <D5EAC257-27CA-472D-9F4A-F504BEDEE80A@xxxxxxxxxxxxx>
> >MIME-Version: 1.0
> >Content-Type: text/plain;
> > charset="Utf-8"
> >Content-Transfer-Encoding: 7bit
> >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!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windows.server.sbs:222512
> >X-Tomcat-NG: microsoft.public.windows.server.sbs
> >
> >I have one PC in the field that cannot connect to desktops using RWW. All
> >other PC's can connect to internal desktops but this one. When you choose
> the
> >desktop you want to connect to and click connect you get a dialog box that
> >says an invalid server name was encountered. Is there a way to delete the
> >active X controll that was downloaded originaly to this system and have it
> >re-installed?
> >
>
>
.

Relevant Pages

  • RE: Connectivity to the Remote Computer Could Not Be Established
    ... connect to the SBS via RWW, you cannot RDP to an internal client. ... received an error message 'Connectivity to the remote computer could not be ... client computer through Remote Web Workplace (RWW), ... At the SBS end, do you have a hardware router? ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot connect to desktops on LAN using RWW or RDC
    ... > I understand that you cannot RDP to client workstations neither from LAN ... but you can RDP to the server. ... > Users cannot connect to remote desktops by using the Windows Small ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote Application Installation
    ... client desktop using RWW? ... the remote desktop. ... What is the correct way to do a remote installation from a CD to a ... RWW, or Remote Desktop or RDP is a unique networking method that is optimized for screen-keyboard-mouse interactions, rather than file transfers. ...
    (microsoft.public.windows.server.sbs)
  • RE: sbs 2008 remote computer connection problem
    ... Some remote users cannot connect to client's desktop through SBS 2008 RWW ... a remote application when you use Terminal Services Web Access or Remote ... it will help us to isolate the issue to SBS RWW or client side's ...
    (microsoft.public.windows.server.sbs)
  • Re: vpn to server then remote desktop to client
    ... I can now log on to RWW however I cannot connect to client PCs. ... The client could not connect to the remote computer. ... servers but not on the other. ...
    (microsoft.public.windows.server.sbs)