Cannot Conntact To OMA

Have a look at the list of Virtual Directories under the Default Web Site in IIS Manager.  Make sure that OMA still exists.

"exchange-oma" is listed under "Default Web Site" in IIS

exchange-oma is something different.  If you can't see the one called just oma, then you will need to recreate it.  Method 3 is easiest, I think:
http://support.microsoft.com/kb/883380

I have one item called "OMA" - see attached screenshot

oma.jpg

What happens if you right-click it, and select Browse?

Can you show us the IIS log entries generated when you do that?

When i right click -> browse i get a popup box for my credentials, when i enter them i get the same message:

Unable to connect to your mailbox on server <SERVER-NAME>. Please try again  later. If the problem persists contact your administrator.

I need to see the IIS log entries that are generated.  Look for the latest file in C:\Windows\System32\LogFiles\W3SVC1 .  Double-click it, and it will open in Notepad.  Note the times at the left that are in GMT.  A cluster of entries will be generated by your connection to OMA.  Can you copy/paste them for me?

I'm having trouble tracking the log entries down. I have a file thats as long as my arm - but i dont see any entries relating to OMA :(

They should have GET /oma near the beginning.  If not, look at the properties of the OMA VDir, and make sure that 'Log Visits' is checked. Then at the properties of the Default Web Site, and make sure that 'enable logging' is checked.

Logging was disabled on the Default Web Site - i have enabled it now.

Log is:

#Software: Microsoft Internet Information Services 6.0
#Version: 1.0
#Date: 2008-10-14 16:07:19
#Fields: date time s-sitename s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) sc-status sc-substatus sc-win32-status
2008-10-14 16:07:19 W3SVC1 192.168.1.200 GET /oma - 443 - 192.168.1.200 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.30;+.NET+CLR+3.0.04506.648) 401 2 2148074254
2008-10-14 16:07:24 W3SVC1 192.168.1.200 GET /oma - 443 administrator 192.168.1.200 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.30;+.NET+CLR+3.0.04506.648) 301 0 0
2008-10-14 16:07:24 W3SVC1 192.168.1.200 GET /oma/oma.aspx - 443 administrator 192.168.1.200 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.30;+.NET+CLR+3.0.04506.648) 302 0 0
2008-10-14 16:07:24 W3SVC1 192.168.1.200 GET /oma/oma.aspx - 443 administrator 192.168.1.200 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.30;+.NET+CLR+3.0.04506.648) 200 0 0
2008-10-14 16:07:24 W3SVC1 192.168.1.200 GET /favicon.ico - 443 administrator 192.168.1.200 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.04506.30;+.NET+CLR+3.0.04506.648) 404 0 2

Is there anything after GET /oma/oma.aspx (ignoring favicon.ico, of course)?  There should be some requests for /Exchange (or /exchange-oma if you followed KB817379).  If not, look at the Exchange and exchange-oma VDirs, and make sure that 'log visits' is enabled there, too.

If it is already enabled, then you might have another web site on the server that is using port 80 instead of the Default Web Site.  OMA will get upset by that.

i just came accross these log entries (attached) which mention the iPod and active sync


log.txt

Does this mean that you are running the Default Web Site on port 8080?

Yup

That is why your OMA does not work.  You can connect to the OMA VDir on port 8080 okay, but OMA then send its own internal WebDAV calls to the /Exchange VDir on port 80 (this can't be changed).  The obvious question now is 'can you get your default web site back on port 80'?  Of course, I expect you have a reason for not doing so, but getting your OMA working now is going to be a bit complicated.  Is there another web site on the same server that does use port 80?

"Default SharePoint Website" was on port 80. We changed "Default Web Site" to port 80, now we are getting the following:

Outlook(R) Mobile Access is supported only on Microsoft(R) Exchange Server 2003. Currently your mailbox is stored on an older version of Exchange server. Please contact your system administrator for additional assistance.

Select allOpen in new window

I've never seen that message before.  But is what it is saying true?  Is your mailbox on an E2000 server somewhere?

We only have this one server running Exchange 2003 SP2

Well, I can only Google it, and look at the points raised here:
http://support.microsoft.com/kb/839288

So, the first suggestion is 'The Exchange virtual directory is redirected to a different URL.'  Is that true?  If you go to http://servername/exchange, you should see your OWA GUI.  Also, it should not be redirected to https automatically.

http://servername/exchange ALWAYS redirects to httpS://servername/exchange even though i have unticked "Require Secure Channel (SSL)" on the "Default Web Site"

But did you leave Require SSL ticked on the Exchange VDir?  The DWS setting can be over-ridden there.

Okay, i disabled SSL and i can connect to OWA using http and it does NOT redirect :)

However, http://servername/oma still shows:

Outlook(R) Mobile Access is supported only on Microsoft(R) Exchange Server 2003. Currently your mailbox is stored on an older version of Exchange server. Please contact your system administrator for additional assistance.

Can you post the IIS log entries generated when you now try to use OMA?  They should be different to the ones you posted previously.

Attached is a copy of the logs

ex08101514.log

UPDATE:
We now have OMA working - but still cannot connect our iPhone

I see from the IIS log that you have read KB817379 and created the exchange-oma VDir.  You also removed SSL on that?

Anyway, are you trying to connect the iPhone by using ActievSync?

SSL on exchange-oma is not enabled. Yes we are trying to use ActiveSync.

What address should we be using for the server address on the iPhone?

Usually the public DNS name.  mail.domain.com sort of thing.  No http:// or /exchange or anything like that.

we have exchange.domain.com which redirects to our servers external static IP - but this just gives us account verification failed

our email is a POP3 catchall not an SMTP feed

Yes, just use server.domain.com.

Also, make sure that SSL is not required on the /Exchange virtual directory.  While iPhone uses SSL, it still uses WebDav on 80 so you can't force SSL in IIS6 or the iPhone will receive an 403.4 every time it tries to access the WebDav service, which causes failure to auth.

I found this using a script to redirect http to https on 403.4.

Can you post the IIS log entries generated when you try to use ActiveSync?  You should see requests for 'Microsoft-Server-ActiveSync'.

Okay, i managed to connect to OMA outside of our network and it was giving the IIS IP denied error. i went into OMA and ticked "By default all computers will be granted access" and now i can access OMA perfectly fine externally using https://<IP>/oma

However, my iPhone (and iPod) both still say "Exchange account verification failed" no matter what i use as the server IP. i have disabled SSL on OMA and still get the same error

Did you disable on the /Exchange Virtual Dir too?

Just tried that now - still same error: "Exchange account verification failed"

i think it could be (kinda) talking to the server now, it's now saying exchange account verified, then it says "configured for (null)" and when you go to email there is nothing there.

Attached is the latest logs from IIS

log.txt