Related
Gday all,
I've recently moved over from old nokia to a new windows mobile device (Samsung i620 if it matters). Every time I power cycle the phone, turn the radio off or go out of coverage the clock is automatically set one hour slow, and doesn't even alert me or prompt before doing so.
My laptop, desktop and exchange server all sync the time correctly. All devices are set to the correct locale, time zone and DST settings.
Does ANYONE know how to disable this sync with network 'feature' in WM6? I've found plenty of places that explain how to do so in WM5, but none for WM6. Surely there'll be a registry flag for this?
Many thanks for any helpful suggestions,
Alex
settings/system/clocks & alarms
Thanks, but that doesn't exist in this version - CE OS 5.2.1439 build 17947.0.3.3.
In settings I have:
Phone
Sounds
Display
Profiles
Key Settings
Date and Time (not in here)
Slide settings
Connections (not in here)
Security
Remove Programs
Power Management
Operator Settings (not in here)
Regional Settings (not in here)
Sending SMS Options
Owner info
Memory info
Accessibility
About
Error reporting
Version
Windows Update
I'm pretty certain I have checked every possible setting that can be configured from the UI, hence my wondering about a possible registry key?
Is no-one else seeing this problem?
The Problem: I cannot get Exchange to sync correctly when using any 6.1 ROMs.
AT&T Tilt
AT&T SIM
Exchange 2003
Radio: 1.58.26.20
I really need to be able to Exchange sync in order to accomplish my job. From reading though the many 6.1 threads and searching around, I have found that people seem to be occasionally running into this problem, but there hasn't been any resolutions mentioned yet. The problem for me is that synchronization will not occur in ActiveSync. At one point, it would sync my contacts even though it said the sync failed. Others have reported that it will sync contacts and calendar but not email.
The Active Sync error code that I get after flashing a new 6.1 ROM and setting up Exchange the normal way is:
Result: Synchronization could not be completed. Try again later.
Support Code: 0x80830003
Here is a list of things that I have tried so far from searching and asking around that did not work:
1. Didn't work: Installing "remove hidden proxy" .cabs.
2. Didn't work: "What, exactly, are you having issues with? It's not an Exchange 2k3 incompatibility, as mine is synching fine. I did have to go into Settings > Connections > USB and turn off advanced network capabilities, though."
http://forum.xda-developers.com/showpost.php?p=1940649&postcount=1155
3. Verify the following Exchange setting (already checked): "On the Exchange server, launch Internet Services Manager. Right click on the Microsoft-Server-ActiveSync virtual directory and choose Properties. Select the Directory Security tab. Click the Edit button in the Secure Communications section and select the option to 'Ignore client certificates.'"
http://download.microsoft.com/downl...ices-Deploying_Microsoft_Mobile_Messaging.doc
4. Verify the following Exchange setting (not running Exchange 2007): "I also had trouble syncing with Exchange. I run Exchange 2007 and had to enable the option to allow the enrolment of non-supported devices in my ActiveSync policy. With WM5.0 or 6.0 it always worked flawlessly."
http://forum.xda-developers.com/showpost.php?p=1938858&postcount=1025
5: After trying kewlair's suggestion:
"The first issue I had was the initial setup. I set up my account properly, but ActiveSync would report that it cannot sync at this time. I knew that I had to uncheck the Use Proxy for this Connection option to solve this issue, but I couldn't find where to get to that setting for the MEdia Net connection that was being used. I finally found it in Settings -> Connections -> Advanced Tab, then tap the Select Networks button and where it says "Programs that automatically connect..." select MEdia Net instead of My ISP and then you can tap the Edit... button and remove the proxy server selection."
http://forum.xda-developers.com/showpost.php?p=1957501&postcount=3
...attempting to force a sync gives this. I also tried changing "Programs that automatically connect..." to My ISP with the same result:
ActiveSync tries to connect using either MEdia Net or My ISP and then says:
"Cannot Connect
Dialed: Cannot connect for an unknown reason. To check your connection settings and change them if needed, tap Settings. If the problem continues, reset your mobile device according to your manufacturer's documentation and try again."
ActiveSync Reports: "Waiting for network"
Right i am pissed so i might be being a ****, but, it would help if you told us
a) what version of exchange you are running.
b) whether you are using ssl to sync with the server
c) whether you are talking about syncing when connected to the pc, over gprs or such, or both.
Rob
Yeah, I have noticed some issues as well. I'm using dutty's official 6.1 release.
The first issue I had was the initial setup. I set up my account properly, but ActiveSync would report that it cannot sync at this time. I knew that I had to uncheck the Use Proxy for this Connection option to solve this issue, but I couldn't find where to get to that setting for the MEdia Net connection that was being used. I finally found it in Settings -> Connections -> Advanced Tab, then tap the Select Networks button and where it says "Programs that automatically connect..." select MEdia Net instead of My ISP and then you can tap the Edit... button and remove the proxy server selection.
The second issue I have found is that after a while (not sure on specific time) ActiveSync just seems to stop working, almost as if it is hung up. When I go to the ActiveSync window and tap Sync, it does absolutely nothing. Basically the only way i've found to get it to start working again is doing a soft reset.
Hopefully this will help you or other people out, because it took me FOREVER to figure this out. I am curious if anybody else is having problems with ActiveSync stopping responding with 6.1 also.
Same here
Hello,
I am having the same problem here.
I am using DCS 1.5 and windows Vista (Windows Mobilde Device Center). It has been working beautifully for a week..
But now I cannot connect the device to my computer through USB. When I do the charge led is on, but the device is not seen by vista.
I checked off "enable advanced network functionnality" in the USB to PC settings.... But nada!
Any help from otehrs would be appreciated.
Juju
I'm sorry, I might not have been clear. ActiveSync on the device hangs up, not on my computer. I haven't had any issues with ActiveSync on my computer so I think this is a different issue.
rjefferis said:
Right i am pissed so i might be being a ****, but, it would help if you told us
a) what version of exchange you are running. Exchange 2003
b) whether you are using ssl to sync with the server. No SSL.
c) whether you are talking about syncing when connected to the pc, over gprs or such, or both. The PC sync works fine, but over the air it does not.
Rob
Click to expand...
Click to collapse
See answers.
kewlair said:
Yeah, I have noticed some issues as well. I'm using dutty's official 6.1 release.
The first issue I had was the initial setup. I set up my account properly, but ActiveSync would report that it cannot sync at this time. I knew that I had to uncheck the Use Proxy for this Connection option to solve this issue, but I couldn't find where to get to that setting for the MEdia Net connection that was being used. I finally found it in Settings -> Connections -> Advanced Tab, then tap the Select Networks button and where it says "Programs that automatically connect..." select MEdia Net instead of My ISP and then you can tap the Edit... button and remove the proxy server selection.
The second issue I have found is that after a while (not sure on specific time) ActiveSync just seems to stop working, almost as if it is hung up. When I go to the ActiveSync window and tap Sync, it does absolutely nothing. Basically the only way i've found to get it to start working again is doing a soft reset.
Hopefully this will help you or other people out, because it took me FOREVER to figure this out. I am curious if anybody else is having problems with ActiveSync stopping responding with 6.1 also.
Click to expand...
Click to collapse
Lots of good info there. Thanks and I will let you know if this works the next time I flash.
kewlair said:
I'm sorry, I might not have been clear. ActiveSync on the device hangs up, not on my computer. I haven't had any issues with ActiveSync on my computer so I think this is a different issue.
Click to expand...
Click to collapse
juju-35's is a different issue. I agree. I am talking about over the air sync/push. I will try to edit the thread title to be more clear.
Camp said:
juju-35's is a different issue. I agree. I am talking about over the air sync/push. I will try to edit the thread title to be more clear.
Click to expand...
Click to collapse
Sorry for the confusion, I thought you were talking USB since you mentionned the PC to USB thing. Still annoying though . I will repost in the DCS thread!
Direct push works without issues over AT&T's network on 3.0 Sleuth. My job depends on it working too. I've used it over MEdiaNet and My ISP connections although you need to be able to use my ISP to get it to work correctly (without 7minute delays). You can tell if its using the correct connection by waiting for direct push to connect after a reset then tapping on the big 3G icon. It should say its connected using My ISP (this assumes you let the connection wizard discover your provider and set you up of course).
The only difference between your settings and mine is that my email system uses SSL.
Certs aren't an issue if your exchange implementation doesn't need SSL.
I would really like to see the exact activesync error code you are getting btw.
Sleuth255 said:
Direct push works without issues over AT&T's network on 3.0 Sleuth. My job depends on it working too. I've used it over MEdiaNet and My ISP connections although you need to be able to use my ISP to get it to work correctly (without 7minute delays). You can tell if its using the correct connection by waiting for direct push to connect after a reset then tapping on the big 3G icon. It should say its connected using My ISP (this assumes you let the connection wizard discover your provider and set you up of course).
The only difference between your settings and mine is that my email system uses SSL.
Certs aren't an issue if your exchange implementation doesn't need SSL.
I would really like to see the exact activesync error code you are getting btw.
Click to expand...
Click to collapse
It also happened to me on your newest 6.1 ROM Sleuth, thanks for chiming in here. I can only work on this issue during the weekend because come Monday I have to reflash to a working 6.0 ROM. I just reflashed with Dutty's newest 6.1 ROM and here are my updates (updated in first post also):
The ActiveSync error code that I originally got with all of the 6.1 ROMs is:
Result: Synchronization could not be completed. Try again later.
Support Code: 0x80830003
After trying kewlair's suggestion:
"The first issue I had was the initial setup. I set up my account properly, but ActiveSync would report that it cannot sync at this time. I knew that I had to uncheck the Use Proxy for this Connection option to solve this issue, but I couldn't find where to get to that setting for the MEdia Net connection that was being used. I finally found it in Settings -> Connections -> Advanced Tab, then tap the Select Networks button and where it says "Programs that automatically connect..." select MEdia Net instead of My ISP and then you can tap the Edit... button and remove the proxy server selection."
I get this ActiveSync error code. I also tried changing "Programs that automatically connect..." to My ISP with the same result:
ActiveSync tries to connect using either MEdia Net or My ISP and then says:
"Cannot Connect
Dialed: Cannot connect for an unknown reason. To check your connection settings and change them if needed, tap Settings. If the problem continues, reset your mobile device according to your manufacturer's documentation and try again."
ActiveSync Reports: "Waiting for network"
Thanks for all the help so far everyone.
Anyone else have any other ideas that I can try?
Have you tried not letting the network communication run and enter the att network connections manually. Just say No to configure your network config. I have had issues with the network communications auto setup.
1) Set up My Isp to use either wap.cingular or isp.cingular (depending on you data plan) and not setup the proxy.
2) Set up the work connection as medianet to use wap.cingular with the proxy setting
3) Set up MMS connection using the correct setting and using work connection (medianet) with proxy.
It really sounds like your issue is related to the network settings. If you look up your active sync error code on google all seem to point to the ATT proxy issues.
Good Luck
All
I use push Mail and have tries Sleuths and duttys 6.1 ROM without issues
SSL based Authentication
Cheers
Mario said:
All
I use push Mail and have tries Sleuths and duttys 6.1 ROM without issues
SSL based Authentication
Cheers
Click to expand...
Click to collapse
Same for me DCS 1.5 and now 1.7 with SSL no problem at all
Everyone does not need to post that yes it does work. Mine works as well as 99% of other people. This thread is just for the OP and any others whose does not work.
Yes, It does work for 99% to 99.9% of people!
eagle 1 said:
Everyone does not need to post that yes it does work. Mine works as well as 99% of other people. This thread is just for the OP and any others whose does not work.
Yes, It does work for 99% to 99.9% of people!
Click to expand...
Click to collapse
Thx but in that case error code would help. Because not working could come from many factor.
More strange is not working config when "upgrading" from WM6 to WM6.1 with STRICTsame config...
So if people could put more details it will help
The error code indicates that your exchange server is set to use client certs btw. Here's the exact recommendation to fix:
1. On the Exchange server, launch Internet Services Manager. Right click on the Microsoft-Server-ActiveSync virtual directory and choose Properties. Select the Directory Security tab. Click the Edit button in the Secure Communications section and select the option to “Ignore client certificates.”
Click to expand...
Click to collapse
This is a server-side fix though. If you're not the IT staff that did this, then you need to get them to give you the client cert again.
your upgrade to WM6.1 caused your client side cert to disappear. The cert store on WM6.1 contains different certs in the root store as well which could cause WM6.0 to have the cert your exchange server requires but not this beta version of WM6.1.
Exchange installations which require client side certs are very rare btw which is why everybody is saying "works great here". Generally, server certs are used instead (require SSL must be checked in this case)
eagle 1 said:
Have you tried not letting the network communication run and enter the att network connections manually. Just say No to configure your network config. I have had issues with the network communications auto setup.
1) Set up My Isp to use either wap.cingular or isp.cingular (depending on you data plan) and not setup the proxy.
2) Set up the work connection as medianet to use wap.cingular with the proxy setting
3) Set up MMS connection using the correct setting and using work connection (medianet) with proxy.
It really sounds like your issue is related to the network settings. If you look up your active sync error code on google all seem to point to the ATT proxy issues.
Good Luck
Click to expand...
Click to collapse
Solved. Thanks for everybody's help on this issue. eagle 1's answer above helped me find out what was wrong.
It was a really simple solution, but I have never had to mess with any of these settings on any of my previous WM devices. The solution was: The "Connection Setup" wizard did not set up my connection settings correctly. I had to set BOTH "Programs that automatically connect..." drop down options in the advanced connection settings to MEdia Net.
Thanks again to everyone that helped out.
surprising that you got a 0x80830003 error instead of the more common 0x8500200B (failed to contact server) message
I cannot connect my AT&T Fuze to my work wireless network. This network requires the following settings:
Network Authentication: Open
Data Encryption: WEP (key is automatically provided)
Authentication: 802.1x Protected EAP (PEAP)
Inner Authentication: Secured password (EAP-MSCHAP v2)
Problem #1 - When I add the wireless network to the Wi-Fi settings, I select EAP type as "PEAP." I try to press the <Properties> button to set the inner authentication to MSCHAPv2, but receive an error message "Cannot log on to the network. This network requires a personal certificate to positively identify you." However this network does not require personal certificates.
Problem #2 - So I ignore that and press <Finish>. I am prompted for my credentials (username/password/domain). I enter them and press <OK>. No good. I am then repeatedly prompted for my credentials. [UPDATE: I just tried it for the 53rd time and just this once I was able to magically connect.]
I have read through many posts of similar complaints. I disabled server certification validatin by adding the ValidateServerCert value to the HKLM\Comm\EAP\Extension\25 key even though I have successfully installed the appropriate root certificate on the device. I also added the ValidateServerCert value to the \26 key just in case. I also set the wireless power mode to Best Performance.
What makes this particularly annoying is that I configured a coworkers iPhone to connect to the network. It was a giant pain because I had to install some sort of enterprise configuration software on a server and email her a mobile configuration profile from this application. Well the joke is on me because my WM6.1 phone cannot even connect.
Advice on what to do next? Thanks for your assistance.
I have the exact same problem... anybody found some sort of solution?
In case you still have the problem:
http://www.securew2.org/
Their program helped me overcome my issues with peap. Hope it works for you too
(taken from http://forum.xda-developers.com/showthread.php?t=284534&page=2 )
Thanks! Just how i tried - and too workng!
In case you still have the problem:
http://www.securew2.org/
Their program helped me overcome my issues with peap. Hope it works for you too
Click to expand...
Click to collapse
I am the OP. I was looking at SecureW2 as a last resort, as I am generally opposed to installing 3rd party applications to perform what should be core OS functions. Too many potential issues down the road. Fortunately I overcame my problem #2 stated above. On a separate post, somebody captured network traffic and determined that credential request/response was getting out of sync b/c the access point was not allowing enough time to respond. So after entering credentials and checking the "Save" box, I just banged away on the <OK> button as fast as possible. Eventually I connected. At this point the credentials are cached so I immediately connect from then on. I have tried this on two different HTC Fuze devices to my company's 802.1x PEAP MSCHAPv2 wireless network and it works great.
I also verified that since I installed the proper root certificate on my Fuze, I do not need to disable certificate validation by changing the ValidateServerCert registry value.
So the Windows Mobile 6.1 networking has two problems that will hopefully be fixed in a future update to make this easier for everyone.
So all you do is hit the OK button as fast as possible?
just making short login ans password
So all you do is hit the OK button as fast as possible?
Click to expand...
Click to collapse
Yes if you are experiencing problem #2 in the original post, repeated login prompts even though you know the credentials are correct.
just making short login ans password
Click to expand...
Click to collapse
The length of the username and password do not matter. And most credentials used with corporate networks are subject to complexity rules so cannot be arbitrarily short.
I found another solution, well the It guys from my Uni did.
Apparently you just have to increase the Wifi power setting to max. Otherweise the phone cannot process the peap crypto processes as it is limited by power saving mode.
http://social.microsoft.com/Forums/en-US/windowsmobile/thread/101f89b3-87fc-4cef-ac92-ece1aca9c12f/
i have the same problem. i dont understand how you overcame it
as0r: Changing the wifi power setting did not resolve problem #2 described in my original post, repeated login prompts.
jvar11889: How far did you make it, are you experiencing at problem #2 described in my original post, repeated login prompts? Is your required wifi configuration the same (802.1x PEAP MSCHAPv2)? I have succeeded on two different Fuzes, multiple times.
as0r said:
I have the exact same problem... anybody found some sort of solution?
In case you still have the problem:
http://www.securew2.org/
Their program helped me overcome my issues with peap. Hope it works for you too
(taken from http://forum.xda-developers.com/showthread.php?t=284534&page=2 )
Click to expand...
Click to collapse
I used this solution and worked for me!
Tried all the other tips mentioned, like for example the "power trick", without any luck!
However i have just flashed my TP from stock norwegian ROM to ROMeOS, dont know if this had any influence, but sercurew2 did the trick!
Its not really a 3rd party software, more like and integration into windows mobile!
Follow the instalations and setup guide from the site!
And Thanks for posting this, i have tried to get it working for more than 2 weeks now
Its not really a 3rd party software, more like and integration into windows mobile!
Click to expand...
Click to collapse
I disagree because the release notes clearly list the DLL's installed on your device. There is nothing inherently wrong with 3rd party software; I just like to reduce complexity by only installing additional software when I can't get what I want using the buillt-in features. If this was the only way I could connect to my 802.1x network, I would certainly install it.
I'm glad you are up and running. I have a hard time believing Microsoft is not aware of these problems. If they are serious about WM competing with iPhone and Android, Microsoft needs to jump on top of problems like this.
rlsmith999 said:
I disagree because the release notes clearly list the DLL's installed on your device. There is nothing inherently wrong with 3rd party software; I just like to reduce complexity by only installing additional software when I can't get what I want using the buillt-in features. If this was the only way I could connect to my 802.1x network, I would certainly install it.
I'm glad you are up and running. I have a hard time believing Microsoft is not aware of these problems. If they are serious about WM competing with iPhone and Android, Microsoft needs to jump on top of problems like this.
Click to expand...
Click to collapse
I agree with you! MS should do something about this! However, i talked to the EU HTC Support team, and they said a new ROM / Fimrware is due to be released end of February! Maybe there will be some kind of fix to this problem? Have heard that the HTC TP have some kind of problems installing certificates or something like that (havent read this myself, just heared it from someone working in a Cell Phone shop).
Hope you'll post here if you find a better solution!
Good luck!
zemlol said:
I used this solution and worked for me!
Tried all the other tips mentioned, like for example the "power trick", without any luck!
However i have just flashed my TP from stock norwegian ROM to ROMeOS, dont know if this had any influence, but sercurew2 did the trick!
Its not really a 3rd party software, more like and integration into windows mobile!
Follow the instalations and setup guide from the site!
And Thanks for posting this, i have tried to get it working for more than 2 weeks now
Click to expand...
Click to collapse
I am glad it helped you, but it stopped working for me a couple of days ago. Would you mind posting your config?
Cheers
Try and go into the securew2 settings tab !
And check for "prompt for username and password" ?
It switches on and off sometimes!
What config info you want?
hi boys...
i have the same problem... I cant connect to wifi of my university because his used a protocol that not compatible of andoid...
this is the guide of my University for linux sistem...
Sicurezza wireless: WPA e WPA2 Enterprise
Autenticazione: EAP Protetto (PEAP)
Identita anonima : anonymous
Certificato della CA: (Nessuno)
Versione PEAP: Versione 0
Autenticazione interna: MSCHAPv2
utente : il proprio indirizzo di mail studenti (esempio [email protected])
Password: ( la password del servizio wifi inserita in fase di attivazione)
now the problem is that my liquid ask me only password, and only for this not possible to connect.
anyway help me...
Same here
i have the same issue as well. i have tried all kinds of solutions. adding the reg key, securw2, advanced config tool and many more but nothing has worked. i even flashed a new 6.5 rom and that didnt work either. my fellow techs have i-phones and they find this pretty funny so i would love to get it to work. I like htc and dont really want to go to iphone so hopefully someone out there has the solution that works.
Hey!
I have 11 different mobiles, "powered" by Windows Mobile Professional 6.1 and Windows Mobile Professional 6.5. There are around 8 suppliers for these phones we're testing to see which fits our needs the best.
We use a special service from our ISP, which requires us to set the authentication method to PAP instead of the default which is CHAP and/or CHAP/PAP.
Under Windows Mobile 6.0 we could set this option under System under GPRS settings. I've tried copying over the application to enable, without success. I've also tried to enable the SetGRPSAuthentication under HKLM\Microsoft\Software\RIL to dword:1, without success.
A 3rd party supplier of us hinted that Motorola has patched this and the patch should be available to all (via WSUS?) in late April, which is a bit too far away for our schedule.
Any other's out there who struggle? Or maybe you've found a solution?
Best Regards,
Rune "TheFlyingCorpse" Darrud
Hi there,
I encountered the same issue when i flashed my phone from winmo 6.5 back to 6.1. I couldn't set the authentication within the Connection Settings, which kept my data connection from setting up properly. Here's what I did:
- Open a registry-explorer on your phone ( i'm using SKTools', but any will do i guess... )
- If you're able to search for strings/key's/values, search for the name that you've given your connection. If you can't search for strings, HKLM\\Comm\ConnMgr\Providers should provide settings for your data connections.
- Within the folder, you should also find a key "NDISGPRSAuthType". Your value probably is "1". I've changed it to "2", which allowed me to connect to my providers GPRS. Later on, I installed another settings manager ( I'm using a Samsung B7610, and installed the "Samsung Settings" which allowed me to alter these settings as well ). I've discovered that the Samsung Settings altered the value to "3" when I selected "PAP" authentication. I think that altering this string to "2" or "3" could solve your problem. If not, then I'm affraid I cannot help you with this issue.
Good luck!
Gydeon
Hello there,
I've stumbled upon a problem with my new Sensation & the Facebook for Android official app.
Basically, certain parts of the app - namely the Profile page (would be your Wall in a normal browser) will not load/refresh over a WiFi connection.
Facts I have established are:
- Entire app works when WiFi is switched off & handset just uses 3G/mobile bb.
- With WiFi on, Newsfeed works, contacts work, everything works but your Profile feed. You can look at your info & your photos no problem, and changes are reflected. You cannot post status updates.
- Several different WiFi hotspots used, same result
- FB working fine on laptop clients using same WiFi hotspots
- FB for Android working fine on my gfs Desire using same WiFi hotspots
- m.facebook.com & full site work flawlessly
- FB for Sense (Friendstream, Sync & Sharing) works fine
- Exact same problem noted with Friendcaster - login screen wont show with WiFi enabled, once on 3G - login page shows up fine.
- Multiple clearing of accounts/cache - uninstalling update, testing, reinstalling update & combinations thereof - all fail.
- Checked FB Privacy & Account settings - made sure HTTPS is off etc.
So, essentially various parts of FB are not contactable using some official & unofficial apps over WiFi, but operate fine over 3G.
This is a Sensation from Singapore - just had an OTA update - 1.35.707.1 - which didnt make any difference (problem existed out-of-the-box..and the box was opened last Tuesday).
I've seen other threads vaguely pointing towards this issue on other handsets with various rom revisions, but nothing concrete with the testing I have done above.
Anyone got any bright ideas - or is it just a bug in a common API used by these apps or something...?
Has anyone else even noticed this issue?? Or am I just going mental...?
Cheers
After much mucking about, I traced this issue to a NAT translation problem with my wireess router. Effectively transacting the mtu down to 1100 for some reason. It was a glitch.
Saving config + Factory reset + loading saved config was the solution.
Sent from my HTC Sensation Z710e using XDA App
I had same problem. After change setting of my router, problem solved. Try change dns to 8.8.8.8 and 8.8.4.4.
I got the same problem. Done everything but its useless 'n I 'm going to mad just like the initiator of this thread.
MTU
wasi99 - check the MTU on your internet interface on your wan router; I have seen this problem several times now and always has been due to incorrect MTU for the internet connection in question.
For me, in the original post, I was on an ADSL2 connection, and the modem had its MTU set at 1500 (which is correct), however, my router internet interface was set to something weird like 1400. Once I changed the router internet interface to be 1500, all was well in android app land
Some things are more sensitive to incorrect MTU than others. You might be able to load www pages fine, but not be able to ftp to certain sites - for example.
Hope this helps, and saves some hair!
solory said:
I had same problem. After change setting of my router, problem solved. Try change dns to 8.8.8.8 and 8.8.4.4.
Click to expand...
Click to collapse
Thank a lot mate! It helped