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 now
broken.
The Outlook authentication request appears again and again - it is never
satisfied. Tried running it as "outlook /rpcdiag" and don't get any
additional information that is helpful. Just simply does not authenticate.
Had Virtual PC running on the Windows 2003 machine so we tried using Outlook
2003 from within VPC (On XP as the host OS) and everything was fine.
The firewall is off on Windows 2003. Event logs on the client show nothing.
Event logs on the server show nothing either. Even the log file from IIS on
the RPC directory seems to have everything correct - a 200 response from IIS
on RPC_IN_DATA and RPC_OUT_DATA. And I have gone through KB article 833401
more than once to make sure everything is OK. Also fooled with the new
registry settings for RPC security to no avail.
So is is definitely a problem with using Outlook 2003 with RPC over HTTP on
a Windows 2003 SP1 client.
Any ideas where to look on this one or should I just scrap SP1 on the
client? Thanks for any help.
Randall Hertzler
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 now
broken.
The Outlook authentication request appears again and again - it is never
satisfied. Tried running it as "outlook /rpcdiag" and don't get any
additional information that is helpful. Just simply does not authenticate.
Had Virtual PC running on the Windows 2003 machine so we tried using Outlook
2003 from within VPC (On XP as the host OS) and everything was fine.
The firewall is off on Windows 2003. Event logs on the client show nothing.
Event logs on the server show nothing either. Even the log file from IIS on
the RPC directory seems to have everything correct - a 200 response from IIS
on RPC_IN_DATA and RPC_OUT_DATA. And I have gone through KB article 833401
more than once to make sure everything is OK. Also fooled with the new
registry settings for RPC security to no avail.
So is is definitely a problem with using Outlook 2003 with RPC over HTTP on
a Windows 2003 SP1 client.
Any ideas where to look on this one or should I just scrap SP1 on the
client? Thanks for any help.
Randall Hertzler