OMA/ActiveSync/OWA works on wifi but not mobile

[Stevehewitt]

Hi all,

This isn't a direct exchange issue so please bare with me.

Got 2 handsets. Nokia N95 on Orange and a MDA II on T-Mobile. Both 3g, both support wi-fi.

Using a public broadband wifi (just a BT business broadband package) I can access on both handsets the

http://193.251.xxx.xxx/oma

and /exchange without any problems. That's using WIFI.

However if I switch the connection to use the cellular / mobile network and turn off Wifi the handsets don't work at all. Just a connection time out. I had a look on our firewall (ISA 2004) and it doesn't even see the handsets hitting the firewall - nothing.

Surely it can't be that both Orange AND T-Mobile are blocking traffic to IP or using some sort of scanning to block webmail.....?

Anyone had a similar experience?

Cheers,




Steve.

"They have the internet on computers now!" - Homer Simpson

 

[markdmac]

Do you have a public cert? What errors do you get on the mobile devices?

I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at

http://www.thespidersparlor.com/vbscript

Work SMARTER not HARDER. The Spider's Parlor's Admin Script Pack is a collection of Administrative scripts designed to make IT Administration easier! Save time, get more work done, get the Admin Script Pack.

 

[Stevehewitt]

Hey Mark,

Sorry for the delay in getting back!

There's no error other than connection time-out. ActiveSync aside, I'm getting this just trying to access OMA. After checking out ISA 2004 Application firewall the device isn't even hitting the firewall.


So if I go to the OMA site from a wifi connection, I can view it fine without any problem. I can also see the access on the ISA box. However if I switch the connection from public wifi over to GPRS/3G I get nothing. Just connection timeouts, and it doesn't appear to hit ISA.

For testing purposes I'm using HTTP rather than HTTPS - so there's no SSL. Also I'm just going by IP rather than a DNS name. (Both of these will be changed if/when we go live with it)

Any ideas?!

Thanks,




Steve.

"They have the internet on computers now!" - Homer Simpson

 

[markdmac]

OK, so first off I would re-enable SSL and test from outside the network using the Public DNS name.

https://mail.servername.com/oma

That should be hitting your firewall. If not make sure that you have an A Record for the servername.

Also verify all of your IIS Security settings.

IIS Settings

Default Web site
    Enable Anonymous access
    Integrated Windows Authentication
(doesn’t really matter)

Exadmin
    Integrated Windows Authentication
    Require SSL
        Require 128 bit

Exchange
    Basic Authentication
        Default Domain \
    Require SSL
        Require 128 bit

Exchange-oma
    Integrated Windows Authentication
    Basic Authentication

ExchWeb
    Enable Anonymous access
    Require SSL
        Require 128 bit

Microsoft-Server-ActiveSync
    Scripts and Executables
    Exchange Application Pool
    Basic Authentication
        Default Domain DomainName

OMA
    Scripts Only
    ExchangeMobileBrowseApplicationPool
    Integrated Authentication
        Default Domain DomainName

Public
    Basic Authentication
        Default Domain DomainName
    Integrated Auth
    Require SSL
        Require 128 bit

I hope you find this post helpful.

Regards,

Mark

Check out my scripting solutions at

http://www.thespidersparlor.com/vbscript

Work SMARTER not HARDER. The Spider's Parlor's Admin Script Pack is a collection of Administrative scripts designed to make IT Administration easier! Save time, get more work done, get the Admin Script Pack.