Unable to join network

[Anonymous]

I was working on my iPad connecting wirelessly via my router. Suddenly the connection died. I tried to reconnect without success. I reset the network settings and when I hit "join" I keep getting the message "unable to join the network". I am unable to connect wirelessly using my router on any of my devices. Is this a problem with o2? Their lines are now closed so I can't speak with them over the phone. Is anyone else having this problem?

[Liquid]

Try resetting the router first then get back to us.

I presume your Internet is fine otherwise?

[jonsie]

It's either a problem with your ISP or your router. Is the phone line ok? If it's a broadband problem your provider should be open 24/7.

[Anonymous]

Reset the router or turn it on & off again, reboot your phone, input your network key exactly as it is written eg caps or lower case

[perksie]

If it's an O2 Box, it could have changed channel, you can turn this off in Network settings.

http://www.o2help.co.uk/router-wireless-channel/

Some phones won't connect above channel 11.

[Anonymous]

Thanks all. You've answered my question, I needed to know if this was an O2 issue or related particularly to my router. It looks like it's my router. When I get home I would do as suggested. Thanks again.

[perksie]

Please let us know if that helps.

Auto channel selection can be a source of problems, and a router can't be trusted to choose the best one.

I always used channel 13 but can't any more as my new phone won't see it.

[Anonymous]

Hey Perksie,

For some reason, my router decided to change the encryption settings from WEP to WPA. I had changed the channel previously to 8 having tried a variety of others and found the connection speed to be either very slow or erratic. Thanks to everybody for your suggestions, I knew coming here was the right thing to do 🙂

[perksie]

Glad to help, the encryption can also be set to WPA+WPA2 so more devices can connect.

WEP isn't very strong against wireless attacks.

You may have had a router firmware update which could have been the cause of the changes.

If that has sorted it please mark the thread as solved.