Re: RPC over HTTPS Exchange 2007
- From: "David" <david@xxxxxxxxx>
- Date: Tue, 18 Sep 2007 16:09:05 -0400
I had to open ports 6000 through 6004 from our Exchange server to our Domain
Controllers. That fixed it.
"David" <david@xxxxxxxxx> wrote in message
news:uRg3RHU%23HHA.4568@xxxxxxxxxxxxxxxxxxxxxxx
Both clients are Outlook 2003.
"David" <david@xxxxxxxxx> wrote in message
news:OqS6auT%23HHA.5464@xxxxxxxxxxxxxxxxxxxxxxx
Hi All,
I am trying to get my RPC over HTTPS working, but I am having a slight
issue with it. I configured a client on the LAN and connected up using
outlook.exe /rpcdiag. Over the LAN the client connected no problem and
the connection said HTTPS. When I try to configure a client to connect
from external the client times out when trying to communicate with our
server. I have ports 80 and 443 opened from the web to the Exchange
server and the traffic is making it there. The problem I am having is
with the authentication part of the process. When I open outlook it
tries to authenticate to our Exchange and opens an enter username and
password box. The traffic never makes it to the Exchange server. I see
the request bouncing off my firewall on port 135. I think this is due to
a virtual directory misconfiguration. I don't know why it is trying to
authenticate over this port. Any ideas? Outlook Web Access works
perfectly over port 443.
Thanks,
Dave
A+, Network+, MCP
.
- References:
- RPC over HTTPS Exchange 2007
- From: David
- Re: RPC over HTTPS Exchange 2007
- From: David
- RPC over HTTPS Exchange 2007
- Prev by Date: Re: Publishing Custom forms in Exchange 2007 SP1 Beta 2
- Next by Date: Re: NDR Spam Attach? Help!!!
- Previous by thread: Re: RPC over HTTPS Exchange 2007
- Next by thread: Re: set up with /disasterrecovery
- Index(es):
Relevant Pages
|
