TOT TP Link replacement - just plug in and go?

[WorriedNoodle]

We've got one of these free TP Link Wireless Modem Routers with our TOT ADSL and it has been nothing but a pain to use since we got it 2 years ago. Always needing to reboot the TP-Link to get some devices online, cannot change the DNS etc and presumably hack-able as mentioned on another thread on Thai Visa?

* If I just buy an off the shelf replacement Brand/model Wireless Modem Router from a shopping mall what is recommended and will it just plug in and work or do I need some settings to apply to work with TOT?

[lopburi3]

Other than your name/password all other functions should be set in the modem software setup for TOT. You will have to set up the WiFi to your preference for password and type of operations allowed. Much information available on uTube and Google as well as here. Am sure someone using TOT can provide rundown on settings here just in case automatic set up fails.

[KittenKong]

If you just change the wifi channel on your existing router you may find that it works much better with your devices.

It may also be possible to upgrade the firmware and that may help, but dont do this if you dont know what it involves.

[KhunBENQ]

and will it just plug in and work or do I need some settings to apply to work with TOT?

In a strict sense: no plu&play.

You have to do settings.

If you are lucky you will have a shop clerk who will at least take care for the basic settings for ToT, so that only password and username have to be filled in.

[lopburi3]

Every modem I have bought, and there have been many, had plug and play setup software for Thai ISP's if you wish to use it.

[thedemon]

I would put the TP Link in bridge mode so that it works as an ADSL modem only. Then buy a regular (non ADSL) router/AP to handle routing and WiFi.

There are 2 reasons to do it this way.

1 - More stable ADSL sync.

2 - You will then have a router that is still compatible with other technologies (e.g. Fibre). ADSL is a sunset technology.

If the ADSL modem won't self configure, apart from user/PW, the only TOT specific settings you may need are;

VPI=1

VCI=32

ADSL2+

Annex M

[Superpiggy]

If problem with changing the DNS is that you can't save, use Internet Explorer. For some reason Firefox and Chrome doesn't work for that.

[WorriedNoodle]

Thanks guys. Appreciate the advice from all. My main problem is we have Samsung Android portable devices around the house that sometimes take ages to get an external IP. Tried changing channels, no difference - everything on DHCP but still hold ups on Android. Don't get this at our other 3BB and True wifi hub locations we use with same devices. Only on TOT and TP Link. Will try your advices anyway. Thanks

[RichCor]

<...> My main problem is we have Samsung Android portable devices around the house that sometimes take ages to get an external IP. Tried changing channels, no difference - everything on DHCP but still hold ups on Android. Don't get this at our other 3BB and True wifi hub locations we use with same devices. Only on TOT and TP Link.

Since WiFi is just an 'authenticated' wireless form of an Ethernet connection, the 'hold ups' are usually down to "Security Mode" and "Encryption", and then the internal DHCP Server (from where each device requests automatic configuration (IP Lease)).

On your router, try changing the "Security Mode" to WPA2/PSK (and don't use multiple WPA/WPA2). Could also try changing Encryption to AES (and don't use multiple TKIP/AES).

Signal interference will also cause problems establishing a link. Make sure the WiFi router antennas are at least 20cm away from any dense objects like walls or furniture.

[WorriedNoodle]

Since WiFi is just an 'authenticated' wireless form of an Ethernet connection, the 'hold ups' are usually down to "Security Mode" and "Encryption", and then the internal DHCP Server (from where each device requests automatic configuration (IP Lease)).

On your router, try changing the "Security Mode" to WPA2/PSK (and don't use multiple WPA/WPA2). Could also try changing Encryption to AES (and don't use multiple TKIP/AES).

Signal interference will also cause problems establishing a link. Make sure the WiFi router antennas are at least 20cm away from any dense objects like walls or furniture.

Interesting thanks. Taking your advice above, as I don't really understand it, I changed the security from WPA/PSK/WPA2/PSK to WPA2/PSK and the encryption from TKIP/AES to AES, but it made no difference. Even with the Android device held within arms length of the wifi antenna, whereas normally it is next room - it cannot always get an external IP without rebooting the TP-Link.

We have another network at another location using a Billion modem on True Online and that uses WPA/PSK/WPA2/PSK Security and TKIP/AES encryption and the same android devices connect without issues.

Ah well, will try further to understand the differences.

[RichCor]

<...>

Taking your advice above, as I don't really understand it, ...

<...>

The issue you're experiencing with the TP-Link router could be related with the WiFi portion or its DHCP Service feature.

WiFi devices sometimes have manufacturer compatibility issues, especially when multiple negotiation/authentication protocols are offered. By selecting only ONE Security Mode and Encryption we try to negate this as an issue during diagnosis.

In another topic post you found that some of your portable WiFi devices were causing issues with DHCP leased IP addresses (as the WiFi devices were converting previous 'leased' IP address into a 'static' IP addresses when using DNS entries other than those issued by the DHCP service).

