Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2500
  • Last Modified:

port forwarding on netgear DGND3700v2

Hi All,

I am having major trouble port forwarding on the DGND3700v2 router. I have never used this router before and just wondering if anyone knows how to do this sucessfully, everything I have tried just does not work.

All I want to do is set up remote desktop connections to the 5 or so computers I have behind the router. Any ideas what I'm doing wrong?
0
ezekuel
Asked:
ezekuel
  • 3
  • 2
1 Solution
 
bigbigpigCommented:
I've never used that particular router but port forwarding should be pretty straight forward.  Follow this link - it's to the manual of that router.  Look on page 105.  When you're setting it up on your router look for the service name RDP or Remote Desktop.  If it's not there you can create a custom service for TCP 3389.

http://www.downloads.netgear.com/files/GDC/DGND3700V2/DGND3700v2_UM_09Mar12.pdf

Now, you're probably going to have problems with the 5 computers.  If you have 5 computers listening on port 3389 and all 5 are behind a single public IP then it's not going to work.  Well, 1 of the 5 will work.  You can port forward to a single IP on the LAN for that port.  You either need multiple public IP's or you need to have the 5 computers all listening on different ports.
0
 
ezekuelAuthor Commented:
Thanks. How would I make the computers listen on different ports and set up the ports for them on port forwarding
0
 
tailoreddigitalCommented:
You could set the router to forward an external (incoming) port to a particular computer.  

For example,

TCP port 12000 point to 192.168.1.5
               12001 to 192.168.1.6
               12002 to 192.168.1.7       etc.....

So when remoting in,   add the port,   i.e,

xxx.xxx.xxx.xxx:12001   would be the "computer" in the Remote Desktop Connection input

If your ip is dynamic, you can use a service like dyndns.com to use a hostname instead of a IP that will change.

So then for your "computer" you can use something like    hostname.dyndns.org:12001    this would remote into  192.168.1.6  (as above)
0
Cyber Threats to Small Businesses (Part 1)

This past May, Webroot surveyed more than 600 IT decision-makers at medium-sized companies to see how these small businesses perceived new threats facing their organizations.  Read what Webroot CISO, Gary Hayslip, has to say about the survey in part 1 of this 2-part blog series.

 
tailoreddigitalCommented:
If you want to change the computer's listen port,

http://www.techrepublic.com/blog/datacenter/changing-the-rdp-listening-port-on-windows-server/1939


You'll need to reboot after the change.   Plus you'll need to open this port in the system firewall.
0
 
tailoreddigitalCommented:
i use this method for RDP for an office of 25 and at my home of 3.  It's a great method, works well.
0
 
bigbigpigCommented:
If you have the need to access multiple computers or resources inside your network from the Internet then you should consider a VPN.  

But here's how to change the RDP port number.  Leave one of them at default port, which is 3389, then change the other 4 each to a different port.  3390, 3391, 3392, 3393 should work if nothing else is binding to those ports.

From Microsoft (http://support.microsoft.com/kb/306759):
Start Registry Editor.
Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber
On the Edit menu, click Modify, and then click Decimal.
Type the new port number, and then click OK.
Quit Registry Editor.
Restart the computer.

Then do the port forwarding steps from the manual linked above.  Create 5 entries; one for each of the ports.  Make them match your LAN computers IP's.  So if your LAN computer 192.168.0.50 (or whatever) is changed to port 3390 then set up your port forwarding on the Netgear so 3390 goes to 192.168.0.50.

A couple other considerations... make sure your public IP is static or you're using dynamic DNS.  Make sure your LAN computers have static IP's.  Make sure your LAN computers are set to not sleep or go into standby.  That'll kill the network connection.
0

Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now