This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
Port forwarding 3389 through Nighthawk R7000P to Deco wifi
I have a machine using Plex that works much better on our mesh wifi. The issue I have is that I have that machine available viaDeco Port 3389 for RDP offsite. If I put the machine on the wifi, if gets an IP that my Nighthawk R7000P router can't use for port forwarding.
I've tried setting up port forwarding through the wifi's app but no dice.
Is this possible, forwarding RDP traffic through the Nighthawk to a wifi network with a different IP range, or should I tell my wifi to use the same as what the router dishes out somehow?
Re: Port forwarding 3389 through Nighthawk R7000P to Deco wifi
> [...] our mesh wifi. [...]
Not a very detailed description. Maker? Model number?
> [...] my Nighthawk R7000P [...]
Which is connected to what, how? (Hint: If a device has different types of ports, then "connected to device" is not enough detail.)
Where does your ISP connection (modem, ONT, ...) come into this mess?
> [...] If I put the machine on the wifi, if gets an IP that my > Nighthawk R7000P router can't use for port forwarding.
A few actual IP addresses might have made that more helpful.
> I've tried setting up port forwarding through the wifi's app but no > dice.
"I've tried" or "no dice" is not a useful problem description. It does not say what you did. It does not say what happened when you did it. As usual, showing actual actions (commands) with their actual results (error messages, LED indicators, ...) can be more helpful than vague descriptions or interpretations.
Generally, to avoid such IP address problems (as I assume you're seeing), you want one router, not two. I'd guess that whichever router is currently closer to your ISP is the one which you should leave as your router. The other router should be configured as a wireless access point. Presumably, the manual for that router will explain how to do that.
For a Netgear router, visit http://netgear.com/support , put in your (actual) model number, and look for Documentation. Get the User Manual (at least). Read. Look for "access point".
That way, all your client devices should get IP addresses on the same subnet, and you should be able to configure port forwarding (on your remaining router) without such problems.
Also, I would advise against using a well-known port like 3389 externally, unless you _want_ to be attacked from every malware-infested Windows system on the planet. For suggestions for a more discreet configuration, see, for example:
Re: Port forwarding 3389 through Nighthawk R7000P to Deco wifi
> [...] our mesh wifi. [...]
Not a very detailed description. Maker? Model number?
> [...] my Nighthawk R7000P [...]
Which is connected to what, how? (Hint: If a device has different types of ports, then "connected to device" is not enough detail.)
Where does your ISP connection (modem, ONT, ...) come into this mess?
> [...] If I put the machine on the wifi, if gets an IP that my > Nighthawk R7000P router can't use for port forwarding.
A few actual IP addresses might have made that more helpful.
> I've tried setting up port forwarding through the wifi's app but no > dice.
"I've tried" or "no dice" is not a useful problem description. It does not say what you did. It does not say what happened when you did it. As usual, showing actual actions (commands) with their actual results (error messages, LED indicators, ...) can be more helpful than vague descriptions or interpretations.
Generally, to avoid such IP address problems (as I assume you're seeing), you want one router, not two. I'd guess that whichever router is currently closer to your ISP is the one which you should leave as your router. The other router should be configured as a wireless access point. Presumably, the manual for that router will explain how to do that.
For a Netgear router, visit http://netgear.com/support , put in your (actual) model number, and look for Documentation. Get the User Manual (at least). Read. Look for "access point".
That way, all your client devices should get IP addresses on the same subnet, and you should be able to configure port forwarding (on your remaining router) without such problems.
Also, I would advise against using a well-known port like 3389 externally, unless you _want_ to be attacked from every malware-infested Windows system on the planet. For suggestions for a more discreet configuration, see, for example:
Re: Port forwarding 3389 through Nighthawk R7000P to Deco wifi
I mentioned i have the Deco wiri mesh, and what I did was make them access points and not routers themselves dishing out a different IP scheme. The Android app defaults to NOT APs for some reason. Their equipment has a limited number of ports and it made more sense for everyone to have everyone be on the same subnet. Once I did that worked great, as well as changing my port.
Now my issue is with the wifi card itself, so I'll start another topic. Keeps dropping connection every 10s. Thanks for your input.
