cvisionz wrote:
I have researched the heck out of this and tried everything under the sun to get port forwarding to work on my Actiontec MI424WR Router to work, but no matter what I do, it still won't pass the traffic. Please note I was previously a Network Engineer by trade, so I do fully understand firewalls, port forwarding, QoS, port triggering, UPNP, etc. Before I order a new router, I wanted to make one last ditch effort to see if anyone else was having these problems.
For ease of explanation, assume the following:
1. I am trying to setup Remote Desktop (RDP port 3389) from the Internet
2. I have set everything to factory default
3. No other routers or switches are connected, and a direct ethernet connection from my desktop PC to the FIOS router exists.
4. I am using a standard Windows 7 machine with no third-party firewalls, HIPS, or non-standard antivirus products
5. I recently had COMCAST with a simple port forwarding rule on their router and everything worked fine. No changes to the PC or infrastructure (other than new FiOS service) has occured since then.
Troubleshooting done:
1. Tested that Remote Desktop was working fine on the internal network from different computers connected wirelessly.
2. Ensured Windows firewall was properly set to accept RDP/3389 connections
3. Set Port Forwarding for RDP using the built-in application selector for RDP, where you only choose your computer name and the application and click apply. It automattically adds it to the list.
4. Clicked apply apply, etc and ensured the status of the new port forwarding rule = ACTIVE.
5. Tried to remote from external -- timed out.
6. From inside the network, different online port scanners showed port 3389 as CLOSED.
7. Deleted simple rule and created custom rule using the following:
-- [Hostname 192.168.1.X]
-- Source Ports = ANY
-- Destination Ports = SPECIFY --> 3389
-- WAN Connection Type = All Broadband Devices
-- Forward to Port = Same as Incoming Port
-- Schedule = Always
8. Clicked apply apply, etc and ensured the status of the new custom port forwarding rule = ACTIVE.
9. Tried to remote from external -- timed out. From inside the network, different online port scanners STILL showed port 3389 as CLOSED.
10. Disabled custom rule and placed Computer in the DMZ. Apply, apply, etc. Tried to remote from external -- timed out. From inside the network, different online port scanners STILL showed port 3389 as CLOSED.
11. Configured General Firewall Setting to (Low). Still no works and external port shows closed.
12. Created custom Port Trigger for application RDP for incoming ports: TCP Any -> 3389. Still no works and external port shows closed. Even though it has nothing to do with it, tried setting up for outgoing port trigger TCP 3389. No works.
13. Upgraded the firmware on the device. Rebooted. Still no works and external port shows closed.
14. Used UPNP Forwading on PC and checked it was enabled on Router. Still no works and external port shows closed.
With that all said, is there anything else anyone can think of or tell me about some service that I am not getting because of XYZ reason before I order a replacement router and monkey with setting this all up again??
Thanks in advance,
-cvisionz-
Have you looked at the logs on the router to see if you see the incoming traffic there.
Your rule looks fine, I assume you forwarded tcp AND udp?
should say
TCPany -> 3389
UDPany -> 3389
forward to port same as incoming
schedule always
however I have a 9100em
Personally I change the listener port to something more obscure than 3389. I have no issue accessing via rdp from the outside to 3 nested levels of routers and subnets.