NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Can't access Extender via www.mywifiext.net
I just installed a Netgear WN2500RP range extender, and it seems to be working correctly; however, I am unable to log in to www.mywifiext.net to access the device using a browser. Attempting to access...
pawnslinger wrote: It sounds like the subnet mask in the extender is different from that in your computer. That is a classic problem with this class of device. If you think this might be the case, you can establish communications with the device by connecting it by wire to your computer and making sure your computer has no other lan/internet path (connect while both are powered down). Power up the device first, let it settle a couple of minutes, then power on your computer. With no access to your main router, it will use the DHCP in the device to set the subnet mask and get an ip address. You can now use the browser to access the device.
Okay, I'm having the same problem accessing my Extender using www.mywifiext.net which keeps rerouting to the general netgear support site. Your subnet issue makes sense and is no doubt my problem.
Thru repeated full Extender resets and starting all over from the beginning, I am able to enter the www.mywifiext.net configuration menus UNTIL I select a router to connect to. The moment this connection is made, it seems the router's DHCP subnet immediately takes hold and contact with the Extender is dropped, consequently preventing further settings changes and any web access to the Extender again. Very aggravating!
Your alternative hard-wired access method sounds like it could work but I don't have an ethernet cable at hand to try it. And, some devices these days dont even have ethernet ports. I think I should be able to wirelessly access this unique subnet extender any time I want to make and test various settings tweaks. Maybe I can use the "route" command line to create a static connection between www.mywifiext.net and the Extender's internal subnet. Can you tell me what the default Extender subnet is?
Any other suggestions?
Was having what seemed to be the same problem. The solution from Netgear's LiveChat (which actually worked!) was based on the fact that I have a WEP router, not WPA.
So I several times did a factory reset on the Extender. I could always connect to it initially via mywifiex.com or .net. For me, I would always lose access to mywifiext and all internet after I connected to the newly named router.
I used someone else's tip on here not to change the default name given to the Extender ([name]_2GEXT). Don't know if that would have mattered or not, that alone didn't fix it.
Then it asks for your Passphrase and generates 4 Keys -- for WEP systems, you put your wifi password in as Key 1, and don't click "generate."
I'm sure others know this difference for WPA vs WEP, I had no idea and it was not spelled out in the instructions that were with the product, nor those online. The LiveChat person said he was passing on the suggestion that this instruction be included -- otherwise I don't know how anyone with an old router is using the product?
Maybe this will help someone else and you can avoid the same problem -- good luck!
So I several times did a factory reset on the Extender. I could always connect to it initially via mywifiex.com or .net. For me, I would always lose access to mywifiext and all internet after I connected to the newly named router.
I used someone else's tip on here not to change the default name given to the Extender ([name]_2GEXT). Don't know if that would have mattered or not, that alone didn't fix it.
Then it asks for your Passphrase and generates 4 Keys -- for WEP systems, you put your wifi password in as Key 1, and don't click "generate."
I'm sure others know this difference for WPA vs WEP, I had no idea and it was not spelled out in the instructions that were with the product, nor those online. The LiveChat person said he was passing on the suggestion that this instruction be included -- otherwise I don't know how anyone with an old router is using the product?
Maybe this will help someone else and you can avoid the same problem -- good luck!