Re: SBS2003 Outlook HTTP/RPC not working

Tech-Archive recommends: Speed Up your PC by fixing your registry

This may shed some light. Basically, RPC grabs some ports dynamically that may be needed by other processes.

\<snip>
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
\<endsnip>

--
Les Connor [SBS-MVP]


____________________________
"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message news:OoRT2qoRJHA.5056@xxxxxxxxxxxxxxxxxxxxxxx
I still haven't found why I have the file. There's a KB article about adding the key in relation to RWW but it doesn't have all the reg values. I tend to name these things with as decent reminder as possible (due to bad RAM) and would have expected 'rww rpc fix' rather than just 'rpc fix' if I had saved it in relation to rww alone.

http://support.microsoft.com/kb/154596 discusses the key in relation to firewalls, and the fact that the key may not exist. The kb also has a link to a tool for configuring rpc on server 2003.

Dave, it could be a red herring. This, not self-promotion, is why my original reply started with the suggestion that I could look at the system. The few posts before I became involved simply indicated to me that:
a) you had approached the problem well and tried not only what was likely to be suggested but a few things beyond what many members of the group would have been aware of.
b) I reckon it's something very simple that is wrong.
c) I think that rather than rpc not working the problem is due to it not being found (why I was asking about DNS).

and d) the problem has existed much longer than should happen.

I see that Robbin from MS has noticed the thread. I think you've already covered the suggestions but suggest following through it (cross your i's dot your t's :-) and if it still don't work Robbin may have further advice.

"Dave Cattley" <DaveCattley@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:29AA8A7A-FE3B-4128-819E-BF7D617D41D0@xxxxxxxxxxxxxxxx


"SuperGumby [SBS MVP]" wrote:


[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\Internet]
"Ports"=hex(7):33,00,33,00,38,00,39,00,2d,00,33,00,33,00,38,00,39,00,00,00,00,00
"PortsInternetAvailable"="N"
"UseInternetPorts"="Y"



This key does not exist on my SBS2003 machine. The Rpc key has subkeys of

ClientProtocols\
NameService\
NetBios\
RpcProxy\
SecurityService;

I am curious to know, did you expect them to be present?

Regards,
-dave



.

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: Remote Web Workplace not completely working.
    ... In order to allow a remote desktop connection to a client computer through ... TS requests through a firewall on TCP port 4125, ... To open the port 4125 on ISA, we can re-run CEICW to confirm it. ... server certificate) and then click Next. ...
    (microsoft.public.windows.server.sbs)
  • Re: Intersite Replication problem
    ... As for RPC The default value for the RPC Replication Timeout registry ... from Windows 2000 to Windows Server 2003, the value for the RPC Replication ... Remote Procedure Call dynamic port allocation is used by remote ...
    (microsoft.public.windows.server.active_directory)
  • Re: Intersite Replication problem
    ... I followed Antony's DNS advise and I seens to be working. ... To perform the replication I've schedule a task on the W3K server to dial ... As for RPC The default value for the RPC Replication Timeout registry ... Remote Procedure Call dynamic port allocation is used by remote ...
    (microsoft.public.windows.server.active_directory)
  • 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)