Results 11 to 15 of 15
This is a discussion on 192.168.0.1 within the Sky Router forums, part of the Sky Broadband help category; just spent 40 mins on the phone waiting for techinical support and the guy advised me that they would have ...
- 16-09-06, 02:42 PM #11
just spent 40 mins on the phone waiting for techinical support and the guy advised me that they would have to do tests on the line as there are no active connections
as i advised him that the router as gone kack up stream as this was why i could not access it under the 192.168.0.1
he thought he knows besyt and said no thats because there is no adsl line
but the adsl line is on the fornt of my box i replied
oh well someone will call u back in 24 - 48 hours was his reply
- 16-09-06, 06:28 PM #12
Sorry if this has already been suggested, but I resolved this by going into the NetGear config screens (after resetting the box and my PC) via 192.168.0.1 and disabling UPnP - as suggested in another forum thread.
This gave me a continuous connection, and I could then go in and tweak other settings in the box to get my wireless going, etc.
- 16-09-06, 06:33 PM #13
When I've had problems on the net I've always been able to access the router page.
- 16-09-06, 08:20 PM #14
Have you tried http://192.168.0.1 or just the numbers?Service recovery 02392 899292
You got 3 right!
D'oh! Not good, dude.
- 16-09-06, 10:12 PM #15
This is exactly the behaviour that I had with my router in the first 3 weeks on Sky BB. My connection to the internet would seemingly break and would not be able to surf or even access the router config (192.168.0.1). Each time I would have to reboot the router and wait for a fair few minutes for it to get an IP address.
I spoke to Sky tech support and they suggested faulty router. 3 weeks later and everything has stabalized (only 1 dropout in past week). Sky eventually sent me a replacement router, but I have yet to take it out of the box. Also, I have not made any changes whatsoever to my PC's config, software or hardware in the past few weeks.
This means [for me] that something that is out of my hands is to blame - the connection, line, exchange, whatever. At least I now know that it was nothing that I did wrong and it was nothing to do with my setup.