can't contact extender via IP address
Region : UnitedKingdom
Model : TL-WA830RE
Hardware Version : V1
Firmware Version :
Range extender is working. My computer can see that it is part of the network and displays its IP address. However, when I try to access the IP address wirelessly via browser to explore the setting, I just get a 'page not available' message. Windows diagnostics says device not responding. Do you need a hardwired connection to do this? If not, any other reason for this behaviour?
Try to check your computer's IP addressing and IP address on TP-Link. I think that you have other classes addresses on devices.
No, that is not the problem. All IP addresses are good.
I know that addresses are good, because network is working, but my question was abut classes IP addresses on devices. Please give us example, what is your IP address on computer and on TP-Link.
Originally Posted by jimasek
I think something might be getting lost in translation here. There are no duplicated IP addresses. Is that what you mean?
I currently have 3 TP-Link devices
*TL-WA701ND (192.168.0.253) <- configured as repeater
*TL-WA730RE (192.168.0.254) <- configured as repeater
My PC is connected to the TL-WA730RE via a wifi connection and so far
I can access both the 701ND and 730RE's GUI via a firefox browser.
Both the 701ND and 730RE will also work as a repeater if their LAN IP is 192.168.x.x (any number) but if you
will try to access it via a browser, the GUI will not load. You need configure it on the same network with your
Hope this helps. Good luck.
so you are saying that i cant access mine because my router ip is 192.168.2.1 and my extenders ip is 192.168.1.254, if so how would i go around changing the ip of the extender to match the .2. of my router when i cant access the settings and i cant change the routers ip because it virgin media wont let me do it?
logging on to TL WA830RE
This thread has confused me. My user guide tells me to put http://tplinkextender.net into a browser and that should open the log in page. I could not get that to work when I used my default Chrome browser (I just got a load of doubtful advertising) but it worked fine when I reverted to Internet Explorer.