Link to home
Start Free TrialLog in
Avatar of pepps11976
pepps11976

asked on

Exchange 2003 Windows XP and Office 2007

We have an issue where a company we are supporting has there mail on a hosted mail server, this is only happening with XP Users, when they try to connect to Exchange 2013 they are continually prompted for Username and password, and it does not connect even though the credentials are right.

I know XP support has ended but I need to get this working, they have latest SP for Both XP and for office

Any help guys much appreciated
Avatar of Scott C
Scott C
Flag of United States of America image

Has this always been the case or has this worked in the past?

What happens if you use a new client?  WIn 7 and office 2013?
Avatar of pepps11976
pepps11976

ASKER

This has just happened since we have switched to Exchange 2013 from Exchange 2007, works fine with other office I am thinking its an XP security thing
Hi.
You try to do the following?
The problem actually was in the SAN certificate, mainly on the Subject Alternative Names field. Put on that field as 1st line not webmail.domainname.com put domainname.com. So Exchange was presenting itself to XP machines wrongly and it seems that XP is not willing to look at next lines on a SAN certificate. Windows 7 thou does it, therefore that problem never happened on Windows 7. So after I used that command:

Set-OutlookProvider EXPR -CertPrincipalName:"msstd:mydomain.com"
ASKER CERTIFIED SOLUTION
Avatar of Scott C
Scott C
Flag of United States of America 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
ScottCha as much as I agree with you this is not going to be an option, some companies simply will not part with money that easily :(

Guillermo Rodrigo Gil, if I was to set that command how could I roll it back if this caused further issues?