Theme

Welcome · log in · join

Forums → Equipment Support → Hardware By Brand →

Netgear → Re: Port Forwarding not working on WNR1000v2 with latest firmware

uniqs
33

« Upgraded From r6300v2 to R7000-Problems/Issues-Go Back? Advice/Info? • Netgear constantly needs rebooted or my speeds become terrible »

This is a sub-selection from Port Forwarding not working on WNR1000v2 with latest firmware

joe7dust @73.32.17.x	joe7dust to NetFixer Anon 2014-Aug-22 4:33 pm to NetFixer Re: Port Forwarding not working on WNR1000v2 with latest firmware arris tm702g/ct modem router info: Hardware Version WNR1000v2-VC Firmware Version V1.2.2.72NA GUI Language Version V1.0.0.71
	· actions · 2014-Aug-22 4:33 pm ·
joe7dust	joe7dust Anon 2014-Aug-22 4:44 pm Is there a way to update the modem firmware? When you click on advanced tab you get an authentication error, and the comcast tech said this is normal as they added in links for possible future features that were never added. He assured me this modem has no firewall and can't be blocking. It's pretty old and before the time when modems were made with routers/firewalls built in.
	· actions · 2014-Aug-22 4:44 pm ·
NetFixer From My Cold Dead Hands Premium Member join:2004-06-24 The Boro	NetFixer Premium Member 2014-Aug-22 4:53 pm said by joe7dust : Is there a way to update the modem firmware? No, only Comcast can push new firmware to a cable modem on their network.
	· actions · 2014-Aug-22 4:53 pm ·
joedust @73.32.17.x	joedust Anon 2014-Aug-22 4:59 pm Well I provided the info, any leads?
	· actions · 2014-Aug-22 4:59 pm ·
