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,
newgentechnologiesAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Alan HardistyCo-OwnerCommented:
Sembee (Mestha) is taking a break and has not posted anything new this year!

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.
0
newgentechnologiesAuthor Commented:
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
0
newgentechnologiesAuthor Commented:
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.SocketException
Stack Trace:
at System.Net.Dns.GetAddrInfo(String name)
at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6)
at System.Net.Dns.GetHostAddresses(String hostNameOrAddress)
at Microsoft.Exchange.Tools.ExRca.Tests.ResolveHostTest.PerformTestReally()


This is odd, because I can go to the website for the domain and pull up OWA in a second.
 
 
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Alan HardistyCo-OwnerCommented:
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
0
Alan HardistyCo-OwnerCommented:
Does mail.yourdomain.com resolve properly to your IP?
0
newgentechnologiesAuthor Commented:
"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?
0
newgentechnologiesAuthor Commented:
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"
0
Alan HardistyCo-OwnerCommented:
Sounds certificate related.  My earlier post should help.
0
newgentechnologiesAuthor Commented:
Ah, so even if OWA works with no cert errors, this doesn't guarantee that Outlook would?
0
Alan HardistyCo-OwnerCommented:
The title of the article "Wildcard Certificate causes client connectivity issues with Outlook Anywhere" is rather appropriate.
0
newgentechnologiesAuthor Commented:
Right, but there are over 50 other client computers using RPC over HTTP without any issue, this is why I am skeptic.
0
Alan HardistyCo-OwnerCommented:
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?
0
Satya PathakLead Technical ConsultantCommented:
Okay, I would suggest you rename profile and create new ond and check it.
0
newgentechnologiesAuthor Commented:
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.
0
newgentechnologiesAuthor Commented:
SatyPathak:

Rename the profile where? You mean rename the user himself?
0
Alan HardistyCo-OwnerCommented:
Okay that sounds PC related. Any firewall software or similar installed?

Service Packs and Windows updates for Windows / Office up to date?
0
newgentechnologiesAuthor Commented:
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.
0
Alan HardistyCo-OwnerCommented:
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.
0
newgentechnologiesAuthor Commented:
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.
0
Alan HardistyCo-OwnerCommented:
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!
0
newgentechnologiesAuthor Commented:
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.
0
Alan HardistyCo-OwnerCommented:
Oh great!  That's not good news.
What version of Windows is the troublesome computer running on?
0
newgentechnologiesAuthor Commented:
Windows XP SP2.
0
newgentechnologiesAuthor Commented:
We have resolved this issue by simply reinstalling all of Outlook, not sure why this issue was occurring. Requesting refund,
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
newgentechnologiesAuthor Commented:
Self-resolved.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.