DLNA server not found from wifi devices on Access Point

[shadowb]

My primary RAX50 is on one end of the house and the second RAX50 is in AP mode at the other end of the house connected via Ethernet cable.  I run Servio DLNA on a computer connected to the Prmary router.  All TVs and Firesticks wifi connected to the Primary router see the DLNA.  None of the TVs and Firesticks wifi connected to the RAX50 in AP mode see it.  What do I need to change?  Ive read lots of similar posts but havent found a solution for my problem.  

[metroboulotdodo · Accepted solution]

Hi, this is my second answer:

I search around and saw at the release of the predecessor Firmware 1-0-12-120 the issue "

• Fixes the issue where multicast packet failed to forward between Wi-Fi and Ethernet clients."

https://kb.netgear.com/000065385/RAX50-RAX50S-Firmware-Version-1-0-12-120

I tested now by downgrading to this version: the problems encountered in my former post (and maybe connected to your problem) have gone.

My guess: maybe the solved issue in 1-0-12-120 has been reopened in V1.0.16.132

[FURRYe38]

How is AP mode configured on the 2nd RAX in AP mode? 

FW versions the same on both? 

[shadowb]

What should I be looking for configuration wise?  All I did was set mode to AP.  Didn't change anything else except SSID and password.  

Ethernet cable from Primary router is plugged into Ethernet port on AP router (I tried plugging into Port 1 with no difference).  

I also tried making the SSID the same as the Primary - no help.  

Which configuration settings are involved?  

[shadowb]

Firmware levels the same:  

AP router          V1.0.16.132_2.0.92

Primary Router V1.0.16.132_2.0.92 

[FURRYe38]

Try setting a static IP address configuration on the 2nd AP? 

WAN port should be connected from the 2nd AP to the LAN port on the 1st host router. 

Other than this, shouldn't be any other configurations needed. Possible something isn't working to let the DLNA data pass thru the 2nd AP to connected devices. Might try a different router or AP system to check this. 

[shadowb]

Sorry, I should have mentioned I already have set fixed IP on the AP and I verified the Ethernet cable is plugged into the WAN port on the AP.  Been trying lots of things from various forums.

Are there any settings on the Fire Stick networking setup I need to change?  I have other devices connected via wifi to the same AP and they have the same problem.  Devices connected via Ethernet cable (e.g., TV) do NOT have the problem.  

[metroboulotdodo]

(Sorry, no solution)

I encounter a problem maybe related:

1 Router and 2 APs (one RAX50)

When connected to RAX50, no DLNA Renderer or DLNA Server are found though there are some on 2 QNAPs/ 1BananaPI. Only Airplay Service is detected.

When connected to other AP, everything is found.

(Connecting back to RAX50 with DLNA Client opened, the former detected DLNA Server can be used, but after a refresh it wouldn't show up again).

(Network configuration is quite simple: no VLAN or strange settings made)

My guess: RAX50 could have some problem with dealing with DLNA Broadcasts/UDP Packets. Very old power line adapters had those problems, I remember.

Solution: none 😞

[metroboulotdodo · Accepted solution]

Hi, this is my second answer:

I search around and saw at the release of the predecessor Firmware 1-0-12-120 the issue "

• Fixes the issue where multicast packet failed to forward between Wi-Fi and Ethernet clients."

https://kb.netgear.com/000065385/RAX50-RAX50S-Firmware-Version-1-0-12-120

I tested now by downgrading to this version: the problems encountered in my former post (and maybe connected to your problem) have gone.

My guess: maybe the solved issue in 1-0-12-120 has been reopened in V1.0.16.132

[shadowb]

Thanks for your information.  I did a workaround by adding an Ethernet adapter to my Fire Stick and using a wired connection.  All DLNA works now.  Netgear obviously has a problem with DLNA on the RAX50 series.  

[FURRYe38]

Can someone open a support ticket regarding this with NG and let them know what you see on this. 

@DarrenM