- Mar 22, 2014
- 9
- 0
- 4,510
Setup: I have a TP-Link TL-WA801ND wireless access point connected via ethernet and Belkin powerline adapters to my router, a Netgear Nighthawk AC1900 model R7000. This is being fed by my ISP's modem/router which I turned into just being a modem. The router broadcasts a wireless network at the front of the apartment and the AP broadcasts a different network at the back of the apartment with a different SSID. The AP has a static IP. DHCP is disabled on the AP and is handled by the router. Router IP is 10.0.0.1, AP IP is 10.0.0.200, subnet mask is 255.255.255.0. I've had the access point for three days. Firmware on router and AP are up to date.
Problem: Devices connecting to the AP network don't always get access to the internet and the devices (android phones, a Windows 10 desktop and two Windows 7 laptops) get stuck at "Obtaining IP Address..." with the android devices, "Connected, no internet" with Windows 10, and "Identifying..." with Windows 7. With the android devices, sometimes they show "obtaining IP address..." for a few seconds then give up trying to access. There appears to be no chronological pattern as to when the devices will or will not be able to access the internet. Sometimes they can, sometimes they can and then get disconnected, sometimes they can't from the moment of booting the machine or entering the network area. Some devices can access the AP network whilst, simultaneously, other devices can't access the network. The AP network is always visible. When it works you can access both the router's admin software and the AP's admin software using the same device by pointing a browser at the IP addresses, and you can see all currently connected devices on both networks listed in the router admin software. Both Belkin Powerline devices always report a healthy signal and communication level. Up until this afternoon I had the AP IP being determined by DHCP - I gave it a static IP hoping it would fix the issue, but it appears to have not.
An obvious potential weak link is the Powerline, but I've used the units in different properties with no issues so I trust their status reports. Could it be an issue with the way the AP and the router are talking to each other? The fact that some devices can access it at the same time as other's not being able to is really throwing me.
What is going on? Is there anything obvious that I'm missing? Apologies for the wall of text, wanted to be thorough!
Problem: Devices connecting to the AP network don't always get access to the internet and the devices (android phones, a Windows 10 desktop and two Windows 7 laptops) get stuck at "Obtaining IP Address..." with the android devices, "Connected, no internet" with Windows 10, and "Identifying..." with Windows 7. With the android devices, sometimes they show "obtaining IP address..." for a few seconds then give up trying to access. There appears to be no chronological pattern as to when the devices will or will not be able to access the internet. Sometimes they can, sometimes they can and then get disconnected, sometimes they can't from the moment of booting the machine or entering the network area. Some devices can access the AP network whilst, simultaneously, other devices can't access the network. The AP network is always visible. When it works you can access both the router's admin software and the AP's admin software using the same device by pointing a browser at the IP addresses, and you can see all currently connected devices on both networks listed in the router admin software. Both Belkin Powerline devices always report a healthy signal and communication level. Up until this afternoon I had the AP IP being determined by DHCP - I gave it a static IP hoping it would fix the issue, but it appears to have not.
An obvious potential weak link is the Powerline, but I've used the units in different properties with no issues so I trust their status reports. Could it be an issue with the way the AP and the router are talking to each other? The fact that some devices can access it at the same time as other's not being able to is really throwing me.
What is going on? Is there anything obvious that I'm missing? Apologies for the wall of text, wanted to be thorough!
Facebook
Twitter
Instagram