NetFixer From My Cold Dead Hands Premium Member join:2004-06-24 The Boro Netgear CM500 Pace 5268AC TRENDnet TEW-829DRU 3 edits	NetFixer to joe7dust Premium Member 2014-Aug-22 5:12 pm to joe7dust said by joe7dust : arris tm702g/ct modem router info: Hardware Version WNR1000v2-VC Firmware Version V1.2.2.72NA GUI Language Version V1.0.0.71 OK, your Arris modem is actually a modem and not a gateway, so that shouldn't be a problem (but I don't have access to one of those modems with Comcast firmware, so I can't guarantee that Comcast hasn't added a crude firewall to the code). Your Netgear router is the same model as mine with the same firmware, so that is not the source of your problem. I suggest that as a test you put the game PC's local IP address into the router's DMZ, startup the game server, and go to »nmapv4.packetsize.net/ and setup the test as shown in the screen shots below: Shown below is the result I get with my notebook in the DMZ (using my web server on port 6112 instead of your game server): Starting Nmap 5.00 ( »nmap.org ) at 2014-08-22 22:46 CEST NSE: Loaded 0 scripts for scanning. Initiating Ping Scan at 22:46 Scanning 69.137.72.214 [1 port] Completed Ping Scan at 22:46, 0.22s elapsed (1 total hosts) Initiating Parallel DNS resolution of 1 host. at 22:46 Completed Parallel DNS resolution of 1 host. at 22:46, 0.00s elapsed Initiating Connect Scan at 22:46 Scanning c-69-137-72-214.hsd1.tn.comcast.net (69.137.72.214) [1000 ports] Discovered open port 8008/tcp on 69.137.72.214 Discovered open port 8800/tcp on 69.137.72.214 Discovered open port 6112/tcp on 69.137.72.214 Completed Connect Scan at 22:47, 23.44s elapsed (1000 total ports) Host c-69-137-72-214.hsd1.tn.comcast.net (69.137.72.214) is up (0.15s latency). Interesting ports on c-69-137-72-214.hsd1.tn.comcast.net (69.137.72.214): Not shown: 997 filtered ports PORT STATE SERVICE 6112/tcp open dtspc 8008/tcp open http 8800/tcp open unknown Read data files from: /usr/share/nmap Nmap done: 1 IP address (1 host up) scanned in 23.92 seconds Raw packets sent: 1 (28B) \| Rcvd: 1 (28B) Shown below is the result I get with my notebook with only port 6112 forwarded to my web server on port 6112: Starting Nmap 5.00 ( »nmap.org ) at 2014-08-22 23:06 CEST NSE: Loaded 0 scripts for scanning. Initiating Ping Scan at 23:06 Scanning 69.137.72.214 [1 port] Completed Ping Scan at 23:06, 0.22s elapsed (1 total hosts) Initiating Parallel DNS resolution of 1 host. at 23:06 Completed Parallel DNS resolution of 1 host. at 23:06, 0.00s elapsed Initiating Connect Scan at 23:06 Scanning c-69-137-72-214.hsd1.tn.comcast.net (69.137.72.214) [1000 ports] Connect Scan Timing: About 20.00% done; ETC: 23:09 (0:02:04 remaining) Discovered open port 6112/tcp on 69.137.72.214 Discovered open port 8800/tcp on 69.137.72.214 Completed Connect Scan at 23:07, 56.85s elapsed (1000 total ports) Host c-69-137-72-214.hsd1.tn.comcast.net (69.137.72.214) is up (0.16s latency). Interesting ports on c-69-137-72-214.hsd1.tn.comcast.net (69.137.72.214): Not shown: 998 filtered ports PORT STATE SERVICE 6112/tcp open dtspc 8800/tcp open unknown Read data files from: /usr/share/nmap Nmap done: 1 IP address (1 host up) scanned in 57.33 seconds Raw packets sent: 1 (28B) \| Rcvd: 1 (28B) If you don't see port 6112 open on the above test site, then either your game is not actually using port 6112, or the game is not actually configured to be a server, or there is a software firewall (or other security software) on the host PC that is blocking port 6112. A troubleshooting step you can try if the above test does not show port 6112 open is to open a command prompt window and use the built-in netstat utility to find out if your game server is actually listening on port 6112. Here is my result from doing that: C:\>netstat -ano Active Connections Proto Local Address Foreign Address State PID TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 1932 TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 1128 TCP 0.0.0.0:443 0.0.0.0:0 LISTENING 1932 TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4 TCP 0.0.0.0:1026 0.0.0.0:0 LISTENING 1932 TCP 0.0.0.0:1029 0.0.0.0:0 LISTENING 1272 TCP 0.0.0.0:1801 0.0.0.0:0 LISTENING 1272 TCP 0.0.0.0:2103 0.0.0.0:0 LISTENING 1272 TCP 0.0.0.0:2105 0.0.0.0:0 LISTENING 1272 TCP 0.0.0.0:2107 0.0.0.0:0 LISTENING 1272 TCP 0.0.0.0:5900 0.0.0.0:0 LISTENING 1328 TCP 0.0.0.0:6112 0.0.0.0:0 LISTENING 1932 TCP 0.0.0.0:8008 0.0.0.0:0 LISTENING 1932 TCP 0.0.0.0:8023 0.0.0.0:0 LISTENING 2180 TCP 127.0.0.1:1025 127.0.0.1:1027 ESTABLISHED 816 TCP 127.0.0.1:1027 127.0.0.1:1025 ESTABLISHED 1328 TCP 127.0.0.1:1032 127.0.0.1:1033 ESTABLISHED 1328 TCP 127.0.0.1:1033 127.0.0.1:1032 ESTABLISHED 1328 TCP 127.0.0.1:4494 127.0.0.1:4495 ESTABLISHED 1532 TCP 127.0.0.1:4495 127.0.0.1:4494 ESTABLISHED 1532 TCP 192.168.10.16:139 0.0.0.0:0 LISTENING 4 TCP 192.168.10.16:1199 64.91.230.234:443 ESTABLISHED 1532 TCP 192.168.10.16:1210 64.91.230.234:443 ESTABLISHED 1532 TCP 192.168.10.16:1212 199.188.202.39:443 TIME_WAIT 0 TCP [::]:135 [::]:0 LISTENING 1128 TCP [::]:1026 [::]:0 LISTENING 1932 TCP [::]:1029 [::]:0 LISTENING 1272 TCP [::]:2103 [::]:0 LISTENING 1272 TCP [::]:2105 [::]:0 LISTENING 1272 TCP [::]:2107 [::]:0 LISTENING 1272 TCP [::]:5900 [::]:0 LISTENING 1328 TCP [::]:8023 [::]:0 LISTENING 2180 TCP [2601:5:1f00:8d8:217:a4ff:fee3:e7cf]:1703 [2400:cb00:2048:1::c629:d7b9]:80 TIME_WAIT 0 TCP [2601:5:1f00:8d8:217:a4ff:fee3:e7cf]:1704 [2400:cb00:2048:1::c629:d7b9]:80 TIME_WAIT 0 UDP 0.0.0.0:445 : 4 UDP 0.0.0.0:1028 : 1272 UDP 0.0.0.0:3456 : 1932 UDP 0.0.0.0:3527 : 1272 UDP 127.0.0.1:123 : 1340 UDP 192.168.10.16:123 : 1340 UDP 192.168.10.16:137 : 4 UDP 192.168.10.16:138 : 4 C:\>tasklist Image Name PID Session Name Session# Mem Usage ========================= ====== ================ ======== ============ System Idle Process 0 0 28 K System 4 0 22,692 K smss.exe 548 0 432 K avgrsx.exe 584 0 20,176 K avgcsrvx.exe 624 0 46,084 K csrss.exe 836 0 2,948 K winlogon.exe 868 0 12,128 K services.exe 912 0 9,840 K lsass.exe 924 0 2,644 K svchost.exe 1080 0 6,788 K svchost.exe 1128 0 9,228 K InCDsrv.exe 1196 0 6,760 K svchost.exe 1340 0 55,348 K svchost.exe 1384 0 7,324 K WLTRYSVC.EXE 1404 0 4,856 K BCMWLTRY.EXE 1416 0 12,000 K spoolsv.exe 1468 0 13,876 K ccs.exe 1536 0 9,056 K msdtc.exe 1664 0 7,548 K avgidsagent.exe 1724 0 19,952 K avgwdsvc.exe 1736 0 20,052 K BTNtService.exe 1752 0 6,132 K svchost.exe 1892 0 5,944 K inetinfo.exe 1932 0 15,192 K TFService.exe 252 0 4,536 K vncserver.exe 816 0 6,776 K mqsvc.exe 1272 0 9,884 K vncserver.exe 1328 0 9,116 K explorer.exe 2600 0 46,964 K mqtgsvc.exe 2700 0 6,952 K vncserver.exe 3644 0 8,296 K SynTPEnh.exe 3656 0 8,824 K QLBCTRL.exe 3956 0 10,776 K HP Wireless Assistant.exe 4052 0 9,880 K smax4pnp.exe 4088 0 7,648 K WLTRAY.EXE 2024 0 10,064 K hpqWmiEx.exe 2572 0 8,288 K InCD.exe 2740 0 6,264 K TFTray.exe 2796 0 3,416 K avgui.exe 2940 0 23,372 K wmiprvse.exe 2972 0 9,228 K ADU.exe 3068 0 8,240 K ctfmon.exe 396 0 7,024 K Dynamic DNS Client.exe 3300 0 37,744 K qvp32.exe 3516 0 8,396 K NetPerSec.exe 368 0 6,880 K HPQTOA~1.EXE 2316 0 8,604 K taskmgr.exe 3572 0 2,848 K tlntsvr.exe 2180 0 7,736 K cmd.exe 2380 0 1,644 K seamonkey.exe 1532 0 149,248 K sleep.exe 2712 0 4,848 K cmd.exe 2880 0 5,740 K tasklist.exe 2732 0 7,924 K wmiprvse.exe 2860 0 9,672 K The above two commands tell me that I do have a process that is listening on TCP port 6112, and that process is inetinfo.exe (the MS IIS web server application). You can also use the command netstat -anb, but that takes longer to run, and its output is not as neat and easy to read.
	· actions · 2014-Aug-22 5:12 pm ·
