RE: Remote Web Workplace not completely working.

Hi jsmithmis,

Thanks for using the SBS newsgroup.

From your description, I understand the issue to be: the RWW site can not
be work properly and receive error message "Connectivity to the remote
computer could not be established¡­" when attempting to connect to one
computer. If I am off base, please don't hesitate to let me know.

In order to allow a remote desktop connection to a client computer through
Remote Web Workplace (RWW), a component called TS Proxy is used to forward
TS requests through a firewall on TCP port 4125, in essence keeping the
connection alive. Once the connection is established on port 4125, the
traffic is then redirected to another dynamically allocated port. All
subsequence traffic will flow through the new port at the server to the
client at port 3389. In most cases, it's a firewall related issue and the
first troubleshooting step would be to check if port 4125 is open in ISA
and the router/firewall.

To open the port 4125 on ISA, we can re-run CEICW to confirm it. You can
refer to the following steps:

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. In the
next page, make sure the services you want to publish to internet is
checked in services configuration page.
4. Click Next and then select Allow access to the following web site
services from the internet.
5. Make sure Remote Web Workspace 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.

I suggest you refer to KB 825763 to configure the network connection:

825763 How to configure Internet access in Windows Small Business Server
2003
http://support.microsoft.com/?id=825763

To check if the port 4125 is opened in the router/firewall, we can run
command "telnet publicFQDN:4125" (no quotation marks) from one internet
computer. What is the result? If the connection can not be setup, this
indicates that the port 4125 is not opened. After ensure the port 4125 on
ISA and router/firewall is opened, please test the issue again and let me
know the result.

If the issue persists, please logon the on the SBS server, check if there's
any application is listening on port 4125. To do so, click Start, click
Run, type "cmd" and press ENTER. Type the following command and press ENTER.

netstat -ano | find ":4125"

You should see a line similar to the following if something is listening on
4125:

TCP 192.168.16.2:4125 0.0.0.0:0 LISTENING 2340

Where the "2340" is the ID of the process that is listening on port 4125.

If the process is mad.exe, the issue is similar to the one documented in
the following Knowledge Base article:

329155 "The Server May Be Too Busy" Error Message If Terminal Services
Installed in Remote Administration Mode
http://support.microsoft.com/?id=329155

Please add the registry keys to exclude TCP port 4125 from the ports
available to the Remote Procedure Call service. To do so:

WARNING: If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system. Microsoft
cannot guarantee that you can solve problems that result from using
Registry Editor incorrectly. Use Registry Editor at your own risk.

A. On the SBS server, open Regedit.
B. Add the registry key
"HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\Internet".
C. To this key, add the following values:

Ports REG_MULTI_SZ 4125
PortsInternetAvailable REG_SZ N
UseInternetPorts REG_SZ Y

D. Exit Regedit, restart the server and see if the issue persists.

If the issue persists, please help me collect the ISA log for analyze:

Clean the existing ISA log, reproduce the problem, and then gather the
updated ISA web proxy log:

1. Enable all the ISA logging options

In ISA Management console ' navigate to 'Servers and Arrays' ' 'Monitoring
Configuration' ' Logs, double click 'ISA Server Web Proxy Service' and
switch to the 'Fields' tab, and then click 'Select All'.

2. Clean Up the existing logs

1) Stop all the ISA services which includes 'MS Web Proxy', 'MS Firewall'
and 'MS Scheduled Cache Content Download'.

2) Delete all the log files in 'C:\Program Files\Microsoft ISA
Server\ISALogs'.

3) Restart the services: 'MS Web Proxy', 'MS Firewall' and 'MS Scheduled
Cache Content Download'.

3. Reproduce the problem on one XP client, and then compress and send all
new generated logs to me (C:\Program Files\Microsoft ISA Server\ISALogs).
Please also NOTE the XP client IP.

Please mail me the log files to my working mailbox: v-yanniw@xxxxxxxxxxxxx

Hope above information helps! I am happy to be assistance to you and look
forward to your reply!

Have a nice day!

Sincerely,

Jenny Wu
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.


