Link to home
Start Free TrialLog in
Avatar of andrew_2706
andrew_2706

asked on

Outlook 2007 asks for password on Outlook Anywhere but Outlook 2010 is ok

Exchange 2010 Version: 14.02.0247.005

2008 R2 Enterprise

Outlook 2007 persistently asks  for password on Outlook Anywhere and even if the details are enter it's not accepted as been correct but Outlook 2010 works ok.

I've tried changing the following key HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\RPC  to 1 as per http://support.microsoft.com/kb/956531 but without success.
Avatar of Haresh Nikumbh
Haresh Nikumbh
Flag of India image

Avatar of andrew_2706
andrew_2706

ASKER

yes as above as it's in that kb 956531
And i hope you have already verified  "Integrated Windows Authentication" setting in IIS correct?
Windows Authentication on Autodiscover is enabled
ASKER CERTIFIED SOLUTION
Avatar of Haresh Nikumbh
Haresh Nikumbh
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I get a warning with this
Testing NSPI "Check Name" for user ted@****.eu against server ***-EXCHANGE.******.
       The test passed with some warnings encountered. Please expand the additional details.
              
      Additional Details
       NspiBind returned ecNotSupported. This typically indicates that your server requires RPC encryption. The Microsoft Connectivity Analyzer will attempt the NSPI test again with encryption.
      Testing NSPI "Check Name" for user ted@****.eu against server ***-EXCHANGE.******.
       Check Name succeeded.
Found a solution for now.

In email account on Outlook 2007, advanced settings, proxy settings. Untick Only connect to proxy servers that have this principle name.........

The principle name is different although the new email domain is in the certificate as an alternative name.
Good 2 know you found solution
This pointed me towards the fact that in Outlook the "Only connect to proxy servers with this principle name" was ticked and the domain is actually an SAN on the certificate so it stopped it from working.