UKVoIPTalk.com

"JakeD" <JakeD@jdjdjvvdjdjdj.com> wrote in message
news:gvmqe3hj5sph6jlt3n8pc6gpl23nk4t1ru@4ax.com...[color=blue]
> On Sun, 16 Sep 2007 17:10:40 +0100, JakeD <JakeD@jdjdjvvdjdjdj.com>
> wrote:
>[color=green]
>>PS. Today, during one of the breaks in my bradband connection, I
>>disconnected the loud bell from the BT master socket. This made no
>>difference; I still could not conect to the net.
>>
>>When the new master socket arrives, I'll try replacing the face plate.[/color]
>
> PPS
> During a period of OK-connection, with my adsl filter plugged into the
> hidden socket behind the master socket's face plate, I did a speed
> test today, at:
>
> [url]http://www.speedtest.bbmax.co.uk/[/url]
>
> The results were:
> 971 kbps download speed
> 243 kbps upload speed
>
> Does this indicate anything?
>
> Thanks,
>
> Jake D
>[/color]


Hi Jake,


I have been mulling on this.

I think we are pretty much at where we had got to with all this. Shortly,
you should be able to eliminate all possibilities on your side (assuming -
lol - you have done the full monty of my suggestions to the letter - i.e.
verifying your ADSL kit and its cables and filters and and, etc. , your
computer, etc. - where verifying means checking your kit somewhere else to
see that a known good connection at another place continues to work with
your kit; and equally using someone else's known good kit at your place to
see if their kit also fails with your connection / line, etc.)... (p.s. some
of that may be a bit of the top - but not really / not in reality!)..
(particularly after you have replaced the master socket) at which juncture
this ball is more firmly in either your ISPs court (something wrong on their
side - e.g. / i.e. their line card if you're LLU with Talk Talk, or their
modem bank, or some other such on their side) or BT Open Reach's court
(something wrong with the line, etc.).

Hope this helps.

Otherwise - your connection speeds / throughput seem nice. I think the real
question though is "packet loss"... i.e. when your connection is working are
you suffering a lot of frequent noise / errors on the line - i.e. data
having to be resent because it got lost / corrupted due to noise / a bad
connection, etc. Their are various ways you can test this... the easiest
would be either one of the online programs or free programs, else you can do
it with Windows itself - just not quite so exciting, fun or user friendly.
Go to "Start" button -> choose Run -> type "command" -> in the black text
window that comes up type "ping -t www.bbc.co.uk" . This will keep testing
the connection to, in this case [url]www.bbc.co.uk[/url], until you tell it to stop.
You can press CTRL + BREAK (on the "Pause" key - usually top right of the
keyboard, near Scroll Lock and Print Screen) - this will give you a live
update on the statistics without interrupting the test. Or when you want to
stop the test press CTRL + C . This will stop the test and give the final
results.

What you are interested in is the "Lost" count.. should really be 0% or
maybe very very low i.e. 1% or less. Equally, you can look at the pattern of
speeds for each data packets as it when to the bbc .... watch as it scrolls
past and look at the time = bit... in ms... It should be fairly steady or
constant. If it is fluctuating a lot (>10/20%) and regularly... this may be
another issue...

Let us know what you discover and how you get on, etc. !


Best wishes,



News Reader

P.s. The packet loss tests, etc. are a bit superfluous really because you
are suffering a serious connection problem - i.e. complete loss of sync /
disconnection. Hence, their is a more major or real and serious problem
either with your hardware, their hardware or the configuration, etc. (Hence
why your genuine and full complete fault testing of your own hardware, etc.
is probably so necessary / more important).

