OWA works well though we need to login twice. I am trying to get active sync working but it wants to hit the FQDN of our CAS box which is MSEXCHCAS01
We are using ISA 2006. I am pretty sure this is a cert issue and wanted to know if there were options to work around without having to get a cert with out CAS machine name in it.
Posts: 2244
Joined: 12.Apr.2004
From: Taylorville, IL
Status: offline
Tom Do you have any articles dealing specifically with OMA and ActiveSync with a Single Exchange behind ISA on the LAN (no FE, no BE, no DMZ). My OWA works fine but can't get anywhere with OMA or ActiveSync, I don't even know how to test them in a way that eliminates the Pocket PC device as being part of the problem.
That's the configuration I run in my own office and haven't had to do anything special to make it work. Well, for Exchange 2003. I don't have much expereience with the horkage named Exchange 2007
However, Debi is harassing me to get HTML mail working on her pocket PC phone, so I'll need to figure out how to get everything in Exchange 2007 working. I might just set up Windows Essentail Business Server and use that for my email domain.
Posts: 2244
Joined: 12.Apr.2004
From: Taylorville, IL
Status: offline
Hi Tom! Good to hear from you!
Horkage?
Ya better get on that for Deb. You don't want to have to sleep on the couch.
When I try the OWA URL (OMA?) with my pocket PC I first get the prompt about the Cert that it claims isn't trusted,...I tell it "yes" to continue. Then I immediately get the "Page cannot be displayed" along with a "401 Unauthorized" at the bottom. I never get a login prompt.
If I try to do an "Activesync" and pointing it at the same URL it just says that the Sync failed with no explaination or any details.
The normal OWA works perfectly fine with FBA when using a normal PC.
If you want to poke around with this more later, maybe we should start a different thread. I don't want to hyjack the OP's thread any more than I have already.
Posts: 4663
Joined: 30.Jul.2002
From: United Kingdom
Status: offline
quote:
ORIGINAL: vwalsh
Greetings,
I am pretty sure why I am getting this error but I need a work around that doesn't involve buying a new Cert
We have Exchange 2007 up and running well in a multi-server cong We have 1 Hub, 1 Cas, 2 Mailbox CCR'd and 1 UM servers in the same blade enclosure
Our cert points to .com" target=_blank>https://owa.<companyname>.com
OWA works well though we need to login twice. I am trying to get active sync working but it wants to hit the FQDN of our CAS box which is MSEXCHCAS01
We are using ISA 2006. I am pretty sure this is a cert issue and wanted to know if there were options to work around without having to get a cert with out CAS machine name in it.
-Vance
The neatest way to solve this is with the use of Unified Communications or SAN cert. Have a look at the following document which provides a lot of good background on the options available:
The key to getting a working Exchange 2007 remote access solution with ISA is based upon the configuration of Exchange autodiscovery and the 'internalurl' and 'externalurl' parameters. These parameters allow you to define external DNS names that are used for external clients as opposed to trying to connect to internal NetBIOS names.
P.S. You shouldn't have to login twice for OWA so this sounds a bit suspect...
Cheers
JJ
< Message edited by Jason Jones -- 18.Dec.2007 7:13:51 PM >