[BUG] 4.1.0.1636 Will not connect

[toyzrme]

MMA connected to MMW only ONCE with 1609, NEVER with 1639.

Windows 7/x64, all the latest patches. On a Lenovo W510 w/12GB RAM.
MMW: 4.1.0.1636 & 1609 - both installed as portable, in separate directories.
MMA: 1.0.4.0127
on Galaxy Note
Android ICS 4.0.4
Debug logs sent 10:48pm Eastern May 8, 2013

I was able to get 4.1.0.1609 to connect, ONCE, but never again. Never could get 1636 to connect even once.

1609 would not connect at all. I shut down Symantec Endpoint Protection - nothing. I added MMW .exe to Windows firewall to grant local access. Nothing. I tried adding the MMW COM exe, and *that* seemed to let it connect. ONCE. Thereafter it would never connect again. MMW should be configuring these, or at least ask me if I want the rules configured.

On 1639, I could NEVER get it to connect, even once, even after configuring the firewall.

I tried doing a USB connection, it found the phone (MTP), and I enable remote sync. Nope - still could not connect wirelessly.

There seems to be no way to forget/disconnect/disable a sync server in MMA.

There is no way to do an uninstall on MMW, even though your FAQ says to do a clean install (unless you just mean wipe the directory - if so, just say so!).

You're going to need a LOT better user tooling for your users to diagnose connection problems, or you are going to suffer some painful debugging support. Better doc on how to add/remove sync servers, what each feature does (like do I need to *add* a sync server? why would I ever need that function, ie 2 sync servers on the same MM instance?) Better status notification/logging would go a long way - let me know each step it is taking - like that it found the server *machine*, even before trying to get access to the MMW library. All-or-nothing "hail Mary" communication logging is begging for things to fail in the middle - at every possible place.

MMA also seems to hang when the connection fails - which is all the time. I have to kill it through the task list.

Rebooting Android does not help.

Thanks.

[Lowlander]

Do you see the MMW UPnP server in MMA? If not your wifi may be on a separate network or the firewall is blocking access. If you have any other UPnP clients do they see the MMW UPnP server?

[toyzrme]

Update: I tried the "open MMA, open MMW, hit "sync now" on MMA and while its syncing I close MMW and re-open it" that others have had to use to get it to work, and this worked with MMW-1609. This is REPEATABLE, if done *exactly* this way.

1636 STILL DOES NOT WORK, even using this method.

However, it took ~2 minutes to sync 1 song (26MB) - I have an N wireless network. PerfMon says it's sending ~260KB/second. This is slower than USB - this should be more like 20MB/second...

MMA does not like to cancel/stop - I usually have to kill it in the Android task manager.

And when connection fails, the "Sync Failed" message box won't dismiss - again, I have to kill it with Task Mon.

Note: every time I start MMW, I get a popup from my firewall that says it wants to broadcast to 239.255.255.250 using port 1900 (SSDD) - I allow this every time. It is only after I grant that permission that the phone/MMA sees the MMW server (still using the strange start/stop/start method above).

[toyzrme]

Both devices (MMW & MMA) have 192.168.2.x addresses (which is my home network).

I don't have any other UPnP devices to test with, but I brought up MM 4.0.7 on another PC, and it does not see the MMW 4.1.0.x server listed under "Media Servers" - is this what you mean? But then why does the above "start/stop/start" sequence work reliably? If the firewall was blocking things, it shouldn't matter that I start & stop the app - it should always be blocked, shouldn't it?

Thanks.

[Lowlander]

And when connection fails, the "Sync Failed" message box won't dismiss - again, I have to kill it with Task Mon.

This has already been reported and using the back button allows you to leave this state.

What internet provider/router do you have? Some have settings blocking UPnP.

[toyzrme]

I use DD-WRT v24-sp2 (06/12/10) mega

UPnP was DISABLED, so I ENABLED it, and rebooted the router. MMW 407 on my other machine now sees my MMW 4.1.x machine. FYI I could not find 'IGMP' in DD-WRT.

BUT: now 1609 *won't* connect EITHER, even with the start/stop/start routine - I can't get MMA to connect no matter what I do.