- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
YARLF (Yet Another Router Login Failure) Question
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
YARLF (Yet Another Router Login Failure) Question
I assure everyone that I've read the FAQ and paid special attention to #6 including the Nighthawk app (Genie). Still no joy. However, while I think I know the cause, I do know a workaround. Here's the situation:
My Nighthawk router is installed as part of my existing home network (PakEdge) as an access point. I didn't do the installation. I simply chose "access point" as the Nighthawk's installation option. As it happens, when I look at the network connection status details (using Windows 10), the Nighthawk's IPV4 Gateway, and server IPs are identical to those of the PakEdge - 192.168.1.99. This is understandable, I suppose, since the Nighthawk was installed as an access point. Both WiFi SSDs are visible and working fine (interestingly, the Nighthawk is substantially faster). Finally, my Nighthawk router and its PakEdge counterpart are connected via an ethernet cable.
This may be part and parcel of a problem I asked about in a very recent post about how I might setup two separate WiFi networks using the same ethernet. It arose as a consequence of wanting to access the Nighthawk router and disable smart connect. But, can't login to Nighthawk.
Anyway, any advice would be greatly appreciated.
Michael
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: YARLF (Yet Another Router Login Failure) Question
> [...] can't login to Nighthawk.
"can't" 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.
If you configured your R7900 (whatever its undisclosed firmware
version might be), the default would have been for it to get its new LAN
IP address using DHCP, so, probably from your main router.
I know nothing about your "PakEdge" router, but I'd guess that it
offers some kind of "Attached Devices" or "DHCP Clients" (or similar)
report, where the R7900-as-WAP should appear, revealing its new LAN IP
address. You should be able to reach its management web site at that
address.
> [...] in a very recent post [...]
Thanks for the helpful link. This?:
https://community.netgear.com/t5/x/x/m-p/2015183
> [...] how I might setup two separate WiFi networks using the same
> ethernet. [...]
I don't know what you mean by "separate" here. Different SSID? One
can't communicate with the other?
In that other thread, regarding "does not (cannot)", see "can't",
above.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: YARLF (Yet Another Router Login Failure) Question
What do you have controlling dhcp? Are you able to log into that and check the attached devices?
It should be whats assigning the IP address. It shouldn't be the same as the pakedge.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: YARLF (Yet Another Router Login Failure) Question
I am amazed at your response to the word "can't" as in "can't login...". Perhaps you're unfamiliar with the 6th question of the FAQ (referred to in the intro to my post). Question #6 describes the problem clearly and succinctly AND provides a number of suggestions as to how to solve the login issue - each of which, as I wrote, I had tried. If that's not clear enough for you, then I am at a loss.
But, perhaps I'm too hasty in taking offense. As described in the FAQ, when a login fails you get redirected to a microsoft supported website with a bunch of links which assume you used the wrong IP address or credentials. The site then provides the ability to look up the correct IP address and default credentials for the particular make and model of the router. There does that help?
You're right about my not mentioning the firmware version. It's the latest. V1.0.1.4_10.0.12.
As for you knowing nothing about the PakEdge router I can't help that short of providing a link to the user manual which I'm more than willing to do if I thought it would help. I would suggest that routers offer a range of functionality, most of which are held in common but differ in the details. With commonality in mind, one approach (not yours, sadly) might be to offer one or more suggestions or further questions like "did you try ...?" or "have you thought of doing ..."
Regards,
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: YARLF (Yet Another Router Login Failure) Question
> I am amazed at your response [...]
Why? Do you believe that I can see what you're doing? Or that your
description conveyed any useful information?
> [...] Perhaps you're unfamiliar with the 6th question of the FAQ [...]
I don't know which "the FAQ" you mean, or where you found it. And
even if I were reading it, it still might not tell me what _you_ did, or
what happened when you did it.
> [...] There does that help?
Not at all.
Visit http://netgear.com/support , put in your (actual) model number,
and look for Documentation. Get the User Manual. Read. Look for
"Types of Logins". Further reading might not hurt, either.
> You're right about my not mentioning the firmware version. It's the
> latest. V1.0.1.4_10.0.12.
I'll bite. For what is _that_ "the latest" firmware? Look for
"Model" on the product label.
> As for you knowing nothing about the PakEdge router I can't help that
> short of providing a link to the user manual which I'm more than willing
> to do if I thought it would help. [...]
As it's your router, it might be more helpful if _you_ read its user
manual first.
> [...] one approach (not yours, sadly) might be to offer one or more
> suggestions or further questions like "did you try ...?" or "have you
> thought of doing ..."
I'm still waiting for answers to questions already asked. For
example, you've already had two different suggestions to look at your
main router to get the IP address of your R7900-as-WAP:
> I know nothing about your "PakEdge" router, but I'd guess that it
> offers some kind of "Attached Devices" or "DHCP Clients" (or similar)
> report, where the R7900-as-WAP should appear, revealing its new LAN IP
> address. You should be able to reach its management web site at that
> address.
> What do you have controlling dhcp? Are you able to log into that and
> check the attached devices?
> It should be whats assigning the IP address. [...]
What's still unclear about those?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: YARLF (Yet Another Router Login Failure) Question
@mtp1032 wrote:
As described in the FAQ, when a login fails you get redirected to a microsoft supported website with a bunch of links which assume you used the wrong IP address or credentials. The site then provides the ability to look up the correct IP address and default credentials for the particular make and model of the router.
Which FAQ is that? You have yet to point a link to one.
I know of no FAQ that would direct anyone to a Microsoft site.
The failure to login to any Netgear device is highly unlikely to take you out to Microsoft.
It would be nice to have a link to that FAQ. It could provide useful extra information alongside this:
How do I log in to my NETGEAR wireless router? | Answer | NETGEAR Support
and this:
If you cannot login to your router | Answer | NETGEAR Support
Nothing there goes out to Microsoft. Maybe something on your system redirected you. If so, that could offer some clues as to what really went on at your end.
• What is the difference between WiFi 6 and WiFi 7?
• Yes! WiFi 7 is backwards compatible with other Wifi devices? Learn more