Welcome to ISAserver.org

OMA/Exchange Active Sync Issue

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA 2006 Publishing] >> Exchange Publishing >> OMA/Exchange Active Sync Issue

Page: [1]

Message

<< Older Topic Newer Topic >>

OMA/Exchange Active Sync Issue - 29.Jul.2008 2:43:25 AM

pjscott13

Posts: 18
Joined: 12.Nov.2007
Status: offline

Hi All,

Previously we were using a Checkpoint Firewall and just allowed Direct HTTPS traffic to be forwarded from the firewall to our Exchange Server.

Just this weekend, we have removed the Checkpoint Firewall and are now using ISA 2006. We are now publishing our Exchange Server via the ISA server. Everything is working great except for OMA/Active Sync.

I have used the Exchange Web Client Publishing rule to publish Exchange for OWA, Outlook RPC/HTTPS, OMA and ActiveSync.

Outlook Web Access and Outlook RCP/HTTPS is working great... absolutely no problems there, but no PDA's or Smartphones will Sync. When I attempt to sync using my phone, I can see a connection is made... and I see the ISA server receives the request, but then nothing:

Allowed Connection
Log type: Web Proxy (Reverse) Status: 500 Internal Server Error Rule: Exchange Web Publishing Rule Source: External (119.X.X.X) Destination: (192.168.18.X:443) Request: POST http://mail.domainname.com.au/Microsoft-Server-ActiveSync?User=UserName&DeviceId=DeviceID&DeviceType=DeviceType&Cmd=FolderSync Filter information: Req ID: 0dfcc6f9; Compression: client=No, server=No, compress rate=0% decompress rate=0% ; FBA cookie: exists=no, valid=no, updated=yes, logged off=no, client type=unknown, user activity=yes Protocol: https User: DOMAIN\UserName Additional information Client agent: RoadSync-S60/3.0Object source: Internet (Source is the Internet. Object was added to the cache.)Cache info: 0x40040008 (Request includes the AUTHORIZATION header. Response includes the CACHE-CONTROL: NO-CACHE or PRAGMA: NO-CACHE header. Response should not be cached.)Processing time: 282 msMIME type:

Needless to say the device returns an Error (Server Error 500). My guess is that the following MS article "http://support.microsoft.com/kb/817379" which I used to setup OMA/ActiveSync prior to ISA, may be the reason why it's not working. Should I reverse this? or do you have other ideas as to the problem?

< Message edited by pjscott13 -- 29.Jul.2008 2:47:14 AM >

Post #: 1

Featured Links*

RE: OMA/Exchange Active Sync Issue - 29.Jul.2008 10:18:36 AM

PCC

Posts: 185
Joined: 13.Nov.2001
From: Michigan
Status: offline

I also used the "Exchange Web Client Access Publishing Rule" to publish OWA, OMA, RPC/HTTP & ActiveSync. I have the web listener on the ISA server using SSL and FBA. When trying to connect with a mobile client I get the 500 error page. OWA and OMA both work fine (haven't tried RPC/HTTP yet) from a normal browser on a laptop/desktop client but I can log into the FBA page with the normal browser on the laptop/desktop where you can't with a mobile client.

Isn't a mobile client supposed to bypass the FBA page?

(in reply to pjscott13)

Post #: 2

RE: OMA/Exchange Active Sync Issue - 7.Aug.2008 2:50:28 PM

PCC

Posts: 185
Joined: 13.Nov.2001
From: Michigan
Status: offline

quote:

ORIGINAL: PCC

I also used the "Exchange Web Client Access Publishing Rule" to publish OWA, OMA, RPC/HTTP & ActiveSync. I have the web listener on the ISA server using SSL and FBA. When trying to connect with a mobile client I get the 500 error page. OWA and OMA both work fine (haven't tried RPC/HTTP yet) from a normal browser on a laptop/desktop client but I can log into the FBA page with the normal browser on the laptop/desktop where you can't with a mobile client.

Isn't a mobile client supposed to bypass the FBA page?

Does anyone know if this is true?

(in reply to PCC)

Post #: 3

RE: OMA/Exchange Active Sync Issue - 18.Aug.2008 8:40:56 AM

PCC

Posts: 185
Joined: 13.Nov.2001
From: Michigan
Status: offline

I still can't get this working. ActiveSync works fine on a WM 6.0 client after loading CA and website certificates. But when trying to connect to OMA I still get the 500 error page.

(in reply to PCC)

Post #: 4