NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
remote desktop
2 TopicsRDP blocked on internal network?
I recently got an Orbi to upgrade from my previous Netgear router. Since getting the new network (which is actually the exact same subnet as the previous), I have been unable to RDP between any of my windows machines (neither by hostname nor ip address). Yet, all machines can be pinged and SMB shares have no problem. There doesn't seem to be any settings on the Orbi that would affect this one way or another. Facts: All Windows machines in question were 100% accessible with RDP with my previous gen Netgear My Windows machines are on the same subnet and wired network plugged into the base unit - wireless isolation is not the issue Network settings on the machines are set to Private with file/print sharing and discoverable Windows Firewalls on the machines are OFF There is no 3rd party software that contains a firewall on any of the machines The machines are pingable by each other and file shares can be accessed Yes, RDP is enabled on the default 3389 port and remote access is enabled and not restricted at all All Windows machine IP's are set statically (on the same subnet) and are outside the DHCP pool These machines _CAN_ be accessed via RDP externally via port forwarding. However, none of them can RDP to eachother within the local network. Any help/ideas are very welcome!!! Thanks!Remote Desktop Setup
I would like to setup my network so that the amchien with IP address 192.168.1.40 can be accessed with a static IP provided by my ISP, let's call that one 50.149.12.741. On my last router (a sonicwall) there was a way to tell the router that an RDP request (either on our LAN or from an outside computer) to 50.149.12.741 should be routed to 192.168.1.40; but I cannot find how to do that one this Nighthawk R7000. Is this type of setup possible with the router I've chosen?Solved32KViews0likes4Comments