Activesync doesn't work remotely (Full Version)

All Forums >> [Microsoft Exchange 2003] >> General



Message


elsandalos -> Activesync doesn't work remotely (6.May2005 4:16:00 PM)

Hi all,
Just spend ages reading up on all the issues surrounding Activesync, and now i've got my PPC synching with Exchange 2003 whilst cradled.

Unfortunately it only works if i use the server's local IP. If i connect remotely (not cradled) using our public IP for the server i'm getting a "Your account does not have permission to sync ...." error (HTTP_400)

So i've come a long way since this morning, but something is still wrong. I'm sure my firewall is configured fine, since OMA is working great when using our external IP.

HELP! "[Confused]"

Pete




Guest -> RE: Activesync doesn't work remotely (7.May2005 12:40:00 PM)

What firewall are you using?

If you try to get to the ActiveSync website using internet explorer - what message to you get back?

PM'ed you too [Smile]




jwpaco -> RE: Activesync doesn't work remotely (8.May2005 6:18:00 AM)

I am also trying to access exchange remotely with Versamail on my Treo and I cannot connect. I have https set up and I am thinking that the self-signed certificate may be my problem? Is this a known issue? DOes the certificate have to be signed by a known CA?




marcus2v -> RE: Activesync doesn't work remotely (8.May2005 11:29:00 AM)

I'm not sure what Certificate Authorities the Treo trusts by default. It might be worth checking this out to make sure it is trusting the certificate that you have installed on the Activesync server.




elsandalos -> RE: Activesync doesn't work remotely (9.May2005 12:28:00 PM)

quote:
Originally posted by <markt>:
What firewall are you using?

If you try to get to the ActiveSync website using internet explorer - what message to you get back?

PM'ed you too [Smile]

It's a very non-standard product provided by our ISP (www.star.co.uk). I thought activesync just used ports 80 and 443 though? (which are working fine with OMA) Unfortunately noone at our ISP knows about Activesync so i drew a blank there.

.. and what is the Activesync website?

cheers
El.




marcus2v -> RE: Activesync doesn't work remotely (9.May2005 8:09:00 PM)

jwpaco

Maybe this helps?
http://www.handspring.com/products/smartphones/treo650/activesync-faqs.jhtml

Pete,

Try going to https://your-external-servername/Microsoft-Server-ActiveSync/

You should get a 501 Not Implemented back if its all ok.

Marcus




elsandalos -> RE: Activesync doesn't work remotely (13.May2005 4:50:00 PM)

quote:
Originally posted by marcus2v:
Try going to https://your-external-servername/Microsoft-Server-ActiveSync/

You should get a 501 Not Implemented back if its all ok.

Marcus[/QB]

ok, just tried that. I a login dialog box pops up, and then get a 501 page when i've tried to login.

Pete




PMattsson -> RE: Activesync doesn't work remotely (18.May2005 4:16:00 AM)

Hey!

and then what ?? [Wink]
I have the same problem... I think.

But when I setup ActiveSync on Q-tek, the traffic does NOT reach Firewall. No-show of packets...

But when we surf from Q-tek to https://company.com/Microsoft-Server-ActiveSync/
I can see the packets reach FireWall...

Strange, ...
We are checking with Mobile ISP if the can see the packages....
Any Ideas??

Thanx-thanx




PMattsson -> RE: Activesync doesn't work remotely (18.May2005 8:06:00 AM)

...and I solved it:

I typed https://mobil.company.com in field for activesync server... not good.

typed (after a insider tip) mobil.company.com instead in ServerSctiveSync in Q-tek...

and it works...




donaldsmarshall -> RE: Activesync doesn't work remotely (18.May2005 9:52:00 AM)

i have a similar issue, I can see it via the web, but when I use activesync I get "account permission" errors




marcus2v -> RE: Activesync doesn't work remotely (18.May2005 4:46:00 PM)

DSM,

Front-end / Back-end or single server ?

What (if any) firewalls between the activesync client and the Exchange server?

