RPC Over HTTP cannot connect

I have configured my Exchange 2003 SP2 server with RPC Over HTTP and tested
the connection and certificate. It all works fine. I have configured a
remote client's Outlook to access the Exchange server over HTTP with Basic
Authentication because the Exchange server is behind a firewall. When I try
to connect the Outlook I am prompted for a user name and password which I
provide. After about a 2 minute wait Outlook returns the following error
"The connection to the Microsoft Exchange Server in unavailable. Outlook
must be online or connected to complete this action."

Any ideas would be appreciated.

Deanna

Are you working with a single server or a FE/BE configuration?


"Deanna" wrote in message
...
I have configured my Exchange 2003 SP2 server with RPC Over HTTP and tested
the connection and certificate. It all works fine. I have configured a
remote client's Outlook to access the Exchange server over HTTP with Basic
Authentication because the Exchange server is behind a firewall. When I
try
to connect the Outlook I am prompted for a user name and password which I
provide. After about a 2 minute wait Outlook returns the following error
"The connection to the Microsoft Exchange Server in unavailable. Outlook
must be online or connected to complete this action."

Any ideas would be appreciated.

Deanna

It is a single server environment.

"neo [mvp outlook]" wrote:

Are you working with a single server or a FE/BE configuration?


"Deanna" wrote in message
...
I have configured my Exchange 2003 SP2 server with RPC Over HTTP and tested
the connection and certificate. It all works fine. I have configured a
remote client's Outlook to access the Exchange server over HTTP with Basic
Authentication because the Exchange server is behind a firewall. When I
try
to connect the Outlook I am prompted for a user name and password which I
provide. After about a 2 minute wait Outlook returns the following error
"The connection to the Microsoft Exchange Server in unavailable. Outlook
must be online or connected to complete this action."

Any ideas would be appreciated.

Deanna

Assuming you are running Exchange 2003 with Service Pack 2, you will need to
go into Exchange System Manager and specify that said server is a Backend
server. (Open ESM and drill to the server. R-click on it and select
properties. Go to RPC-HTTP tab. Radio button at bottom for backend server.
If not at SP2 for Exchange 2003, post back because you will need to create
some registry keys on the Exchange server + Windows 2003 DC/GCs.)

"Deanna" wrote in message
...
It is a single server environment.

"neo [mvp outlook]" wrote:

Are you working with a single server or a FE/BE configuration?


"Deanna" wrote in message
...
I have configured my Exchange 2003 SP2 server with RPC Over HTTP and
tested
the connection and certificate. It all works fine. I have configured
a
remote client's Outlook to access the Exchange server over HTTP with
Basic
Authentication because the Exchange server is behind a firewall. When
I
try
to connect the Outlook I am prompted for a user name and password which
I
provide. After about a 2 minute wait Outlook returns the following
error
"The connection to the Microsoft Exchange Server in unavailable.
Outlook
must be online or connected to complete this action."

Any ideas would be appreciated.

Deanna

My mistake, it is Exchange 2003 SP1, not SP2. the backend server option is
selected. Can you send me the registry hacks? Thanks.

Deanna

"neo [mvp outlook]" wrote:

Assuming you are running Exchange 2003 with Service Pack 2, you will need to
go into Exchange System Manager and specify that said server is a Backend
server. (Open ESM and drill to the server. R-click on it and select
properties. Go to RPC-HTTP tab. Radio button at bottom for backend server.
If not at SP2 for Exchange 2003, post back because you will need to create
some registry keys on the Exchange server + Windows 2003 DC/GCs.)

"Deanna" wrote in message
...
It is a single server environment.

"neo [mvp outlook]" wrote:

Are you working with a single server or a FE/BE configuration?


"Deanna" wrote in message
...
I have configured my Exchange 2003 SP2 server with RPC Over HTTP and
tested
the connection and certificate. It all works fine. I have configured
a
remote client's Outlook to access the Exchange server over HTTP with
Basic
Authentication because the Exchange server is behind a firewall. When
I
try
to connect the Outlook I am prompted for a user name and password which
I
provide. After about a 2 minute wait Outlook returns the following
error
"The connection to the Microsoft Exchange Server in unavailable.
Outlook
must be online or connected to complete this action."

Any ideas would be appreciated.

Deanna

Selecting backend server on that RPC-HTTP should create the following
registry keys on the Exchange server.


HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\MSExchangeIS\ParametersSystem
Value name: Rpc/HTTP Port
Value type: REG_DWORD
Value data: 0x1771 (Decimal 6001)


HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\MSExchangeSA\Parameters
Value name: HTTP Port
Value type: REG_DWORD
Value data: 0x1772 (Decimal 6002)


HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\MSExchangeSA\Parameters
Value name: Rpc/HTTP NSPI Port
Value type: REG_DWORD
Value data: 0x1774 (Decimal 6004)


HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\RpcProxy
Value name: ValidPorts
Value type: REG_SZ
Value data:
ExchangeServer:6001-6002;ExchangeServerFQDN:6001-6002;ExchangeServer:6004;ExchangeServerFQDN:6004

HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\RpcProxy
Value name: Enabled
Value type: REG_DWORD
Value data: 1


/neo

PS - There is nothing that needs to be changed on your Windows 2003 GCs
because Exchange 2003 SP1 & later is going to act as the proxy for directory
(gal) stuff. If the registry keys exists, then the next step is to reboot.

PSS - Outside of that, I'm assuming that you don't have any problems with
SSL certificate on the server. (Meaning client workstation can validate that
certificate back to the issuing CA.)



"Deanna" wrote in message
news
My mistake, it is Exchange 2003 SP1, not SP2. the backend server option is
selected. Can you send me the registry hacks? Thanks.

Deanna

"neo [mvp outlook]" wrote:

Assuming you are running Exchange 2003 with Service Pack 2, you will need
to
go into Exchange System Manager and specify that said server is a Backend
server. (Open ESM and drill to the server. R-click on it and select
properties. Go to RPC-HTTP tab. Radio button at bottom for backend
server.
If not at SP2 for Exchange 2003, post back because you will need to
create
some registry keys on the Exchange server + Windows 2003 DC/GCs.)

"Deanna" wrote in message
...
It is a single server environment.

"neo [mvp outlook]" wrote:

Are you working with a single server or a FE/BE configuration?


"Deanna" wrote in message
...
I have configured my Exchange 2003 SP2 server with RPC Over HTTP and
tested
the connection and certificate. It all works fine. I have
configured
a
remote client's Outlook to access the Exchange server over HTTP with
Basic
Authentication because the Exchange server is behind a firewall.
When
I
try
to connect the Outlook I am prompted for a user name and password
which
I
provide. After about a 2 minute wait Outlook returns the following
error
"The connection to the Microsoft Exchange Server in unavailable.
Outlook
must be online or connected to complete this action."

Any ideas would be appreciated.

Deanna

The registry key for this shows the following data:

HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\RpcProxy
Value name: ValidPorts
Value type: REG_SZ
Value data:
servername:100-5000

instead of
ExchangeServer:6001-6002;ExchangeServerFQDN:6001-6002;ExchangeServer:6004;ExchangeServerFQDN:6004.
All other registry keys are there and I have not rebooted the Exchange
server since I implemented this.


"neo [mvp outlook]" wrote:

Selecting backend server on that RPC-HTTP should create the following
registry keys on the Exchange server.


HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\MSExchangeIS\ParametersSystem
Value name: Rpc/HTTP Port
Value type: REG_DWORD
Value data: 0x1771 (Decimal 6001)


HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\MSExchangeSA\Parameters
Value name: HTTP Port
Value type: REG_DWORD
Value data: 0x1772 (Decimal 6002)


HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\MSExchangeSA\Parameters
Value name: Rpc/HTTP NSPI Port
Value type: REG_DWORD
Value data: 0x1774 (Decimal 6004)


HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\RpcProxy
Value name: ValidPorts
Value type: REG_SZ
Value data:
ExchangeServer:6001-6002;ExchangeServerFQDN:6001-6002;ExchangeServer:6004;ExchangeServerFQDN:6004

HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\RpcProxy
Value name: Enabled
Value type: REG_DWORD
Value data: 1


/neo

PS - There is nothing that needs to be changed on your Windows 2003 GCs
because Exchange 2003 SP1 & later is going to act as the proxy for directory
(gal) stuff. If the registry keys exists, then the next step is to reboot.

PSS - Outside of that, I'm assuming that you don't have any problems with
SSL certificate on the server. (Meaning client workstation can validate that
certificate back to the issuing CA.)



