Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows Server 2003Windows 2000Windows NTSmall Business ServerVirtual ServerExchange ServerIISHost Integration ServerISA ServerSMSWSUSMOMWindows Media ServerSecurityCertification
Related Topics
SQL ServerMS WindowsMS OfficePC HardwareMore Topics ...

Windows Server Forum / Small Business Server / SBS 2003 / September 2005

Tip: Looking for answers? Try searching our database.

Problems getting RCP over HTTP to work

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Lee Smith - 27 Sep 2005 22:49 GMT
RCP over HTTP

I asked this before and got no response.  It is one of those things I come
back to when I have time to play with settings.

I have a SBS 2003 server.  It is behind a Firebox x700 firewall.  From the
outside world I can connect to the server and get my email via POP3 and OWA.
I can also connect using the remote option and use the features listed
there.  What I am unable to do is get Outlook 2003 to connect to my server
and get email via RCP over HTTP.

In my research I have read about front end and back end server.  I think
with the SBS setup that don't apply to my setup.  I have seen articles about
needing to have registry keys setup for port 6001, 6002 and 6004.  In other
articles I read similar registry keys but on 5000 and 5001.  I think I have
ran and reran the network config tool several times.  I have setup a
Certificate.  On my Firebox I have tried opening up the ports for 6001, 6002
and 6004.  I also tried it with the 5000 and 5001.  I finally just did an
any any rule for my test machine at my home.  Still no go.  I am hoping some
one may have some ideas and/or suggestions as to what I could try to get
this working.  I should mention if I run it at work it does work just fine.
When I test from the outside world it gets to the login screen and just
keeps asking for user/password over and over.  It does not give and error
and never gets past that screen.

If I try using the outlook /rcpdiag command while trying to log on the
rcpdiag screen comes up and shows the following lines.  It does not change
as I put in user name/password.

Server Name                Type    Interface           Conn    Status
Req/Fail Avg Resp

---                                Directory                      ---  
Connecting

gtsvr.GWTech.local      Referral                        ---  
Connecting

---                                Directory                      ---  
Connecting

gtsvr.GWTech.local      Referral                        ---  
Connecting

Some of the changes I have made to my server regarding trying to get this to
work are below.

I tried following the steps in article 833401, 155931

None of this seems to be working for me.  Any one experiences this or
something similar with any ideas?

Any help or ideas would greatly be appricated!

Lee Smith

leeasmith2@hotmail.com
Russ Grover - 28 Sep 2005 03:48 GMT
First besure your Certificate is created and a FQDN

Example servername.yourdomain.com
(You may need to have a subdomain created where you host and point this to
your external IP)

Next make sure ports are open.

