TL-WR1042N Wireless Router - Connection Refused Web Interface

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

TL-WR1042N Wireless Router - Connection Refused Web Interface

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
TL-WR1042N Wireless Router - Connection Refused Web Interface
TL-WR1042N Wireless Router - Connection Refused Web Interface
2015-11-03 09:24:45
Model :

Hardware Version : Not Clear

Firmware Version :

ISP :

Hi all, new here and hoping to get some assistance! :)

Basically there is a large house with 16 bedrooms, thick walls etc. So my friend has gone out and purchased some TL-WR1042N Wireless Routers thinking they would work for WiFi coverage.

I thought it should not be a problem as we can just enable WiFi on them and not make use of the WAN ports.

So here is what has been done:

- Access points are connected to the LAN via the LAN1 port and they are connected to a gigabit unmanaged switch.
- Each AP has had DHCP switched OFF.
- Each AP has been given a different SSID and password to make it easier to know the location.
- Each AP is set to a different channel, there is very little overlap in terms of coverage anyway.
- All devices from the switch connect to the main router acting as a Gateway.

Issue is that people are complaining that they are loosing connection, they apparently remain connected to the WiFi but the connection drops and then comes back. - This has all happened over the weekend.

- Internet has been checked and the connection is not dropping at all. All devices seem stable, router responds to internal and external pings.
- Router is responsible for DHCP, each TP-Link AP has a static IP set outside of the DHCP scope.

Basically I have remoted on today and discovered the above and since everything else responds I assume the TP-Link routers may be at fault.
When I try to load the webpage for them I get CONNECTION REFUSED in google chrome. They all still respond to pings internally.

They are all displaying the same message! I rebooted them and they are working fine again, i can connect to them and all is working!

I have disabled the SPI firewall on one of them incase this is causing the issue. They are part of the internal network so no firewall is needed on them really, they are only being used as access points.

Does anyone else know what could be causing this?
I did try to get into the logs, but after a rebooted the previous logs are wiped. I cannot have the logs email automatically because it keeps telling me it cannot connect to the mail server- I assume this is because it is looking to it's own WAN address and there is nothing plugged into that.

I am concerned it is going to happen again, any ideas on this one?

Thanks in advance! :)
  0      
  0      
#1
Options