About storerc_

storerc_ · ‎06-14-2010

PR 529608. No further info/response from engineering yet.

storerc_ · ‎06-12-2010

@RichardG wrote: I have the same problem with a SA 2000 and 6.5R4. Do you have a solution now? No solution yet, but Juniepr has finally been able to consistently reproduce the issue on both my 4500 and their lab SA's. They've kicked up to engineering, but I don't have any updates yet. At least the issue has been verified and acknowledged. I'll be looking for an update from them on Monday, I'll try to get an official PR you can reference. Surprised nobody else has run into this....

storerc_ · ‎02-24-2010

We're preparing to deploy a new SA4500 into production, starting with OWA and Active Sync for mobile devices. I started with 6.5r2 as I believe (please correct me if I'm wrong) the option to enforce EAS traffic only on an auth-only URL is only available in the 6.5 series, and this is something we wanted. I have a number of devices using the EAS URL I've setup and have confirmed that all devices are experiencing "stalls" or delays with push email via EAS. Manual refresh always works, and after a manual check the push functionality seems good for 10-20 minutes. After that it seems to stall and we are experiencing 20-30 minute delays on receipt of push email. I have confirmed this behavior on Palm WebOS and Android in addition to Windows Mobile. I've also updated to 6.5r3.1 with no change. Before purchasing the SA4500, I had a 2500 demo unit for a period of time that was running 6.3, and I'm near positive push email was working consistently and cleanly without this stall or delay, but it did not have the option to enforce EAS only traffic on the auth-only URL. I'm about to contact JTAC but thought it might be worth posting here to see if anyone else has noticed or experienced anything similar in the 6.5 series. My config: auth-only url setup specifically for EAS, option for "Allow ActiveSync Traffic Only" is enabled (though I've tried disabling that with no effect) Specific role setup for EAS only access. Combination of credentials and login URL map to the EAS only role. Per documentation, the only settings on the role are to allow untrusted SSL (to work around a cert mismatch internally) and the HTTP connection timeout is set to the max of 1800s. No source or browser restrictions. Exchange 2007 on the back-end. Thanks!

storerc_ · ‎02-08-2010

My apologies - I thought I had seen some folks continuing to have issues even once moving EAS services back to the root IVE. I just went back and re-read through the whole thread and found that is not the case. Kindest regards,

storerc_ · ‎02-06-2010

I actually did open a case w/ JTAC and, much to my chagrin, while I was gathering info for the tech I found that my in my current iteration of deleting and recreating the auth-only URL, I had mistakenly left out the appropriate Web ACL which was dropping access from my clients. I've fixed the web ACL and my current auth-only OWA/EAS URL is functioning at the moment, but I know I had the ACL in place the first time around and it had been working but randomly stopped mid-morning one day while I was out running around between some of our sites (and suddenly stopped received email on my phone). I've left my JTAC case open, honestly hoping it will fail again - I'm not at all comfortable rolling EAS into production via the SA given the issues others have had any my own unexplained random failure. FWIW, not sure I had mentioned it in earlier post, but I'm running mine in IVE, not IVS. If anything useful or significant pops up I'll post it here. Thanks,

storerc_ · ‎02-04-2010

Any update on this? I have a new SA4500 we're getting ready to deploy running 6.5R2 - no legacy stuff from older configs, but having the same issue. FWIW, for various reasons we're actually using the same Authorization Only URL for both EAS and external OWA access (don't ask...) and OWA via this path is broken as well. It seems to be the Authorization Only functionality that is broken, not specifically EAS. I see the same thing descibred above when doing a TCPDump - I can se my client hit the IVE, but the IVE never sends any traffic to the internal resource - I've tried both hostname and IP for the internal resource, and no dice either way. Same thing happens for any other authorization only URL I configure. The weird thing is, the very first time I configured the auth only URL, it worked for a period of time. Then it just stopped and started throwing the 500 errors. I've deleted it, recreated it, rebooted the device, created other auth only URL's pointing to the same as well as different internal resources, and nothing. If no useful updates, I'll go ahead and contact JTAC as well and post ticket here for cross reference. Thanks,

Re: EAS "push" delays on 6.5

Re: EAS "push" delays on 6.5

EAS "push" delays on 6.5

Re: AcrtiveSync seems to have Problems in 6.5R2

Re: AcrtiveSync seems to have Problems in 6.5R2

Re: AcrtiveSync seems to have Problems in 6.5R2