jdewing
Feb 24, 2011Cirrus
RPC Client Access
I'm having an issue getting outlook client to work with RPC Client Access. I follow the steps from the F5 Deployment Guide "Microsoft Exchange 2010". Everything is working with OWA and Hub Transport,...
We are seeing a similar issue.
We have 2 Client Access Servers and we have also set up CASARRAY.company.com. Casarray is pointed to F5. Following is the issue we are seeing: -
User is conected via LAN.
User opens up Outlook it asks for ID and password.
Once you provide ID and password it works but problem is why it is asking for ID and password when user is connected on LAN we have checked there are no delays on LAN.
When we right click on Outlook Icon in system Tray and click on "Connection Status" it shows some of the connections are going via TCP/IP and some HTTPS.
I think is the reason it prompots for ID and password because some or one of the connections going via Outlook Anywhere (RPC over HTTPs).
If we connect directly to CAS server all the connections goes via TCP/IP and it never asks for Password prompt.
My question is what could be the cause of mixed connections TCP/IP and HTTPS?
Thanks,
Regards
Raman