Configure Cisco FTD Port Forwarding (via FDM)
KB ID 0001680 Problem You have a Cisco FTD device that you manage via FDM, and you would like to setup port forwarding. In the example below I will forward TCP Port 80 (HTTP) traffic from the outside interface of my FTD Device (Firepower 1010) to an internal web server on 10.254.254.212 Solution (Step 1: Create an FTD NAT Policy) Using a web browser connect to the FDM > Polices > NAT > Add. Set the following options; Title:...
Cisco ASA – Port Forward a ‘Range of Ports’
KB ID 0001111 Note: This is for Cisco ASA 5500, 5500-x, and Cisco Firepower devices running ASA Code. This comes up on forums a lot, some applications and most phone systems require a ‘LOT’ of ports to be open. Normally thats fine you just give the internal IP a static public IP and open the ports. But what if you don’t have a spare public IP? I’ve already covered port forwarding before. Cisco PIX / ASA Port...
Sonicwall 2040 Port Forwarding
KB ID 0000346 Problem You would like to set up port forwarding on a Sonicwall 2040, in this example I will assume we are forwarding SMTP (TCP port 25). Sonicwall Pro 2040 – System Screen Note: Notice the “Network Interfaces” section, take note of the names of the interfaces and what they are doing, this will become relevant later. Solution 1. Log into the Sonicwall’s management console. 2. If you have not...
Windows Change the RDP (Remote Desktop) Listening Port
KB ID 0000166 Problem If you didn’t already know the Remote Desktop Protocol Port is TCP 3389, that fine but what if you want to change it to something else? That begs another question, Why? Well some people like to change the port to something else, so that different ports are open in the even of a nasty type performing a port scan on your machine/firewall, even the most clueless script kiddies know that if they see TCP 3389...
Cisco Routers – Port Forwarding
KB ID 0000533 Problem If you have a server or host that you want to be publicly addressable and only have one public IP address then port forwarding is what you require. Solution Assumptions 1. You have a public IP on the outside of your Router. 2. You are performing NAT from your internal range of IP address to your External IP address. To Make Sure 1. Run the following command: PetesRouter#show run | include ip nat inside You...