RE: [MLO] WIFI Sync Failure
m...@grantsmiths.org
Hi, Michael.
You are posting your message on a forum of MLO users. If you heard no response, it probably means that none of us recognizes your issue. Perhaps you should consider contacting the support people, at sup...@mylifeoorganized.net
-Dwight
From: mylifeo...@googlegroups.com [mailto:mylifeo...@googlegroups.com] On Behalf Of Michael F. Schneider
Sent: Wednesday, November 21, 2012 6:35 PM
To: mylifeo...@googlegroups.com
Subject: [MLO] WIFI Sync Failure
Hello,
I posted this problem on MLO-Android some time ago but got no answer, neither affirmative nor negative, just _no_ answer. As the problem persisted I chose to just ignore the (paid!) Android app until I would get a solution. Today I receive the Android update and found out about the new 3.6.2 release for Windows. So I just tried again to sync my phone with the desktop, but the problem is still there, nothing changed. So here are the hardcore details:
* Desktop: MLO 3.6.2 on Windows XP (SP3), AV and Firewall is disabled
* Phone: MLO for Android 1.6.6 (Pro), HTC Desire HD running JellyTime (Jelly Bean 4.1.2), but problem occured exactly the same on original ROM 2.3.5.
* PC connected to router by wire (fixed IP), phone connected by WIFI (IP by DHCP), both using IP addresses from the same private C-Net.
* MLO desktop is listening on port 2103
* neither pc nor phone have ever been successfully synched, MLO on phone is completely virgin.
* pairing works, so the connection between both MLOs is definitely working.
Now, when I start the sync, I can see TWO(!) connections to port 2103, both in the state ESTABLISHED.
Meanwhile MLO on the phone shows the message "Synchronizing WiFi ...".
After 4 to 5 secs, the sync is aborted with an error message "Timeout while waiting response. Probably due to network connection problem."
All the time and still after the error message, the TCP/IP connection remains in state ESTABLISHED.
A few minutes later (sorry, haven't timed), the TCP/IP connections turn to state CLOSE_WAIT and finally to FIN_WAIT1/2; this transitions may be caused by TCP/IP timeouts.
If I retry the sync, I get two more connections (again and again), while the previous connections are still alive.
At the same time as the sync connection is established, the cpu usage of MLO desktop skyrockets to 100% and stays there until after the last connection has timed out, only then will it fall back to idle.
I can not see where I could be doing anything wrong, neither that there is some hardware or software problem of the environment involved. Can anybody help?
Best regards,
Michael F. Schneider
--
You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group.
To view this discussion on the web visit https://groups.google.com/d/msg/mylifeorganized/-/v-hciyxvpooJ.
To post to this group, send email to mylifeo...@googlegroups.com.
To unsubscribe from this group, send email to mylifeorganiz...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/mylifeorganized?hl=en.
m...@grantsmiths.org
Andrey Tkachuk (MLO)
I have not heard such problem before. My guess is that something is blocking the connection on your desktop. Do you have a chance to test it on other computer within your network (or other network)?
The other idea is to try to change the port for WiFi sync on desktop to other predefined port: 21030 or 21031
To change it you need to edit the registry:
Run regedit.exe
Open:
HKEY_CURRENT_USER\Software\MyLifeOrganized.net\MyLife\WiFiSync
Edit:
Port (DWORD) - change it to 21030
Restart MLO on desktop and try again.
If it does not help try to run mlo.exe on desktop from other folder so that Windows asks for the Exception in Firewall again and allow connections to MLO. Try to pair and sync.
Let me know the results. I do not have other ideas at the moment since we cannot reproduce the issue locally.
Andrey.