P.p.s. You can test your connection to any address - doesn't have to be the
bbc - just enter the address you want to test. E.g. [url]www.yahoo.com[/url] ;
[url]www.nasa.gov[/url] ; [url]www.sega.co.jp[/url] ; [url]www.bmw.de[/url] ; etc. Also normally ping testing
is done with out the " -t " bit which just tells the computer to keep
checking until you tell it to stop. The standard version of a ping test is
to test 3 or 4 times and give you the average results - feel free to try it
(i.e. without the " -t " bit) - it is just in this case we are acutely
trying to test packet loss (and a known or specific problem scenario) rather
than latency (how long it takes a data packet to get to a destination) (or
just a general test / general interest test of an otherwise expected or
known to be working normally connection) so lots of tests rather than just 3
or 4 is more useful / necessary, etc. And whilst we are at it, the other one
you might like is tracert. Same as above... but instead of typing ping type
"tracert www.bbc.co.uk" ... you don't need any other bits (like -t, etc.).
This will test the whole route, every step, and three times for each step,
anything not working or a lost packet will come up as a * . Again, you
should not have packet loss ( * 's ) and times should be fairly consistent,
no big differences on the same line (or THAT big between lines - depends,
e.g. if tracing the route to NASA in America one of the lines will be a leap
across the Atlantic ocean so you expect a good 20 / 30 ms leap between lines
their!). Equally, some hosts (bbc, yahoo, etc.) do not allow ping tests
(which is all traceroute is a fancy version of really), and so will only
show *'s or 100% packet loss (i.e. they are probably firewalled and refusing
to acknowledge your or reply). Likewise with traceroute, you may find some
hops on the list refuse to reply so for that line you may get all *'s ... or
if your final destination is firewalled / not replying.. you will get all
*'s... and it will keep on trying so press CTRL+C to stop it if you are sure
it has reached the end host and the end host is not replying., etc. You will
get the hang of it / the idea. Finally, for courtesy's sake, some people see
excess pinging as a bit like spam, or attacking. The odd handful of a few
pings is fine, and people like the bbc don't mind at all - it is all part of
useful network testing and diagnostics, but for the record / completeness
whatever I am just letting you know that some people don't like it -
basically it is fine and a normal, sensible and necessary part of the
internet, but don't go to crazy pinging the living xyz out of your neighbour
for example ;) or the military (not that I suppose they will really mind /
care - but still). :)

"News Reader" <no@email.invalid> wrote in message
news:Y2cIi.32172$ka7.23251@newsfe4-gui.ntli.net...[color=blue]
>
> "JakeD" <JakeD@jdjdjvvdjdjdj.com> wrote in message
> news:gvmqe3hj5sph6jlt3n8pc6gpl23nk4t1ru@4ax.com...[color=green]
>> On Sun, 16 Sep 2007 17:10:40 +0100, JakeD <JakeD@jdjdjvvdjdjdj.com>
>> wrote:
>>[color=darkred]
>>>PS. Today, during one of the breaks in my bradband connection, I
>>>disconnected the loud bell from the BT master socket. This made no
>>>difference; I still could not conect to the net.
>>>
>>>When the new master socket arrives, I'll try replacing the face plate.[/color][/color][/color]


< SNIP > useful network testing and diagnostics, but for the record /
completeness[color=blue]
> whatever I am just letting you know that some people don't like it -
> basically it is fine and a normal, sensible and necessary part of the
> internet, but don't go to crazy pinging the living xyz out of your
> neighbour for example ;) or the military (not that I suppose they will
> really mind / care - but still). :)
>
>
>
>[/color]


By the way...

For completeness...


The black text window is called a command prompt. I told you to open it
using "command", that was because I don't know what version of Windows you
are using, and that should work with most versions, however you can use
"cmd" if you have a newer version of windows and it should be a slightly
more feature rich version (not that you will be able to tell very easily
:) ).

Further, the correct way to end a command prompt session is to type "exit"
at the... lol - funnily enough... command prompt, and the session / window
will close. :) .. Failing that just hit the "X" in the top right - lol.
Usually a good idea to and standard practise to bang CTRL+C or CTRL+BREAK a
few times if you get stuck with something in a command prompt window (it
means cancel or abort) and short return you to the command prompt where you
can try something else or type "exit" to finish.

All the bits in "quotes" are to be typed exactly as they appear within the
quotes but without typing the quotes ;) .


Best wishes,



News Reader