Ports
     Table A: Ports that Enable Remote Access to SBS Services
     TCP Port Service Description
     21 FTP Enables external and internal file transfer
     25 Exchange Server Enables incoming and outgoing SMTP mail
     80 (http://) IIS Enables all nonsecure browser access, including:
internal access to IIS Webs including the company Web, Windows SharePoint
Web, Windows SharePoint administration Web, and server monitoring and usage
reports Enables internal access to Exchange by OWA and OMA clients
     110 POP3 Enables Exchange to accept incoming POP3 mail
     123 (UDP port) NTP Enables the system to synchronize time with an
external Network Time Protocol (NTP) server
     143 IMAP4 Enables Exchange to accept incoming IMAP4-compliant messages
     220 IMAP3 Enables Exchange to accept incoming IMAP3-compliant messages
     443 (https://) Outlook Enables all secure browser access, including
external access to Exchange for Outlook 2003, OWA, and OMA clients; required
for external access to server monitoring and usage reports
     444 Windows Share Point Services Enables internal and external access
to the SharePoint Web
     500 IPSec Enables external VPN connections by using IPSec
     1701 L2TP clients Enables external L2TP VPN connections
     1723 PPTP clients Enables external PPTP VPN connections
     3389 Terminal Services Enables internal and external Terminal Services
client connections
     4125 (Note: you can change this port in RRAS) Remote Web Workplace
Enables external OWA access to Exchange, plus internal and external HTTPS
access to the client Web site
     4500 IPSec Internet Key Exchange (IKE) Network Address Translation
(NAT) traversal

Once the ports are open

Run CEICW Wizard (Internet Connection Wizard)

Make sure you have Services enabled...

Go to https://servername/Remote or https://ExternalIP/Remote if you are
outside your intranet.
and click on Configure Outlook via the Internet

Configure Outlook 2003  With that information..
(I will look similar to below but your server will have it's own unique
properties Do not follow below just to show you what it looks like)

Using Outlook via the Internet
If you are using Microsoft® Office Outlook® 2003, you can connect to the
computer running Windows® Small Business Server through the Internet using
the feature called RPC over HTTP. This means you can remotely access your
server e-mail account from the Internet when you are working outside your
organization's firewall. You do not need security-related hardware or
software (such as smart cards or security tokens), and you do not have to
establish a virtual private network (VPN) connection to the server.

Comparing RPC over HTTP and Outlook Web Access
When using RPC over HTTP to access your mailbox, you get the full
functionality of Outlook 2003. For example, you can work offline, use
Microsoft Office Word 2003 as your e-mail editor, and easily organize your
mailbox.

To use Outlook via the Internet
Ensure that the following requirements have been met on the client computer:

Verify that the computer is running Microsoft Windows XP Service Pack 1 or
later
 a.. Click Start, right-click My Computer, and then click Properties.
 The version of the operating system and service pack is displayed under
System. If you do not see a service pack version, there is no service pack
installed.
Verify that Windows update Q331320 is installed on the computer (not
required if you are running Windows XP Service Pack 2 or later)
 1.. Click Start, click Control Panel, and then open Add or Remove
Programs.
 2.. Under Currently installed programs, search for the item Windows XP
Hotfix (SP2) Q331320.
 3.. If the item is not present, go to the Microsoft Web site
(http://go.microsoft.com/fwlink/?LinkId=18651) and follow the instructions
to download and install it.
Verify that the computer is running Outlook 2003 or later
 1.. Open Outlook.
 2.. Click the Help menu, and then click About Microsoft Office Outlook.
The version number appears at the top of the box.
Verify that the computer trusts the certificate used by the server
 1.. Open Internet Explorer, and then in the address bar type:
 https://SmallBusinessITSupport.com/remote

   a.. If the certificate is trusted, a certificate warning does not
appear. In this case, continue with step 1 under Ensure that you have an
Outlook profile configured for the server.
   b.. If the certificate is not trusted, a warning appears. Click View
Certificate, click Install Certificate, and then follow the instructions.
Ensure that you have an Outlook profile configured for the server
 1.. Click Start, and then click Control Panel.
   a.. If you are viewing Control Panel in the default Category view,
switch to Classic view, and then double-click Mail.
   b.. If you are viewing Control Panel in Classic view, double-click Mail.
 2.. In the Mail Setup dialog box, click Show Profiles. If your profile
appears in the list, select your profile, click Properties, click E-mail
Accounts, select View or change existing e-mail accounts, and then click
Next. If your profile does not appear, open Outlook and follow the
instructions to create a profile before proceeding.
   a.. If Microsoft Exchange Server does not appear in the list, the
existing profile is not associated with a Microsoft Exchange Server e-mail
account. Click Cancel, and then click Close. Continue with step 3 to add a
profile.
   b.. If there is an existing Microsoft Exchange Server profile, continue
with step 3 under Configure the computer for RPC over HTTP.
 3.. Click Add. The New Profile dialog box appears.
 4.. In the Profile Name box, type a name for the new profile, and then
click OK. The E-mail Accounts dialog box appears.
 5.. Under E-mail, select Add a new e-mail account, and then click Next.
The Server Type dialog box appears.
 6.. Click Microsoft Exchange Server, and then click Next.
 7.. Continue with step 4 under Configure the computer for RPC over HTTP.
Configure the computer for RPC over HTTP
 1.. Click Start, and then click Control Panel.
   a.. If you are viewing Control Panel in the default Category view,
switch to Classic view, and then double-click Mail.
   b.. If you are viewing Control Panel in Classic view, double-click Mail.
 2.. In the Mail Setup dialog box, click E-mail accounts, click View or
change existing e-mail accounts, and then click Next.
 3.. In the E-mail accounts dialog box, click Microsoft Exchange Server,
and then click Change.
 4.. In the Microsoft Exchange Server box, type the local name of the
Exchange server:
 sbs2003.smallbusiness.local

 5.. In the User Name box, type the user name that you use to log on to the
Remote Web Workplace. Do not click Check Name.

 6.. In the Exchange Server settings page, click More Settings.
 7.. On the Connection tab, under Exchange over the Internet, select
Connect to my Exchange mailbox using HTTP, and then click Exchange Proxy
Settings. The Exchange Proxy Settings dialog box appears.
 8.. Under Use this URL to connect to my proxy server for Exchange, type
the following URL:
 SmallBusinessITSupport.com

 9.. Select Connect using SSL only, and then select Mutually authenticate
the session when connecting with SSL.
 10.. In the Principal name for proxy server box, type the following text:
 msstd:SmallBusinessITSupport.com

 11.. Select On slow networks, connect using HTTP first, then connect using
TCP/IP.
 12.. Under Proxy authentication settings, select Basic Authentication.
 13.. Click OK, and then click OK again. Click Next, and then click Finish.
Click Close.
 14.. In the Mail dialog box, if Always use this profile is selected,
choose the newly configured profile.
 15.. Open Outlook and type your Windows Small Business Server user name
(in the format SMALLBUSINESS\user name) and password. You can now work with
your Outlook mailbox.
Doing all theses things it should work. (I don't think I forgot anything?)

Russ

Signature

Russ Grover
Small Business IT Support
SBS Rocks!
Portland/Beaverton OR
Email: Sales at SmallBusinessITSupport.com
Website: http://www.SmallBusinessITSupport.com

> RCP over HTTP
>
[quoted text clipped - 51 lines]
>
> leeasmith2@hotmail.com
"Charles Yang [MSFT]" - 28 Sep 2005 04:03 GMT
HI Lee,

Welcome to SBS newsgroup.

Issue description:
==============

I understand that you want to use configure RPC over HTTP on SBS 2003, but
you encounter problem about authentication issue when connect from outside
with outlook 2003.

Analyzing and suggestions:
===============

Generally speaking, the SBS 2003 can be configured using RPC over HTTP, you
did not need to configure it using Front-End and Back-End, we can use only
one SBS 2003 server to do this task.

For the SBS 2K3 server, we do not need to configure everything manually by
using the steps outlined in ''833401 How to configure RPC over HTTP on a
single server in Exchange Server 2003 -
http://support.microsoft.com/?id=833401
'

Make sure you 've enabled ''Outlook over the Internet'' and ''Remote Web
Workplace'' in the CEICW (Configure E-mail and Internet Connection wizard),
then you will logon to the Remote Web Workplace (https://serverfqdn/remote)
as a user and look at the link for ''Configure Outlook via the Internet''.
You can see it from the server by going into https://localhost/remote. If
the option is not displayed, then the feature is not configured on the
server.

Click ''Configure Outlook via the Internet'' and then the webpage ''Using
Outlook via the Internet'' will appear which has pretty much a step by step
list of instructions. If it tells you to use ''server.domain.local'', use
that. If it tells you to use ''server.domain.com'', use that. Follow the
steps exactly, double check all the settings. Most of the time the error
was configuration problems at the outlook.

In addition, when you go to https://domainname/remote does IE pop up with
certificate warning? Ensure to click ''View Certificate'' and ''Install''.

In the SBS 2K3 without ISA installed scenario, when you run CEICW, you are
prompted to ''Create a new Web server certificate'', the name you input
there (for example, server.domain.local) will be automatically be created
as the certificate used by IIS Websites. To configure Outlook Over HTTP,
you must use the certificate name (FQDN). That means, on the Internet, you
need be able to resolve the FQDN to the Internet IP of your SBS server.

Have you registered the certificate (FQDN) with your ISP so that when you
ping the FQDN, it can be resolved to your SBS external IP?

If you do not have FQDN registered on the Internet, you will have to make
every Internet clients be able to resolve the FQDN to the Internet IP of
your SBS. To do this, you will need to manually create hosts file on every
clients:

1.    On the Internet client computers, locate the hosts file in the folder
%systemroot%\system32\drivers\etc.

Add the following contents to the file: Internet IP of your SBS Certificate
FQDN;     For example:

2.    157.22.12.81 certificate.mydoain.local

3.    Follow the steps in the RWW link ''Configure Outlook via the Internet''
to configure Outlook on the client computers.

Please make sure that you use basic authentication not the NTLM
authentications.

Hope the above information helpful, I appreciate your effort on this issue.
I am glad to help you.

Best regards,

Charles Yang (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

Signature

======================================================
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.

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| From: "Russ Grover" <russ@NoSPam.SmallBusinessITSupport.com>
| References: <OsQCE06wFHA.2008@TK2MSFTNGP10.phx.gbl>
[quoted text clipped - 232 lines]
| >
| > leeasmith2@hotmail.com
Lee Smith - 28 Sep 2005 20:09 GMT
Thanks for your response.

I do have a FQDN and if I go to any machine and ping it the ping does
resolve the correct IP address.  This makes me believe that part is right.

As to give some more details I will start with your open port suggestion.  I
have systems in my home.  They all are using private IP address and 1 public
IP.  That public IP has been setup on my Firebox x700 to allow ANY ANY for
incoming/outgoing ports to my network.  So all the ports are open.  With
that in mind I think I have open all ports covered.

I have run the internet connection wizard several times and for now I have
every thing allowed.  What I mean by this on the screen where it asks me if
I want the out side world to see I have checked the option Allow access to
the entire Web site from the Internet.  Before I had that I had all the
boxes checked under the Allow access to only the following Web Site services
from the Internet.

When I go to https://domain.com/remote I have been prompted with the
certificate and I have installed it.  So now when I bring up my site I do
not get the prompt no more.

Under the options I do see configure your computer to use Outlook via the
Internet so again I think it is setup right.

Now the next thing you mention is the actual setup of Outlook 2003 to
connect to Exchange.  I have done this and I know it does work.  If I take
my laptop into work I can connect and read, send delete email just fine
connected with the RCP over HTTP option.  (I do have to change where it
points to seeing it on the private side of network when I do this)

So basically up to this point all your recommendations I have done and I
feel they are working right.  Yet when I take the laptop that works just
fine at work setup this way home and try to logon I still get the same
problem of it asking for the username/password over and over and never
connects.  I have tried using my account, the admin account and a test
account just to see if that helped what it did not.

Any thoughts as to what my next step may be?

Lee Smith

leeasmith2@hotmail.com

> First besure your Certificate is created and a FQDN
>
[quoted text clipped - 220 lines]
>>
>> leeasmith2@hotmail.com
"Charles Yang [MSFT]" - 29 Sep 2005 02:20 GMT
HI Lee,

Thanks for your updates.

From your description, I understand that when you use outlook at the office
via RPC over HTTP, you will not encountered the issue, if you use it over
internet, you will encountered the issue,

As I referred, this should be the authentication issue, in order to make
the issue more clear, please help double check the option below:

When the rpcproxy is unregisted and re-registered or the RPCProxy service
has been
uninstalled and reinstalled it resets the Valid Ports key in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\RpcProxy to 100-5000.  The
MSExchange
keys do not get altered in any way. but you will need to manually enter the
correct
values for Valid Ports which are listed below.

Troubleshooting Steps:

1. Verify that the patch from KB article 331320 has been applied to the
client
machine.
2.  Verify that the certificate is installed by going to
https://mydomain.com/remote or /owa.  You should not be  prompted for the
certificate.

3. Verify the following settings in the Outlook profile properties:

a.  The Exchange server name.  This should be the internal FQDN of the
exchange
server, example: Server.mydomain.local

b.  On the connection tab:
"Connect to my Exchange mailbox using HTTP" should be checked.

c.  In Exchange proxy settings:

The URL should be the same one as the FQDN of the certificate.  Example:  
http://mydomain.com
The "Connect Using SSL only" box should be checked.
The "Mutually authenticate the session when connecting with SSL" box should
be checked.
The Principal name for the proxy server should be the same as the FQDN on
the certificate.  Example:  msstd:mydomain.com.
The "On slow networks, connect using HTTP first, then connect using TCP/IP"
box should be checked.

d. Under Proxy Authentication the setting should be Basic Authentication.

Verify that the following registry keys exist with these settings:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\RpcProxy]
"Enabled"=dword:00000001
"ValidPorts"="<netbios name of server>:593;<netbios name of
server>6001-6002;<netbios name of server>:6004;f<Internal FQDN of
server>:593;<internal FQDN of server>:6001-6002;<internal FQDN of
server>:6004"

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\Parameters
System

Value: Rpc/HTTP Port
Type: REG_DWORD
Data: 0x00001771 (6001)

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeSA\Parameters
Value: HTTP Port
Type: REG_DWORD
Data: 0x00001772 (6002)

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeSA\Parameters
Value: Rpc/HTTP NSPI Port
Type: REG_DWORD
Data: 0x00001774 (6004)

Verify the settings for the RPC Virtual Directory in IIS, the defaults are
as
follows:

Local Path:  C:\Windows\System32\RPC Proxy
The following boxes are checked:  Log Visits, Index this resource
Application Name:  Default Application
Starting Point:  Default Website
Execute Permissions:  Scripts and Executables
Application Pool:  Default AppPool

Directory Security:

Authentication Methods:  Basic
Secure Communications:  Require Secure Channel is checked.  Require 128 bit
Encryption is checked.  Ignore Client Certificates is cehcked.

Verify that the RPCProxy.dll is present in the %systemroot%\System32\RPC
Proxy

If all the settings are correct you can use the RPCPing2 utility to assist
with the troubleshooting proccess.  This tool can help verify that the
connection type is good enough for RPC over HTTP.

If the completion time values are from, say 200 to 600 ms, then the
connection type is good.  If they are higher it could cause connection
problems.

The RPCPing2 utility is available from http://xcsi.  Click on the RPC over
HTTP link.
There are two files, a script file rpcping.exe and a .cmd file.
Extract the files to a folder on the C:\drive.
Go to a command prompt and change to the folder with the RPC files in it
then run the rpcping2.cmd from the command prompt with the following
parameters:

rpcping2 "Internal FQDN of Mailbox server" "Public URL of RPCProxy Server"
username domain

For example:  rpcping2 clt-msg-10.northamerica.corp.microsoft.com
mail.microsoft.com reneeg northamerica

You will be prompted for passwords.

Here is an example of successful output from rpcping:

C:\rpcping>rpcping2 clt-msg-10.northamerica.corp.microsoft.com
mail.microsoft.com reneeg northamerica

Executing with Command Line Parameters:
 ExchangeServerName = clt-msg-10.northamerica.corp.microsoft.com
 RPCProxyServerName = mail.microsoft.com
 UserName = reneeg
 Domain = northamerica

Action: RpcPing
--------------------------------------------------------------
 Authentication Level = Connect                (-a connect)
 Protocol Sequence    = ncacn_http             (-t ncacn_http)
 Security Package     = NTLM                   (-u 10)
 Verbose Level        = Maximum                (-v 3)
 Restrict to Proxy    = YES                    (-E)
 RPC/HTTP Flags       = SSL                    (-F 3)
 RPC/HTTP Auth Scheme = Basic                  (-H 1)
 HTTP Proxy           = None                   (-R none)
 RpcProxy             = mail.microsoft.com     (-o
RpcProxy=mail.microsoft.com)

Environment Variables
 ExchangeServerName   = (-s clt-msg-10.northamerica.corp.microsoft.com)
 RPCProxyServerName   = (RPCProxy=mail.microsoft.com)
 RPCProxy Auth Identity  = (-P "reneeg,northamerica,*")
 Exchange Auth Identity  = (-I "reneeg,northamerica,*")
RPCPing v2.12. Copyright (C) Microsoft Corporation, 2002
OS Version is: 5.2
Enter password for server:
Enter password for RPC/HTTP proxy:

RPCPinging proxy server mail.microsoft.com with Echo Request Packet
Sending ping to server
Response from server received: 200
Pinging successfully completed in 3437 ms

Here is an example of a bad RPCPing test:

C:\RPCPing>rpcping2 bengal.tiger.local 65.53.10.165 administrator tiger

Executing with Command Line Parameters:
 ExchangeServerName = bengal.tiger.local
 RPCProxyServerName = 65.53.10.165
 UserName = administrator
 Domain = tiger

Action: RpcPing
--------------------------------------------------------------
 Authentication Level = Connect                (-a connect)
 Protocol Sequence    = ncacn_http             (-t ncacn_http)
 Security Package     = NTLM                   (-u 10)
 Verbose Level        = Maximum                (-v 3)
 Restrict to Proxy    = YES                    (-E)
 RPC/HTTP Flags       = SSL                    (-F 3)
 RPC/HTTP Auth Scheme = Basic                  (-H 1)
 HTTP Proxy           = None                   (-R none)
 RpcProxy             = 65.53.10.165   (-o RpcProxy=65.53.10.165)
Environment Variables
 ExchangeServerName   = (-s bengal.tiger.local)
 RPCProxyServerName   = (RPCProxy=65.53.10.165)
 RPCProxy Auth Identity  = (-P "administrator,tiger,*")
 Exchange Auth Identity  = (-I "administrator,tiger,*")
RPCPing v2.12. Copyright (C) Microsoft Corporation, 2002
OS Version is: 5.1, Service Pack 1, QFE Q331320 present
Enter password for server:
Enter password for RPC/HTTP proxy:

RPCPinging proxy server 65.53.10.165 with Echo Request Packet
Sending ping to server
Response from server received: 404
Ping failed.

A 401 code is Access Denied (bad username or password)
A problem with the SSL certificate will also produce errors.  Here is the
output
when the installed certificate does not match the one on the server:

RPCPinging proxy server 65.53.10.165 with Echo Request Packet
Sending ping to server
Error 12175 returned in the WinHttpSendRequest.
Ping failed.

Please test according to the steps above at home to see if the problem
still exist or not you can try to connect your laptop to the external NIC
of SBS 2003 and do the test to see the results.

I appreciate your effort on this issue, please feel free to post back. I am
glad to be of assistance.

Best regards,

Charles Yang (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

Signature

======================================================
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.

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| From: "Lee Smith" <leeasmith2@hotmail.com>
| References: <OsQCE06wFHA.2008@TK2MSFTNGP10.phx.gbl>
<OAGFkc9wFHA.3720@TK2MSFTNGP11.phx.gbl>
| Subject: Re: Problems getting RCP over HTTP to work
| Date: Wed, 28 Sep 2005 13:10:37 -0600
[quoted text clipped - 17 lines]
|
| As to give some more details I will start with your open port suggestion.
I
| have systems in my home.  They all are using private IP address and 1 public
| IP.  That public IP has been setup on my Firebox x700 to allow ANY ANY for
[quoted text clipped - 222 lines]
| >> 6001, 6002 and 6004.  I also tried it with the 5000 and 5001.  I finally
| >> just did an any any rule for my test machine at my home.  Still no go.
I
| >> am hoping some one may have some ideas and/or suggestions as to what I
| >> could try to get this working.  I should mention if I run it at work it
[quoted text clipped - 32 lines]
| >>
| >> leeasmith2@hotmail.com
Lee Smith - 29 Sep 2005 20:01 GMT
Ok going over your steps I have checked things out.  The only thing that did
not match your example was the values in the ValidPorts.  I had to add the
593:NetBIOS name and 593:FQDN to the valid ports key.  Every thing else was
as it should be.  This includes the registry keys you pointed out as well as
the settings under IIS RPC settings.  I would like to try the RPCPing2
Utility you mention but I can not locate it.

http://xcsi does not bring up any thing that seems to lead to that.  More so
a search on Google, Lycos and on Microsoft page brings up no usable results
for RPCPing2.exe.  I do have the rpcping.exe in my C:\Program Files\Windows
Resource Kits\Tools directory.   If I try to use that from a dos window I
get Exception 5 (0x0000005).  If I run it from windows GUI it does come up
with a window prompting for information.  I put in my exchange server
NetBIOS name, local FQDN and even the local IP address.  No matter what
parameter I use I get an error 'Failed to Bind on ALL Protocols'.  This
happens on machines local and outside my network.  So hopping you can direct
me to another location to find the file you indicated.

Lastly I just wanted to point out after adding the 593 port in the validport
key I did try again on my home test bed.  The results have not changed but I
did notice it now takes about 30seconds to a min before it comes up and
prompts me for the username/password.  This used to come up instantly.  Don't
know what this means but figure give you any/all new information I have.

Lee Smith

leeasmith2@hotmail.com

> HI Lee,
>
[quoted text clipped - 626 lines]
> | >>
> | >> leeasmith2@hotmail.com
"Charles Yang [MSFT]" - 30 Sep 2005 10:51 GMT
HI Lee,

Thanks for updates.

For the RPC ping issue, it might be caused by the RPCping tools on your SBS
2003 is corrupted, you can download it again from the following link:

http://www.microsoft.com/downloads/details.aspx?displaylang=en&familyid=9d46
7a69-57ff-4ae7-96ee-b18c4790cffd

Here I would like to give you an KB article about how to use RPC ping tools
to test outlook connection with Exchange 2003:

831051 How to use the RPC Ping utility to troubleshoot connectivity issues
with
http://support.microsoft.com/?id=831051

I appreciate your understand on this issue, please feel free to test and
paste the results. I am glad to be of assistance.

Best regards,

Charles Yang (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

Signature

======================================================
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.

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| From: "Lee Smith" <leeasmith2@hotmail.com>
| References: <OsQCE06wFHA.2008@TK2MSFTNGP10.phx.gbl>
<OAGFkc9wFHA.3720@TK2MSFTNGP11.phx.gbl>
<O2Kzx$FxFHA.2620@TK2MSFTNGP09.phx.gbl>
<W3dv6PJxFHA.628@TK2MSFTNGXA01.phx.gbl>
| Subject: Re: Problems getting RCP over HTTP to work
| Date: Thu, 29 Sep 2005 13:01:20 -0600
[quoted text clipped - 103 lines]
| > server>:593;<internal FQDN of server>:6001-6002;<internal FQDN of
| > server>:6004"

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\Parameters
| > System
| >
| > Value: Rpc/HTTP Port
| > Type: REG_DWORD
| > Data: 0x00001771 (6001)

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeSA\Parameters
| > Value: HTTP Port
| > Type: REG_DWORD
| > Data: 0x00001772 (6002)

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeSA\Parameters
| > Value: Rpc/HTTP NSPI Port
| > Type: REG_DWORD
[quoted text clipped - 548 lines]
| > | >>
| > | >> leeasmith2@hotmail.com
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2012 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.