can't sync after last update

Post a reply


In an effort to prevent automatic submissions, we require that you complete the following challenge.
Smilies
:D :) :( :o :-? 8) :lol: :x :P :oops: :cry: :evil: :roll: :wink:

BBCode is ON
[img] is ON
[flash] is OFF
[url] is ON
Smilies are ON

Topic review
   

Expand view Topic review: can't sync after last update

Re: can't sync after last update

by Peke » Mon Jan 02, 2017 6:38 am

Yes it is possible, as we optimized sync procedure in 624 and 1.3.0 Beta.

Re: can't sync after last update

by MaTzeTung » Sun Jan 01, 2017 4:41 pm

Hi,
sorry for the delay, my kids demanded more of my time during xmas season, not sure why ;)
However, it's solved!!!
Since the last update (when I started the thread I used MMA: 1.2.0.0623, now it's 1.2.0.0624) it's working again. Nothing else changed in the config so I assume that the new release changed something. All I noticed was that MMA said "since you connect the first time ..."
Does it make sense? Could the changes in the 2 builds have an impact?

Re: can't sync after last update

by Lowlander » Mon Dec 26, 2016 1:55 pm

Use UPnP in MMA itself (from Homescreen) and see if you can find and access the MMW server.

Re: can't sync after last update

by MaTzeTung » Mon Dec 26, 2016 1:52 pm

How do you want me to check? As said, I can "see" MediaMonkey Upnp from another laptop. What / how do you want me to check?
Thx
M.

Re: can't sync after last update

by Peke » Thu Dec 22, 2016 6:24 pm

Can you check is UPNP works?

can't sync after last update

by MaTzeTung » Thu Dec 22, 2016 5:55 am

Hi,
since the last MMA update I can't sync anymore. No connection established = Sync incomplete, Connection failed!
MMW: 4.1.14.1813
MMA: 1.2.0.0623
I can ping from windows to device (Android 6.01, ZTE Axon 7) & vice versa, from a different device I can see MediaMonkey Upnp server. If I call IPadress:61242 I see "Not implemented for Mediamonkey 4" in the browser.
Since my MMW is running in a Vmware (Windows7 Pro) to avoid any unwanted changes I guess it's the last MMA update that's causing the issue. Anyone else having the problem, too?
Next step: open a support ticket?

Top