joedust @73.32.17.x	joedust Anon 2014-Aug-22 6:28 pm I followed your instructions and it did find 1 port! 2869 was open and this reminded me about UPnP, so I installed the UPnP components for windows XP then followed a guide on getting the router to show in My Network Places. Then I set my UPnP in my router to refresh more often and rebooted everything. PORT STATE SERVICE 6112/tcp open dtspc Now when I run the scanner it shows 6112 as open. I got excited thinking this would be the end of my frustration, but noone is able to join my games. I ran the netstat command you suggested and it is showing that the game is listening. Is it normal for it to list a different port by my IP address? I was expecting this: proto local address foreign address TCP 192.168.1.4:6112 206.17.175.52:6112 but instead it shows: TCP 192.168.1.4:1257 206.17.175.52:6112 This all suggests to me that the port forwarding and DMZ I setup were not actually working in the router correctly as advertised, because UPnP just basically is supposed to do the same thing but automatic right? So UPnP being enabled shouldn't have changed anything but it did. If you can explain that discrepancy you probably have my solution.
	· actions · 2014-Aug-22 6:28 pm ·
joedust	joedust Anon 2014-Aug-22 7:02 pm Another weird thing... when I go into the router UPnP section there isn't anything listed under UPnP Portmap Table. I hit refresh and still nothing.
	· actions · 2014-Aug-22 7:02 pm ·
