A Few Questions About IDnet Please

[DeViTTo]

I'm slightly puzzled, Dev. I saw the Vigor and said "Draytek" in my mind. AFAIK, Vigor is a Draytek brand name, not D-Link.

I use a Draytek Vigor ADSL2 modem with a cable Dlink DIR655 Router, find it performs great with draft N and Gigabyte switch. It passes the IP staright to the DIR655 transparent allows me to use cable modem.

[Rik]

In which case, the chipset in the Draytek is the one to concern yourself with, as it's the communication with the DSLAM that counts.

[DeViTTo]

In which case, the chipset in the Draytek is the one to concern yourself with, as it's the communication with the DSLAM that counts.

But it was disconnecting with the Netgear also. Do you think it is just training on the line for 10 days, aren't I supposed to get disconnets a bit?

[Rik]

You will get some sync drops during training as the line management software works out how fast your line can go. However, iirc, the Netgear and Draytek both use the same chipset on the modem side, so the random disconnection problem applies to both. I did move from a Vigor 2600+ to a Netgear on moving to Max, I found the Draytek was great at fixed speed, but much less stable at Max.

[DeViTTo]

You will get some sync drops during training as the line management software works out how fast your line can go. However, iirc, the Netgear and Draytek both use the same chipset on the modem side, so the random disconnection problem applies to both. I did move from a Vigor 2600+ to a Netgear on moving to Max, I found the Draytek was great at fixed speed, but much less stable at Max.

Hmm I'll have to wait and see then I like this combo it usually works a treat, Thanks Rik.

[Rik]

I think the key is to let the system settle for a while, Dev. Once you've got through training, there may be tweaks to be applied, but if you fiddle too much now, you are likely to confused the BT software into thinking the line is unstable.

[DeViTTo]

I think the key is to let the system settle for a while, Dev. Once you've got through training, there may be tweaks to be applied, but if you fiddle too much now, you are likely to confused the BT software into thinking the line is unstable.

Ok i'm not doing anything else my thooughts as well just want to remain connected for the min and hope my profile will change back to its original spec. If it doesnt and I get stability back from my end not BT can I request the profile change back? Or have I mucked it up with the disconnects I have been getting?

[Rik]

The profile should recover automatically if you maintain a stable sync, Dev.

[DeViTTo]

The profile should recover automatically if you maintain a stable sync, Dev.

K 

[DeViTTo]

The profile should recover automatically if you maintain a stable sync, Dev.

Had a few disconnects at weekend, my speed is droping each time now about 3mb and my ping is not as good. Have spoken to IDnet who are raising a ticket with BT as I have tried two routers and tried it on different sockets in the house checked all the wiring and even changed some of the older filters.

I'm worried as my profile will not recover if teh line disconnects all the time.

[Rik]

It won't, Dev, but if IDNet have raised it with BT, the cause of the problem should be resolved and things will then stabilise and recover.

[Sebby]

I'm worried as my profile will not recover if teh line disconnects all the time.

Correct, which is why it's important to get to the bottom of the problem so that your connection is stable.

[DeViTTo]

Correct, which is why it's important to get to the bottom of the problem so that your connection is stable.

Spoke to Andrew on phone, he arranged BT call. BT say there is something wrong with the line. I have tried 3 routers now my usual setup Draytek Vigor + Dlink 655 a Netgear DG834N and a Nokia IP55 (webramp) although I will be trying to test it on this again as I didn't have enough time. I don't think they are AR chipset.

My only worry is that BT don't find a fault on the line, and charge me the call out fee. I have checked all telephone sockets again tonight nothing is wrong with any of them that I can see. I had the same Line readings from what I think is the main faceplate and the ext one I use.

All I know is my speed is dropping, but my connection seems to disconnect less when in use, but disconnects quite often whilst no one is using the line. It was 95% stable on AOL, then the switch to CPW it disconnected all the time then and now its half stable.

I hope they do find the fault, but not at this end as I seem to have exhausted all other possibilities. I'm going to try plugging a phone in up here and dial that test number (cant remmember what it is for quite line) and see if there is any noise. There isn't on the other lines and as the readings are the same from all sockets it should be OK here, but ill make sure anyways.

[Rik]

The number you want is 17070, Dev, option 2. If BT are saying there is something wrong with the line, I don't see how you could incur a charge.

[DeViTTo]

The number you want is 17070, Dev, option 2. If BT are saying there is something wrong with the line, I don't see how you could incur a charge.

Thanks Rik, but the problem could be in house, would be just my luck , but I have checked everything.

[Rik]

It could be, Dev, but if you don't have an NTE5, there's no way to eliminate that - as I found out...

[DeViTTo]

It could be, Dev, but if you don't have an NTE5, there's no way to eliminate that - as I found out...

I have just tested the line all is quite, but i can detect a tic sound every .5 secs thats all. Any thouhts very faint.

[Rik]

Probably just background noise - I've never heard a line that was totally quiet, but then I've never known whether the phone I was using was perfectly quiet either.

[DeViTTo]

Probably just background noise - I've never heard a line that was totally quiet, but then I've never known whether the phone I was using was perfectly quiet either.

