Welcome to ISAserver.org

Problems with Exchange 2003 behind ISA

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2000 General] >> Server Publishing >> Problems with Exchange 2003 behind ISA

Page: [1]

Message

<< Older Topic Newer Topic >>

Problems with Exchange 2003 behind ISA - 24.Jun.2008 6:48:39 PM

GibsonSG

Posts: 1
Joined: 24.Jun.2008
Status: offline

I have 2 servers, both running Windows 2000 Server.

1 has Microsoft ISA Server 2000 installed on it with SP2 and the registry entry needed for Direct Push, the other has Exchange 2003 SP2.

I set everything up for direct push awhile back and have been using it for quite some time. Originally with Motorola Q phones, then those got replaced with Sprint Moguls, both on Sprint. It's been working fine. Users usually get a notification on the phone before an email ever hits thier inbox.

Recently I got myself a T-mobile Wing and set it up for direct push. The problem is that it doesn't work correctly. Seems the phone will initially sync and remain connected for about 30 seconds, then it will disconnect for 8 mins, then connect and sync... just over and over in a cycle. As a result I only get email about every 8 minutes after it has connected.

I've tried everything I can think to do to get it working, and nothing has helped so far. When I turn on Verbose logging for Active Sync, I'm getting this message after the ping request:

=-=- [24/06/2008 09:37:0240.000] -=-=
=-=-=-= Server Response =-=-=-
HTTP/1.1 504 Gateway Timeout
Content-Length: 1244

On a hunch, I setup VPN access on the phone. When it is connected through the VPN and I am using the internal address for the exchange server, direct push works exactly as it should. Disconnect from the VPN and set it back to the external address and it goes back to having issues.

This only occurs on my phone, The T-Mobile Wing... the Sprint Moguls all work flawlessly.

My assumption is that one way or another something with that ping is getting blocked by the ISA server, so the keep alives aren't happening. But I wanted to double check with some people who might know more than me. Maybe there is a setting somewhere I don't have correct, I don't know.

It just baffles me that the Moguls work fine, but my phone will not.

Also, on the T-mobile wing... I can pull up a browser and access OWA and OMA with no problems whatsoever. It's only ActiveSync that is having the issues. Also during the verbose logging if I check the Ctrl log, I see message about Heartbeat failed with code 0x85010018. Everything I can find on this code states it's related to network issues. But the phone isn't dropping data connection or anything as far as I can tell.