SSL Certificates? Do you have the corresponding root certificate on the activesync client?




elsandalos -> RE: Activesync doesn't work remotely (20.May2005 12:36:00 PM)

This is still driving me nuts. I've followed every tutorial i can find (creating ExchDAV etc), and yet OMA works internall and externally and Activesync works internally ... but not externally.

A weird thing though ... it worked externally ONCE. I was playing with the authentication settings on my PPC, and when i changed them back to what they were before it synched once. When i hit sync again, i got the same old error (Your account does not have permission to sync with current settings ... HTTP_403). Did a search and found another guy who had the same thing happen to him.

Am i right that i am actually getting through to the exchange server when i get this error. On the PPC Activesynch throws the error up as soon as it moves from 'Connecting ...' to 'Looking for changes...', so it seems that authentication goes ok.

Pete




Neo_omega -> RE: Activesync doesn't work remotely (20.May2005 12:59:00 PM)

we have some issue with our ActiveSync too. The solution for us is using seperated Virtual Server for the ActiveSync, in order to make the OWA works and ActiveSync works at the same time.




donaldsmarshall -> RE: Activesync doesn't work remotely (20.May2005 5:02:00 PM)

quote:
Originally posted by marcus2v:
DSM,

Front-end / Back-end or single server ?

What (if any) firewalls between the activesync client and the Exchange server?

SSL Certificates? Do you have the corresponding root certificate on the activesync client?

single server
Firewall turned off for testing
as for ssl, I cant import the cert as it was created using selfssl, as cert manager ones are giving a cannot find server message, but i have disabled ssl for testing same issue.

thanks




marcus2v -> RE: Activesync doesn't work remotely (22.May2005 7:13:00 AM)

1. Using ESM, create a new HTTP virtual server called "OMA-ActiveSync".

2. Create Virtual Directories under the new Virtual Server called 'Microsoft-Server-ActiveSync' and 'OMA', setting the Exchange path as relevant for each one.

3. Authentication for the OMA-ActiveSync virtual server should be set to Basic.

4. Open up IIS Manager and right click on the new Virtual server and choose properties. Set the IP address if necessary to something different.

5. Authentication should be set to Anonymous, Basic, Integrated.

6. Set up a new SSL certificate for the virtual server, using the name as it would be appear to external users (e.g. mobile.mydomain.com), do not require SSL. The certificate authority needs to be one that is trusted on your activesync device or you can disable this certificate checking on your device (there's a microsoft KB on which root certificates are on the smartphones and also a utility to disable the checking).

7. Under the Virtual server you should have OMA, Microsoft-Server-ActiveSync and ExchWeb showing up, in IIS manager.

8. Set up the natting on your firewall and the DNS for your external FQDN for ActiveSync.




donaldsmarshall -> RE: Activesync doesn't work remotely (22.May2005 11:58:00 AM)

tried those instructions same issue, however the error code changed to http_400 from http_403

thanks




marcus2v -> RE: Activesync doesn't work remotely (22.May2005 4:33:00 PM)

DSM,

I've sent you a private message




graphico -> RE: Activesync doesn't work remotely (28.May2005 11:14:00 PM)

I noticed you started with a mention of the ole HTTP_400 error - an error that seems to occur very randomly.

I finally found some helpful info... this error is caused by too many messages in your Inbox folder. Simply create a new subfolder, move all your messages from your Inbox to this new folder, and then run ActiveSync and everything should sync fine. After it has, you should be able to move all of your messages BACK to the inobx, sync again, and things should work just fine.

Good luck!




donaldsmarshall -> RE: Activesync doesn't work remotely (2.Jun.2005 3:35:00 AM)

yeah but in my case, i have nothing in my inbox [Smile]

thanks anyway




donaldsmarshall -> RE: Activesync doesn't work remotely (3.Jun.2005 3:46:00 AM)

just to say I now have it working, I needed a SMTPProxy added to the registry, and a few other tweaks to get it working [Big Grin]

Thanks for the help guys.




Page: [1] 2   next >   >>