Exchange 2003 - Unable to make OMA connection

Hello and thank you for taking the time to look at my issue.

We have Ex 2003 running and have been having Outlook Mobile Access running for months.  Now we are getting username/password incorrect messages.  I checked to make sure OMA is enabled for the users.

Please advise.

Thank you and have a great day,

Don
GEMCCAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

SreRajCommented:
Hi Don,

Please verify that SSL certificate used is not expired.

1. Click Start, point to All Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
2. In Internet Services Manager, in the console tree, expand SERVERNAME (your local computer), and then expand Web Sites.
3. In the console tree, right-click Default Web Site, and then click Properties.
4. In the Default Web Site Properties dialog box, click Directory Security.
5. On the Directory Security tab, click Server Certificate.
0
GEMCCAuthor Commented:
Hi SreRaj,

The certificate is not due to expire until 26 January 2018.

Any other ideas?

Have a great day,

Don
0
SreRajCommented:
You could try restarting IIS with the command iisreset

Also please check application log in event viewer for any critical alerts logged regarding OMA or IIS.

You could also test connectivity from internet using https://testexchangeconnectivity.com
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!

GEMCCAuthor Commented:
OK, I always forget about https://testexchangeconnectivity.com.  Anyway, here are the results:

 
 The Microsoft Connectivity Analyzer is testing Exchange ActiveSync.  
  The Exchange ActiveSync test failed.  
 
 Attempting the Autodiscover and Exchange ActiveSync test (if requested).
  Testing of Autodiscover for Exchange ActiveSync failed.
 
 Attempting each method of contacting the Autodiscover service.
  The Autodiscover service couldn't be contacted successfully by any method.
 
 Attempting to test potential Autodiscover URL https://domainname.org/AutoDiscover/AutoDiscover.xml 
  Testing of this potential Autodiscover URL failed.
 
 Attempting to resolve the host name domainname.org in DNS.
  The host name resolved successfully.
 
IP addresses returned: 216.185.152.151

 Testing TCP port 443 on host domainname.org to ensure it's listening and open.
  The specified port is either blocked, not listening, or not producing the expected response.
 
 Attempting to test potential Autodiscover URL https://autodiscover.domainname.org/AutoDiscover/AutoDiscover.xml 
  Testing of this potential Autodiscover URL failed.
 
 Attempting to resolve the host name autodiscover.domainname.org in DNS.
  The host name couldn't be resolved.  

 Attempting to contact the Autodiscover service using the HTTP redirect method.
  The attempt to contact Autodiscover using the HTTP Redirect method failed.
 
 Attempting to resolve the host name autodiscover.domainname.org in DNS.
  The host name couldn't be resolved.
 
Host autodiscover.domainname.org couldn't be resolved in DNS InfoDomainNonexistent.
 
 Attempting to contact the Autodiscover service using the DNS SRV redirect method.
  The Microsoft Connectivity Analyzer failed to contact the Autodiscover service using the DNS SRV redirect method.  
 
 Attempting to locate SRV record _autodiscover._tcp.domainname.org in DNS.
  The Autodiscover SRV record wasn't found in DNS.

It appears someone has changed A record settings in DNS, correct?

Thanks for your help.

Have a great day,

Don
0
SreRajCommented:
The first url domainname.org is getting resolved to an IP address, but it's unable to provide autodiscover service. Please verify this IP is your internet facing front-end.
0
GEMCCAuthor Commented:
The client changed web hosting companies and had DNS changes made without realizing the impact of mail.  Made the appropriate changes, now everything is fine.
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
GEMCCAuthor Commented:
Issue 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
Outlook

From novice to tech pro — start learning today.