View Full Version : activesync server sync help!!!!
xfaethorx
22-07-2006, 02:48 AM
Hi guys,
Right i have an XDA exec and an XDA mini , ones for work ones for personal use.
I've set up an exchange server at home for the mini however it has to listen on port 8080 (the web outlook frontend).
However I'm trying to connect the activesync client to this via
address:8080 in the server field on the device but it doesn't seem to work
I can obviously access the site via 8080 on http but not via activesync. I've tried this on both the XDA MINI and the XDA EXEC and neither can access the server and i can't move the ports :(.
does the client support ports?
can you override them?
help!!!!
jcleek
22-07-2006, 03:54 AM
Activesync works by default over port 80 (non-secure) and 443 (secure) only. There may be a reg hack but I am unaware of one. If your cable or phone company is blocking port 80 just install a certificate, which you REALLY should be using anyway) and connect over 443 using SSL.
xfaethorx
22-07-2006, 08:56 AM
this is the problem, both portss 80 and 443 are taken up already by an apache web server.
I have exchange running under a virtual machine on the linux server. The windows 2003 box intergates with the existing mail sub system giving me access to the pop3 and smtp service on the linux side of things so its transparrent.
So apache runs on both port 80 and 443 so I can't bind anything to them.
I was looking into a reg hack if there was one.
If i find anything i'll post it but until then i have the same problem...which is a real annoyance!
xfaethorx
22-07-2006, 09:23 AM
the other thing is that the server i'm working with is only allowing port 8080 to be directed to it. Does activesync use any other port for the sync via web? As that might be the other problem.
xfaethorx
22-07-2006, 10:48 AM
right i've found a partial solution.
What i've done is use mod_proxy as part of the apache2 stuff to do a reverse proxy to the server over a virtual host on the system...
soo all traffic for the virtual domain foo.com goes to 192.168.1.20 which is the server behind the firewall (which just happens to be a bridged virtual machine).
That means now I can access exchange web via http on port 80 so atcive syn now connect to it.
unforutnately the crap thing is now active sync constantly asks for a username and password all the time and doesn't sync. So I'm guess it can see the server but not get any further...
so does anyone know if active sync needs access to any other ports as I can forward them much easily through the firewall.
help and thoughts please :).
xfaethorx
22-07-2006, 12:07 PM
right that did it...
two things..i'd made a mistake int he domain name on active sync and added an E into the domain name where I should have!
also because i'd promoted the VM to a Domain Controller after installing IIS etc I had to re-register the ASP.NET framework so OMA worked.
I now have push mail working on linux out of a VM whilst apache is running on the same box :)
nice ;)
jcleek
22-07-2006, 12:14 PM
Can I challenge you to document your setup and post it on a new thread for others to learn from?
xfaethorx
23-07-2006, 11:05 PM
yeah i'll do that , currently however I've been having a bit of a war with the SSL setup as the first pass was "open communications"
I've hit a snag where access to to OWA works for everything bar for internet explorer. I think i know the problem and have a solution so once I've tried that I'll document it and get it up here.
I do have reversed proxy SSL working to exchange though so now everything is secure and I can access OWA via firefox so again thats cool.
The I.E thing im certain is an issue with the actually app and that when it detects I.E it trys to be all clever but unfortuantely the domains don't match atm so its https://foo.com/exchange to http://bar.com/exchange and because of the domain name difference its getting a little twitcy.
theres three solutions, re-install everything from scratch (fat chance).
try to convert the active dicrectory domain to the one that matches foo (have you READ the documentation!....80 odd pages or something). Or change the https domain name on apache and redo the certificate (nice and easy but i'll do it tuesday).
once I can get it working seamlessly i'll do the docus :)
vBulletin® v3.7.4, Copyright ©2000-2009, Jelsoft Enterprises Ltd.