NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Nighthawk R9000, Alexa remote access settings
I've just installed a band-new Nighthawk R9000. In doing so I thought I'd install the PLEX server and instead of using my Seagate USB drive full of media on my Raspberry Pi I'd plug the Seagate into...
Your RasPi was operating on the first LAN behind the provider NAT router - thus simple port fowarding does the job, probably it did it automatically by UPnP.
What's the point of adding another router doing NAT again? Your choice ... Check this:
https://support.plex.tv/articles/200931138-troubleshooting-remote-access/
Add a DHCP reservation for the R9000 WAN/Internet MAC address (connected to the provider NAT router LAN), then add aport forwarding for port 32400/TCP on the provider router to the R9000 "WAN" IP.
Your RasPi was operating on the first LAN behind the provider NAT router - thus simple port fowarding does the job, probably it did it automatically by UPnP.
What's the point of adding another router doing NAT again? Your choice ... Check this:
https://support.plex.tv/articles/200931138-troubleshooting-remote-access/
Add a DHCP reservation for the R9000 WAN/Internet MAC address (connected to the provider NAT router LAN), then add aport forwarding for port 32400/TCP on the provider router to the R9000 "WAN" IP.
Hello schumaku, I think a solution as you describe is probably worth trying - I like the sound of fixing the ports - it just sounds the correct and elegant thing to do. Unfortunately I am not into tinkering with these things, but I know someone who is up to the job who is visiting in a couple of weeks and I shall show them what you have written and get them to sort it out for me (I will report back then). In any event for the moment I appear to have implemented that seems to be working, but I don't know why. I plugged in the Seagate drive into one of the USB ports on the R9000, then two nights ago I power cycled the R9000 with the drive attached. At the time it did not appear to have changed things and it still didn't work. However, knowing that sometimes these things get their underwear in a bit of knot I left it all cogitating and went to work. At lunchtime I tried my Android phone and lo and behold there it was and when I got home Alexa had no problems hooking up to the music on the drive, which was the original problem. Happy? Yes! Baffled? Certainly!
For the moment I shall leave it apparently working, but in case a 'dynamic change' of port in the future upsets it I am keen to apply your solution, so many thanks