Cable Forum - View Single Post

General Maximus · 18-07-2014, 23:40

what qas is trying to ascertain is whether the shub is locking up and dropping all local connections (i.e. cutting off your pc/laptop etc) or whether it is stays up and running and your lan is ok and for some reason it is losing its "internet" connection.

Next time it happens open a command prompt (click start and type cmd) and type "ipconfig". If the ip address of your device comes back as something like 192.168.0.2 then you are still connected to the shub even if you don't have internet access. The next step is to ping the shub and from the command prompt type "ping 192.168.0.1" which is the ip address of the shub. If you can ping the shub try logging into it. Somewhere on a status page (don't know because mine is in modem mode) it will tell you what the wan ip address is (the ip address VM gives you). If it says anything other than something like 82.16.254.2 then you have lost your connection. You might also see some dodgy stats in the power levels table like only one channel's info being populated or a message like "unable to lock onto downstream". If the ip address looks ok then go back to your command prompt and type "tracert www.bbc.co.uk". This will send a ping to all the routers between you and the bbc routers and you can see where your connection is failing within VM's network.

Going back to the first step, if you do an ipconfig and your ip address comes back as something like 169.254.10.3 then you have lost your connection to the shub.

18-07-2014, 23:40	#6
General Maximus cf.mega poster Join Date: Nov 2008 Location: Lincoln Services: phone + 1gbit BB + SkyQ Posts: 11,021	Re: Superhub 2 keeps losing connection what qas is trying to ascertain is whether the shub is locking up and dropping all local connections (i.e. cutting off your pc/laptop etc) or whether it is stays up and running and your lan is ok and for some reason it is losing its "internet" connection. Next time it happens open a command prompt (click start and type cmd) and type "ipconfig". If the ip address of your device comes back as something like 192.168.0.2 then you are still connected to the shub even if you don't have internet access. The next step is to ping the shub and from the command prompt type "ping 192.168.0.1" which is the ip address of the shub. If you can ping the shub try logging into it. Somewhere on a status page (don't know because mine is in modem mode) it will tell you what the wan ip address is (the ip address VM gives you). If it says anything other than something like 82.16.254.2 then you have lost your connection. You might also see some dodgy stats in the power levels table like only one channel's info being populated or a message like "unable to lock onto downstream". If the ip address looks ok then go back to your command prompt and type "tracert www.bbc.co.uk". This will send a ping to all the routers between you and the bbc routers and you can see where your connection is failing within VM's network. Going back to the first step, if you do an ipconfig and your ip address comes back as something like 169.254.10.3 then you have lost your connection to the shub.