Can other users post their latest TBB Quality Monitor graph please?

[JamesAllen]

No-one can give you a definitive answer as long as you're loading the connection, James. If you talk to support, they'll either ask you to do what I'm suggesting or to boot into safe mode with networking support. Without knowing what processes are using the 'net on your machine, all anyone can do is give you a general answer.

True, but it can also help me to identify things on my own system that I need to pay attention to. As I said, a useful learning experience. I understand that from a support perspective everything has to be stripped down to be able to properly diagnose any issues at work - something I know very well from my own work in web programming etc.
I just meant that other people may be using their connections in a similar way and seeing the same type of graphs which at least would say - well that's perfectly normal. This data is not totally useless taking in isolation, especially not when backed up with information on how the connection is being used during those times etc.

[Rik]

Do we have that information, though, James?

[JamesAllen]

Do we have that information, though, James?

Well I did give a break down of the streaming I was doing etc that allowed esh to provide some useful things to consider. Which has provided me with some areas to look into etc.
The thing is, I had a failure last night during a broadcast which normally goes fine so thought it worthwhile to post the graph to get some feedback from people who may have seen similar results while using their connections in this way. If that was wrong or not worthwhile I apologise Rik.

[Rik]

It's not wrong, James. I just feel it would be useful to get a baseline graph for your line so that we can judge whether there's an inherent problem or a locally-generated one.

[JamesAllen]

It's not wrong, James. I just feel it would be useful to get a baseline graph for your line so that we can judge whether there's an inherent problem or a locally-generated one.

Ah don't get me wrong Rik, I do think that is a good idea. I'm going to see when I can arrange to minimise traffic on my network - I do have quite a few machines in play. Might start with shutting some of them down and only using one machine to at least see how that affects things, and also keep net activity right down. A total shutdown may not be possible for now but I can at least change some variables and observe the results.
Thanks again for the advice.

[Rik]

NP.

[davej99]

This thread has suggested there was a problem with packet loss caused by IDNET, rather than by Thinkbroadband monitoring, or BT, or the internet in general, or user equipment, setup and traffic.

I do not understand the technicalities and much of the evidence presented, so can I ask if there was a clear IDNET problem, what was the cause and if it is fixed?

[Steve]

I'm not sure we know Dave, The packet loss seemed to be restricted to Idnet users,an Idnet core router was suspected to be at fault but things seemed to resolve themselves a few hours prior to the planned reboot and as far as I'm aware all remains well.

[Bill]

This thread has suggested there was a problem with packet loss caused by IDNET

I think the packet loss was more of a symptom than the real problem- that appeared to be faulty routing causing some links to become overloaded.

As Rik said, for most people it seemed to clear up a few hours prior to the router reboot, but I have seen one user where it recurred just before the reboot so that "clear up" may have been coincidence.

We'll never really know for sure... comms is weird

[davej99]

Thanks, Steve and Bill, that seems like a very reasonable conclusion.

Some customers were concerned, IDNET had a look, they addressed a possible cause, the problem might have gone away on its own, it was probably work worth doing anyway, we are not sure of the real cause. I guess the jury is out and for sure, "Comms is weird."

Perhaps next time, though, we customers should be a little kinder to tech support and not rush to judgement too quickly.

[Rik]

I'm always kind to tech support, I give them a week off from my phone calls at least once a month.

[.Griff.]

This thread has suggested there was a problem with packet loss caused by IDNET

Did it? I don't see anyone pointing the finger directly at IDNET.

The thread was started by me with the intention of seeing if it was my connection specifically or multiple lines that exhibited the same symtoms.

I never mentioned IDNET as being the cause of the problem and I can't see anyone else stating that either.

Perhaps next time, though, we customers should be a little kinder to tech support and not rush to judgement too quickly.

Again.. What?

I don't see any anger at IDNET support or wild innacurate claims against them.

IDNET, via Simon, suggested a cause and how they'd rectify it. I, and others, thanked them for that and by whatever method the problem has so far disappeared.

I'm a bit baffled about how we should be kinder to tech support?!? Perhaps posts have been deleted I've not seen?!?

[davej99]

O wad some Power....

[.Griff.]

Makes sense now..

[davej99]

... the giftie gie us

[Technical Ben]

Perhaps it was that Coronal Ejection?
http://www.bbc.co.uk/news/science-environment-12493980

[.Griff.]

Either that or Tesco had a sale on Shandy.

[esh]

Without knowing what processes are using the 'net on your machine, all anyone can do is give you a general answer.

Just for the record, you can use Win 7 resource monitor to see what is using your bandwidth.

[.Griff.]

Just for the record, you can use Win 7 resource monitor to see what is using your bandwidth.

Doesn't the resource monitor shows network use (network bandwidth) rather than internet bandwidth though?

I guess you could use it as a good indicator if you only have one PC at home but if you have a small home network and transfer files between PC's then the resource monitor isn't going to accurately reflect your internet use.

[esh]

It should be completely obvious if a program is communicating over LAN as the target IP will most likely be a 192.168/16 address or other non-IANA address range.

[sobranie]

This looks a mess, comments please!!

[Bill]

This looks a mess, comments please!!

Yup, it's a mess

Looks like a call to support to me... and maybe a question to Jake over on tbb, I can't see where those downward spikes of yellow are coming from.

[joe]

What does this signify?  I don't appear to have any problems but that is not what the graph suggests!

[Rik]

It suggest to me that your router isn't responding to ICMP traffic.

[Bill]

Yup, classic result of "respond to WAN pings" not being turned on.