Outlook 2003 RPC over HTTPS breaks after Windows 2003 SP1 applied on client

R

Randall Hertzler

Have Exchange 2003 running on SBS2003 and has been running great for over a
year. Many users use Outlook 2003 remotely using RPC over HTTPS with no
problem. Then one user running Windows Server 2003 STD on a laptop (a client
machine) applied the new SP1 and Outlook connection over HTTPS is broken.

First it didn't seem to want to connect at all. Then we got it to connect
after trying the username as (e-mail address removed) instead of domain\user. But
then the password dialog would pop up every few minutes or so. Sometimes it
would be satisfied and go away and other time came back repeatedly. So I
opened the connection status window and saw that the three "mail"
connections were listed as "established", but the two directory connections
were "disconnected". When clicking the reconnect button, we got the
authentication request again and would end up in the same situation.

Event logs on the client show nothing. Event logs on the server show
successful logons and then logoffs. Another strange thing is that in the
connection status window, the two directory listings showing as disconnected
list the server name as "--" and then "name" where the mail listings show
the server name as name.domain.com.

On the client that just received SP1, we turned off the firewall to take
that out of the equation. Also, the client and the server both received the
recent security fixes via auto-update.

Any ideas where to look on this one or should I just scrap SP1 on the
client? Thanks for any help.

Randall Hertzler
bigwindow.net
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top