A Microsoft Outlook email forum. Outlook Banter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » Outlook Banter forum » Microsoft Outlook Email Newsgroups » Outlook - Installation
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

RPC Over HTTP cannot connect



 
 
Thread Tools Search this Thread Display Modes
  #1  
Old October 12th 06, 07:29 PM posted to microsoft.public.outlook.installation
Deanna
external usenet poster
 
Posts: 12
Default 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
  #2  
Old October 12th 06, 08:26 PM posted to microsoft.public.outlook.installation
neo [mvp outlook]
external usenet poster
 
Posts: 293
Default RPC Over HTTP cannot connect

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



  #3  
Old October 12th 06, 09:17 PM posted to microsoft.public.outlook.installation
Deanna
external usenet poster
 
Posts: 12
Default RPC Over HTTP cannot connect

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




  #4  
Old October 13th 06, 12:23 AM posted to microsoft.public.outlook.installation
neo [mvp outlook]
external usenet poster
 
Posts: 293
Default RPC Over HTTP cannot connect

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






  #5  
Old October 13th 06, 05:03 PM posted to microsoft.public.outlook.installation
Deanna
external usenet poster
 
Posts: 12
Default RPC Over HTTP cannot connect

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






  #6  
Old October 13th 06, 05:38 PM posted to microsoft.public.outlook.installation
neo [mvp outlook]
external usenet poster
 
Posts: 293
Default RPC Over HTTP cannot connect

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








 




Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
RPC Over HTTP Outlook cannot connect Deanna Outlook - Installation 0 October 12th 06 07:24 PM
RPC over HTTP Alex Baker Outlook - Installation 1 September 21st 06 09:54 PM
Outlook 2007 RPC-HTTP Cannot Connect Jay Outlook - Installation 1 June 26th 06 02:10 AM
RPC over HTTP Jerry Outlook - Installation 0 April 5th 06 05:11 PM
rpc over http jmiller Outlook - Installation 2 February 5th 06 03:09 PM


All times are GMT +1. The time now is 11:48 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.Search Engine Friendly URLs by vBSEO 2.4.0
Copyright ©2004-2025 Outlook Banter.
The comments are property of their posters.