Hi folks,
I have a T-mobile dash (WM5) with a data plan (but no blackberry plan). My new employer uses only Palm OS Treo's and Blackberries for mobile corp email - although they use Outlook for desktop corp email !
The IT guys were a little puzzled with the Windows Mobile Device ! Anyway, I was wondering if there is a way to
1) Use my T-mobile dash's data plan
2) Along with a WM5 app
3) to connect to my corp blackberry's server.
I downloaded the WM5 blackberry app but it doesn't seem to connect anywhere, nor could I figure out how to set it up. Is there a step by step guide somewhere ?
Also, is that app very similar to the Treo/blackberries ? Then I could simply give my dash+BB connect to the IT guys and they could configure it (if the UI etc are similar to blackberries ... they know only treos and blackberries).
On a final note, I wanted to convince the head IT tech to support WM5 Outlook 'officially'. For this I need some information on how easy, secure it is to deploy this setup. Their current exchange server is mostly inside the corp firewall, so copying the desktop outlook settings to the dash doesn't work (desktop is inside corp firewall, dash is outside).
Thanks folks
Sid
Hello Sid!
I just came from a similar scenario- here's how I resolved my issues.
To be able to support direct push in Microsoft Exchange, a patch has to be applied to the server (The patch is called "Messaging and Security Feature Pack (MSFP) for Windows Mobile 5.0"). Direct Push allows your WM device to be in constant communication with the exchange server by pinging the exchange box for any changes to that user account (email). When a new email arrives in your inbox, your phone then downloads the new message. You can also sync your contacts, calendar, etc.
Unfortunately, my company has not applied this patch yet. When I went from my blackberry to WM5 device, they were not thrilled.
Thankfully, T-Mobile offers a push service called T-Mobile MyEmail which allows you to push email from any exchange/POP3 address. It will automatically locate the server address for you, just provide it your company email address and password.
From a security stand point, Microsoft's Direct Push is the most secure. It will also allow your system admin to remotely flash your handset if happens to get lost or stolen.
If you are interested in learning more about T-Mobile's MyEmail, go to:
http://www.myemail.t-mobile.com
For more information regarding Microsoft's Direct Push Technology, check out:
http://www.microsoft.com/windowsmobile/articles/directpush.mspx
Cheers
sublevel said:
Hello Sid!
Thankfully, T-Mobile offers a push service called T-Mobile MyEmail which allows you to push email from any exchange/POP3 address. It will automatically locate the server address for you, just provide it your company email address and password.
From a security stand point, Microsoft's Direct Push is the most secure. It will also allow your system admin to remotely flash your handset if happens to get lost or stolen.
Click to expand...
Click to collapse
But my corp email isin't POP or IMAP ... its exchange and blackberry. So while its a good suggestion, it won't help my situation. (?) I tried setting up my email via the "setup my email icon" but it doesn't work.
Also, exchange is inside the firewall so only "real" computers can access it via VPN/corp ethernet. Blackberry is outside the firewall. This is why my WM5 outlook can't even reach the real outlook server. I think I have two options
1) convince them to setup Exchange to talk to mobile devices
--> I'm going to forward your link to the IT guys so they can evaluate this option - thanks!
2) make my own WM5 device look/work reasonably similar to the Treo/Blackberries they are used to configuring. Then say "please set this up like a blackberry like you normally do".
For 2) I think I have found the app (bb connect?) but don't know
2.1) how to configure it
2.2) if it's the latest version (where do I get the latest version?)
2.3) If having just the data plan is good enough or do I need the special blackberry plan for this to work.
Hope that sheds more light .... thanks folks
Sid
Stoneage
Hi,
I have the same problem, only there's no convincing my IT department to support WM5 device. It supports only BB that are company property.
I have an external outlook privately setup with push mail and an alias for my corporate email, but the it seems like the redirect and auto forward rules I've defined in my outlook are forbidden or something, since they won't forward the mails I get from my exchange account to my external account.
Any idea how to go around this?
Some outlook plugin/software that will automatically forward mails to my external account?
Thanks.
Why don't you just get a blackberry data plan added to your account and use the blackberry connect client? That is all you need, as long as IT setup an account on your BES server at work.
Not that simple
If only life was that simple.
Not everybody can get a BB in our company and the IT department will not support devices that aren't owned by the company.
So, I'm looking for the workaround.
I have been trying to get my 8525 to do OTA Push Mail from our corporate Exchange 2003 SP2 server here where I work. I am the admin so I have access to the Exchange server and all settings are correct on the server itself to deal with OMA.
I can use the web browser of my 8525 and actually browse to our server and view both OWA and OMA directly, but when I configure the server through Activesync it always comes back with error code 80072ee7 (server name not resolved) error.
I am running vp3g's official v3 AT&T rom, and radio 1.48 if that matters. But here's where I think my problem lies and maybe someone with more experience regarding this can correct me if I'm wrong. We are running our OWA site on a high port number above 50000. We also have the OWA site under a subdirectory of the server. When I configure the server in Activesync, I enter the servername, port number and path to the OWA site, but once AS fails and I look at the server setting I find that it has dumped any path information and only keeps the server name and port number info.
So am I correct in assuming that M$ direct push only works with a server where the OWA site exists off the root directory of the IIS server? Or can it support paths into the site?
Actually push email relies on the Microsoft-Server-Activesync web application, and has little to do with OWA/OMA. I seem to recall that specifying port numbers and/or directory paths won't work though... May I ask why you're running the Exchange web services in such an unusual manner? Are you hosting other sites in that same IIS server as well?
kltye said:
Actually push email relies on the Microsoft-Server-Activesync web application, and has little to do with OWA/OMA. I seem to recall that specifying port numbers and/or directory paths won't work though... May I ask why you're running the Exchange web services in such an unusual manner? Are you hosting other sites in that same IIS server as well?
Click to expand...
Click to collapse
Actually that's the way it was set up before I started with the company. We have outside sales people that use the site and they felt it would be slightly more secure if it wasn't sitting on port 80 like most web sites. The boss won't let me change the port number at this time.
So activesync on the 8525 won't allow a port number? I thought it would because it keeps that in the server config info it'll dump any path info, but I figured out the path was not needed after a little tweaking. I just can't do anything about the port at this time.
I'm with kltye... don't think push has much (if anything) to do with OWA/OMA. It runs over port 443 (https). I believe it actually starts on port 80 (http) then switches to 443, but I'll spare you the ugly details on that one. Only need to know that for firewall config purposes.
Drop the port # and path and see how that goes.
Codevyper said:
Actually that's the way it was set up before I started with the company. We have outside sales people that use the site and they felt it would be slightly more secure if it wasn't sitting on port 80 like most web sites. The boss won't let me change the port number at this time.
So activesync on the 8525 won't allow a port number? I thought it would because it keeps that in the server config info it'll dump any path info, but I figured out the path was not needed after a little tweaking. I just can't do anything about the port at this time.
Click to expand...
Click to collapse
Security through obscurity eh?
I'm with vp3g as well: doesn't the https site run over 443? If it doesn't, maybe you can create a new Website and use the same settings as the original Exchange-Activesync web app, but have it listen on 443 for https. Are you able (i.e. "have permission") to open up port 443 on your corporate firewall?
Just did a quick perusal of my Exchange Server... appears as though push is an extension of OMA. If you don't have a Microsoft-Server-ActiveSync virtual directory off the Default Web Site (or some site listening on ports 80 & 443), you may be hosed.
Possibly related, but do you have a trusted SSL cert installed on the server? Without that, you might have a problem connecting.
vp3G said:
Just did a quick perusal of my Exchange Server... appears as though push is an extension of OMA. If you don't have a Microsoft-Server-ActiveSync virtual directory off the Default Web Site (or some site listening on ports 80 & 443), you may be hosed.
Click to expand...
Click to collapse
Yeah that's what I figured. I have the ActiveSync virtual directory within the Default Website along with OMA, but the server is listening on ports 60000 & 443 rather than the typical port 80.
You would think there would be a registry hack for AS on the mobile device whereby you could specify a non-standard port for syncing.
TaurusBullba, to answer your question. We don't have a cert (yet) for the Exchange server. That however doesn't matter for normal http connections, only if I attempt to use port 443 as the connect point for AS. Before the year is out, we'll more than likely acquire a cert for that server as well as our http server, but at the moment. I got nothing.
Inline........
Codevyper said:
Yeah that's what I figured. I have the ActiveSync virtual directory within the Default Website along with OMA, but the server is listening on ports 60000 & 443 rather than the typical port 80.
60000 is probably the killer as I noted earlier that push starts on 80 and jumps to 443.
You would think there would be a registry hack for AS on the mobile device whereby you could specify a non-standard port for syncing.
I think it was built around 80/443 to avoid client-side firewall issues.
TaurusBullba, to answer your question. We don't have a cert (yet) for the Exchange server. That however doesn't matter for normal http connections, only if I attempt to use port 443 as the connect point for AS. Before the year is out, we'll more than likely acquire a cert for that server as well as our http server, but at the moment. I got nothing.
You can do a "self-signed" certificate (i.e., generated by Windows Server) at zero cost. Downside is that it must be exported, copied to the device and installed.
Click to expand...
Click to collapse
vp3G said:
Inline........
Click to expand...
Click to collapse
Thanks for the help everyone. We will be building a new Exchange server later this year and I'll push to throw the site back on 80 at that time. In the meantime, I'll try the self-signed cert and see if that gets me in. Thanks everyone for your help! This site is a great resource for WinMo newbies like myself. BTW vp3g... lovin your AT&T v3 ROM. Solid and no problems overall!
BTW, I don't think ActiveSync starts off with port 80 - I was running a personal Exchange server off my cable connection whose incoming port 80 is blocked and everything worked fine using only 443. Good luck with the setup!
I am currently using WM6 and am trying to get EMail through our Exchange server setup; however, my Dash s620 will not properly save the server's address.
The address for our OWA is (ex) mail.email.com:8888/exchange
and this address works fine in Internet Explorer etc, but when I enter this into the phone it removes the /exchange and only saves up to :8888, which then gives me "Error synchronizing" when trying to connect. Our Exchange server does have Exchange ActiveSync enabled along with Direct Push enabled.
Any ideas?
Thanks in advance
I think that you have to check your ActiveSync settings on Exchange. I know that Microsoft have a lot of KB's about that.
It does the same thing on mine, erases exchange, but mine is cool. Are you sure you are putting in the Domain?
jt76542 said:
It does the same thing on mine, erases exchange, but mine is cool. Are you sure you are putting in the Domain?
Click to expand...
Click to collapse
Yeah I've tried every which way I could think of for the login credentials.
I'll sift through some more MS articles tomorrow afternoon, see if I can't find anything... baffled though, really.
K this is going to be a huge PITA I can tell.
I adjusted the Virtual Directory for the default web site in Exchange System manager to point directly to /exchange, eliminating the need for anything after the :8888. It works fine in IE etc, quickly brings up a login prompt. Using the phone's IE and going to the http://mail.email.com:8888 works fine, prompts a login accordingly...
I configured a coworkers Blackberry to use our OWA and it works fine, but I'm not sure if it uses Push Email (Exchange ActiveSync).
What is it about the Dash that won't mesh? The server is not using SSL so I couldn't see it being a certificate issue (maybe it still is?). Is there anyone around who manages an Exchange Server and could perhaps shed some light on common settings that need to be adjusted for Exchange ActiveSync?
Such a nuisance
ActiveSync on the phone reports "The server could not be reached. Please verify the server name." Support code: 0x80072EE7
It reports back with this no matter how I enter the address (which again, works fine in IE). Devil phone
8888 is definetly not standard for publishing ActiveSync.
the software will connect to either MailServer:80 if the SSL checkbox is cleared or MailServer:443 if the checkbox is checked.
don't think you'll get ActiveSync connect to something else.
Why don't you change your port back to 80?
you are already exposing your server to internet without any form of protection (no SSL so your password can be sniffed over the network) and having port 8888 buys you nothing in terms of security since any port scanner will report the port as opened and eventually get the HTTP banner from the IIS Server.
So, get back to a standard config and you'll love your DASH again.
UM
hey guys,
am desperately trying to fix my home based exchange server. it's been running fine with 100% uptime since last december. about a week back i was twiddling with some settings in windows and completely destroyed it.
i lost my backup of the entier machine too (it's pretty much a dedicated box for exchange). hence did a rebuild.
however now i'm just not getting it to start up. symptoms:
- OWA (outlook web access) worked. both secure and insecure modes. works on my pc.
- does not work on my PDA - OWA works but no activesync
- disabled ssh and followed the instructions here
- the phone now gives error support code 85010004 "your account in microsoft exchange server does not have permission to synchronise with your current settings. contact your exchange server administrator."
kind of annoying!
- form based authentication is enabled
- basic authentication and integrated windows authentication are ON
- same error whether or not i require SSL.
any tips?
I occasionally get the exact same error message when I sync with my company's exchange server, I have to do a soft reset on the phone and then it works fine. No idea how to fix it so bump
we had quite a few issues originally and think this is one of them i think.
Most revolved around having a recognised accessible dns address that allowed a direct link.
never got ssl to work.
the other issue was getting appropriate certificates that were private to be issued when creating the sync partnership.
can u sync internally using exchange server via a cradled activesync?
get this 2 work first, then look to external push.
I ended up paying it engineers to get it to work over an sbs 2003 box as it was all to much.
but dns addresses being made public, that were also accessible internally (reverse lookup i think) along with no ssl and certificates being correct were our main hurdles.
issue fixed i'm all live! after all that effort i really feel i should open this up to those who don't want to spend days fixing it up...
check http://forum.xda-developers.com/showthread.php?t=346022. currently looking for testers for 1-2 days before i make a subscription based service!
Is anyone else having trouble with configuring the Exchange Server e-mail to work on the Tilt 2 Phone? I know that I've entered the right settings for the server name, domain, etc. Unfortunately, though, I keep getting an error message saying "error synchronizing." When configuring via Active Sync, the specific support code that I'm getting is 0x80072EE7. I've tried everything else that I know how to do. Is there anything that I'm missing? Has anyone else had this problem and figured it out? Thanks for the help.
The only thing that I can suggest is to check the user name that you are entering. In mine it asks for the user name but it really wants the whole email address again. Good luck, I hope that helps.
Exchange Server Problems...
thedon0369 said:
The only thing that I can suggest is to check the user name that you are entering. In mine it asks for the user name but it really wants the whole email address again. Good luck, I hope that helps.
Click to expand...
Click to collapse
Thanks a lot for the reply. I did go ahead and try as you suggested. Unfortunately, it doesn't seem to be working. I tried several variations of what you suggested, but still nothing worked... frustrating!
Exchange Server Problems
AT&T is saying that I need to pay for a different data plan - more money, of course - for me to be able to access the Exchange Server. I guess the 40 dollars that I pay each month for data and text messaging isn't enough. They said that I'd need to pay them another 15 dollars, or so, a month for me to access Exchange Server e-mail. I guess it's different from accessing regular POP3 or IMAP e-mail. Does this sound right? Would I need to pay additional money, beyond the full data package that I already pay for, in order to access Exchange e-mail? There has to be another way, right?
No other way around it that I know of. You need an Enterprise data plan to hit an Exchange Server. The extra charge is probably due to the extra data useage of being constantly connected to the Exchange Server. I'm not saying the extra charge is justified. An unlimited data plan should be unlimited. But we all know AT&T has a different definition of "unlimited". It's just the way the great Death Star operates.
PiSigma said:
No other way around it that I know of. You need an Enterprise data plan to hit an Exchange Server. The extra charge is probably due to the extra data useage of being constantly connected to the Exchange Server. I'm not saying the extra charge is justified. An unlimited data plan should be unlimited. But we all know AT&T has a different definition of "unlimited". It's just the way the great Death Star operates.
Click to expand...
Click to collapse
That's what I feared... Thanks for your time and assistance with this. I appreciate it. (I won't be paying them anymore money, though! I'll just have to deal with it...)
Weird...both my wife and I have the $30/month data plan and it lets us download from Exchange.
Try configuring the server via the Activesync. My company's email address and username (login name for your corporate network) are not the same and I don't think it prompts you during initial setup. If your company has a similar infrastructure as mine, be sure to enter your email address where it asks for that, and your network login username (not your email address) when it asks for the login credentials.
Edit: A quick Bing search came up with this: http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_22027911.html
Scroll all the way to the bottom of the page to see what the resolution is for that exact error code. Basically, it boils down to your SSL/encryption settings on your phone not matching what's required by Exchange. It has nothing to do with sending AT&T more money.
e_dogg said:
Scroll all the way to the bottom of the page to see what the resolution is for that exact error code. Basically, it boils down to your SSL/encryption settings on your phone not matching what's required by Exchange. It has nothing to do with sending AT&T more money.
Click to expand...
Click to collapse
I'm also getting Exchange mail on the $30 a month data plan.
That's a good suggestion on the SSL settings--try either checking or unchecking that box during the setup.
One thing to try is hook up your phone to WiFi to see if that stops the error, then you know its AT&T thats stopping your Exchange from working. Otherwise you know its another error.
DD7374 said:
AT&T is saying that I need to pay for a different data plan - more money, of course - for me to be able to access the Exchange Server. I guess the 40 dollars that I pay each month for data and text messaging isn't enough. They said that I'd need to pay them another 15 dollars, or so, a month for me to access Exchange Server e-mail. I guess it's different from accessing regular POP3 or IMAP e-mail. Does this sound right? Would I need to pay additional money, beyond the full data package that I already pay for, in order to access Exchange e-mail? There has to be another way, right?
Click to expand...
Click to collapse
Exchange Server ActiveSync operates 100% over HTTP over SSL. If you can go to websites that are prefixed with "https://" then you can access Exchange Server ActiveSync provided you are configured correctly.
The first thing that I would suggest doing, is verifying that the web services for the Exchange you're trying to connect to are properly configured, by visiting the following URL:
https://[DNS host of your Exchange]/Microsoft-Server-ActiveSync/
If you're prompted to enter credentials, enter them:
[DOMAIN]\[username]
[password]
And see if you get an HTTP 501. If you do get this HTTP Status Code, it means that Exchange Server ActiveSync is properly configured on the Exchange end. If you do not get this status code, or do not get prompted for credentials, it means that either the Exchange server is not [properly] configured for Exchange Server ActiveSync, or that, that service is not properly published to the internet.
If you are warned about an untrusted certificate, this could be your problem. You will need to obtain a copy of the root certification authority which signed the SSL certificate for the Exchange, and install it on your phone.
Then, try going to this address on your phone. You should experience the same behaviour. This means that either:
A. You are setting up your phone wrong.
B. Your e-mail account has been blocked from using ActiveSync by an Exchange administrator.
If you cannot go to this address on your phone, try going to another site that is HTTPS, and see if that succeeds.
I just got exchange working for myself, after coming up against what felt like a brick wall, and smacking my head against it for a few days.
First things first, check if your server is set up for it. go to https://youremailserver/oma and see what you get. You should get prompted for your username/password, then (maybe) get a warning about an unsupported device, then get a super-pared-down screen with links to inbox etc...
As a side note, this should also work from your phone's web browser (that's what that site was made for), though you'll be zooming in after every click.
If you don't get all that, or get an error message, then contact your administrator, 'cause it's not set up.
If you are the administrator, or your administrator wants to set it up but doesn't know how, let me know (by PM, I'll probably forget to look here later) and I'll send you the steps. It's server config stuff and you'd need admin privileges on the exchange server. The default settings in Exchange Server simply don't allow for OMA.
Just a follow up to my earlier post - I spoke with three different AT&T CS reps today, including one from the Wireless Data Group, and they all told me you would be violating your ToS if you access an Exchange Server with a PDA Personal plan. So, while this may not be the technical cause of your problems, it could be an issue if you get caught. Sort of like those of us who tether without a tethering plan.
Just FYI......
kay7 said:
I just got exchange working for myself, after coming up against what felt like a brick wall, and smacking my head against it for a few days.
First things first, check if your server is set up for it. go to https://youremailserver/oma and see what you get. You should get prompted for your username/password, then (maybe) get a warning about an unsupported device, then get a super-pared-down screen with links to inbox etc...
As a side note, this should also work from your phone's web browser (that's what that site was made for), though you'll be zooming in after every click.
If you don't get all that, or get an error message, then contact your administrator, 'cause it's not set up.
If you are the administrator, or your administrator wants to set it up but doesn't know how, let me know (by PM, I'll probably forget to look here later) and I'll send you the steps. It's server config stuff and you'd need admin privileges on the exchange server. The default settings in Exchange Server simply don't allow for OMA.
Click to expand...
Click to collapse
I don't know what version of Exchange you're thinking of, but I'm running Exchange Server 2007, and "OMA" is not a virtual directory on my CAS.
PiSigma said:
Just a follow up to my earlier post - I spoke with three different AT&T CS reps today, including one from the Wireless Data Group, and they all told me you would be violating your ToS if you access an Exchange Server with a PDA Personal plan. So, while this may not be the technical cause of your problems, it could be an issue if you get caught. Sort of like those of us who tether without a tethering plan.
Just FYI......
Click to expand...
Click to collapse
How are they going to catch you? Crack open that SSL tunnel and examine your traffic?
I think they have better things to do.
Just thought I'd mention that I've gotten my Exchange Server to work. Thank you to everyone who's given suggestions to me in order to resolve my problem. It's nice to know that everyone here is so helpful. Thanks again.
PiSigma said:
Just a follow up to my earlier post - I spoke with three different AT&T CS reps today, including one from the Wireless Data Group, and they all told me you would be violating your ToS if you access an Exchange Server with a PDA Personal plan. So, while this may not be the technical cause of your problems, it could be an issue if you get caught. Sort of like those of us who tether without a tethering plan.
Just FYI......
Click to expand...
Click to collapse
Thanks for the tips... I appreciate all your time.
kay7 said:
I just got exchange working for myself, after coming up against what felt like a brick wall, and smacking my head against it for a few days.
First things first, check if your server is set up for it. go to https://youremailserver/oma and see what you get. You should get prompted for your username/password, then (maybe) get a warning about an unsupported device, then get a super-pared-down screen with links to inbox etc...
As a side note, this should also work from your phone's web browser (that's what that site was made for), though you'll be zooming in after every click.
If you don't get all that, or get an error message, then contact your administrator, 'cause it's not set up.
If you are the administrator, or your administrator wants to set it up but doesn't know how, let me know (by PM, I'll probably forget to look here later) and I'll send you the steps. It's server config stuff and you'd need admin privileges on the exchange server. The default settings in Exchange Server simply don't allow for OMA.
Click to expand...
Click to collapse
I got it! Thanks for your help.
Spike15 said:
Exchange Server ActiveSync operates 100% over HTTP over SSL. If you can go to websites that are prefixed with "https://" then you can access Exchange Server ActiveSync provided you are configured correctly.
The first thing that I would suggest doing, is verifying that the web services for the Exchange you're trying to connect to are properly configured, by visiting the following URL:
https://[DNS host of your Exchange]/Microsoft-Server-ActiveSync/
If you're prompted to enter credentials, enter them:
[DOMAIN]\[username]
[password]
And see if you get an HTTP 501. If you do get this HTTP Status Code, it means that Exchange Server ActiveSync is properly configured on the Exchange end. If you do not get this status code, or do not get prompted for credentials, it means that either the Exchange server is not [properly] configured for Exchange Server ActiveSync, or that, that service is not properly published to the internet.
If you are warned about an untrusted certificate, this could be your problem. You will need to obtain a copy of the root certification authority which signed the SSL certificate for the Exchange, and install it on your phone.
Then, try going to this address on your phone. You should experience the same behaviour. This means that either:
A. You are setting up your phone wrong.
B. Your e-mail account has been blocked from using ActiveSync by an Exchange administrator.
If you cannot go to this address on your phone, try going to another site that is HTTPS, and see if that succeeds.
Click to expand...
Click to collapse
I got it! Thanks for your help.
kay7 said:
I just got exchange working for myself, after coming up against what felt like a brick wall, and smacking my head against it for a few days.
First things first, check if your server is set up for it. go to https://youremailserver/oma and see what you get. You should get prompted for your username/password, then (maybe) get a warning about an unsupported device, then get a super-pared-down screen with links to inbox etc...
As a side note, this should also work from your phone's web browser (that's what that site was made for), though you'll be zooming in after every click.
If you don't get all that, or get an error message, then contact your administrator, 'cause it's not set up.
If you are the administrator, or your administrator wants to set it up but doesn't know how, let me know (by PM, I'll probably forget to look here later) and I'll send you the steps. It's server config stuff and you'd need admin privileges on the exchange server. The default settings in Exchange Server simply don't allow for OMA.
Click to expand...
Click to collapse
if you could send it to me that would be great, i'll pm you
Hi,
I had a similar problem with my TP2. Its unbranded and connected to T-Mobile UK. The phone woould not load any https sites, because the t-mobile connection settings has the 'Use proxy server' option checked. As soon as i unchecked that it sync'd to exchange perfectly.
not sure f that option is checked on yours.
Ian..