Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[tech285]

Hello,

I am trying to set up Remote Desktop to access a server on my LAN from else where in the world.
I have a DSL-520b modem and a DIR-655 (HW ver B1 FW ver 2.10NA) router. The DIR-655 is connected to the router. I have 2 desktops on the LAN. On the DIR-655 I am forwarding port 3389 to the IP of the server. I am testing with another desktop on the LAN (same subnet as the server). If I Remote Desktop connect to the WAN IP address of the DIR-655 router, the connection is successful. So I assume this tells me the port forwarding on the DIR-655 is working correctly. If I try and Remote Desktop to the outside IP address, the WAN IP of the DSL-520b, 108.225.X.X, it does not work. So I assume I do not have the DSL-520b set up correctly.  I have the NAT Virtual Server set up all External/Internal start and end ports set to 3389 TCP and the server IP is set to the IP I am trying to connect to. Remote server is blank. I also have Port Triggering set on 3389 TCP.  I used a port scanner and verified that 3389 is open.

The client i'm testing with is Windows 8 and the server is Windows Server 2012. That shouldn't matter, though. It works fine on the LAN behind the firewalls, and on the WAN side of the router, just not on the WAN side of the DSL-520b modem.

Any help is greatly appreciated

[FurryNutz]

Link>Welcome!

• What region are you located?

Internet Service Provider and Modem Configurations

• If this modem has a built in router, it's best to bridge the modem. Having 2 routers on the same line can cause connection problems: Link>Double NAT and How NAT Works. To tell if the modem is bridged or not, look at the routers web page, Status/Device Info/Wan Section, if there is a 192.168.0.# address in the WAN IP address field, then the modem is not bridged. If the modem can't be bridged then see if the modem has a DMZ option and input the IP address the router gets from the modem and put that into the modems DMZ. Also check the routers DHCP IP address maybe conflicting with the ISP modems IP address 192.168.0.1. Check to see if this is the same on the ISP modem and if modem can't be bridged. If so, change the DIR router to 192.168.1.1 or .0.254.
  Example of a D-Link router configured for PPPoE with ISP Modem bridged: PPPoE Configuration on Router

RDP works with out any PF on the LAN side. PF or Virtual Server maybe needed if you are attempting to RDP from a remote location from the WAN side thru the ISP modem to the 655 router. Public IP address is needed on the WAN side of the 655 router...

[tech285]

I'm in Southern California.

Here is the info from the device info, WAN:
Port/VPI/VCI = 0/0/35
Con. ID        = 1
Category      = UBR
Service        = pppoe_0_0_35_1
Interface      =     nas_0_0_35
Protocol       = Bridge
QoS             = Disabled
State           = Enabled
Status          = Unknown
IP Addr        = <blank>

Does Protocol = Bridge and no IP mean it is in bridge mode?

[tech285]

The modem has a LAN address of 192.168.1.1 and is running DHCP and gives 192.168.1.2 (router WAN IP) to the router. All PC and devices are connected to the router and all have 192.168.0.X IP addresses.

[FurryNutz]

So you seem to have a double NAT condition here since the 655 seems to be getting a 192.168.1.2 address on the WAN side. Is this ok if your not trying to RDP from the WAN side. This means that the ISP modem is not bridged and has NAT enabled. We recommend bridging the ISP modem if possible and let the 655 handle the NAT only. Then RDP from the WAN side will be good. RDP from the 655 LAN side with devices connected to it will should still work. Just not between the 655 and ISP modem. You'll need to contact your ISP to ask them about bridging the ISP modem if this is needed.