WiFi sync not working on Pixel XL on 5G AC

[ninja6o4]

Picked up a new Pixel XL, setting everything back up.. For some reason MMA cannot see my MMW 4.14 server. My old Nexus 6 can still see the server no problem.
Tried these steps: http://www.mediamonkey.com/support/inde ... lna-server
Installed Fing, and my phone can see the open port on my MMW server, but it just doesn't appear in MMA. Computer's firewall is OFF.

Any suggestions? I posted a support request a while ago but got no response. Log ID RWCAJV1AS2

[ninja6o4]

Hmm.. OK I was able to get it to see the server once after syncing via USB. It actually saw my Plex server as well.
I changed the port back to it's original random port (58741) and now both MMW and Plex are gone again. Reverted to test port 4000, and it's still gone.
I was running MMA 1.3 beta, so I returned to 1.2. A popup appeared saying my MMW version is outdated and to upgrade to 4.1.10.1178+ (lol!), but still no server appears.

So, after screwing around for a while, with my Nexus 6 and my Pixel XL, it's working now, but I have no idea why. All tests below were done on MMA 1.2 and MMW 4.1.14.
I discovered that my N6 was on 2.4 GHz, while my XL was on 5GHz.
Here were my tests (in between each change, I force stopped MMA to start it from scratch)
Switching N6 to 5GHz caused it to break.
Switching XL to 2.4GHz caused it to work.
So, both in 2.4GHz work fine. Neither in 5GHz worked. OK...

Here is what I did to "fix" it:
Went to select sync server while in 2.4GHz, server was visible.
Pulled down the notification bar, and switched to 5GHz.
Selected the server while connected at 5GHz.
It connected and then synced!

This made no sense to me, so I stopped MMA again and loaded while at 5GHz - again, server is missing.
Repeated the 2.4GHz "scan", switch to 5GHz to "connect" trick. Worked again!

Stopped MMA again while on 5GHz - server appeared (!?!!?)
Connected and synced, without any help from 2.4GHz.
Repeated Force Stop -> Select server at 5GHz, 3 more times, and now it appears consistent.

So yeah. No idea what I did, but it seems to be working now.

[Lowlander]

Seems like a router issue. Good it's fixed now.

[ninja6o4]

Seems like a router issue. Good it's fixed now.

I don't know about that. When I ran Fing, the device could see the open port. MMA was simply not seeing it.
My router is an Asus RT-AC87U.

I've tried it again just now, and it cannot see the server on 5GHz.
There is a firmware update for it, which I've now applied (3.0.0.4.380_3459)
Repeated the test and it is the same result - only visible on 2.4GHz, but switching to 5GHz once it's been detected seems to work fine.

I don't know if there's anyone else out there running 5G or Asus routers that could do this test as well? I wouldn't consider my solution a "fix", just a workaround.

[Lowlander]

I do, I had no issues when I ran them separately, now combined still no issue. It would seem the router has an issue routing between 5Ghz and LAN (if MM is on LAN not wifi). Are you sure it's not a separated guest network? Have you tried turning off the router and restarting it?

[Peke]

Try to install WiFi Analyzer https://play.google.com/store/apps/deta ... yzer&hl=en and/or FING tools https://play.google.com/store/apps/deta ... fing&hl=en as like lowlander I also think that there is some hole in Router settings which make things problematic.

[rivorson]

For what it's worth I have at RT-AC68U running firmware 3.0.0.4.380_4164 and a Nexus 6. For me the 5GHz WiFi works exactly the same as the 2.4GHz.

[ninja6o4]

Thank you for all the suggestions.

I do, I had no issues when I ran them separately, now combined still no issue. It would seem the router has an issue routing between 5Ghz and LAN (if MM is on LAN not wifi). Are you sure it's not a separated guest network? Have you tried turning off the router and restarting it?

Yes, MMW is wired into LAN. There are no guest networks or anything, LAN and WiFi are bridged and using same DHCP server. The router was restarted after the firmwater update, but I did a hard reboot and the behaviour is unchanged.

