Author Topic: Some NAT Port forward suddenly fail in WHR-HP-G54  (Read 2982 times)

hellfighter

  • Calf
  • *
  • Posts: 2
Some NAT Port forward suddenly fail in WHR-HP-G54
« on: April 06, 2009, 09:45:35 pm »
   I have a WHR-HP-G54 which set the NAT for the Web (Port 80), FTP (Port 20,21) and Remote Desktop before . But after I restored my computer in this few days. Only the web service can work. The FTP and the remote desktop fail to connected. The internal IP and the Port No. same as before. I can connect it using the internal IP. The router doesn't has any error message in the NAT table, ever I deleted the original entry and then add a new one. Is it the hardware problem of the router ? As the wireless signal become unstable in the past few months, but the configuration and the firmware unchange.

Aveyer

  • Big Bull
  • *****
  • Posts: 501
Re: Some NAT Port forward suddenly fail in WHR-HP-G54
« Reply #1 on: April 06, 2009, 10:37:29 pm »
   Although the port forwarding rule stayed the same( the IP of the PC etc), Are you sure the PC is getting the IP that it should be so that the port forwarding rule is set for that PC (port forward for 192.168.11.2 so the PC IP should be 192.168.11.2 etc)

hellfighter

  • Calf
  • *
  • Posts: 2
Re: Some NAT Port forward suddenly fail in WHR-HP-G54
« Reply #2 on: April 06, 2009, 11:01:12 pm »
   It's using the static internal ip and the ip address is same as the ip address in the NAT table.  In the NAT table. WEB (port 80) will forward to ip 192.168.1.117 (port 80) , ftp ( port 20,21) will forward to 192.168.1.117 (port 20,21) and remote desktop (port 11298) will forward to 192.168.1.110 (port 3389) . Now only the web can work. I have already tried using other computer in the lan to connect the ftp or remote desktop service using that internal ip address. It's work and doesn't have any problem.

Aveyer

  • Big Bull
  • *****
  • Posts: 501
Re: Some NAT Port forward suddenly fail in WHR-HP-G54
« Reply #3 on: April 06, 2009, 11:11:38 pm »
   Since this only started happening since you restored your PC or similar I would think the problem lies there rather than the router, have you checked that these programs/ports are opened in Windows Firewall?