NetFixer From My Cold Dead Hands Premium Member join:2004-06-24 The Boro Netgear CM500 Pace 5268AC TRENDnet TEW-829DRU	NetFixer to joedust Premium Member 2014-Aug-22 7:16 pm to joedust said by joedust : I followed your instructions and it did find 1 port! 2869 was open and this reminded me about UPnP, so I installed the UPnP components for windows XP then followed a guide on getting the router to show in My Network Places. Then I set my UPnP in my router to refresh more often and rebooted everything. PORT STATE SERVICE 6112/tcp open dtspc Now when I run the scanner it shows 6112 as open. I got excited thinking this would be the end of my frustration, but noone is able to join my games. I ran the netstat command you suggested and it is showing that the game is listening. Is it normal for it to list a different port by my IP address? I was expecting this: proto local address foreign address TCP 192.168.1.4:6112 206.17.175.52:6112 but instead it shows: TCP 192.168.1.4:1257 206.17.175.52:6112 This all suggests to me that the port forwarding and DMZ I setup were not actually working in the router correctly as advertised, because UPnP just basically is supposed to do the same thing but automatic right? So UPnP being enabled shouldn't have changed anything but it did. If you can explain that discrepancy you probably have my solution. I can't explain why installing and configuring UPnP allowed port 6112 port forwarding to work. I do not have UPnP enabled on any router on my network, and I have disabled or uninstalled it on every PC under my control. I had no problems with port 6112 forwarding to my notebook without using UPnP. However, I think I may be able to answer your other questions. The source port being different from the destination port is normal for most TCP connections. However, if 192.168.1.4 is both the local IP address for your game host PC and for a PC that you are trying to connect to that host using a public IP address or hostname; then that will not likely work because the WNR1000v2-VC does not properly support something called NAT loopback. That means that you can't connect via a public IP address or hostname to a server running behind the WNR1000v2-VC from any device that is on your LAN behind the WNR1000v2-VC. Here are examples of the NAT loopback problem: This is a connection to my notebook's web server from the Internet (from a PC that is not behind the WNR1000v2-VC's LAN): This is a failed connection to my notebooks web server using it's public hostname from the notebook itself: OTOH, this is a connection to my notebook's web server from itself, but using its private hostname:
	· actions · 2014-Aug-22 7:16 pm ·
NetFixer	NetFixer to joedust Premium Member 2014-Aug-22 7:19 pm to joedust said by joedust : Another weird thing... when I go into the router UPnP section there isn't anything listed under UPnP Portmap Table. I hit refresh and still nothing. I have no explanation for that. I don't use UPnP, and I have no interest in even temporarily installing/activating UPnP even for a test.
	· actions · 2014-Aug-22 7:19 pm ·
joedust @73.32.17.x	joedust to NetFixer Anon 2014-Aug-22 7:19 pm to NetFixer I don't think my issue has anything to do with loopback. 1) Connect to bnet. 2) Tell bnet you're making a game. 3) bnet tells everyone else you made a game and where to find it. 4) Everyone connects to your game. (hopefully)
	· actions · 2014-Aug-22 7:19 pm ·
