NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
AdrianL
Oct 10, 2020Aspirant
Access Point - cannot reach routerlogin
Hi there! (I have no real previous experience with access points and the like so excuse me for my lack of knowledge haha..) I bought a NETGEAR Access Point (WAC104) a few days ago and I...
- Oct 11, 2020Thank you so much for the reply, antinode!
A friend of mine just managed to figure it out for me. In case anyone ever comes across this post, here's how we did it;
We went into the command prompt (cmd) and wrote down 'arp -a' (Windows laptop). Then it was basically a matter of writing down the IP addresses in one of those MAC Adress Lookup sites until one of them mentioned NETGEAR.
That IP adress directed me to NETGEAR's routerlogin and I was able to login using 'admin' as the username and 'password' as.. well.. the password.
No idea if any of this makes sense but it worked for me, haha. The IP listed on the label on the back of the access point didn't work and all the basic ones didn't either - probably because my router already assigned an IP and Gateway.
Cheers!
Adrian
antinode
Oct 10, 2020Guru
> However, writing down the labeled IP of the access point in my browser
> doesn't work [...]
"the labeled IP of the access point"? Which is what? And what's the
IP address of your computer with the web browser?
When you connect a wireless access point to your (unspecified) "my
router", the WAP might use DHCP to get a new IP address from (the DHCP
server in) your (unspecified) "my router". If your (unspecified) "my
router" provides an "Attached Devices" or "DHCP Clients" or similar
report, then you might discover the new address of the WAP there.
> [...] routerlogin doesn't work either ('You may not be connected to
> your router's WiFi network'). [...]
That's typically a DNS problem:
https://community.netgear.com/t5/x/x/m-p/1976674
> [...] it makes sense that the gateway is the same as my router as it's
> basically the same network [...]
More than "basically". But, if you can discover the new address of
the WAP, then that should work from anyplace on your (one big) LAN.
> [...] and your router is from a different brand?
Wouldn't matter. You could have the same trouble with any router.
AdrianL
Oct 11, 2020Aspirant
Thank you so much for the reply, antinode!
A friend of mine just managed to figure it out for me. In case anyone ever comes across this post, here's how we did it;
We went into the command prompt (cmd) and wrote down 'arp -a' (Windows laptop). Then it was basically a matter of writing down the IP addresses in one of those MAC Adress Lookup sites until one of them mentioned NETGEAR.
That IP adress directed me to NETGEAR's routerlogin and I was able to login using 'admin' as the username and 'password' as.. well.. the password.
No idea if any of this makes sense but it worked for me, haha. The IP listed on the label on the back of the access point didn't work and all the basic ones didn't either - probably because my router already assigned an IP and Gateway.
Cheers!
Adrian
A friend of mine just managed to figure it out for me. In case anyone ever comes across this post, here's how we did it;
We went into the command prompt (cmd) and wrote down 'arp -a' (Windows laptop). Then it was basically a matter of writing down the IP addresses in one of those MAC Adress Lookup sites until one of them mentioned NETGEAR.
That IP adress directed me to NETGEAR's routerlogin and I was able to login using 'admin' as the username and 'password' as.. well.. the password.
No idea if any of this makes sense but it worked for me, haha. The IP listed on the label on the back of the access point didn't work and all the basic ones didn't either - probably because my router already assigned an IP and Gateway.
Cheers!
Adrian