NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R7000 Cannot get to settings from Wired Connection
I cannot get to the settings on my R7000 router through a wired connection. I can from a wireless connection. If I try routerlogin.net I get a screen that says "You are not connected to your Route...
- I am embarrassed to say I solved the problem. I still had the wired desktop connected to the att RG. I moved the cable to the R7000 and everything is working as it should now. Thank you again for you input.
> [...] If I try routerlogin.net I get a screen that says "You are not
> connected to your Router's WiFi network. [...]
Welcome to what may be the worst error message in the world. For an
explanation, try:
https://community.netgear.com/t5/x/x/m-p/1365830
Briefly, the idea is that "[www.]routerlogin.net" (or ".com") should
point to your own router, but that's true only if you use your own
router for DNS name resolution. Regardless, you should be able to get
to the thing using its IP address, if you can determine (or guess) that.
Normally, that would be something like "192.168.1.1", but it could be
different.
> [...] If I try 10.0.0.1 [...]
Why that address? It's not certainly wrong, but it's less likely
than the default, "192.168.1.1". If the R7000 really is at "10.0.0.1",
then I'd expect that its WAN/Internet port is connected to some other
router (which uses "192.168.1.*" for its LAN). What's that other
router?
> [...] I am using windows 10 [...]
Ok. Open a Command Prompt (CMD.EXE) window, and get an "ipconfig"
report. What are the IP address of the computer itself, of the Gateway,
and of the DNS server(s)? How do those data compare with those on a
device with a wireless connection?
And, if you have another router, then why? If you've added the
R7000 to extend your wireless-network coverage, then, rather than
cascading multiple routers, you might do better if you configured one of
them (probably the R7000) as a wireless access point rather than as a
full-function router.
Visit http://netgear.com/support , put in your model number, and look
for Documentation. Get the User Manual. Look for "Use the Router as a
Wireless Access Point".
Thanks for your reply. Here are the answers to your questions:
Why 10.0.0.1? I am using an ATT Uverse Residentail gateway in passthrough mode. When I did the initial configurartion of the netgear router is automatically changed the IP address to 10.0.0.1. 10.0.0.1 is correct, as I mentioned in my initial post I can get to the router settings wirelessly using 10.0.0.1 from my laptop. I just acnat get there from my wired desktop.
What are the IP address of the computer itself, of the Gateway, and of the DNS server(s)? How do those data compare with those on a device with a wireless connection? The laptop is on the 10.0.0.1 default gateway. The wired dekstop is not on the 10.0.0.1 gateway.
> [...] I am using an ATT Uverse Residentail gateway in passthrough
> mode. [...]
Not really a model number, but I'm willing to assume that it's some
kind of modem+router. Which would explain the R7000 selecting
"10.0.0.*" for its LAN subnet. I don't know what "in passthrough mode"
means to you, but all the visible evidence suggests that it's operating
as a (modem+)router.
> [...] I just acnat get there from my wired desktop.
> The wired dekstop is not on the 10.0.0.1 gateway.
As usual, showing actual actions with their actual results (error
messages, LED indicators, ...) can be more helpful than vague
descriptions or interpretations. (For example, what's the address of
the "wired dekstop"? I'll guess something like "192.168.1.x".)
That would make sense if your "my wired desktop" were wired to the
AT&T gateway. A computer/device which is connected to the R7000 should
have a "10.0.0.x" address, and it should have no trouble reaching the
R7000 management web site (at "routerlogin.net" or "10.0.0.1").
A computer/device which is connected to the AT&T gateway should have
an address like "192.168.1.x". If that gateway gets a message from your
web browser asking about "10.0.0.1", then it will see that as a foriegn
address, and, if it does anything with it, then it will send it to your
ISP, where it will be discarded. That's because the AT&T gateway has no
idea that there's a "10.0.0.*" subnet hiding on the other side of your
R7000.
If you configure the R7000 as a WAP, then you'll have one big
(extended) LAN, all devices will have addresses in the "192.168.1.*"
subnet, and every device on that subnet should be able to reach every
other device on that subnet (including the R7000-as-WAP, although at
some non-default address).
If there were some reason for you to keep the R7000 in full-function
router mode, then there might be a way to inform the AT&T gateway about
how to reach the devices on the R7000 LAN, but I'd guess that the
R7000-as-WAP scheme would serve you better.- I am embarrassed to say I solved the problem. I still had the wired desktop connected to the att RG. I moved the cable to the R7000 and everything is working as it should now. Thank you again for you input.