A Few Questions About IDnet Please

[Lance]

As you suggested, Dev, Seb or Rik will be along soon to comment. 

Aren't you forgetting someone, Simon!!! 

[DeViTTo]

Hi Dev,

From those stats, there is absolutely no reason for any disconnects. I can only suggest that either you experience massive (and they would have to be truely massive) bursts of noise which cause your noise margin to drop, or the disconnects are being caused by CPW.

One thing you could try doing is running a program called routerstats, which you can use to graph and log your noise margin.

Finally, I think most people use an MTU of 1500, although some fall back to 1458. Either way, the router should be left 'wide open' on 1500, with any adjustments being made from within windows.

Hope this helps!

The short wait will be over comeThursday i'll post then my results. Others are having same problem with CPW change they are all getting random disconnects. One person gave me the senario that 50000 say uses and 1 joins then one gets kicked off. i.e the network is at saturation and so the cycle continues, I don't know if this is the case but who cares i'll be on IDnet soon, but thanks Lance BTW I think Simon did forget you. 

[Sebby]

I'm wired not on wireless,no its since the forced switch from AOL to CPW it disconnects about 30-40 times a day in the router logs, has done about 5 times this evening. It was stable on AOL, but CPW sucks keeps allways disconnecting. It does it on the netgear to, so I know its a network issue. Soon all will be resolved.
I found out I'm not on StAustell exchange I'm actually on Lostwithiel which is 3.2km as crow flies with low usage at the exchange. So as you say the stats are good, not too many errors etc maybe I could be onto some good speeds. BTW Seb went for SuperMax because someone else has chipped in so going to give it a go.

If required and our usage proves we should be on lower package might rethink, but I'm online so much its cheaper than going to pub every night lol.

We need to establish whether the router is losing sync with the exchange or whether it's just disconnecting from the ISP. I'm not familiar with the Draytek; can you see anywhere that gives you any other time periods, other than the system uptime? Like I said, your stats do not suggest that you'd be experiencing disconnects from the exchange.

SuperMax is a great product and will do you well.

I forgot to mention MTU in my last post. It certainly wouldn't cause disconnects, so it's something we can dismiss for now.

[DeViTTo]

We need to establish whether the router is losing sync with the exchange or whether it's just disconnecting from the ISP. I'm not familiar with the Draytek; can you see anywhere that gives you any other time periods, other than the system uptime? Like I said, your stats do not suggest that you'd be experiencing disconnects from the exchange.

SuperMax is a great product and will do you well.

I forgot to mention MTU in my last post. It certainly wouldn't cause disconnects, so it's something we can dismiss for now.

The Netgear does the same don't worry Seb, I just hope it doesnt do it on IDnet. It only started about 15 days ago when the change happened. Like I said Thursday. I hope the SuperMax is I would love to get better results.

[Sebby]

Well if you can get anymore information from the router, it might help diagnose the problem, or wait until you're with IDNet and see if it still happens.

[Rik]

Hi Dev

What Sebby and Lance have said. Simon Davies recommends an MTU of 1500, Miriam goes with 1458. I've tried both and found no difference, so I leave things 'wide open' at 1500.

[Sebby]

There's also the ping method (as I believe is detailed in Rik's excellent FAQs), which is the "scientific" way of getting the best figure. For me, it turns out to be 1500 anyway.

[MoHux]

In XP with the MTU wide open at 1500, 'MTU Discovery' negotiates the optimum with the target server (they use different packet sizes to suit the job they are designed to do).  Any setting less than 1500 will suit some, but not all.

In Vista, the O/S negotiates the optimum MTU, and adjusts the RWindow size to suit automatically.
There is no point in trying to set either setting in Vista as they are not kept in the registry like XP.
Having said that, you can still of course adjust the router MTU/MRU, but the remarks for XP would then apply.

[Simon]

Aren't you forgetting someone, Simon!!! 

Sorry Lance! 

[DeViTTo]

Hi guys well I'm officially an IDnet user, came home entered my details and look what i got 

[madasahatter]

exceellleeent (in best Mr.Burns voice)

[DeViTTo]

exceellleeent (in best Mr.Burns voice)

Yep fantastic feels very snappy i'm pleased i wonder if it will get even better if i dont disconnect over next 10 days lol

[Inactive]

Brilliant, a warm welcome to happy land.

[Rik]

Hi Dev

Welcome and congratulations. How are your ping times? If you post your router stats, we can see if there's anything more to be squeezed from the line.

[DeViTTo]

Hi Dev

Welcome and congratulations. How are your ping times? If you post your router stats, we can see if there's anything more to be squeezed from the line.

Will do a little later, downstairs comp updating some software at min give it an hour ill post some sample trace routes etc ok.

[DeViTTo]

Hi Dev

Welcome and congratulations. How are your ping times? If you post your router stats, we can see if there's anything more to be squeezed from the line.

tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.251.203]
over a maximum of 30 hops:

  1    15 ms    16 ms    17 ms  telehouse-gw2-msdp.idnet.net [212.69.63.51]
  2    16 ms    15 ms    28 ms  telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243
]
  3    17 ms    18 ms    16 ms  rt-lonap-b.thdo.bbc.co.uk [193.203.5.91]
  4    19 ms    18 ms    30 ms  212.58.238.149
  5    20 ms    17 ms    15 ms  212.58.239.62
  6    19 ms    15 ms    15 ms  www3.telhc.bbc.co.uk [212.58.251.203]

Trace complete.

tracert www.westwood.com

Tracing route to napdhome.pogo.com [159.153.235.27]
over a maximum of 30 hops:

  1    15 ms   113 ms    15 ms  telehouse-gw2-msdp.idnet.net [212.69.63.51]
  2    16 ms    16 ms    15 ms  telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243
]
  3    17 ms    16 ms    15 ms  y-s-2.lon1.arbinet.net [213.232.64.76]
  4    18 ms    17 ms    18 ms  sl-bb21-lon-10-0-0.sprintlink.net [213.206.131.2
1]
  5    85 ms    87 ms    85 ms  sl-bb21-tuk-10-0.sprintlink.net [144.232.19.69]

  6    95 ms    89 ms    95 ms  sl-bb23-pen-13-0.sprintlink.net [144.232.20.138]

  7    89 ms    89 ms    90 ms  sl-bb22-pen-14-0.sprintlink.net [144.232.8.178]

  8    89 ms    89 ms    90 ms  sl-bb27-rly-3-0.sprintlink.net [144.232.18.186]

  9    90 ms    90 ms    91 ms  sl-bb23-rly-13-0.sprintlink.net [144.232.14.141]

10    95 ms    91 ms    92 ms  sl-bb21-dc-13-0-0.sprintlink.net [144.232.9.214]

11    90 ms    90 ms    91 ms  sl-st20-ash-11-0.sprintlink.net [144.232.20.150]

12    90 ms    89 ms    89 ms  144.223.246.6
13    89 ms    94 ms    89 ms  159.153.224.166
14    89 ms    89 ms    91 ms  eaocore01-eqx-iad.ea.com [159.153.224.90]
15    93 ms    90 ms    94 ms  www.ea.com [159.153.235.27]

Trace complete.

Tracing route to www.jolt.co.uk [82.133.85.65]
over a maximum of 30 hops:

  1    18 ms    15 ms    21 ms  telehouse-gw2-msdp.idnet.net [212.69.63.51]
  2    18 ms    19 ms    17 ms  telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243
]
  3    17 ms    17 ms    17 ms  g3-35-501.cr05.hx2.bb.pipex.net [193.203.5.14]
  4    48 ms    53 ms    54 ms  v3953.cr05.tn5.bb.pipex.net [62.72.137.29]
  5    18 ms    19 ms    16 ms  g1-1-6.ar01.tn5.bb.pipex.net [62.72.140.142]
  6    21 ms    25 ms    22 ms  ge-0-0-0-3801.jolt-gw.cust.pipex.net [212.241.24
1.14]
  7    16 ms    16 ms    19 ms  secure.jolt.co.uk [82.133.85.65]

Trace complete.

I did jolt because everyone wants to do that one although I dont use them, I dont like the spike at hop 4 with Pipex, but nothing to do with my connection or IDnet.

To say i'm happy but I would like to get my profile and see if during training it gets even better.

[Rik]

Only one way, Dev, persuade the BT tester to cough it up (which it will sometimes do even if it fails to complete the test).

[DeViTTo]

i'm going to try it now and see, but its busy.

[Rik]

How do you feel about getting up in 11 hours then? 

[DeViTTo]

How do you feel about getting up in 11 hours then? 

I know its allways busy, but will my profile be higher do you think, or will it go higher in 10 days time after training etc?

[Rik]

I can only guess, Dev, which won't help you much. It depends on line stability and where the profile is now.

[RA-1972]

Mine has gone up loads since training has finished plus a little work on my internal wireing . this is mine now it stared in the 2 mb bracket .

  IP profile for your line is - 6500 kbps
    DSL connection rate: 448 kbps(UP-STREAM)  7616 kbps(DOWN-STREAM)
    Actual IP throughput achieved during the test was - 6074 kbps

If you wish to discuss these results please contact your ISP.

If you are experiencing problems with specific applications, servers or websites please contact your ISP for assistance.

Your test has completed please close this window to exit the performance tester.

[RA-1972]

Rik you are so quick with replys cant keep up with you . I do suppose you do have over 29k post.

[DeViTTo]

Thanks for the welcome guys it's nice to be in Happy Land lol.

Iv'e been quite a few ISP and to be honest the CPW was the worst others were ok for amount I paid.

I'll try for the speedcheck and i'll get back to you.

[Rik]

Rik you are so quick with replys cant keep up with you . I do suppose you do have over 29k post.

I'm so quick I can't always keep up with me.