| Author |
Message |
Chuck Rich
Guest
|
 Posted:
Tue Jan 11, 2005 10:51 pm Post subject:
RPC-HTTP Almost There |
|
|
I'm running a single server Exchange 2003 SP1 config. I've managed to
connect successfully from outside the network using the Outlook 2003
Exchange Proxy config. However, the Exchange Server Connector keeps showing
either a connecting or disconnected state for "Directory." Everything else
connects fine. I can get to public folders and receive email fine. The
only thing it seems to affect is name lookups when you try to share personal
folders. What am I missing? My SSL cert is working otherwise I wouldn't be
able to connect at all. I have the correct registry setting on the server.
The RPC settings in IIS are set to spec. The server is set as a back end
server in System Manager and RPC Proxy is installed on the Exchange Server.
Keep in mind I only have one Exchange server and another Domain Controller.
The Exchange Server is configured as the Global Catalogue Server. So,
everything involved in RPC-HTTP is running on the Exchange Server.
Chuck Rich
|
|
| Back to top |
|
 |
Tim Hackbart [MSFT]
Guest
|
| Posted:
Wed Jan 12, 2005 2:33 am Post subject:
Re: RPC-HTTP Almost There |
|
|
It sounds like it might be your Valid Ports key and your Directory service
mapping
If you have a single Exchange server that is also a Global Catalog running
SP1 then you would still need to statically map your NTDS Directory service
to 6004 and manually create the Valid ports key. The best KB is:
833401 How to configure RPC over HTTP on a single server in Exchange Server
2003
http://support.microsoft.com/?id=833401
I would pay special attention to
"Step 1: To configure the RPC proxy server to use specific ports, follow
these steps. "
and
"Step 2: Configure all your global catalogs to use specific ports for RPC
over HTTP for directory services"
Since you are unable to connect to the directory service, make sure the
registry entry is correct as defined in Step 2.
Hope this helps
--
Tim Hackbart M.C.S.E.
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
"Chuck Rich" <crich@richtechllc.com> wrote in message
news:e7GtN3$9EHA.2180@TK2MSFTNGP12.phx.gbl...
| Quote: | I'm running a single server Exchange 2003 SP1 config. I've managed to
connect successfully from outside the network using the Outlook 2003
Exchange Proxy config. However, the Exchange Server Connector keeps
showing
either a connecting or disconnected state for "Directory." Everything
else
connects fine. I can get to public folders and receive email fine. The
only thing it seems to affect is name lookups when you try to share
personal
folders. What am I missing? My SSL cert is working otherwise I wouldn't
be
able to connect at all. I have the correct registry setting on the
server.
The RPC settings in IIS are set to spec. The server is set as a back end
server in System Manager and RPC Proxy is installed on the Exchange
Server.
Keep in mind I only have one Exchange server and another Domain
Controller.
The Exchange Server is configured as the Global Catalogue Server. So,
everything involved in RPC-HTTP is running on the Exchange Server.
Chuck Rich
|
|
|
| Back to top |
|
|
Chuck Rich
Guest
|
| Posted:
Wed Jan 12, 2005 7:00 am Post subject:
Re: RPC-HTTP Almost There |
|
|
Thanks for your help. I verified all the registry entries and they were
correct. However, after a fresh reboot of the Exchange Server, everything
is working nicely.
Thanks,
Chuck Rich
"Tim Hackbart [MSFT]" <Timhack@online.microsoft.com> wrote in message
news:OKqrazB%23EHA.3596@TK2MSFTNGP12.phx.gbl...
| Quote: | It sounds like it might be your Valid Ports key and your Directory service
mapping
If you have a single Exchange server that is also a Global Catalog running
SP1 then you would still need to statically map your NTDS Directory
service
to 6004 and manually create the Valid ports key. The best KB is:
833401 How to configure RPC over HTTP on a single server in Exchange
Server
2003
http://support.microsoft.com/?id=833401
I would pay special attention to
"Step 1: To configure the RPC proxy server to use specific ports, follow
these steps. "
and
"Step 2: Configure all your global catalogs to use specific ports for RPC
over HTTP for directory services"
Since you are unable to connect to the directory service, make sure the
registry entry is correct as defined in Step 2.
Hope this helps
--
Tim Hackbart M.C.S.E.
This posting is provided "AS IS" with no warranties, and confers no
rights.
Please do not send email directly to this alias. This alias is for
newsgroup
purposes only.
"Chuck Rich" <crich@richtechllc.com> wrote in message
news:e7GtN3$9EHA.2180@TK2MSFTNGP12.phx.gbl...
I'm running a single server Exchange 2003 SP1 config. I've managed to
connect successfully from outside the network using the Outlook 2003
Exchange Proxy config. However, the Exchange Server Connector keeps
showing
either a connecting or disconnected state for "Directory." Everything
else
connects fine. I can get to public folders and receive email fine. The
only thing it seems to affect is name lookups when you try to share
personal
folders. What am I missing? My SSL cert is working otherwise I wouldn't
be
able to connect at all. I have the correct registry setting on the
server.
The RPC settings in IIS are set to spec. The server is set as a back end
server in System Manager and RPC Proxy is installed on the Exchange
Server.
Keep in mind I only have one Exchange server and another Domain
Controller.
The Exchange Server is configured as the Global Catalogue Server. So,
everything involved in RPC-HTTP is running on the Exchange Server.
Chuck Rich
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in