Problems with wireless dissapearing
 

Hi There,


Just arranged a 50mb mates rates upgrade for my parents and seem to be experiencing some strange problems with the wireless.


The majority of the pc's are all cabled in and appear to be working properly but i have configured the superhub for wireless and its just not working properly. im using it on 2.4ghz on channel 11 and my pc keeps losing the wireless signal. encryption is WPA2 Personal, timeouts, It seems to ve a range issue. Pings between my laptop and router on 192.168.0.1 appear to be timing out. My parents live in a modest 3 bedroom terraced property, If im in the room with the router i get solid responses, However move too the room next door or downstairs and i get timeouts. Any suggestions?, I have the same superhub myself but i dont use the superhub in my home, I have a separate netgear that i use for wireless.

C:\Users\Rich>ping -t 192.168.0.1

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=87ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=5ms TTL=64
Reply from 192.168.0.1: bytes=32 time=173ms TTL=64
Request timed out.
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Request timed out.
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=4ms TTL=64
Reply from 192.168.0.1: bytes=32 time=6ms TTL=64
Reply from 192.168.0.1: bytes=32 time=8ms TTL=64
Reply from 192.168.0.1: bytes=32 time=7ms TTL=64
Request timed out.
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.0.1:
Packets: Sent = 119, Received = 108, Lost = 11 (9% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 173ms, Average = 3ms
Control-C
^C
C:\Users\Rich>

Re: Problems with wireless dissapearing
 

Use the dongle and go to 5ghz mode might help

Re: Problems with wireless dissapearing
 

use a channel below 9

Re: Problems with wireless dissapearing
 

try setting the 802.11 mode to 'up to 145mbps'

Re: Problems with wireless dissapearing
 

Get them a router.

Re: Problems with wireless dissapearing
 

Thanks for the suggestion guys. Will try these suggestions next time im up there. all the best.

Re: Problems with wireless dissapearing
 

Try a channel below 9 or possibly leave it on auto?

Also change the wireless mode to up to 145Mbps.

Re: Problems with wireless dissapearing
 

lol, do you know what, as soon as i saw the title for this thread I knew it was going to be about the pooperhub

Re: Problems with wireless dissapearing
 

Is this a known problem with the Superhub?

I've kept our Router on channel 11 for years - and the Superhub in the last month or so, but the last few days (possibly since the R25 update?) it's become unreliable.

Re: Problems with wireless dissapearing
 

yeah, if you have a look around the forum you'll see tonnes of posts with exactly the same issue and the same solution to fix the problem

Re: Problems with wireless dissapearing
 

You have answered your own question here.

I had to post this as I was told I was not very helpful with my last one. Perhaps VM will be more helpful with supplying better kit in trhe future.

Re: Problems with wireless dissapearing
 

Everything seemed to be ok when I changed the channel to 9 after it was recommended in the above posts (although the signal strength isn't anywhere near as good as it is on Channel 11), but since R26 the wireless seems to stop working after a short time.

A reboot of the "Superhub" or restarting the wireless through the web interface makes it work again for a while, but it's very annoying.

Does anyone have any idea what could be happening?

Re: Problems with wireless dissapearing
 

Try changing the DCHP lease time, just stick an extra 0 on it.

Re: Problems with wireless dissapearing
 

Thanks.

I've given that a go.

I've also put the wireless channel to "AUTO".

Re: Problems with wireless dissapearing
 

Auto channel select does not seem to be a good option for the superhub. Use InSSider to see what other wireless channels may be interfering with your signal and select a channel accordingly.

Re: Problems with wireless dissapearing
 

My Superhub has been on Auto since day one and works fine.

Re: Problems with wireless dissapearing
 

Same with mine, and in fact my mate who was having wireless issues with the Superhub, had it set on a particular channel after advice from someone. I told him to change it to auto and his wireless has been prefectly fine since.

Re: Problems with wireless dissapearing
 

Don't forget that interference may not be Wifi related - some cordless phones, bluetooth, wireless video senders, etc. all use the same frequencies.

It is possible to get little USB devices (spectrum analysers) to check for interference, but it may just be easier to try different channels. Don't forget that the channels overlap.

Also, it may not be interference. In the past I've had problems on a laptop where disabling the "allow this device to be put to sleep when not in use" (or whatever it's called) checkbox has cured a similar problem.

If you need a stand-alone wifi access point, I can't recommend the Apple airport extreme enough, although it is a little on the expensive side.

Re: Problems with wireless dissapearing
 

Re: Problems with wireless dissapearing
 

For just one use, certainly not. Unless you think they're really cool, of course.

Re: Problems with wireless dissapearing
 

I get 3 bars auto or 4 on channel 1