RDP Through RT-AC66U Using Merlin 3.0.0.4.374.32

[cejack]

I've noticed I cannot connect via Windows Remote Desktop through the router using the newer Merlin FW. I was able to map non-standard ports to port 3389 through the router to a computer IP on the local network before with the Asus factory firmware.

I have other services such as web server mapped to a non-standard port, SSH, and FTP services coming through the router via port mappings and these work just fine with the Merlin firmware.

However, Windows RDP has been a problem with Merlin FW. I can't seem to figure what could be blocking / stopping RDP. I thought perhaps someone here on this forum may have an idea. Interesting thing is that I experimented with using the standard RDP port 3389 on both the external and the internal port forward and it works but only to one of my desktops on the internal network running Windows 7. It does NOT work with 3389 on both the external and internal ports connecting to a desktop running Windows XP Professional. I hope this may identify the culprit to someone more savvy than I.

Also RDP doesn't work with the original setup from Port 2389 (external) to Port 3389 (internal) piped to an internal Windows XP Pro desktop running RDP. Was wondering why I can't remap the the ports when this used to work with the older Asus FW on the same router.

This is a Merlin Build installed in the last month on my RT-AC66U. Was using older Factory Asus firmware in production environment before this with no problems providing Remote Desktop access.

(Will look up FW revision of the original Asus FW if it's important. Bought another identical RT-AC66U refurb and hooked up it up at the home office and took the original to the work office.)

Any ideas or comments are appreciated. Don't want to go back to the Asus firmware as I wanted to try Open VPN with Merlin firmware but RDP is more important to me at this time.

~cj

 

[RMerlin]

Why do you need a port forward if you intend to use OpenVPN?

I strongly recommend against opening RDesktop on the WAN side anyway, for security reasons.

Are you actually testing the port forward from outside your network? I would check the firewall on your Windows desktop, it might reject RDesktop connections that aren't originating from your LAN. Have a close look at any installed security software.

Also make sure you don't have local and remote ports entered backward on the webui, and double check the destination IP of the target machine.

 

[grimy55]

I'm using RDP through a non-standard port from inside and outside my LAN without any issue to connect a win7 machine. I have the Merlin build .33 and had .32 before that on my AC66R. The port redirection works well.

I would say, given these info, your problem is likely to come from a setting issue.

 

[cejack]

Why do you need a port forward if you intend to use OpenVPN?

.

I'm too lazy yet to set up OpenVPN.

I understand Open VPN will be the best way to do this in the future as the VPN Client will appear as a local machine on the LAN once logged in. Just haven't had the time to delve into that yet.

Just started a new position with lots of responsibilities and trying to shave time off the clock any way I can right now.

Just curious why I lost Rdesktop. Probably some arcane Windows thing. I'll try the Windows dudes on IRC and see if they have any ideas.

I'm suspecting maybe network topology could also possibly be an issue since I bought two AC-66U units. Just finding it strange as this used to be pretty seamless before.

Tried all your recommendations. I'm going to have a second set of eyes look at this things. Can't seem to figure out what could be the issue here.