Showing results for 
Search instead for 
Do you mean 
Reply
Rob_ZA
Posts: 4
Registered: ‎06-21-2010

WAG120N - Port Forwarding, Remote Management, DMZ does not work

Hi Guys

I've recently bought a WAG120N.  Great looking device :smileyhappy:  Anyways, before I used it I flashed it to the latest firmware (Ver.1.00.12 (ETSI) Annex A).  I am on Annex A....ADSL over POTS, so I am using the correct firmware :smileyhappy:

Everything works except port forwarding and remote management.  I have tried everything.  Reset to default...flash new firmware...reset to default....re-configure....same issues.  

After each reset, I try only one failing component at a time.  So I haven't setup remote admin, port forwarding and DMZ (even though they should be able to co-exist no problem.  For the purpose of trouble shooting, one thing at a time).

I use port forwarding to remote access into my windows 7 machine via RDP (3389).  The config screen does indicate the port is forwarded to the correct internal IP.  But no connectivity.

The DMZ issue freaked me out as I normally use that as a test when port forwarding is giving me issues.

This happens with remote management too.  With it enabled (or disabled), I cannot access the admin pages from an external IP.

And I’ve disabled all forms of firewalls on the device and from my windows machine.

I was able to perform all the above on my previous wireless router (different vendor).  I’m also getting second thoughts about this WAG120N thinking back to what I had.

One thing can be said, this is a very secure internet gateway!  It does not accept any connection via the WAN :smileyhappy:


Expert
Expert
Posts: 12,649
Registered: ‎07-16-2006

Re: WAG120N - Port Forwarding, Remote Management, DMZ does not work

How do you test connections from the internet? Do you really test from the internet? You cannot test port forwarding etc. from within your LAN.

1. Please post the exact port forwarding, port triggering, DMZ host and UPnP settings of your router.

2. On the computer to which you forward those ports, open a command prompt window and enter "ipconfig /all" and "netstat -an". Post the full output.
Rob_ZA
Posts: 4
Registered: ‎06-21-2010

Re: WAG120N - Port Forwarding, Remote Management, DMZ does not work

Thanks for the pointers.  I understand the fundamentals of networking :smileyhappy:  I test from work and from a friends house.  He has a similar setup ,different router, and im able to connect to his RDP.  I've asked him to review my setup even.  He couldnt find anything wrong. 

 

I'm at work at the moment.  I'll post the results of the commands you've suggested as soon as I'm in front of the machine a bit later :smileyhappy:

Rob_ZA
Posts: 4
Registered: ‎06-21-2010

Re: WAG120N - Port Forwarding, Remote Management, DMZ does not work

[ Edited ]

OK....settings as promised.  The items requested in point 1 are links to screenshots.

 

 

C:\>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : *******
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom 570x Gigabit Integrated Con
troller
Physical Address. . . . . . . . . : 00-19-B9-62-A8-E3
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.200
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 168.210.2.2
196.14.239.2

C:\netstat -an

Active Connections

Proto Local Address Foreign Address State
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2869 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1025 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1161 0.0.0.0:0 LISTENING
TCP 192.168.1.200:139 0.0.0.0:0 LISTENING
TCP 192.168.1.200:1097 67.215.233.130:80 TIME_WAIT
TCP 192.168.1.200:1115 41.144.16.23:18832 TIME_WAIT
TCP 192.168.1.200:1126 196.210.230.57:55000 TIME_WAIT
TCP 192.168.1.200:1127 41.133.65.161:50567 TIME_WAIT
TCP 192.168.1.200:1146 41.185.92.128:52597 TIME_WAIT
TCP 192.168.1.200:1159 192.168.1.100:2869 TIME_WAIT
TCP 192.168.1.200:1160 192.168.1.100:2869 TIME_WAIT
TCP 192.168.1.200:2869 192.168.1.1:1148 CLOSE_WAIT
TCP 192.168.1.200:3389 192.168.1.100:51024 ESTABLISHED
TCP 192.168.1.200:47771 192.168.1.200:1112 TIME_WAIT
TCP 192.168.1.200:47771 192.168.1.200:1117 TIME_WAIT
TCP 192.168.1.200:47771 192.168.1.200:1122 TIME_WAIT
UDP 0.0.0.0:445 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:4500 *:*
UDP 127.0.0.1:123 *:*
UDP 127.0.0.1:1900 *:*
UDP 192.168.1.200:123 *:*
UDP 192.168.1.200:137 *:*
UDP 192.168.1.200:138 *:*
UDP 192.168.1.200:1900 *:*

c:\

 

Links to screenshots;

 

http://img375.imageshack.us/img375/3868/dmz.gif

http://img580.imageshack.us/img580/6562/portforwarding.gif

http://img202.imageshack.us/img202/9672/portrangeforwarding.gif

http://img821.imageshack.us/img821/816/portrangetriggering.gif

http://img204.imageshack.us/img204/98/upnp.gif

Expert
Expert
Posts: 12,649
Registered: ‎07-16-2006

Re: WAG120N - Port Forwarding, Remote Management, DMZ does not work

O.K. All that looks correct. You forward TCP port 3389 to 192.168.1.200 and the computer on 192.168.1.200 is listening on that port. The router configuration looks correct. It should work this way.

1. Sometimes the internal configuration of the router gets corrupted which means that although some setting is visible in the web interface it does not affect the real settings internally. You have a couple of other forwardings in the port forwarding page. All are disabled except the last one for 3389. I would suggest you reset the router to factory defaults (30 seconds reset button) and then make minimal changes to establish the internet connection and test port forwarding of 3389. Maybe it makes a difference...

2. Some routers have a firmware bug where port forwarding of a single port does not work but port range forwarding works. Try port range forwarding instead of single port forwarding.

3. Does DMZ host work?

4. Occasionally, it helps to reflash the latest firmware, then reset to factory defaults and the reconfigure.

5. If all that does not help, I would say it's a firmware bug and you have to call Linksys support to fix this.