NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
WN2500RPv2 Factory reset now wont see http://mywifiext
So I moved and wanted to reset this up after having used it a few years at my old place. I did the push button factory reset on it and now (as per the setup guide) have connected both wirelessly and ...
I was not able to get connected to my EX2700 extender using the IP address I know was right as I double check it always from the tablet which is connected to the extender. My router does dynamic addressing and I set the range.
I finely got connected to the extender by using that URL this site doesn't want to be displayed. The one that starts with (mywifi) I didn't change anything, but it connected and worked as it should and use to when only using the IP address of extender which is easy to find. I know I could assign extender an IP, but it is easy to find. I did notice when using that mywifi...... URL browser puts the HTTP:// in front. If I change the HTTP to HTTPS:// with the mywifi.............. I get the same error as when I use only an IP address, which is unable to reach device. Error a little different in all 3 browsers I tried, but means the same.
> I was not able to get connected to my EX2700 extender [...]
"not able" 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.
> [...] using the IP address I know was right as I double check it
> always from the tablet which is connected to the extender. [...]
It's nice that you're happy, but I can't see your "the IP address I
know was right", and I have no idea how you "double check it". I do
know that specifying a wrong IP address is a good way to get a failure.
People come to these forums every day, claiming to "know" something
which isn't true. Such experience leads to skepticism about any claim
which includes "I know", but no actual evidence.
> [...] If I change the HTTP to HTTPS:// with the mywifi..............
> I get the same error as when I use only an IP address, which is unable
> to reach device. [...]
These devices are too simple to use HTTPS ("https://<whatever>").
With some browsers, you might need to specify "http://" explicitly.
And what happens if you specify some known-wrong IP address?