NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Struggling with Port Forwarding
I'm going nuts trying to get this to work...
I have a wireless WansView IP Camera set up on a static local IP and port: 192.168.1.178:2331
When I visit that address, I get the camera. So far, so good.
So now I want to be able to visit my router's WAN address on that port and get the same camera. I get the WAN address from the Router Status page (and confirm it by visiting whatismyipaddress.com). When I hit port 80, I get the login screen for my router, so I'm sure I've got it right. But when I hit <router address>:2331, nothing.
I set up port forwarding TCP/UDP. (Added a Custom Service and forwarded external 2331 to the same port internal on 192.168.1.178). I test this by going to canyouseeme.org and having it check port 2331, and then looking at the Router Logs. The logs actually show it being forwarded:
[LAN access from remote] from 52.202.215.126:58819 to 192.168.1.178:2331, Sunday, Apr 08,2018 09:29:48
But when I hit <my public IP>:2331, I still get nothing (connection timeout). I'm at a loss for what to try next to figure out where these packets are being dropped...? Thanks in advance for any help/pointers.
4 Replies
> Model: R6300v2|AC1750 Dual Band Gigabit router
Is that accurate? Firmware version?
> I have a wireless WansView IP Camera set up on a static local IP and
> port: 192.168.1.178:2331
> When I visit that address, I get the camera.
That's "http://192.168.1.178:2331"?
What are the first two octets ("a.b" out of "a.b.c.d") in your public
IP address?
> [...] But when I hit <router address>:2331, nothing.
> But when I hit <my public IP>:2331, I still get nothing (connection
> timeout).
Same thing or different things?
Are you doing this from inside the LAN or from the outside world?
(Both should work.)
> I set up port forwarding TCP/UDP. (Added a Custom Service [...]
That sounds ok to me. Copy+paste of the actual rule would be
reassuring.
As I write, the in-line pictures are still obscure, waiting for
moderator approval.Thanks for the rapid response!
> Is that accurate? Firmware version?
Hardware Version R6300v2
Firmware Version V1.0.3.6_1.0.63CH
> That's "http://192.168.1.178:2331"?
Correct. Although my browser seems to drop the protocol portion. I guess it doesn't care.
> What are the first two octets ("a.b" out of "a.b.c.d") in your public IP address?
68.184.x.x
> Same thing or different things?
Same, yes. Sorry for using different terms.
> Are you doing this from inside the LAN or from the outside world? (Both should work.)
Both. I'm testing from inside the LAN (my desktop on wifi) and from the canyouseeme site. Interestingly, I just tried it from my phone with wifi turned off (forcing it onto the cellular network) and the only difference is that for port 80 I do not get the router's login page. I'm guessing that's some default security setting on the router.
> That sounds ok to me. Copy+paste of the actual rule would be
reassuring. As I write, the in-line pictures are still obscure, waiting for
moderator approval.The pic is a screenshot of the rule, but I'll try pasting the table here:
# Service Name External Start Port Internal Start Port Internal IP address 1 MooseCam 2331 2331 192.168.1.178 Last thing I should mention -- I have a dual-boot Windows 10/Ubuntu system, so I can use tools on either OS to help diagnose. I tried a public traceroute (http://www.monitis.com/traceroute/) but didn't really understand the results. Network stuff is not my strong suit.
> Firmware Version V1.0.3.6_1.0.63CH
Oooh. Charter-specific firmware. You could have atypical problems.
> 68.184.x.x
Sounds like Charter.
> [...] Although my browser seems to drop the protocol portion. I guess
> it doesn't care.
Modern browsers typically hide the annoying "scheme://" details, so
you don't get confused by reality.
> [...] the only difference is that for port 80 I do not get the
> router's login page. I'm guessing that's some default security setting
> on the router.
Yup. Perhaps: ADVANCED > Advanced Setup > Remote Mangement. These
routers seem to be willing to allow access unconditionally from the LAN,
but enforce the restrictions on access from the WAN.
I could be missing something, but it all looks good to me. I know
nothing, but the "CH" firmware worries me. You might see if Charter
knows anything, or if you can find a Charter-user forum where more
people might know more.
What a headache. WansvieW camera works fine here on hole network. The other set of caleras we have in NH work just fine. When i leave home, camera says off line.
i do not know if this is a nighthawk x6 issue, which we have been having or an issue with camera or an issue with ports. Very frustrating.