newgentechnologies
asked on
RPC over HTTP won't authenticate with Outlook 2007
A customer of mine cannot connect to his company's Exchange server with RCP. I have tested connecting with all the same authentication information on my own computer, and it worked. RPC connections work for everyone else in the company as well.
I logged into his computer with the local administrator account and tried again to connect with RCP over HTTP, but it keeps just asking for the domain\username and the password when I click on Check Name.
Sembee and others, your help is most appreciated here. We're pretty much at the point of reinstalling the Office suite, but would like to figure this out before we take that route.
Thank you,
I logged into his computer with the local administrator account and tried again to connect with RCP over HTTP, but it keeps just asking for the domain\username and the password when I click on Check Name.
Sembee and others, your help is most appreciated here. We're pretty much at the point of reinstalling the Office suite, but would like to figure this out before we take that route.
Thank you,
ASKER
Well, I started with autodiscover (simply because I forgot to put in manual settings), and got the following error:
The certificate common name *.<mydomain>.com, doesn't validate against Mutual Authentication string provided msstd:mail.<mydomain>.com
Do note that this customer DOES use a wildcard SSL cert, hence the *.<mydomain>.com
The certificate common name *.<mydomain>.com, doesn't validate against Mutual Authentication string provided msstd:mail.<mydomain>.com
Do note that this customer DOES use a wildcard SSL cert, hence the *.<mydomain>.com
ASKER
When entering in all the proper manual information, the following error occurs:
Testing RPC/HTTP connectivity
RPC/HTTP test failed
Test Steps
Attempting to resolve the host name mail.<mydomain>.com in DNS.
The Host could not be resolved.
Tell me more about this issue and how to resolve it
Additional Details
Host mail.<mydomain>.com could not be resolved in DNS Exception Details:
Message: No such host is known
Type: System.Net.Sockets.SocketE
Stack Trace:
at System.Net.Dns.GetAddrInfo
at System.Net.Dns.InternalGet
at System.Net.Dns.GetHostAddr
at Microsoft.Exchange.Tools.E
This is odd, because I can go to the website for the domain and pull up OWA in a second.
Testing RPC/HTTP connectivity
RPC/HTTP test failed
Test Steps
Attempting to resolve the host name mail.<mydomain>.com in DNS.
The Host could not be resolved.
Tell me more about this issue and how to resolve it
Additional Details
Host mail.<mydomain>.com could not be resolved in DNS Exception Details:
Message: No such host is known
Type: System.Net.Sockets.SocketE
Stack Trace:
at System.Net.Dns.GetAddrInfo
at System.Net.Dns.InternalGet
at System.Net.Dns.GetHostAddr
at Microsoft.Exchange.Tools.E
This is odd, because I can go to the website for the domain and pull up OWA in a second.
Please have a look at the following Technet article and make sure you have followed the guidelines:
http://technet.microsoft.com/en-us/library/cc535023(EXCHG.80).aspx
http://technet.microsoft.com/en-us/library/cc535023(EXCHG.80).aspx
Does mail.yourdomain.com resolve properly to your IP?
ASKER
"Please have a look at the following Technet article and make sure you have followed the guidelines:
http://technet.microsoft.com/en-us/library/cc535023(EXCHG.80).aspx"
Is this still applicable? Everyone in the company works. It even works when I connect to his mailbox with RPC over HTTP from my computer
"Does mail.yourdomain.com resolve properly to your IP?"
It resolves to the same external IP of the email server. Is this the correct IP you are talking about?
http://technet.microsoft.com/en-us/library/cc535023(EXCHG.80).aspx"
Is this still applicable? Everyone in the company works. It even works when I connect to his mailbox with RPC over HTTP from my computer
"Does mail.yourdomain.com resolve properly to your IP?"
It resolves to the same external IP of the email server. Is this the correct IP you are talking about?
ASKER
Oops, my manual setting was typo'd in the server name. I did the test again, with the proper domain name, and it came back with the previous error of "The certificate common name *.<mydomain>.com, doesn't validate against Mutual Authentication string provided msstd:mail.<mydomain>.com"
Sounds certificate related. My earlier post should help.
ASKER
Ah, so even if OWA works with no cert errors, this doesn't guarantee that Outlook would?
The title of the article "Wildcard Certificate causes client connectivity issues with Outlook Anywhere" is rather appropriate.
ASKER
Right, but there are over 50 other client computers using RPC over HTTP without any issue, this is why I am skeptic.
Sorry - I had missed that bit : (
Does his account work happily on another PC?
Do other users accounts work on his PC?
Is the certificate a 3rd party cert or self-signed. If self signed, has the certificate been installed on the PC?
Does his account work happily on another PC?
Do other users accounts work on his PC?
Is the certificate a 3rd party cert or self-signed. If self signed, has the certificate been installed on the PC?
Okay, I would suggest you rename profile and create new ond and check it.
ASKER
His account works fine on my PC.
I have tried out our administrator account on his PC and it had the same problem I mentioned earlier.
The cert is a 3rd party GeoTrust TrueBizID Wildcard certificate.
I have tried out our administrator account on his PC and it had the same problem I mentioned earlier.
The cert is a 3rd party GeoTrust TrueBizID Wildcard certificate.
ASKER
SatyPathak:
Rename the profile where? You mean rename the user himself?
Rename the profile where? You mean rename the user himself?
Okay that sounds PC related. Any firewall software or similar installed?
Service Packs and Windows updates for Windows / Office up to date?
Service Packs and Windows updates for Windows / Office up to date?
ASKER
He is using Microsoft Security Essentials, and Symantec Endpoint Protection (it has been disabled for the sake of this situation).
Doing 50 or so Windows updates, only one was for Office.
Doing 50 or so Windows updates, only one was for Office.
Are all clients using Microsoft Security Essentials and Symantec Endpoint Protection (SEP)?
Have you got the network threat protection enabled on SEP?
Can you uninstall SEP, reboot and try again please.
Have you got the network threat protection enabled on SEP?
Can you uninstall SEP, reboot and try again please.
ASKER
Sounds like a plan Alan.
At this moment I am doing Windows updates. Once they are done I will try the RPC connection again, if no dice, I will remove SEP.
And the entire company is using SEP, I have no idea why this guy is using MSE (Microsoft Security Essentials). SEP is disabled though, network threat protection as well.
At this moment I am doing Windows updates. Once they are done I will try the RPC connection again, if no dice, I will remove SEP.
And the entire company is using SEP, I have no idea why this guy is using MSE (Microsoft Security Essentials). SEP is disabled though, network threat protection as well.
I would imagine that the combination of Microsoft Security Essentials (Anti-Virus / Anti-Spyware etc) and Symantec Endpoint Protection (Anti-Virus / Network Threat Protection etc) is not a good combination as they will be fighting each other.
If after removing SEP - still no dice - remove Microsoft Security Essentials too and then try again. If good, re-install SEP client and test again. Hopefully all will still be well.
You could always start by removing Microsoft Security Essentials first!
If after removing SEP - still no dice - remove Microsoft Security Essentials too and then try again. If good, re-install SEP client and test again. Hopefully all will still be well.
You could always start by removing Microsoft Security Essentials first!
ASKER
MSE is gone, SEP is gone, computer is fully updated with all Windows and Office updates, same problem - it won't authenticate to the server.
Oh great! That's not good news.
What version of Windows is the troublesome computer running on?
What version of Windows is the troublesome computer running on?
ASKER
Windows XP SP2.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Self-resolved.
Best bet is to visit https://www.testexchangeconnectivity.com and run the HTTP over TPC test - specify manual server settings and see what results you get. You can use autodiscover later if all is well with manual settings.