NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Setting up RDP through EX7000
I have a NG Router and NG EX7000 extender - working fine. I'd like to set up RDP for devices connected to the extender. I've set up a static (reserved) IP for the one laptop for which I'll need acc...
> I have a NG Router [...]
C3700-100NA S
V2.02.22
Xfinity
> [...] and NG EX7000 extender [...]
used mywifiext.net wizard - new extender
V1.0.0.66_1.0.126 - I upgraded but everything stopped working, so I backed out the upgrade
> I've set up a static (reserved) IP for the one laptop for which I'll
> need access.
On router (Address Reservation): 192.168.0.253
This laptop is connected to the the SSID of the extender.
I can get to it via RDP with another machine on the LAN.
> I've set up port forwarding (port 3389) [...]
24.39...
I cannot RDP from outside the LAN
Port Forwarding Rule:
- Service Name: Remote Desktop
- External Port: TCP/UDP: 3389
- External IP Address: Any
- Interenal Port: TCP/UDP: 3389
- Internal IP Address: 192.168.0.253
> I can't seem to get [there] using RDP. [...]
Using Windows RDP:
Generic "Remote Desktop can't connect to the remote computer for one of these reasons:
1) Remote access to the server is not enabled
2) The remote computer is turned off
3) The remote computer is not available on the network.
> [...] Do I need to do anything on the extender? [...]
I would connect directly to the router, but I got the extender because there are parts of the house that the router doesn't reach very well - the extender is the solution.
> Any other good resources?
I don't know enough yet to suggest any solutions.
Thanks for your help!!
> I can get to it via RDP with another machine on the LAN.
That would seem to absolve the extender, especially if the Remote
Desktop client is connected more directly to the router.
Is that using the LAN IP address of the laptop? What about using the
WAN/Internet IP address of the router (from within the LAN)? That
should test the router's port forwarding (unless its NAT loopback
feature is broken).
> I would connect directly to the router, but [...]
Yeah, but a short test might be interesting.
Is there some Windows Firewall setting which is needed for off-LAN
access?
Otherwise, it all looks plausible to me. However, if you ever do get
it to work, then you might want to use a different (non-default)
external port number, to avoid making yourself an easy target for
malrfactors.
So, I got frustrated and rebooted the router.
RDP then worked.
Thanks, again!