NetFixer From My Cold Dead Hands Premium Member join:2004-06-24 The Boro Netgear CM500 Pace 5268AC TRENDnet TEW-829DRU 1 edit	NetFixer Premium Member 2014-Aug-22 7:22 pm said by joedust : I don't think my issue has anything to do with loopback. 1) Connect to bnet. 2) Tell bnet you're making a game. 3) bnet tells everyone else you made a game and where to find it. 4) Everyone connects to your game. (hopefully) No that example would not be affected by NAT loopback, but the previous example you posted did seem to imply that you were testing from your LAN behind the router.
	· actions · 2014-Aug-22 7:22 pm ·
joedust @73.32.17.x	joedust Anon 2014-Aug-22 8:19 pm I'm still not able to host games.... wonder what it could be? Are the 0.0.0.0 IP addresses normal on the line where it says listening to port 6112?
	· actions · 2014-Aug-22 8:19 pm ·

joedust	joedust to NetFixer Anon 2014-Aug-22 9:41 pm to NetFixer Forget about UPnP. The correct port is open when scanned online. You implied I should run netstat and I did, but I am not sure what to make of the 0.0.0.0 IP shown where the listening port is. (paste below) Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\Admin>netstat -ano Active Connections Proto Local Address Foreign Address State PID TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 928 TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4 TCP 0.0.0.0:2869 0.0.0.0:0 LISTENING 1116 TCP 0.0.0.0:6113 0.0.0.0:0 LISTENING 2748 TCP 127.0.0.1:1029 0.0.0.0:0 LISTENING 1920 TCP 127.0.0.1:1101 127.0.0.1:1102 ESTABLISHED 3124 TCP 127.0.0.1:1102 127.0.0.1:1101 ESTABLISHED 3124 TCP 127.0.0.1:5152 0.0.0.0:0 LISTENING 1856 TCP 192.168.1.4:139 0.0.0.0:0 LISTENING 4 TCP 192.168.1.4:2128 64.91.230.234:443 ESTABLISHED 3124 TCP 192.168.1.4:2135 206.17.175.57:6112 ESTABLISHED 2748 TCP 192.168.1.4:2869 192.168.1.1:3984 CLOSE_WAIT 1116 UDP 0.0.0.0:445 : 4 UDP 0.0.0.0:500 : 692 UDP 0.0.0.0:4500 : 692 UDP 127.0.0.1:123 : 964 UDP 127.0.0.1:1900 : 1116 UDP 127.0.0.1:2142 : 964 UDP 127.0.0.1:2200 : 1380 UDP 192.168.1.4:123 : 964 UDP 192.168.1.4:137 : 4 UDP 192.168.1.4:138 : 4 UDP 192.168.1.4:1900 : 1116 C:\Documents and Settings\Admin> note: I changed the port to 6113 for troubleshooting.
	· actions · 2014-Aug-22 9:41 pm ·
