Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
TP-Link Wireless Access Point problem.
12 views
Skip to first unread message
Dave Symes
Oct 23, 2012, 2:12:03 PM10/23/12
to
Pre-amble...
Got a Tablet/pad recently but never saw in all the stuff I read about them
that without a wireless network connection, they are mostly just bricks.
We have a number of RO and Win computers and accessories networked in the
house by cable via Netgear Router and that works perfectly.
To get this brick usable, I've added a TP-Link TL-WA801ND Wireless Access
Point to one of the Router network sockets.
It works, and the initial setup worked so that is has a network name, WPA2
encryption and a security key.
Both the Tab/pad and my Smartphone connect and do the business with it.
Problem:
I can't connect with it to access the Config pages, of which the QI guide
says: "Open your web browser and type in 192.168.1.154 and press enter.
That times out and cannot be found on any browser I have, beit Firefox,
MIE, Chrome or even Netsurf.
Neither can it be found by pinging from either Win PC or RO CLI.
Does any knowledgeable person have some usefull suggestions to throw my
way.
Thanks
Dave
--
Dave Triffid
Got a Tablet/pad recently but never saw in all the stuff I read about them
that without a wireless network connection, they are mostly just bricks.
We have a number of RO and Win computers and accessories networked in the
house by cable via Netgear Router and that works perfectly.
To get this brick usable, I've added a TP-Link TL-WA801ND Wireless Access
Point to one of the Router network sockets.
It works, and the initial setup worked so that is has a network name, WPA2
encryption and a security key.
Both the Tab/pad and my Smartphone connect and do the business with it.
Problem:
I can't connect with it to access the Config pages, of which the QI guide
says: "Open your web browser and type in 192.168.1.154 and press enter.
That times out and cannot be found on any browser I have, beit Firefox,
MIE, Chrome or even Netsurf.
Neither can it be found by pinging from either Win PC or RO CLI.
Does any knowledgeable person have some usefull suggestions to throw my
way.
Thanks
Dave
--
Dave Triffid
Jeremy Nicoll - news posts
Oct 23, 2012, 3:03:30 PM10/23/12
to
Dave Symes <da...@triffid.co.uk> wrote:
>I can't connect with it to access the Config pages, of which the QI guide
>says: "Open your web browser and type in 192.168.1.154 and press enter.
This implies that your LAN doesn't use 192.168.1.xxx addresses for your
>I can't connect with it to access the Config pages, of which the QI guide
>says: "Open your web browser and type in 192.168.1.154 and press enter.
local devices. Assuming that's the case, you will need to temporarily
change the PC you want to do the configuration from so that it does have a
suitable ip address & netmask.
To set the PC's network address etc, go (in XP terms) to Network Conenctions
-> Local Area Connection -> Properties -> General -> Internet Protoco TCP/IP
-> Properties and then set the specific IP address and netmask (probably
255.255.255.0) that you want rather than whatever you currently have there.
If you currently have "obtain an address automatically" change it to "use
the following address").
Connect the PC to the box with a LAN cable. (In the old days you might also
have needed this to be a crossover cable, but modern equipment is usually
capable or determining that there's a direct connection to another computer
- rather than an intermediate switch - and using the approriate cores in the
cable.) Then disable and re-enable the LAN connection on that PC.
Afterwards, reverse the changes.
--
Jeremy C B Nicoll - my opinions are my own.
Email sent to my from-address will be deleted. Instead, please reply
to newsre...@wingsandbeaks.org.uk replacing "aaa" by "284".
Dave Symes
Oct 23, 2012, 5:05:55 PM10/23/12
to
In article <mpro.mcd0xt...@wingsandbeaks.org.uk.invalid>,
Jeremy Nicoll - news posts <jn.nntp....@wingsandbeaks.org.uk>
wrote:
I did the above noted (Win 7 BTW) and indeedy it all worked as expected.
Thanks for the info Jeremy, appreciated.
Dave
Afterthought...
It appears from the meagre handbook that you can change the device
address, so I'm wondering if I changed it to 192.168.1.254 it might also
solve the problem? (So I wouldn't have to do the above if I wanted to
change something in the config next time).
D.
--
Dave Triffid
Jeremy Nicoll - news posts <jn.nntp....@wingsandbeaks.org.uk>
wrote:
> Dave Symes <da...@triffid.co.uk> wrote:
> >I can't connect with it to access the Config pages, of which the QI
> >guide says: "Open your web browser and type in 192.168.1.154 and press
> >enter.
> This implies that your LAN doesn't use 192.168.1.xxx addresses for your
> local devices. Assuming that's the case, you will need to temporarily
> change the PC you want to do the configuration from so that it does have
> a suitable ip address & netmask.
> To set the PC's network address etc, go (in XP terms) to Network
> Conenctions -> Local Area Connection -> Properties -> General ->
> Internet Protoco TCP/IP -> Properties and then set the specific IP
> address and netmask (probably 255.255.255.0) that you want rather than
> whatever you currently have there. If you currently have "obtain an
> address automatically" change it to "use the following address").
> Connect the PC to the box with a LAN cable. (In the old days you might
> also have needed this to be a crossover cable, but modern equipment is
> usually capable or determining that there's a direct connection to
> another computer - rather than an intermediate switch - and using the
> approriate cores in the cable.) Then disable and re-enable the LAN
> connection on that PC.
> Afterwards, reverse the changes.
Indeedy my LAN uses 192.168.0.xxx addresses.
> >I can't connect with it to access the Config pages, of which the QI
> >guide says: "Open your web browser and type in 192.168.1.154 and press
> >enter.
> This implies that your LAN doesn't use 192.168.1.xxx addresses for your
> local devices. Assuming that's the case, you will need to temporarily
> change the PC you want to do the configuration from so that it does have
> a suitable ip address & netmask.
> To set the PC's network address etc, go (in XP terms) to Network
> Conenctions -> Local Area Connection -> Properties -> General ->
> Internet Protoco TCP/IP -> Properties and then set the specific IP
> address and netmask (probably 255.255.255.0) that you want rather than
> whatever you currently have there. If you currently have "obtain an
> address automatically" change it to "use the following address").
> Connect the PC to the box with a LAN cable. (In the old days you might
> also have needed this to be a crossover cable, but modern equipment is
> usually capable or determining that there's a direct connection to
> another computer - rather than an intermediate switch - and using the
> approriate cores in the cable.) Then disable and re-enable the LAN
> connection on that PC.
> Afterwards, reverse the changes.
I did the above noted (Win 7 BTW) and indeedy it all worked as expected.
Thanks for the info Jeremy, appreciated.
Dave
Afterthought...
It appears from the meagre handbook that you can change the device
address, so I'm wondering if I changed it to 192.168.1.254 it might also
solve the problem? (So I wouldn't have to do the above if I wanted to
change something in the config next time).
D.
--
Dave Triffid
M. Wynn
Oct 23, 2012, 5:14:17 PM10/23/12
to
"Dave Symes" <da...@triffid.co.uk> wrote in message
news:52e3481...@triffid.co.uk...
1) To connect to the TP-Link you need to connect via wires direct to a PC.
2) I would assign an address in the same order as your setup currently uses.
Martin.
Jeremy Nicoll - news posts
Oct 23, 2012, 5:18:24 PM10/23/12
to
Dave Symes <da...@triffid.co.uk> wrote:
>Indeedy my LAN uses 192.168.0.xxx addresses.
>I did the above noted (Win 7 BTW) and indeedy it all worked as expected.
>Thanks for the info Jeremy, appreciated.
Great!
>Indeedy my LAN uses 192.168.0.xxx addresses.
>I did the above noted (Win 7 BTW) and indeedy it all worked as expected.
>Thanks for the info Jeremy, appreciated.
> It appears from the meagre handbook that you can change the device
> address, so I'm wondering if I changed it to 192.168.1.254 it might also
> solve the problem?
Changing it to 192.168.0.xxx should work, provided you choose an xxx value
that nothing else on your lan uses, outwith the range of addresses DHCP
might serve up (if that's turned on in your router).
> (So I wouldn't have to do the above if I wanted to change something in the
> config next time).
will (probably) revert to the original address though.
Dave Symes
Oct 23, 2012, 11:55:56 PM10/23/12
to
In article <mpro.mcd76n...@wingsandbeaks.org.uk.invalid>,
> > It appears from the meagre handbook that you can change the device
> > address, so I'm wondering if I changed it to 192.168.1.254 it might
> > also solve the problem?
> No. But I think you didn't type what you meant to. ;-)
> Changing it to 192.168.0.xxx should work, provided you choose an xxx
> value that nothing else on your lan uses, outwith the range of addresses
> DHCP might serve up (if that's turned on in your router).
Bwaaa! You are so right Jeremy, good catch, indeed I did mean a 0.xxx
change on the Access Point.
When I originally configured the Netgear Router (Few years ago) I set a
collection of address as reserved for manual use and they are used for
much of the home machinery on which DHCP is configured Off (The SARPCs for
example) so there are only a couple of DHCP addresses in use on the Router
that follow on directly from the reserved set.
I'll probably set the Access Point to something like 0.100
> > (So I wouldn't have to do the above if I wanted to change something in
> > the config next time).
> Correct. Bear in mind if you ever hardware reset the access point then
> it will (probably) revert to the original address though.
Yes I think that would be a given.
Thanks again for the advice.
Dave
--
Dave Triffid
Jeremy Nicoll - news posts <jn.nntp....@wingsandbeaks.org.uk>
wrote:
> Dave Symes <da...@triffid.co.uk> wrote:
[Snippy]
wrote:
> Dave Symes <da...@triffid.co.uk> wrote:
> > It appears from the meagre handbook that you can change the device
> > address, so I'm wondering if I changed it to 192.168.1.254 it might
> > also solve the problem?
> No. But I think you didn't type what you meant to. ;-)
> Changing it to 192.168.0.xxx should work, provided you choose an xxx
> value that nothing else on your lan uses, outwith the range of addresses
> DHCP might serve up (if that's turned on in your router).
change on the Access Point.
When I originally configured the Netgear Router (Few years ago) I set a
collection of address as reserved for manual use and they are used for
much of the home machinery on which DHCP is configured Off (The SARPCs for
example) so there are only a couple of DHCP addresses in use on the Router
that follow on directly from the reserved set.
I'll probably set the Access Point to something like 0.100
> > (So I wouldn't have to do the above if I wanted to change something in
> > the config next time).
> Correct. Bear in mind if you ever hardware reset the access point then
> it will (probably) revert to the original address though.
Thanks again for the advice.
Dave
--
Dave Triffid
0 new messages