Wifi connects but then disconnects

Forums › LAN (ethernet/Wifi/routers/Bluetooth) › Wifi connects but then disconnects

andywhitenz

17 posts

Geek

#171636 25-Apr-2015 20:42

Looking for some assistance with my router - can't work out what's going on.

My wifi router is playing up. When I turn it off and on again everything works fine - devices can connect to it and the internet works. But that only lasts about two minutes, then I lose the connection on any wireless device and when I try to re-connect I get a timeout/'unable to join' message.

The wifi signal is always there, and the internet connection is always working (I'm writing this on a computer that is wired to the router).

Any advice would be much appreciated.

Jase2985

13513 posts

Uber Geek
+1 received by user: 5942

ID Verified

Lifetime subscriber

#1291514 25-Apr-2015 20:50

sorry to ask a super obvious question but what device are you using?

andywhitenz

17 posts

Geek

#1291518 25-Apr-2015 21:00

Sorry, something I clearly should have put in the original post!

It's a D-Link DSL-2730B. I've had it for a while and it's worked fine until very recently.

webwat

2036 posts

Uber Geek
+1 received by user: 145

Trusted

#1291577 26-Apr-2015 00:19

Might be getting old? Save the settings, reset to factory default, reload the settings. See if it helps

Time to find a new industry!

linw

2865 posts

Uber Geek
+1 received by user: 1169

#1291593 26-Apr-2015 07:50

Might be worth checking inside. Had a look in a faulty switch the other day and found two swelled up electrolytics that were causing the problems.

pdath

253 posts

Ultimate Geek
+1 received by user: 116

#1292333 27-Apr-2015 16:57

andywhitenz: Looking for some assistance with my router - can't work out what's going on.

My wifi router is playing up. When I turn it off and on again everything works fine - devices can connect to it and the internet works. But that only lasts about two minutes, then I lose the connection on any wireless device and when I try to re-connect I get a timeout/'unable to join' message.

The wifi signal is always there, and the internet connection is always working (I'm writing this on a computer that is wired to the router).

Any advice would be much appreciated.

A really common problem that causes this is when the access point and client device have an error negotiating power saving settings (aka, software bug in one of the two). Try disabling any power saving options on your client device. The hint that this is a likely cause is when you say you have to turn it off and back on again, which resets the power saving levels negotiated.

Another [less likely] thing that causes this in the 2.4Ghz band can be bluetooth. Bluetooth also uses 2.4Ghz. Do you have any Bluetooth devices attached to your machine (mouse, keyboard, speakers, headphones, etc)? if you have bluetooth on your machine, try disabling it for a short while to see if it makes any difference.

Try my latest project, a Cisco type 5 enable secret password cracker written in javascript!

Kiwifruta

1423 posts

Uber Geek
+1 received by user: 336

ID Verified

#1292358 27-Apr-2015 17:51

andywhitenz: Looking for some assistance with my router - can't work out what's going on.

My wifi router is playing up. When I turn it off and on again everything works fine - devices can connect to it and the internet works. But that only lasts about two minutes, then I lose the connection on any wireless device and when I try to re-connect I get a timeout/'unable to join' message.

The wifi signal is always there, and the internet connection is always working (I'm writing this on a computer that is wired to the router).

Any advice would be much appreciated.

Possibly someone else is using the same channel as you. check using wifi analyzer on android or vistumbler on windows.

best of luck

andywhitenz

17 posts

Geek

#1292741 28-Apr-2015 09:38

Thanks everyone for the advice - much appreciated.

I tried various things including your suggestions and in the end a good old restore factory settings job seems to have done the trick (the second time I did it, anyway). Really not sure what the problem was but hopefully it's resolved now.