Try to install WiFi Analyzer https://play.google.com/store/apps/deta ... yzer&hl=en and/or FING tools https://play.google.com/store/apps/deta ... fing&hl=en as like lowlander I also think that there is some hole in Router settings which make things problematic.

The signal is strong, and as you can see from the screenshot, the service port is open and visible while on 5GHz:

For what it's worth I have at RT-AC68U running firmware 3.0.0.4.380_4164 and a Nexus 6. For me the 5GHz WiFi works exactly the same as the 2.4GHz.

Thanks for the info.

Testing it again today...

Nexus 6 sees the server almost instantly on 5GHz. (Running OS 6.0.1)
Pixel XL (OS 7.1.1) does not see server on 5GHz. Switching to 2.4GHz still doesn't see it.
Uninstalled MMA again, rebooted phone, deleted MediaMonkey folder.
Installed MMA, accepted T&C, recognized Pro. Spinning circle on the top by the search icon.
Still does not see server. Log ID ZHJWL72WTF (heh WTF)
Tried clean MMW ini file and shared server, no luck.
Reverted ini and browsed to http://192.168.16.2:58741/DeviceDescription.xml - this worked, on both my PC and the Pixel. But, it still can't find it in MMA.


Enough for tonight...

[Peke]

No images are uploaded.

Do Fing See your PC on LAN on both 2.4 and 5ghz?

Also does http://www.advanced-ip-scanner.com/ see your WiFi Connected Devices?

[ninja6o4]

No images are uploaded.

Do Fing See your PC on LAN on both 2.4 and 5ghz?

Also does http://www.advanced-ip-scanner.com/ see your WiFi Connected Devices?

Sorry for the late reply. I haven't needed MM in a while. I updated the img links.

The PC can see the Pixel no problem, and vice versa. However, your suggestion gave me an idea, and I may have finally found an interesting culprit: the Pixel seems to have wildly inconsistent ping responses on WiFi through my AC87U. When I test with my Nexus 6, the pings are far more consistent.

Searching online, this appears to be a common issue with Android devices + AC87U wifi. I have been messing around with the router configuration with some suggested solutions and found one that helps - under LAN -> Switch Control, I enabled Jumbo Frames. It didn't seem to cure the ping consistency, but trying a few times and it's able to see both my UPNP servers (MM and Plex.)

An interesting note is when I try Cast Device from MMA, it doesn't see any available targets, when I do have one (Roku 3).

I realize this isn't much to go on. I'm not saying there is a bug in MMA, but what I can say is that the Plex for Android app does not exhibit any connectivity issues, despite the apparent ping problem. Maybe Plex has better error handling in the data stream, or.. ?

[rivorson]

Maybe Plex has better error handling in the data stream, or.. ?

I'm not certain of this but I think Plex attempts a direct connection for devices that it has seen before. MMA relies solely on DLNA broadcast. Consequently if there is an issue affecting the DLNA broadcast on the router then Plex can still connect to devices that it already knows about as long as the address hasn't changed but MMA won't be able to connect at all.

You could test for that by uninstalling and reinstalling Plex for Android next time MMA can't see the servers. Since a freshly installed Plex shouldn't have any device history it should be forced to rely on the DLNA broadcast.
A fresh install would mean needing to set up the app again though, which may be inconvenient. I haven't used Plex for Android so I don't know how much set up it needs.

[ninja6o4]

Checking again this morning, MMA has my MMW server known before I even get to UPNP (it's already populated when I get there.)
I think enabling Jumbo Frames on my AC87U was the trick that did it. For whatever reason, the Pixel seems to need this on whereas the Nexus 6 did not.
I will check it a couple more times and then mark my problem as solved. Hopefully this helps someone else down the road

[Lowlander]

Plex can direct connect (I guess relying on some form of broadcast), but also can connect via internet. Thus if Plex works it may not indicate anything about your local network.

Jumbo Frames are known to be able to cause problems between different hardware, although generally disabling them would resolve problems.