LS420 not showing up on EERO gateway

[danesoper]

My ISP switched me to EERO.  Everything wired and wireless is displayed in the app except my LS420 NAS. I have a switch between the erro and the LS420 NAS.   
When I try to use NAS Navigator 2, it has an error saying there is a Connection Error: Drive information not returned. Error information not returned.  NAS Navigator 2 shows the IP as 192.168.4.x but I cannot see the wired connection in the eero app.  All other wired connects are show and also have the 192.168.4.x range.
I attempted selecting the properties of the LS420 in NAS Navigator 2, then requesting a renewed IP address, but it gets an error saying No reply from drive.
I have rebooted the LS420 several times with no changes.

[1000001101000]

Two things:

It sounds like you might have had a static IP address defined and now that address is incompatible with the new network setup. If so you can correct this by resetting the network settings to their default (DHCP). The manual has a procedure for doing this (I believe by holding a button during boot).


NasNavigator and related tools may have trouble connecting on your network eero (and other "mesh" routers) often don't deliver UDP broadcast packets across the whole network. This is somewhat discussed here:
https://www.reddit.com/r/eero/comments/du4woc/a_weird_one_losing_osc_udp_broadcast_messages/

[danesoper]

Initializing with the Function Button was the fix.  I am able to see the LS420 on eero, and I can not launch settings in NAS Navigator.

I am new to posting so I don't know how to mark your post as the solution, or how to migrate it to the solved directory.

Thank you!

[1000001101000]

I think you can solve the NasNavigator portion by some sort of setting change on the EERO to allow UDP broadcast packets to be routed to/from this host. If you do figure out how to do that please post the solution.

Otherwise I'd expect it to work if you connect the device and your PC to the same switch when using NasNavigator. I don't thing EERO blocks the packets entirely, I think it just doesn't forward them from one "network" to another for performance reasons. I expect this will come up more if mesh networks become more popular.