--------------------
From: "32solutions" <jsmithmis@xxxxxxxxx>
Newsgroups: microsoft.public.windows.server.sbs
Subject: Remote Web Workplace not completely working.
Date: 2 Mar 2006 05:51:30 -0800
Organization: http://groups.google.com
Lines: 30
Message-ID: <1141307490.705247.44880@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
NNTP-Posting-Host: 68.15.131.201
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1141307499 31398 127.0.0.1 (2 Mar 2006
13:51:39 GMT)
X-Complaints-To: groups-abuse@xxxxxxxxxx
NNTP-Posting-Date: Thu, 2 Mar 2006 13:51:39 +0000 (UTC)
User-Agent: G2/0.2
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; .NET
CLR 1.1.4322),gzip(gfe),gzip(gfe)
X-HTTP-Via: 1.0 KC-DC1, 1.0 InstaGate-EX2:8080 (Squid/2.4.STABLE7)
Complaints-To: groups-abuse@xxxxxxxxxx
Injection-Info: v46g2000cwv.googlegroups.com; posting-host=68.15.131.201;
posting-account=s0lc8wwAAACSCjySFB9HD2pqhyDPmSOy
Path:
TK2MSFTNGXA03.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onli
ne.de!border2.nntp.dca.giganews.com!nntp.giganews.com!transit3.readnews.com!
news-out.readnews.com!postnews.google.com!v46g2000cwv.googlegroups.com!not-f
or-mail
Xref: TK2MSFTNGXA03.phx.gbl microsoft.public.windows.server.sbs:248757
X-Tomcat-NG: microsoft.public.windows.server.sbs

Hello,

I have read through many of the posts here and I can't seem to find a
solution to the specific issue that I am having. Allow me to explain:

I have a SBS 2003 Server running ISA 2003 with 2 nics installed. The
server is behind a InstaGate EX firewall but the firewall is configured
to allow ports 80, 443, 444, 4125, and 3389 through to the server. I
have added the protocol rules and protocol definitions that are talked
about in the KB article. I can sucessfully RDP into the server from a
remote site and from the server I am able to RDP into a few different
workstations. I have configured the RWW group to include the users
that I want to grant access to.

I try to connect to the machines remotely using Remote Web Workplace
and I am getting an error. I can connect to the site
https://FQDN/remote and log in, but when I select a machine, either
workstation or server to connect to it says...

"Connectivity to the remote computer could not be established. Ensure
that the remote computer is on and connected to the Windows Small
Business Server network"

I have even tried connecting to another machine using RWW from within
the network but it gives me the same message.

Any ideas?

jsmithmis



.

Relevant Pages

  • RE: ISA access rules, help
    ... please let me know whether you're using ISA 2000 or ISA 2004 ... (SBS SP0 or SBS SP1). ... the ISA server will not be used as a proxy server. ... Since SBS already used port 80, ...
    (microsoft.public.windows.server.sbs)
  • RE: How to add a Citrix Server
    ... ISA about the second address (how do I attach a second IP address to the NIC ... the ISA server to handle the incoming traffic that needs to go to the Citrix ... How would I forward the traffic coming in on the new port to port ... that the newsgroups are staffed weekdays by Microsoft Support professionals ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot telnet some ports
    ... Some with remote administration feature I believe. ... >> From a Windows 2003 Server SP2 ... >> fromn the 2k3 serrver but can telnet into any other port. ... kerberos 750/udp kdc # Kerberos udp ...
    (microsoft.public.windows.server.general)
  • Re: ISA Rule for Remote Desktop?
    ... My server has a private IP address on the WAN NIC. ... I've just had an opportunity to try testing Remote Desktop through RWW from ... attempts being made from the logging interface in ISA to port 4125 when I ... There are three connection ...
    (microsoft.public.windows.server.sbs)
  • Re: Unable to Connect to Server/Client Desktop using RWW
    ... Please post the results of an ipconfig /all for the sbs server. ... I did another test after turning off the firewall on the remote. ... If port 4125 was not forwarded on the sbs machine, ...
    (microsoft.public.backoffice.smallbiz)