as i mention above - i suspect the issue is bcoz of the private ip address we are getting instead of public ip. anyway, would like to ask, do we need to hv 'the program' running to test if the port is open? i mean lets take port 80 for example here. its usually for webserver(IIS). so do we do we need to run IIS if we test using online tool like canyouseeme? i think so as it the tool is looking for a reply? thank you,I am not really familiar with the specific device in question, but the port forwarding rule looks fine. You can try running wireshark on the host system and check if the packets are being seen by the host to verify.
Port Forwarding Checklist
- Make sure the ISP allows port fowarding and on which ports (some ISPs will block certain or all ports on home allocated IP blocks)
- Double check your current public IP (whatsmyip.com and many other sites will tell you)
- Make sure the correct ports are open for the application
- Make sure the correct protocols are selected TCP/UDP
- Make sure the application is NAT friendly (some apps don't work well threw NAT)
- Make sure the host IP is statically set (also make sure it is outside the DHCP scope) , or a DHCP reservation
- Make sure the host firewall allows the incoming ports from the router IP
- Make sure the application is running
- Make sure the application is configured correctly
hi, can you give an example to how we could do that? as i try put netstat in command prompt, i think it show us the port that is already connected. it didnt show my iis(80) in there. but its running as i could access it through the browser on another pc on the same network. thanks.You can use netstat locally to make sure the application is listening on the port
To run the netstat command in Windows, open the Command Prompt (press the Windows key + R and type "cmd" and press Enter) and type "netstat" followed by any desired options or flags. Some common options for netstat include:hi, can you give an example to how we could do that? as i try put netstat in command prompt, i think it show us the port that is already connected. it didnt show my iis(80) in there. but its running as i could access it through the browser on another pc on the same network. thanks.
C:\> netstat -a -o
thanks for the netstat tips. hv tried them all and hopefully be useful in future.To run the netstat command in Windows, open the Command Prompt (press the Windows key + R and type "cmd" and press Enter) and type "netstat" followed by any desired options or flags. Some common options for netstat include:
For example, to display all active connections and listening ports and the PID of the process that owns each one, you would type "netstat -a -o" in the Command Prompt and press Enter.
- -a: Displays all active connections and listening ports
- -b: Displays the executable involved in creating each connection or listening port
- -n: Displays active connections and listening ports using numerical IP addresses instead of resolving hostnames
- -o: Displays the process ID (PID) of the process that owns each connection or listening port
--Code:C:\> netstat -a -o
Also, I believe that one of the main issues you may be facing is that the local ports may just be random and not line up with the remote ports you are opening, but not sure.
telnet 192.168.1.188 31400
ok. probably bcoz of other issues. hv ask him to contact his ISP to help solve. thank alot =)Only 10.0.0.0/8, 172.0.0.0/12, and 192.168.0.0/16 are private. 14.192.239.12 is a public IP.