Given this history, we can't be sure that something similar isn't still occurring that is messing with normal DHCP Service lease operations.

I shouldn't have to ask ...but will ask anyway: Are you running only the one TP-Link Router/Wifi, or do you have other WiFi routers, extenders, repeaters, etc on your network? Just trying to find out how many pieces are in play.

Moving on from WiFi establish/negotiation issues brings us to DHCP.

Are all the connecting device back to using DHCP autoconfig, or now have set 'static' IP addresses outside the DHCP IP pool address range?

When does the TP-Link router stop quickly giving out IP addresses after being powered back on?

Any 'odd' devices on your network that might be causing the Router's DHCP Service to lock up?

[WorriedNoodle]

Any 'odd' devices on your network that might be causing the Router's DHCP Service to lock up?

Thanks RichCor for some helpful advice as always. Yes, we have only one TP Link wifi router unit plugged straight in the phone wall jack and no other links/bridges in system.

Yes I mentioned on another thread about our Android devices not connecting and giving some conflicting IP addresses when we were trying to use DNS jumper apps to change the DNS on them, useful for watching global restricted content etc. Unfortunately with Adnroid whenever we changed the DNS it always changed from DHCP to Static IP address, as you said a limitation of Android. So we stopped all that, used DHCP and still had a problem making me wonder about this TP Link Router,

* Then your bottom line had me thinking again. (Thank you for that!). On the network also besides Win10 PC's and Android devices, we have a Smart TV which is using automatic IP - so no issues there we think. But also we have a WD Cloud Mirror NAS drive which on its admin logon page via a web browser on the network had been set at Static IP address outside pool range. When I changed this to DHCP on the WD admin page then the TP Link Router page seemed to include it in the list of attached devices whereas before it did not list it anywhere we could see, even tho the NAS worked. Now with DHCP on the NAS the other Android devices are all connecting OK or faster than before. So maybe problem solved.

** Why did we have NAS set to Static rather than DHCP? Well to log on WD NAS as admin we need to know its IP address to enter as a web browser URL, a nuisance if it keeps changing. Also mapping the NAS drive in Windows isn't so easy if IP address is changing. So far we'll put up with that new nuisance for regaining our ability to reconnect all our Android devices at least.

Edited October 8, 2015 by WorriedNoodle

[RichCor]

Any 'odd' devices on your network that might be causing the Router's DHCP Service to lock up?

<...> But also we have a WD Cloud Mirror NAS drive which on its admin logon page via a web browser on the network had been set at Static IP address outside pool range. When I changed this to DHCP on the WD admin page then the TP Link Router page seemed to include it in the list of attached devices whereas before it did not list it anywhere we could see, even tho the NAS worked. Now with DHCP on the NAS the other Android devices are all connecting OK or faster than before. So maybe problem solved.

** Why did we have NAS set to Static rather than DHCP? Well to log on WD NAS as admin we need to know its IP address to enter as a web browser URL, a nuisance if it keeps changing. Also mapping the NAS drive in Windows isn't so easy if IP address is changing. So far we'll put up with that new nuisance for regaining our ability to reconnect all our Android devices at least.

Switching your WD Cloud Mirror NAS drive from "Static" to "DHCP" and having your devices now get leased IPs OK may just be coincidence.

The real test would be switching it back to a 'Static IP" for a day.

We usually prefer to assign equipment that doesn't 'move' a static IP address because (1) it allows the equipment to go 'online' faster; (2) the equipment and their 'services' will always be at a known IP address. Sometimes a static IP isn't needed as the software will utilize 'host-name' or 'computer-name' rather than IP address when scanning the local LAN for compatible devices.

IF it is the WD Cloud Mirror NAS, see if there are any updates for it's firmware/software.

Try manually assigning it a different IP address (one that doesn't belong to the Router, and not inside the DHCP Pool).

IF you find your network only works well with the WD Cloud Mirror NAS set to DHCP, then your Router may offer a 'hybrid' way of issuing the same IP address only to one device by 'reserving' the IP address to work with a known MAC hardware address.

In webconfig look for:

*** OR ****

[WorriedNoodle]

Thanks for that idea RichCor. I have since tried to use the "Hybrid" method you suggest. On the TP-Link menu there is an option to assign either Static or Auto to each MAC address connecting to the router,

Therefore I set the NAS to Static.

* It then occurred to me why not set the entire list of devices we have to static on the router settings? Is there any drawback to this idea? I have done so for now and all of our portable Android devices now connect for time being. On the devices themselves (including the NAS) the network settings have been left as DHCP.

[RichCor]

^^ That is what it was designed for.

It allows your devices to be issue the same "Static" IP on your home network, but still automatically get dynamic IP assignments under DHCP when out and about on other networks.

Hope it works as intended for you.