O2k3 Connection Status not showing HTTPS

[Brian Madden]

Hello All,

I'm trying to configure Outlook 2003 to use RPC over HTTP. I've configured
the server and client as per the documentation, but I can't connect.

One thing that I notice is that in the Connection Status (by CTRL-right
clicking the Outlook icon in the system tray), it always shows TCP/IP. I
would think that this should indicate either HTTP or HTTPS.

I have both the "fast" and "slow" options checked for the "connect first
using HTTP, then connect using TCP/IP.

Is is possible for me to force O2k3 to user HTTP only, and to completely
remove any chance of using TCP/IP? Also, any recommended log files that let
me see what's actually happening, or should I break out netmon?

Thanks,
Brian

 

[Brian Madden]

Update:

Well, I went ahead and did a packet trace, and it looks like all my
communication is taking place over 443. <sigh> Of course this is a good
thing as far as Outlook is concerned, but I'm not any closer to solving my
problem.

Thanks,
Brian

 

[neo [mvp outlook]]

Since you mentioned that you configured the settings per the documentation,
is it safe for me to assume that you followed the Exchange 2003 Deployment
guide (pages 177-181)? The reason that I ask is that I forgot to modify the
registry on the Global Catalog. I think it is one of the easiest steps to
miss. (You need to modify the registry and reboot the server.)

The other thing to watch for is that the only authentication that works is
Basic Auth. The RPC IIS virtual folder must be configured to accept basic
auth as well as setting that as your option in Outlook. (I will assume that
you are using an internal CA and that your test workstation has the sites
root certificate installed. Outlook doesn't throw a security warning when
making a SSL connection and it can't find the signing root certificate.
Outlook just fails the connection and falls to making a standard RPC call.)

Outside of that, you can bring the rpc connection dialog up right at
outlook's startup by starting outlook with the /rpcdiag command line switch.
It should help you see if it is getting hung up on connecting to the GC.

--
Neo [MVP Outlook]
Due to the Swen virus, all e-mails sent to this account will be deleted
w/out reading.

PS - No to your two last questions and yes, netmon is the only way to see
what is going on in communications.