Sounds electrical as its not random but its faint, i have good hearing and I'm a bit paranoid when I could be facing a bill like I know they could charge what is it about £140 + VAT. Andrew said they detected a fault, but unless you have the right equipment apart from line stats which should give a reasonable picture then what can you do.

I have the same line stats here and at the main socket, both routers disconnect randomly I have to leave it BT with the test equipment they have.

[Rik]

If you don't have an NTE5, Dev, you reach a point where you have to take the chance (or put up with the problem ). Most engineers will fit an NTE5 as a first step, and test from there. Be around if you can and ply him/her with tea and biccies, it really does help.

[DeViTTo]

If you don't have an NTE5, Dev, you reach a point where you have to take the chance (or put up with the problem ). Most engineers will fit an NTE5 as a first step, and test from there. Be around if you can and ply him/her with tea and biccies, it really does help.

I've taken the day off, thats exactly my thoughts lol.  thanks Rik, I think it's important I be there.

[Sebby]

I think even if they did charge you, you could argue that there was no way to prove it was something on your side as you didn't have an NTE5. Good luck!

[Rik]

It didn't work for me, Sebby.

[DeViTTo]

I'm still having radom disconnects I actually found out my direct server IP address I play on. I'm just lagging a lot tonight, since my line has been active my ping to www.bbc.co.uk has gone from 14ms seen in thread earlier to.

Could someone please tracert the 74.53.34.194 ip address, so that I can see what a good connection is returning on this address. I'm timing out alltogether part way through the hops?

Pinging www.bbc.net.uk [212.58.253.70] with 32 bytes of data:

Reply from 212.58.253.70: bytes=32 time=28ms TTL=249
Reply from 212.58.253.70: bytes=32 time=39ms TTL=249
Reply from 212.58.253.70: bytes=32 time=44ms TTL=249
Reply from 212.58.253.70: bytes=32 time=32ms TTL=249

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

And the server I use for recreation 74.53.34.194

C:\Documents and Settings\Garry Smith>tracert 74.53.34.194

Tracing route to c2.22.354a.static.theplanet.com [74.53.34.194]
over a maximum of 30 hops:

  1    27 ms    28 ms    31 ms  telehouse-gw2-msdp.idnet.net [212.69.63.51]
  2    27 ms    29 ms    29 ms  telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243
]
  3    32 ms    30 ms    27 ms  mfnx-gw-a.lonap.net [193.203.5.16]
  4   111 ms   102 ms   100 ms  so-7-0-0.cr1.dca2.us.above.net [64.125.31.186]
  5   127 ms   153 ms   125 ms  so-1-0-0.mpr3.iah1.us.above.net [64.125.29.37]
  6   131 ms   137 ms   135 ms  so-1-1-0.mpr1.dfw2.us.above.net [64.125.26.129]

  7   137 ms   142 ms   131 ms  64.124.79.77.theplanet.com [64.124.79.77]
  8   157 ms   152 ms   153 ms  te7-1.dsr02.dllstx3.theplanet.com [70.87.253.18]

  9   153 ms   154 ms     *     76.fd.5746.static.theplanet.com [70.87.253.118]

10   154 ms   217 ms   158 ms  po2.car05.dllstx6.theplanet.com [12.96.160.39]
11     *      149 ms     *     c2.22.354a.static.theplanet.com [74.53.34.194]
12   148 ms   149 ms     *     c2.22.354a.static.theplanet.com [74.53.34.194]
13   152 ms   148 ms     *     c2.22.354a.static.theplanet.com [74.53.34.194]
14     *      156 ms   158 ms  c2.22.354a.static.theplanet.com [74.53.34.194]

Trace complete.

[Si]

Here you go....

Tracing route to c2.22.354a.static.theplanet.com [74.53.34.194]
over a maximum of 30 hops:

  1     2 ms     2 ms     2 ms  192.168.1.1
  2    26 ms    26 ms    26 ms  telehouse-gw2-msdp.idnet.net [212.69.63.51]
  3    26 ms    27 ms    26 ms  telehouse-gw3-gi0-1-400.idnet.net [212.69.63.243]
  4    32 ms    38 ms    26 ms  mfnx-gw-a.lonap.net [193.203.5.16]
  5    98 ms    99 ms    98 ms  so-7-0-0.cr1.dca2.us.above.net [64.125.31.186]
  6   125 ms   155 ms   124 ms  so-1-0-0.mpr3.iah1.us.above.net [64.125.29.37]
  7   130 ms   129 ms   131 ms  so-1-1-0.mpr1.dfw2.us.above.net [64.125.26.129]
  8   131 ms   131 ms   131 ms  64.124.79.77.theplanet.com [64.124.79.77]
  9   147 ms   145 ms   145 ms  te9-1.dsr02.dllstx3.theplanet.com [70.87.253.22]
10   144 ms   144 ms   146 ms  72.fd.5746.static.theplanet.com [70.87.253.114]
11   144 ms   145 ms   152 ms  po2.car05.dllstx6.theplanet.com [12.96.160.39]
12   144 ms   144 ms   144 ms  c2.22.354a.static.theplanet.com [74.53.34.194]

Trace complete.