Is anyone having a problem connecting to an exchange account using the leaked rooted GB?
HELP....
I'm having a problem. I get an error stating there is not enough memory for encryption....
I can connect to an Exchange 2010 server with no issues using corporate sync. Most Android/Exchange problems that I have seen are a result of Activesync Device Policies on the Exchange server blocking access.
My issue is that it works fine, its just that I cannot download my exchange key!....WTF? I refuse to pay 19 dollars again! my fault I thought you were talking about Touchdown for Android. Disregard!
I'm connecting to Exchange 2007 without issues. But I don't have a custom certificate to install.
What do you mean by exchange key?
For anyone out there that has corporate sync working... When you set up the account, did you only get a prompt for 'Email Address', 'Password', 'Domain' and 'Username'? Those are the only prompts I get. I then press 'Next' and then I get the error "Login to the account failed, please try again." There were never any prompts for 'server name' or 'SSL Encyption' like I have always got before.
UPDATE: It turns out that if you press the menu key there are more options. It's working now.
idtheftvictim said:
Is anyone having a problem connecting to an exchange account using the leaked rooted GB?
HELP....
Click to expand...
Click to collapse
Had the same problem, to fix I had to create a secondary EAS policy (server side) (I'm an Exchange Admin for my company). I had to modify the 'required password' settings:
1: Lowered the "Time without user input befor password must be re-entered (in Minutes)" field.
2: Unchecked the "Allow simple password" field.
You may have to buy your sys admin's a few round of beers to get them to make an additional policy. (LOL)
After that mine and 3 others were able to connect and sync without issue.
BTW: The changes that have been made to the native client rock, they have updated the UI so it's black/gray'ish on white, and you now have the ability to sync sub-folders.
Cheers,
Hatxtrick
Working fine for me with Exchange 2007.
Sent from my DROIDX using XDA App
I also am using Exchange 2007 with SSL cert and it prompted me for the address of the exchange server.
phantom404 said:
I'm having a problem. I get an error stating there is not enough memory for encryption....
Click to expand...
Click to collapse
Phantom404 your company's EAS policy is set to require your device be encrypted, if you are receiving a message that there's not enough space you need to do some app/sdcard cleanup to free up some space..
Cheers,
Sent from my Xoom using Tapatalk
hatxtrick said:
Had the same problem, to fix I had to create a secondary EAS policy (server side) (I'm an Exchange Admin for my company). I had to modify the 'required password' settings:
1: Lowered the "Time without user input befor password must be re-entered (in Minutes)" field.
2: Unchecked the "Allow simple password" field.
You may have to buy your sys admin's a few round of beers to get them to make an additional policy. (LOL)
After that mine and 3 others were able to connect and sync without issue.
BTW: The changes that have been made to the native client rock, they have updated the UI so it's black/gray'ish on white, and you now have the ability to sync sub-folders.
Cheers,
Hatxtrick
Click to expand...
Click to collapse
One issue I'm having is in regards to syncing sub-folders. Just wondering if anyone else is having this issue ? Specifically, I can select "Auto sync in background" for my Sent folder, but it doesn't appear to "stick". I'll go back a couple of screens (or back to home screen), and when I go back in, it is back on Manual again.
Related
I have searched and searched for an answer to this problem and have not been able to find anything. Hopefully someone here has run into this before and might have an idea or solutuion. Her is my problem.
I have two exchange servers (2003 SP2) on of which is a front end server handling OWA and OMA. We sync about 18 Windows Mobile 6.1 devices over the air using OMA. We are using SSL. All of our devices have random problems connecting to the server. They will sync fine most of the time but will randomly for no particular reason ask the user for their exchange password. We are not enforcing any password policies on the server and we are always checking the box to save the password. In order to get the device synching again the user has to re-enter their password multiple times and often has to kill and restart activesync on their device.
Any ideas as to what might be causing this?
Any help would be much appreciated.
You could try unchecking the box in Activesync on the phone that requires SSL. We use SSL as well, but we have to uncheck that box on the phone. Although our problem is that the phone never syncs when its checked as opposed to your problem of randomly not syncing and asking for a password.
Unfortunately that is not an option. Our SSL is required for authentication. It will not connect without it. It seems like what is happening is that the device is not always passing the credentials to the server. Usually when it asks me for the password I enter the password once making sure I check the Save Password box then when it asks me the second time I hit cancel. ActiveSync then gives me a could not authenticate error. Now if I just hit Sync again it goes through and works just fine without asking for the password. So my guess is that it is not passing the credentials until after the connection is reinitialized.
From what I understand, Push Email relies on the OMA functionality which uses IIS. The problem my lie there. Although I've never tried, you may have to uninstall/reinstall (or confirm) that the OMA part of Exchange is functioning correctly. Sorry I can't be of more help.
Do the log files on the server show anything when a phone can't log in?
No, the exchange logs don't show much. I almost think it might be something with the device configuration. At this point I just don't know. We will be migrating to Exchange 2007 sometime in the next few months. Hopefully that will resolve the problem permanently. I was just hoping maybe by some chance someone here had seen this problem before. Thanks a bunch for your help.
Is the FE server doing the authentication (NTLM) or is there an ISA server in the way configured with Forms Based Authentication? You should make sure the IIS virtual directory for OMA is set only for Basic Auth - and the following article might be worth a read.... http://searchexchange.techtarget.com/tip/0,289483,sid43_gci1188440,00.html
Hope that helps - good luck!!
Mark.
^^^What he said. Took the words right out of my mouth. You'll still be secured through the SSL certificate, even though you're doing "basic auth" you aren't exactly sending your password as clear text. Requiring SSL on the OMA site will automatically encrypt the connection so you have no need to worry.
Try it out and get back in here. I manage a site with about 50 WM 6.1 Black Jack II's that sync with Exchange 2007 with no issues whatsoever. Also verify that you have all your hotfixes related to OMA installed on your Exchange 2003 server.
Hello to all.
I am using X1 with Dutch Tmobile.
One of the steps to complete setup for exchange account was providing lock pin/password, this was obligatory.
The problem i have now is that I can not disable it. Checkbox is greyed out and I can only change: lock time (0, 3, 5) and password itself.
I am really happy with Exchange acces from X1 but pin is really annoying.
Any help appreciated.
Cheers
gruczniak said:
Hello to all.
I am using X1 with Dutch Tmobile.
One of the steps to complete setup for exchange account was providing lock pin/password, this was obligatory.
The problem i have now is that I can not disable it. Checkbox is greyed out and I can only change: lock time (0, 3, 5) and password itself.
I am really happy with Exchange acces from X1 but pin is really annoying.
Any help appreciated.
Cheers
Click to expand...
Click to collapse
I have the same problem which is really anoying especially when using Tomtom as I have to type in my password every 5 minutes whilst driving.
From what I have been able to find out, it is caused by the policies on your server/exchange server, where for company information security reasons it requires a password and prohibits the phone user to dissable this function.
To change this, a change in windows server or exchange server is necessary.
If anybody can post instructions on how to do this I would be most grateful.
In Exchange 2003 SP2
You need to open system manager and click the + sign next to global settings. Now right click on mobile settings and select properties.
In the dialog box that has appeared click on device security and then u will have several options to do with the device pin code.
Enjoy.
scotjen1 said:
In Exchange 2003 SP2
You need to open system manager and click the + sign next to global settings. Now right click on mobile settings and select properties.
In the dialog box that has appeared click on device security and then u will have several options to do with the device pin code.
Enjoy.
Click to expand...
Click to collapse
Thanks for pointing me in the right direction.
In exchange 2007, start Exchange Management Console, navigate to Organisation Configuration/Client Access/Mailbox Policy Server. Double click, select Password tab and uncheck require password. Sync with active sync and then you can remove the password.
Huge thanks for that! It has been bugging the hell out of me. Am using Small Business Server 2008 and it does all these settings automatically so I had no clue where to look.
Saddly for me my organization is to big to alter anything on the Exchange server.
Exchange policy update is still a workaround when you do not sync for some time (vacation etc)
Trying to set up ActiveSync on my Telus P4000 (Titan), although the issue should be the same with an WM6.1 phone...
I can't for the life of my figure the right server settings to enter in the Configure Server section, and I have yet to find a definitive "this is how you do it" procedure for it. As near as I've been able to glean, for the "Server address" section, you give it JUST the domain name of the Exchange server, without an http:// or a /exchange or /oma or anything... correct so far? But the catch in my particular instance is that Exchange web access is on port 8080, rather than 80 or 433.
I've tried adding a :8080 to the server address, I've tried adding the http:// and/or https://, I've tried adding the /oma and /exchange to the end, and all combinations of the above, with no luck... when I go back into the settings, it's reverted to JUST the domain name. Is there somewhere else I can tell it to use a non-standard port? Registry key, maybe?
I'm not sure it works with other ports than 80 (HTTP) and 443 (HTTPS).
You just need to put your external A record in the server value.
Try using standard ports first to be sure everything is working, then switch.
Okay, well I managed to get rid of the "Cannot reach server" messages by switching back to "require SLL", and as it turns out, the server wasn't set up for SSL (it is now). So now I'm connecting, but getting certificate errors. At least I've found plenty of info about solving that issue, so on to the next step...
Soundy106 said:
Okay, well I managed to get rid of the "Cannot reach server" messages by switching back to "require SLL", and as it turns out, the server wasn't set up for SSL (it is now). So now I'm connecting, but getting certificate errors. At least I've found plenty of info about solving that issue, so on to the next step...
Click to expand...
Click to collapse
You will probabby have to install a certificate on the phone to be able to communicate with the exchange server. At least i had to...
playerkiller said:
I'm not sure it works with other ports than 80 (HTTP) and 443 (HTTPS).
You just need to put your external A record in the server value.
Try using standard ports first to be sure everything is working, then switch.
Click to expand...
Click to collapse
I've searched everywhere for info on using non-standard ports for activesync, and I haven't found anything, and I couldn't get it to work.
jeen said:
You will probabby have to install a certificate on the phone to be able to communicate with the exchange server. At least i had to...
Click to expand...
Click to collapse
Yeah, did that... still not helping
Go to first new post ActiveSync config for Exchange
Exchange ActiveSync cannot access the server if SSL is set to be required. For
information about how to correctly configure Exchange virtual directory
jeen is right. Unless the certificate is issued form a Trusted Certificate Authority, you will need to import the issuing CA in the Root Certification Authority store of your Phone.
If it's a self signed cert, just export it from exchange server (without Private key) and copy it to your phone. Then, double click it from File Manager. This should be enough.
^Yeah, I did that right off the top (see my reply to jeen). Still no joy.
Perhaps Tendulkar can finish his thought...
To disable SSL requirements for Activesync service is very easy:
Win2003 (IIS6.0)
Open IIS on your cas, expand the Default Website (or the website where ASVritualDir resides) right click on Microsoft-Server-ActiveSync and choose properties.
Go to the tab Directory Security, choose EDIT under Secure Communication.
Remove flag from Require Secure Channel.
Obvsiulsy Click ok.
Win2008 (IIS7)
Open IISManager.
Navigate through site, default website, hilight Microsoft-Server-ActiveSync.
Make sure you have the features view selected (should be by default).
Choose SSL Settings.
Unflag "Remove SSL".
Obviusly click Accept.
playerkiller said:
To disable SSL requirements for Activesync service is very easy:
Win2003 (IIS6.0)
Open IIS on your cas, expand the Default Website (or the website where ASVritualDir resides) right click on Microsoft-Server-ActiveSync and choose properties.
Go to the tab Directory Security, choose EDIT under Secure Communication.
Remove flag from Require Secure Channel.
Obvsiulsy Click ok.
Click to expand...
Click to collapse
Hmmm... "require SSL" was already un-checked. I've re-checked it, let's see what happens with that.
OK lemme know.
make sure you have the same root certificate installed also. you have to trust the same certificate authority as the certificate that you have on your exchange server.
Did anyone find solution
I am having same problem. Certificate installed and tried all connection settings that can find on internet. Cannot get ActiveSync to syn with my server (same certificate error, but hosting company states tested with WM6.1 that all is working fine on their end) and also cannot get Windows Live Messenger to work, states there's a connectivity problem. Funny thing is MMS, surfing net with IE, and Google Maps with GPRS work fine. Only Microsoft network products are not working. My phone is Palm Treo Pro with WM6.1 Professional. Vodaphone version but bought in China and have since added A4 Chinese text editor, which I think could be problem, but need to hard reset phone to check. Any ideas? Better yet, any solutions?
One tip for getting this working in my case (same certificate errors) was that I had to get the certificate off the internally facing OWA server, rather than the externally facing version. Although they're both the same server, the external one goes through an IAS box which seems to be presenting its own certificate rather than the one on the exchange server. Don't ask me - I don't run the system.
As soon as I add the Internal version of the cert, Exchange, OTA Sync and ActiveSync spring into life.
I picked up the focus yesterday and have run into an issue syncing with Outlook/Exchange Server 2003. I receive the error code below after the email account setup runs for a bit, I get contacts and calendar entries, then a few emails before the error is returned (everytime I try to sync later as the msg suggests). I tried finding the error code referenced on MS Support/Forums, AT&T Samsung forums, and even xda developers with no luck.
I did try a hard reset (from settings) and then recreate the account and I tried removing the hub on the start screen and then deleted the account and recreate same error every time.
Samsung Tech Support suggested that I add the same Certificate on my Server to the phone, Did so - still, no luck.
Anyone see this error/issue?
Outlook Error
Not Updated
We're having a problem syncing your
information. Try again later.
Last tried about a minute ago
Erro code: 8500201C--------------------------------------------------------------------------------
Mine has worked flawlessly. Sounds like you did everything I would have suggested except return and get a replacement phone.
I had that problem. the cause of mine was to have the SSL turned on. After I created the account, I went to setting>email and choose the outlook account, clicked on advanced, then scrolled down and uncheck the SSL checkbox. All worked perfect after that. although I guess I am not super secure.. but anyone that wants to hack and read my email.. feel free pretty boring.
It is obviously a software issue. How can a replacement phone solve any problem.
If your exchange server does not use public certificates (the ones that your company has to pay for), or the certificate comes from some publisher that WP7 doesn't know about, it will be touch to set it up. For one, import the server certificates directly does not work. In the past with WM phones, MS suggests you need to import the root certificate instead. So, see if you can find the root certificate for it.
agreed - was able to get Corporate Store to allow me to try settings on another Focus, with same results.
can see the Folders on my Outlook (some are unique to my Exchange Server), so we know that we are nearly there. little more tweaking, and also, update to a new Server,
but, that might not be for week or so, so if anyone has solutions, would be much appreciated.
I had problems with mine and worked with our Exchange admin. We found it was the encryption part of our policies. Both Device and Storage card encryption parts of the policy have to be turned off. After some research this is correct and expected to be fixed in Early 2011 when Microsoft starts pushing this for business.
Oh it also does not support alphanumeric passwords at the moment:
http://social.answers.microsoft.com/Forums/en-US/windowsphone7/thread/ee2ecd48-89bf-4e8c-b48e-553967517a4d
Here is the one about encryption:
http://social.answers.microsoft.com/Forums/en-US/windowsphone7/thread/7c4329c9-9f51-4184-8f48-5d4bc5c6269e
cwiley2566 said:
Oh it also does not support alphanumeric passwords at the moment:
http://social.answers.microsoft.com/Forums/en-US/windowsphone7/thread/ee2ecd48-89bf-4e8c-b48e-553967517a4d
Click to expand...
Click to collapse
That is really strange because my HTC Surround took my alpha numeric password just fine for my exchange email. Haven't had any issues with it at all.
Do you mean a password for the domain or the screen lock password? They are talking about the policy that requires a alpha numeric password (or not allowing simple passwords) for unlocking your screen. Our company allows simple passwords (just numbers) so I didn't see the problem.
We don't have a certificate,and all I had to do was go to advanced and turn off encrypted SSL connection ( I also have alphanumeric and symbol password for exchange)
I am referring to the screen lock policy in Exchange. Of course alphanumeric and symbol passwords for exchange/domain authentication will work.
Installing SSL Cert (quick and dirty)
Email your server's SSL cert to a GMail account. Hotmail blocks the attachment as an unsafe filetype.
Open the attachment and Phone7 should ask you if you want to install. Go back and set up your Outlook account.
Got mine working on Exchange 2003 even after the error messages
This happened to me as well. We have an Exchange 2003 server and what I did was go to "email and accounts" on the phone and went through the proccess and setup everything correctly but still got the error messages.
Now this is what fixed my issue (strange). I got out of the "email and accounts" and went into all programs list and opened "Outlook" , from there I put the settings in again for my account and presto, it just started working and syncing.
I did 2 phones likes this already and it works. Dont ask me how, but it does.
Hope this helps OP and anyone else using Exchange 2003.
After having been connected to my company's MS Exchange server on my HTC EVO for over four months, I was prompted to change my password on the domain (on my PC) and since then, I've not been able to re-connect with the new password.
I tried deleting the account and rebooting my phone and re-creating the account from scratch, but whenever I try to re-connect, I get the following error message:
Setup could not finish
Unable to open connection to server
The IT guy at work put in his own credentials and had the exact same problem.
The interesting thing is that I downloaded a trial of Touchdown for Exchange which uses the same credentials, and that seems to connect fine. I have no idea why one works and not the other.
Does anyone know what might be happening when I try to connect by adding a new account?
My suspicion is that there was some change in the Exchange server settings that impacted me once I changed my password to reconnect, but would like to hear other theories.
aagha said:
After having been connected to my company's MS Exchange server on my HTC EVO for over four months, I was prompted to change my password on the domain (on my PC) and since then, I've not been able to re-connect with the new password.
I tried deleting the account and rebooting my phone and re-creating the account from scratch, but whenever I try to re-connect, I get the following error message:
Setup could not finish
Unable to open connection to server
The IT guy at work put in his own credentials and had the exact same problem.
The interesting thing is that I downloaded a trial of Touchdown for Exchange which uses the same credentials, and that seems to connect fine. I have no idea why one works and not the other.
Does anyone know what might be happening when I try to connect by adding a new account?
My suspicion is that there was some change in the Exchange server settings that impacted me once I changed my password to reconnect, but would like to hear other theories.
Click to expand...
Click to collapse
I for the life of me don't understand why I can connect to my exchange server using a third-party app (touchdown) but not using the native email app.
Sent from my PC36100 using XDA App
If your company made any changes to their exchange server, then you need to figure out exactly what is needed to connect. I have setup 10 different android phones on our exchange server, and the settings to connect were different on 5 of them. We also had 3 of them that were on exchange 2010 instead of exchange 2003, and those settings were even more different.
matt2053 said:
I for the life of me don't understand why I can connect to my exchange server using a third-party app (touchdown) but not using the native email app.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
+1. I've spent hours with IT and with Sprint and nothing. I got this from Sprint to help my get it going, so I will post here in hopes it will help you. They sent me this link:
http://community.sprint.com/baw/message/208942
And this email:
"The only way to fix this issue is by having access to Active Directory on a server with Exchange plugins.
Go Active Directory Users & Computers (Enable Advanced Features if needed)
Open the properties of the user that is having the issue
Click on the Security Tab
Click the Advanced button
In the Default Permissions tab check the box at the bottom for "Include inheritable permissions from this object's parent"
Wait for AD to propagate (5-10 minutes) "
The info on the link I was not able to try because it required changes being made to the server that my company would not allow. The email info they sent me did not apply to me because the server at my job was already set up that way.
Good luck. I gave up getting the native app to work right. I don't know why something that should be so simple is such a mission.
Not sure if this will work or if you have tried it but. Clear the application data/cache from the applications menu in settings.
For you server, did you put in "owa.mycompany.com" or "somethingelse.mycompany.com"?
It sounds like this might be the problem. You need to have your owa server listed there instead of the exchange server for Outlook.
Jye75 said:
For you server, did you put in "owa.mycompany.com" or "somethingelse.mycompany.com"?
It sounds like this might be the problem. You need to have your owa server listed there instead of the exchange server for Outlook.
Click to expand...
Click to collapse
Yes, I gave that a shot: connect.companyname.com
Thanks for the suggestion though.