This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
Just connected the new router to an ATT 3360 modem and it has connected to the internet and appears to be working with a wired connection. Haven't checked the wireless side yet.
Problem:
Can't access the router with the web browser Firefox.
OS is Windows 7 (64bit) SP1
I do not own nor want a smart phone so solutions based on that platform for me is a non-starter.
The error is a screen that tells me what I already know - that I am not on a wifi connection.
I have not reset the router as of yet - would like tio have access to the router before I do.
The URLs in the set up instructions do not work at all - using the gateway address (10.0.0.1) gets me the error message telling me that I am not on wifi!
I am beginning to think that I need to get rid of this router since apparently NETGEAR does not want to support it with basic capabilities. I am hopeful that the user community can point out something that I have missed.
Overnight, I tried a couple things and got better results.
First, I tried accessing the router via a laptop running Linux.and wifi.
It was able to connect to the router using the NETGEAR44 account and got through the registration set up. Also changed passwords, etc.
So, it looks like NETGEAR didn't provide software on the "wired" port to handle such a login. Since they "apparently" assumed that everyone would be accessing it using a telephone, they only provided such a capability on the wireless side of the router.
So, it appears that I am getting good results as long as I use a lap top on the wireless side of the router. So, I am happy for the moment!
I learned a few things and I appreciate the help from the community!
Motorola? Is that a simple modem, or a modem+router?
> The URLs in the set up instructions do not work at all - using the > gateway address (10.0.0.1) gets me the error message telling me that I > am not on wifi!
That address suggests that your "an ATT 3360 modem" is actually a modem+router. Cascading multiple routers can cause multiple problems, including ones like yours. You might want to see if you can find some instructions on how to put it into a modem-only ("bridge") mode. By itself, that might solve your problems.
> The error is a screen that tells me what I already know - that I am > not on a wifi connection.
As usual, the actual error message would be more helpful than your interpretation of the actual error message. Copy+paste is your friend. (A Web or forum search for the actual message text generally works better than a search for what you think it all means.)
My guess would be that you've found what may be the worst error message in the world. For an explanation, try:
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. (Or, if the Netgear router can intercept your DNS queries.) 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" (for a plain router) or "192.168.0.1" (for a modem+router), but it could be different. ("10.0.0.1" is a typical alternate, for example.)
In some cases, disconnecting the router's WAN/Internet port can make it easier to avoid the various problems/pitfalls involved in such situations. That (and cycling the power) could put it back onto the default ("192.168.1.*") LAN subnet, too.
Overnight, I tried a couple things and got better results.
First, I tried accessing the router via a laptop running Linux.and wifi.
It was able to connect to the router using the NETGEAR44 account and got through the registration set up. Also changed passwords, etc.
So, it looks like NETGEAR didn't provide software on the "wired" port to handle such a login. Since they "apparently" assumed that everyone would be accessing it using a telephone, they only provided such a capability on the wireless side of the router.
So, it appears that I am getting good results as long as I use a lap top on the wireless side of the router. So, I am happy for the moment!
I learned a few things and I appreciate the help from the community!
> So, it looks like NETGEAR didn't provide software on the "wired" port > to handle such a login. [...]
It may look that way (to you), but I doubt that that was the problem. It's much more likely that the IP configuration of your Windows 7 system was different from that of a different system which worked as expected. (Or, you had it connected to your "an ATT 3360 modem" instead of to your R6700. Or, ...)
Without answers to any of the previously posed questions, about all I can do is guess.