"Deanna" wrote in message
news
My mistake, it is Exchange 2003 SP1, not SP2. the backend server option is
selected. Can you send me the registry hacks? Thanks.

Deanna

"neo [mvp outlook]" wrote:

Assuming you are running Exchange 2003 with Service Pack 2, you will need
to
go into Exchange System Manager and specify that said server is a Backend
server. (Open ESM and drill to the server. R-click on it and select
properties. Go to RPC-HTTP tab. Radio button at bottom for backend
server.
If not at SP2 for Exchange 2003, post back because you will need to
create
some registry keys on the Exchange server + Windows 2003 DC/GCs.)

"Deanna" wrote in message
...
It is a single server environment.

"neo [mvp outlook]" wrote:

Are you working with a single server or a FE/BE configuration?


"Deanna" wrote in message
...
I have configured my Exchange 2003 SP2 server with RPC Over HTTP and
tested
the connection and certificate. It all works fine. I have
configured
a
remote client's Outlook to access the Exchange server over HTTP with
Basic
Authentication because the Exchange server is behind a firewall.
When
I
try
to connect the Outlook I am prompted for a user name and password
which
I
provide. After about a 2 minute wait Outlook returns the following
error
"The connection to the Microsoft Exchange Server in unavailable.
Outlook
must be online or connected to complete this action."

Any ideas would be appreciated.

Deanna

Okay, so you will need to edit the ValidPorts registry value. Where I have
ExchangeServer or ExchangeServerFQDN, you need to replace it with the name
of your exchange server. Example so this makes sense, assume that name of
the Exchange server is MBX that is part of the consoto.com domain, then the
ValidPorts key would be:

mbx:6001-6002;mbx.constoso.com:6001-6002;mbx:6004;mbx.contoso.com:6004


"Deanna" wrote in message
...
The registry key for this shows the following data:

HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\RpcProxy
Value name: ValidPorts
Value type: REG_SZ
Value data:
servername:100-5000

instead of
ExchangeServer:6001-6002;ExchangeServerFQDN:6001-6002;ExchangeServer:6004;ExchangeServerFQDN:6004.
All other registry keys are there and I have not rebooted the Exchange
server since I implemented this.


"neo [mvp outlook]" wrote:

Selecting backend server on that RPC-HTTP should create the following
registry keys on the Exchange server.


HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\MSExchangeIS\ParametersSystem
Value name: Rpc/HTTP Port
Value type: REG_DWORD
Value data: 0x1771 (Decimal 6001)


HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\MSExchangeSA\Parameters
Value name: HTTP Port
Value type: REG_DWORD
Value data: 0x1772 (Decimal 6002)


HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\MSExchangeSA\Parameters
Value name: Rpc/HTTP NSPI Port
Value type: REG_DWORD
Value data: 0x1774 (Decimal 6004)


HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\RpcProxy
Value name: ValidPorts
Value type: REG_SZ
Value data:
ExchangeServer:6001-6002;ExchangeServerFQDN:6001-6002;ExchangeServer:6004;ExchangeServerFQDN:6004

HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\RpcProxy
Value name: Enabled
Value type: REG_DWORD
Value data: 1


/neo

PS - There is nothing that needs to be changed on your Windows 2003 GCs
because Exchange 2003 SP1 & later is going to act as the proxy for
directory
(gal) stuff. If the registry keys exists, then the next step is to
reboot.

PSS - Outside of that, I'm assuming that you don't have any problems with
SSL certificate on the server. (Meaning client workstation can validate
that
certificate back to the issuing CA.)



"Deanna" wrote in message
news
My mistake, it is Exchange 2003 SP1, not SP2. the backend server option
is
selected. Can you send me the registry hacks? Thanks.

Deanna

"neo [mvp outlook]" wrote:

Assuming you are running Exchange 2003 with Service Pack 2, you will
need
to
go into Exchange System Manager and specify that said server is a
Backend
server. (Open ESM and drill to the server. R-click on it and select
properties. Go to RPC-HTTP tab. Radio button at bottom for backend
server.
If not at SP2 for Exchange 2003, post back because you will need to
create
some registry keys on the Exchange server + Windows 2003 DC/GCs.)

"Deanna" wrote in message
...
It is a single server environment.

"neo [mvp outlook]" wrote:

Are you working with a single server or a FE/BE configuration?