NetFixer From My Cold Dead Hands Premium Member join:2004-06-24 The Boro Netgear CM500 Pace 5268AC TRENDnet TEW-829DRU	NetFixer to joedust Premium Member 2014-Aug-22 10:05 pm to joedust said by joedust : I'm still not able to host games.... wonder what it could be? Are the 0.0.0.0 IP addresses normal on the line where it says listening to port 6112? The 0.0.0.0 address means that the server is listening to all IP addresses (and that is normal for most services installed on a PC with a single active NIC). If a particular server had multiple IP addresses available, a given service could be configured to only listen on a specific IP address (or addresses). Shown below is a netstat I just did from the workstation I am using for this post; it has two active NICS, and you can see that some of the services are indeed bound to specific IP addresses, but others are bound to all IP addresses (and you can also see my connections to this web site): C:\>netstat -ano Active Connections Proto Local Address Foreign Address State PID TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 1352 TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4 TCP 127.0.0.1:1127 127.0.0.1:1128 ESTABLISHED 2512 TCP 127.0.0.1:1128 127.0.0.1:1127 ESTABLISHED 2512 TCP 192.168.9.100:139 0.0.0.0:0 LISTENING 4 TCP 192.168.9.100:1330 64.91.230.234:443 ESTABLISHED 2512 TCP 192.168.9.100:1460 64.91.230.234:443 TIME_WAIT 0 TCP 192.168.9.100:1461 64.91.255.98:80 TIME_WAIT 0 TCP 192.168.9.100:1462 64.91.254.210:80 TIME_WAIT 0 TCP 192.168.9.100:1463 64.91.254.210:80 TIME_WAIT 0 TCP 192.168.9.100:1464 64.91.254.210:80 TIME_WAIT 0 TCP 192.168.9.100:1465 64.91.254.210:80 TIME_WAIT 0 TCP 192.168.9.100:1466 64.91.254.210:80 TIME_WAIT 0 TCP 192.168.9.100:1467 64.91.254.210:80 TIME_WAIT 0 TCP 192.168.9.100:1468 64.91.230.234:443 ESTABLISHED 2512 TCP 192.168.9.100:4905 192.168.9.2:139 ESTABLISHED 4 TCP 192.168.20.100:139 0.0.0.0:0 LISTENING 4 TCP [::]:135 [::]:0 LISTENING 1352 TCP [2601:5:1f00:ac7:e291:f5ff:fe95:b69d]:3456 [2400:cb00:2048:1::c629:d6ba]:80 TIME_WAIT 0 UDP 0.0.0.0:445 : 4 UDP 0.0.0.0:500 : 1132 UDP 0.0.0.0:1029 : 2644 UDP 0.0.0.0:1030 : 2644 UDP 0.0.0.0:1032 : 2644 UDP 0.0.0.0:4500 : 1132 UDP 0.0.0.0:19540 : 4 UDP 0.0.0.0:49300 : 2644 UDP 127.0.0.1:123 : 1712 UDP 192.168.9.100:123 : 1712 UDP 192.168.9.100:137 : 4 UDP 192.168.9.100:138 : 4 UDP 192.168.20.100:123 : 1712 UDP 192.168.20.100:137 : 4 UDP 192.168.20.100:138 : 4 I understand that you are probably leery of posting your public IP address in this public forum, and I won't try to persuade you otherwise (especially since you may be operating your host PC in the router's DMZ, and also have its internal firewall disabled). However, if you register on this site, you can send me an IM with your current public IP address and I can at least tell you if I can make a connection to your server on port 6112. I won't be able to test the game, but I can at least verify if that port is open for inbound connections. Alternatively, you can visit my »portscan.dcs-net.net site (you won't even need to do any scans, and it would not make any difference if you did since I don't store the results of the scans), and my server log should give me that information. I can just look in the server access logs for an IP address beginning with 73.32.17, because I already know that part of your IP address from this site's "anonymous" poster location display. Other than that, without full access to your router and your host PC (and I am not asking for, nor do I want that access), I don't think that I can be of any further help in this matter. From everything you have posted, your game server should be working, and I am out of suggestions.
	· actions · 2014-Aug-22 10:05 pm ·
NetFixer	NetFixer to joedust Premium Member 2014-Aug-22 10:10 pm to joedust said by joedust : Forget about UPnP. The correct port is open when scanned online. You implied I should run netstat and I did, but I am not sure what to make of the 0.0.0.0 IP shown where the listening port is. OK, then you shouldn't need to bother to get your public IP address to me, since you have now verified that the port is open on the Internet. And hopefully I explained the reason for the 0.0.0.0 address in my previous reply.
	· actions · 2014-Aug-22 10:10 pm ·

Forums → Equipment Support → Hardware By Brand → Netgear	« Upgraded From r6300v2 to R7000-Problems/Issues-Go Back? Advice/Info? • Netgear constantly needs rebooted or my speeds become terrible »
This is a sub-selection from Port Forwarding not working on WNR1000v2 with latest firmware