We have an Exchange 2003 where we recently implemented SSL access by purchasing an SSL certificate from a trusted vendor. We got several calls from clients afterwards complaining that they get prompted occasionally for their login credentials in Outlook even if they have logged in to the domain using the same login accounts. Any thoughts on this?

Are they able to reproduce the error? There is a settin in outlook profile , if tht is set, outlook will prompt for username and pwd. Thiyagu | MCTS/MCITP - Exchange 2007 | MCSE 2003[Messaging] | http://www.myExchangeWorld.com. This posting is provided "AS IS" with no warranties, and confers no rights.

I have checked the Outlook Profile settings are they are fine. This all started when we started using an SSL certificate for RPC-Over-HTTP froma trusted vendor.

Hi VeBok, Do you mean the user use the client which joined into your domain and use the outlook with using RPC-Over-HTTP to connect to your exchage server? If the client in your local domain, did you make a test using mapi directly, what is the result. I would suggest that you do not need RPC-Over-HTTP in your local domain for your clients. And what authentication method do you configed on your exchange server and client, is it NTLM? Regards! Gavin

Gavin, The internal users don't use RPC-Over-HTTP. They are set up in Outlook with he usual settings for Exchange connectivity. RPC-Over-HTTP works fine externally and so does OWA. The problem is INTERNALLY. Outlook users get prompted for password every now and then especially when sending emails. OWA doesn't work at all.

Some questions.... When you say "OWA doesn't work at all" do you mean they can't *access* OWA now? Is the problem with Outlook entirely reproducible? Are you using the same internal + external domain name? How did you install your SSL cert? You shouldn't need to require encryption internally.Lanwench [MVP - Exchange] ** Do not fold, spindle or mutilate. Fill in the box completely and erase any stray marks. Use only a #2 pencil.

Some questions.... When you say "OWA doesn't work at all" do you mean they can't *access* OWA now? Is the problem with Outlook entirely reproducible? Are you using the same internal + external domain name? How did you install your SSL cert? You shouldn't need to require encryption internally.Lanwench [MVP - Exchange] ** Do not fold, spindle or mutilate. Fill in the box completely and erase any stray marks. Use only a #2 pencil.

Client of ours is having a similar issue. OWA works fine. Users who use RPC over HTTPS currently are also fine. The 2 issues are: New RPC over HTTPS clients are not authenticating properly. Meaning, it responds with Exchange must be online. The other issue being, users internally are prompted randomly for their credentials. The work around for the internal users is to set their client to only use NTLM. My hunch is that this is related to the wildcard cert on the front end server. As for the first issue. I have attempted using *.domain.com for principal name within outlook client settings - no luck. I also tested with the Exchange Remote Connectivity Analyzer. It fails at testing port 6004 with "The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process." Not sure why since the port is open, the backend server server is listening on 6004 according to netstat and rpcdump, and I can telnet from the front end to the backend on 6004. Rpcping fails however with Exception 1722 which by the looks of KB831051 simply means i need port 593 (EMP) in order to test. Sorry for dumping random information and possible stealing this post but I feel the issue is similar. Thanks in advance.