"Deanna" wrote in message
...
I have configured my Exchange 2003 SP2 server with RPC Over HTTP
and
tested
the connection and certificate. It all works fine. I have
configured
a
remote client's Outlook to access the Exchange server over HTTP
with
Basic
Authentication because the Exchange server is behind a firewall.
When
I
try
to connect the Outlook I am prompted for a user name and password
which
I
provide. After about a 2 minute wait Outlook returns the
following
error
"The connection to the Microsoft Exchange Server in unavailable.
Outlook
must be online or connected to complete this action."

Any ideas would be appreciated.

Deanna

That didn't change anything, I still got the same error from Outlook. I will
try to reboot the server this weekend. Thanks.

Deanna

"neo [mvp outlook]" wrote:

Okay, so you will need to edit the ValidPorts registry value. Where I have
ExchangeServer or ExchangeServerFQDN, you need to replace it with the name
of your exchange server. Example so this makes sense, assume that name of
the Exchange server is MBX that is part of the consoto.com domain, then the
ValidPorts key would be:

mbx:6001-6002;mbx.constoso.com:6001-6002;mbx:6004;mbx.contoso.com:6004


"Deanna" wrote in message
...
The registry key for this shows the following data:

HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\RpcProxy
Value name: ValidPorts
Value type: REG_SZ
Value data:
servername:100-5000

instead of
ExchangeServer:6001-6002;ExchangeServerFQDN:6001-6002;ExchangeServer:6004;ExchangeServerFQDN:6004.
All other registry keys are there and I have not rebooted the Exchange
server since I implemented this.


"neo [mvp outlook]" wrote:

Selecting backend server on that RPC-HTTP should create the following
registry keys on the Exchange server.


HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\MSExchangeIS\ParametersSystem
Value name: Rpc/HTTP Port
Value type: REG_DWORD
Value data: 0x1771 (Decimal 6001)


HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\MSExchangeSA\Parameters
Value name: HTTP Port
Value type: REG_DWORD
Value data: 0x1772 (Decimal 6002)


HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\MSExchangeSA\Parameters
Value name: Rpc/HTTP NSPI Port
Value type: REG_DWORD
Value data: 0x1774 (Decimal 6004)


HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\RpcProxy
Value name: ValidPorts
Value type: REG_SZ
Value data:
ExchangeServer:6001-6002;ExchangeServerFQDN:6001-6002;ExchangeServer:6004;ExchangeServerFQDN:6004

HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\RpcProxy
Value name: Enabled
Value type: REG_DWORD
Value data: 1


/neo

PS - There is nothing that needs to be changed on your Windows 2003 GCs
because Exchange 2003 SP1 & later is going to act as the proxy for
directory
(gal) stuff. If the registry keys exists, then the next step is to
reboot.

PSS - Outside of that, I'm assuming that you don't have any problems with
SSL certificate on the server. (Meaning client workstation can validate
that
certificate back to the issuing CA.)



"Deanna" wrote in message
news My mistake, it is Exchange 2003 SP1, not SP2. the backend server option
is
selected. Can you send me the registry hacks? Thanks.

Deanna

"neo [mvp outlook]" wrote:

Assuming you are running Exchange 2003 with Service Pack 2, you will
need
to
go into Exchange System Manager and specify that said server is a
Backend
server. (Open ESM and drill to the server. R-click on it and select
properties. Go to RPC-HTTP tab. Radio button at bottom for backend
server.
If not at SP2 for Exchange 2003, post back because you will need to
create
some registry keys on the Exchange server + Windows 2003 DC/GCs.)

"Deanna" wrote in message
...
It is a single server environment.

"neo [mvp outlook]" wrote:

Are you working with a single server or a FE/BE configuration?


"Deanna" wrote in message
...
I have configured my Exchange 2003 SP2 server with RPC Over HTTP
and
tested
the connection and certificate. It all works fine. I have
configured
a
remote client's Outlook to access the Exchange server over HTTP
with
Basic
Authentication because the Exchange server is behind a firewall.
When
I
try
to connect the Outlook I am prompted for a user name and password
which
I
provide. After about a 2 minute wait Outlook returns the
following
error
"The connection to the Microsoft Exchange Server in unavailable.
Outlook
must be online or connected to complete this action."

Any ideas would be appreciated.

Deanna