Broadband connection keeps dropping

Emmzi

it's the wireless signal. I've disconnected everything else with a signal (hands free phones, mobiles, etc)

Ok.. how would one change the wireless channel???

espresso

You need to log in to the router by typing http://192.168.2.1 (or whatever it is for a Belkin) into your browser when connected using the Ethernet cable. Then go to the wireless page and choose a channel several channels away from what it is set to now i.e. if it's on 6, set to 1 or 11.

albertross_2

use this to find out what channels others are using, and avoid them

http://www.netstumbler.com/downloads/

When it drops next time.

Do

start, run, cmd

ping 192.168.2.1

if that fails, the issue is wireless, nothing to do with BT

have you encrypted the router?

Emmzi

This is my 'ping' results but I have no clue if they pass or fail! Interpreter please??

~~~~~~~~~~~~~~~~~~~~

Pinging 192.168.2.1 with 32 bytes of data:

Reply from 192.168.2.1: bytes=32 time=1ms TTL=128
Reply from 192.168.2.1: bytes=32 time=1ms TTL=128
Reply from 192.168.2.1: bytes=32 time=1ms TTL=128
Reply from 192.168.2.1: bytes=32 time=1ms TTL=128

Ping statistics for 192.168.2.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms

Emmzi

albertross wrote:

have you encrypted the router?

Does that mean you need a password to sign on to it? If so, yes. My mate who installed put on 64 Bit WEP, it says here...

albertross_2

Reply from 192.168.2.1: bytes=32 time=1ms TTL=128

that is working, you need to repeat this at the point it fails, if it comes up failed, the issue is your connection to the router, and not BT (Assuming that you are using a wireless connection, and not wired).

also try ping https://www.google.com, that will check the whole connection between you and google

WEP is encryption, not very strong, but better than nothing.

Emmzi

Thanks albert.

You guys save me a fortune on premium rate helplines

Emmzi

Ok.. pinging on lost connection gave same result.. and google was..

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Pinging google.com [72.14.207.99] with 32 bytes of data:

Reply from 72.14.207.99: bytes=32 time=123ms TTL=237
Reply from 72.14.207.99: bytes=32 time=117ms TTL=237
Reply from 72.14.207.99: bytes=32 time=111ms TTL=237
Reply from 72.14.207.99: bytes=32 time=113ms TTL=237

Ping statistics for 72.14.207.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 111ms, Maximum = 123ms, Average = 116ms

atnoble32

Apologies for the hijack, but i'm also having problems with a wired bt voyager 240 router and the bt call centre are no help, tried all the usual things, apart from moving pc to the main phone connection, so tried albertross's suggestion with the following results.

Pinging 192.168.2.1 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.2.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Pinging google.com [72.14.207.99] with 32 bytes of data:

Reply from 72.14.207.99: bytes=32 time=130ms TTL=234
Reply from 72.14.207.99: bytes=32 time=127ms TTL=234
Reply from 72.14.207.99: bytes=32 time=127ms TTL=234
Reply from 72.14.207.99: bytes=32 time=130ms TTL=234

Ping statistics for 72.14.207.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 127ms, Maximum = 130ms, Average = 128ms

albertross_2

atnoble,

The diagnostics were to diagnose if it is a wireless issue or not, and don't apply to wired really.. The 2.1 address is different from router to router, to find the one you need to ping

start, run, cmd

ipconfig

and ping the gateway address.