NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Can't access router locally or remotely
I am currently away from my Netgear R6700v3 router which I set up to be able to access remotely, but it is not working. I am guessing it has something to do with the fact that I have redirected port ...
> [...] R6700v3 [...]
(Firmware version?) Connected to what?
> [...] I set up to be able to access remotely, [...]
"set up" _how_, exactly?
> [...] but it is not working. [...]
"not working" is not a useful problem description. It does not say
what you did. It does not say what happened when you did it. As usual,
showing actual actions (commands) with their actual results (error
messages, LED indicators, ...) can be more helpful than vague
descriptions or interpretations.
> [...] I am guessing it has something to do with the fact that I have
> redirected port 80 to one machine in the local network.
Guess again?
Visit http://netgear.com/support , put in your model number, and look
for Documentation. Get the User Manual (at least). Read. Look for
"Set Up Remote Management". Note that "The default [port] is 8443".
> [...] I can't seem to access any webpages. [...]
Regarding "can't seem to", see "not a useful problem description
[...]", above.
I am not aware of the firmware version as I cannot access the router configuration.
I previously enabled remote management on the router, and I copied the address and port, but the request times out.
When trying to access the internet on the local machine, each request times out as well. I am able to access local devices on the network (i.e. IP Cameras), but the router page is still timing out.
I am able to ping the router (and other websites) using the windows command line, but am unable to access them.
Let me know if you need anything else.
> I am not aware of the firmware version as I cannot access the router
> configuration.Hence the parentheses.
> [...] Connected to what?
Still wondering. If the R6700v3 (WAN/Internet port) is connected to
some other NAT router, then you might be doomed. Of course, if you can
get in using Remote Desktop, then that shouldn't be the problem.> I previously enabled remote management on the router, [...]
Did you test it then?
> [...] and I copied the address and port, but the request times out.
With my weak psychic powers, I can't see either of them. Not port 80
or 443, I'll guess. If you're worried about revealing secrets (like,
say, a public IP address), then the top half of the address, "a.b" out
of "a.b.c.d", would satisfy most of my curiosity. Or, plug that address
into the form at: https://whois.arin.net/ , and see if it is a public or
private address. (But, again, if you can get in using Remote Desktop,
...)> When trying to access the internet on the local machine, each request
> times out as well. [...]So, you can get in using Remote Desktop, but systems local to that
router can't get to the outside world? It's possible that its
management web server has died, but the rest of the router continued to
work, but that wouldn't explain the lack of Internet access through it.> Let me know if you need anything else.
A visit to the site? I don't know of a common failure mode which
would produce those symptoms. And if you can't talk to the thing, then
laying on hands might be your only hope.The router is connected to a modem, and all the other devices are connected to it either via LAN or ethernet (the local machine I'm able to access is connected via ethernet)
The remote desktop connection uses port 3389, and the remote management uses port 8443. Unfortunately I was not able to test the remote management.
My IP address is x.x.231.50, even though I don't think this might be much help.
What's really strange to me is that I can still access all devices on the local network, except for the router. And I know I have the correct IP address of the router because it responds to my pings.
> My IP address is x.x.231.50, even though I don't think this might be
> much help.What was actually requested would have been more interesting.
> [...] I know I have the correct IP address of the router because it
> responds to my pings.What you think that you "know" is less interesting than would be a
precise, accurate description of what you actually did, and what
actually happened when you did it.Knowing that "ping <unspecified_IP_address>" got a response when
issued from some unspecified location is much less informative than you
seem to believe.