[DeadKenny]

Originally Posted by carlingman

Hi deadkenny,

You must win the award for perseverance with NTL as I recall a lot of your threads for the old days over at .com

Yeah, on and off I've been ready to throw in the towel often but it's the whole hassle of applying for BT that put me off and then it did kind of get fixed for a long while .

Maybe this will just be a temporary glitch as the upstream has settled down again.

However if you suspect packet loss what do the results of dos prompt below show.

Open up a dos prompt and type in netstat †“s †“p tcp

That should give you an idea of how many packets are being lost and having to be re transmitted to pin point the problem a little more.

TCP Statistics for IPv4

  Active Opens                        = 9071
  Passive Opens                       = 4412
  Failed Connection Attempts          = 51
  Reset Connections                   = 967
  Current Connections                 = 18
  Segments Received                   = 553585
  Segments Sent                       = 513853
  Segments Retransmitted              = 3957

Not sure if that's over a whole session (while PC is running?), though for the last few hours things have settled down since the upstream powered dropped down to 56.

Strange though as normally FEC Errors and packet loss are usually caused by poor downstream rather than fluctuauting upstream levels.

Im guessing from your knowledge you have it spot on though as fluctuating upstreams are normally a sign of a bad connection from you to the UBR or knackered AMP on their network.

Yeah, it's always been upstream problems with me, though before it was with the upstream not even locking on or dropping and rebooting. This time around it's kind of a guess but I'm told it's probably upstream, plus pure downloads seem unaffected whereas requests for pages are affected and so is any transfer from my server.