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.
andrew_2706Asked:
Who is Participating?
 
Haresh NikumbhConnect With a Mentor Sr. Tech leadCommented:
Please run

http://www.testexchangeconnectivity.com/

and check if it gives any additional information
0
 
Haresh NikumbhSr. Tech leadCommented:
0
 
andrew_2706Author Commented:
yes as above as it's in that kb 956531
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
Haresh NikumbhSr. Tech leadCommented:
And i hope you have already verified  "Integrated Windows Authentication" setting in IIS correct?
0
 
andrew_2706Author Commented:
Windows Authentication on Autodiscover is enabled
0
 
andrew_2706Author Commented:
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.
0
 
andrew_2706Author Commented:
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.
0
 
Haresh NikumbhSr. Tech leadCommented:
Good 2 know you found solution
0
 
andrew_2706Author Commented:
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.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.