Online gaming is just too laggy the last few day and my poor keyboard is taking the brunt of it so I finally had enough (pings have been getting worse and worse since joining) and finally contacted tech support.
No answer. The 1st time I actually phone them up and no one's at home. :red:
I think I heard on the news this morning that it is a bank holiday in England. Would it be worth trying an alternative means of communication or is everyone off to Alton Towers for the day?
When my connection worked (see other thread) my latency has increased recently.
I used to get 12-17ms to a plusnet server. I was recently getting 30-45ms....and then sometime 20-30ms. Now I appreciate that this may be down to external factors.
Did you leave a message on the out of hours number, Rich?
Rik
Nope, to be honest I'd rather speak to a human and feel like somethng is being done.
I only tried 01462 476555. Is there a better number?
j.baker
My pings are currently anywhere from 60-160 from a steady 40-50.
When I first signed it was mid 20s. I'm syncing a whole meg less now too. :bawl:
That's the only number you'll get today, Rich, leave a message and someone will get back to you.
Cheers buddy. :thumb:
Well I did as you said Rik and guess what? No one got back to me. It will be a week ago tomorrow that I left my details and brief explanation with them. (http://www.mysmiley.net/imgs/smile/rolleye/rolleye0011.gif)
And now the situation has changed drastically. Resigned to a weekend of no gaming due to the ridiculous pings I haven't been near the PC much. I did note however during more mundane activities that pages were slow to load, updates were sluggish and youtube was unusable (I use Net-Meter and everything coming in barely registered on the graph). Seeing as my connection (pings aside) is usually a stable 6.4 megs sync these days (from 7.4 originally) I just put it down to traffic/contention.
Tonight I had enough an checked my router stats and....
(http://i33.photobucket.com/albums/d67/ou7shined/IDNet/take1.jpg)
Switched off the router (Voyager 205), back on, reset it then configured it as usual with my saved config file, then connect to the net and...
(http://i33.photobucket.com/albums/d67/ou7shined/IDNet/take2.jpg)
Same procedure again and....
(http://i33.photobucket.com/albums/d67/ou7shined/IDNet/take3.jpg)
(http://www.mysmiley.net/imgs/smile/confused/confused0024.gif)
I'm back up to 1 meg again now. Rediculous!(http://www.mysmiley.net/imgs/smile/mad/mad0066.gif)
Sorry to hear that no one got back to you - get onto them again tomorrow.
Unless you've got a really long line, your sync rate is pretty poor, and very variable too, which would suggest a lot of noise on the line. Could you post your stats from the router?
Hi ou7shined, I'm sure someone will get back to you tomorrow ;)
As for the problem at hand, is the sync any better pluged into the test socket? Also, could you try a different filter?
Quote from: Sebby on Jun 01, 2009, 00:05:16
Sorry to hear that no one got back to you - get onto them again tomorrow.
Unless you've got a really long line, your sync rate is pretty poor, and very variable too, which would suggest a lot of noise on the line. Could you post your stats from the router?
How do I obtain them?
Which router do you have?
Quote from: Lance on Jun 01, 2009, 00:10:53
Hi ou7shined, I'm sure someone will get back to you tomorrow ;)
As for the problem at hand, is the sync any better pluged into the test socket? Also, could you try a different filter?
Nope it actually went down again (800Kbps - not uncharacteristic for this problem though). Only have the 1 I'm afraid.
Voyager 205
http://www.kitz.co.uk/adsl/frogstats.php#13
:)
Cheers Sebby.
(http://i33.photobucket.com/albums/d67/ou7shined/IDNet/stats.jpg)
Right, well if those stats are anything to go by, something is seriously wrong. I'm assuming the local line attenuation is the downstream, and at 29dB, you should be achieving full sync easily. At the moment, the sync is way off of what it should be. I suspect your other problems are related. Do you have a master socket with a removable lower half?
I think it might be time for a new filter (or faceplate) just for elimination purposes!
I think the first thing to do, assuming there's an NTE5, is to try the test socket.
QuoteDo you have a master socket with a removable lower half?
Yes and the front is off and I'm plugged into the internal socket as per the previous suggestion.
Sorry I was a way for a bit there. I ran a BT test and....
(http://i33.photobucket.com/albums/d67/ou7shined/IDNet/bttest.jpg)
I've only ever seen 6s and 7s in there before.
In that case there is something seriously wrong with your line. As it is the same plugged in to the test socket, the first thing I would suggest is when support call you tomorrow, ask them to test the line, If that comes back fine, then I reckon you should try a new filter or get a filtered faceplate - adslnation ones come highly recommended.
The new filter might not sort the problem, but it helps to eliminate it. If the new filter doesn't sort it, I would be looking at trying a new router - maybe a friend or IDNet support could lend you one? Hopefully it won't come to that though!
bugger :(
I've found a new filter. No change. :(
I think you need to try an alternative router, if that doesn't change things, then your line needs some serious attention.
I had the router switched off all night, reset it etc this morning, connected and I'm still only getting 992 Kbps. :bawl:
What's a good router to get then?
I'm just round the corner from PC World and had a squint on their webby to see what they offer. The info provided on routers is inconsistent and quite frankly the highlighted features are insulting "can transfer documents, music files, ideal for online gaming" - funnily enough I was able to do all these on dial up. :eyebrow:
I'd suggest asking IDNet if they could lend you a router initially. Failing which, look out for a 2700 on eBay, you should be able to get one for £10-15 delivered.
A guy from Idnet just called and said there's a problem with the line and I should contact BT and ask for a PSTN ???
But you guys were saying that my stats suggest the line's ok :dunno:
No, the line is rubbish, Rich. It should be good, based on the attenuation, but the sync speeds you're getting says that it's very noisy. IDNet would appear to have detected a basic line fault, try dialling 17070 and selecting option 2, the quiet line test. If you hear more than a background hum or hiss, report that to BT as a voice fault, and be careful not to mention ADSL.
This may sound odd but we don't have a telephone. We are a household of mobile users and only have the line for BB, so I can't do that.
How best to get in touch with BT? Google seems to bring up a load of numbers and services that I don't need.
Apologies for being such a space cadet. :blush:
Quote...and be careful not to mention ADSL
Why?
If you do, BT will immediately try to pass the buck.
Quote from: ou7shined on Jun 01, 2009, 10:33:47
This may sound odd but we don't have a telephone. We are a household of mobile users and only have the line for BB, so I can't do that.
How best to get in touch with BT? Google seems to bring up a load of numbers and services that I don't need.
Apologies for being such a space cadet. :blush:
Can you pick up a cheap, wired, handset? You need to be able to dial 151, ideally, from that line. You can do it via the BT website if needs be, but using the phone is the best way.
While trawling BT's site looking for a tech support number (still haven't found it) I found "track a fault". I don't know if this means much...
(http://i33.photobucket.com/albums/d67/ou7shined/IDNet/fault-check.jpg)
You should be able to report a fault from that section of the site, Rich.
Cheers Rik.
Ok BT found a fault and fixed it. I'm impressed. And now I'm syncing at a rip roaring.....
(http://i33.photobucket.com/albums/d67/ou7shined/IDNet/take4.jpg)
That's what I call a result. :)
Quote from: Rik on Jun 01, 2009, 16:08:39
That's what I call a result. :)
Yup the line gets fixed and my connection drops another 128Kbps. :bawl:
Phoning IDnet as I type.
Ouch. Doesn't look like they've really fixed it! Let us know what IDNet say.
Spoke to a fella at IDnet who said "they simply can not push anymore frequency down my line in the state it is in" :dunno: ??
They are sending a BT ADSL engineer out to me.
Well that's true, nothing to do with IDNet. I'm sure INet made you aware, but BT charge £160+ if no fault is found. There definitely is a fault, though, so if they try it on, stand your ground! :)
He never mentioned no £160! :o
What's likely to happen like?
The engineer will check at the test socket behind the faceplate if you have an NTE5, or will disconnect the exchange pair and test there if you don't (hint, if you don't, ask nicely and he'll probably fit an NTE5 for you). If that test shows all is well, he'll say it's your internal wiring (though I don't think that is the case). If it's internal wiring, you will be charged.
And just to cheer myself right up I checked my pings. Yup...... they've doubled. (http://www.mysmiley.net/imgs/smile/sad/sad0047.gif)
There's a few of us seeing higher pings at the moment, Rich, IDNet don't have any network congestion, so I'm not sure why. Often, for reasons I can't explain, re-booting the router will fix it.
Quote from: Rik on Jun 01, 2009, 16:47:22
The engineer will check at the test socket behind the faceplate if you have an NTE5, or will disconnect the exchange pair and test there if you don't (hint, if you don't, ask nicely and he'll probably fit an NTE5 for you). If that test shows all is well, he'll say it's your internal wiring (though I don't think that is the case). If it's internal wiring, you will be charged.
Ah ok. Well I do have a NTE5 and my pc is connected directly to it. So if I understand correctly no internal wiring... unless you mean the stuff between my ears and that's definitely not what it used to be. :D
Mate I have rebooted my router about 15 times today already. But cheers.
No extensions from the NTE5, Rich? Have you tried plugging into the test socket behind the faceplate?
I'm stuck on the pings, IDNet can see no reason, but there's three or four of us at least seeing high figures. I'll keep an eye on it and see if I can spot a pattern.
Quote from: Rik on Jun 01, 2009, 16:58:49
No extensions from the NTE5, Rich? Have you tried plugging into the test socket behind the faceplate?
Yep that's how it is just now. I've just left it like that until the engineer sees it.
You shouldn't have any problems, then. :thumb:
:iagree:
Whenever I try a ping test it always seems to be "telehouse-gw2-lo1.idnet.net [212.69.63.51]" giving largely varying times, such as "43 ms 53 ms 146 ms". Obviously something isn't quite consistent "at the hop - hop hop hop."
Most of the idnet servers are set to give ping requests low priority which is what can sometimes cause the variable results. If you do a search for nameserver you should be able to find the ip address for it which is the one idnet recommend pinging (i'd find it for you but i can't search from my phone).
Just make the engineer lots of tea and a bacon sandwich, Rich, and you should be fine. ;) ;D
I'm screwed.... I'm a vegy. :D
Let's hope BT get to the root of the problem. :)
:groan:
212.68.40.3. :)
I wish he'd hurry up, my line's down to 448 Kbps.
I've got some buns in, in case he has a sweet tooth. :thumb:
Bacon butties generally work well too. :)
Would Echinacea tea with marinated organic tofu slices in a wholemeal high roughage bread roll and a head massage do? (See Reply #51)
We're not that bad really, just very definitely no bacon in the hoose. :D
Choccie biscuits work. :)
I think the Mrs. might have some hidden away in her "secret stash". I'm saved! ;D
;D
What really works with most engineers is talking to them and being friendly. They meet a lot of grumps during the day. A little friendliness goes a long way.
When I had noise on my line the engineer that came out fitted a proper nte5 master socket with filtered faceplate and made the mess of 3 sky + 1 phone extension look somewhat beautiful while he waited for the cherry picker to arrive. The advantages of having a very big brother that everyone seems to know. Cups of tea and friendly attitude will help.
Definitely something wrong with pings at the moment, my Pinggraph for the last hour: -
[attachment deleted by admin]
Can you let support know, Ray. Mine are bad today, worse than yesterday, and re-booting the router hasn't cured it. The more people who let them know, the more notice will get taken.
Quote from: Rik on Jun 02, 2009, 15:13:59
Can you let support know, Ray. Mine are bad today, worse than yesterday, and re-booting the router hasn't cured it. The more people who let them know, the more notice will get taken.
Email sent to support with copy of graph attached, Rik. :thumb:
Thanks, Ray. :thumb:
Looks like he won't be coming today then. (http://www.mysmiley.net/imgs/smile/sad/sad0047.gif)
Another graph sent to support.
Quote from: ou7shined on Jun 02, 2009, 17:52:55
Looks like he won't be coming today then. (http://www.mysmiley.net/imgs/smile/sad/sad0047.gif)
Have you checked with IDNet, they are there till 6:30. 0800 701 2000.
Thanks again Rik.
I called them and explained and the guy just sighed, put me on hold for a bit then asked if they could call back, then the second guy told me that an engineer hadn't been asked to come round to mine (so I'd waited in all day for nothing) and that BT say there isn't a fault but will look into it again tomorrow.
It a bit frustrating watching pictures actually load (like the good old days) and to be told there ain't a fault.
I understand how you feel. I really don't know what to say. ???
Sorry to hear that, Rich. :(
My pings have been a mess also seem better now but its been over 100ms then 58ms then 78ms never seen them so messy :bawl:
So I've made a bit of headway. I managed to get a shot of a mates router and connected it up last night but I'm still syncing at ~300kbps. So thinking that a router fault had been eliminated from the equation I call IDNet and I'm greeted with....
"Ah yes Richard, last we spoke we sent an engineer out to you. How did that go?" (http://www.mysmiley.net/imgs/smile/confused/confused0017.gif) I knew I hadn't imagined it. :rant2: Ooh I really hate being lied to. :no:
Anyway it turns out that I am in fact connected at 7.6 again but my profile has to reset. So in the mean time I'm stuck with...
(http://i33.photobucket.com/albums/d67/ou7shined/IDNet/BT.jpg)
(http://i33.photobucket.com/albums/d67/ou7shined/IDNet/think.jpg)
Also I'm not to switch off the router until it settles..... but yes, you guessed it, my mate needs his router back asap. :(
My pings are still outta whack. Is this because of my profile thing or is everybody still experiencing problem?
Your profile should adjust quickly, given the percentage change. Pings are not affected by profiles. Mine are still about 8ms higher than normal.
Well I'm still choked at 300kbps and my pings are in the 100s. Should I restart the router or is that just as bad as switching it off?
It's no different, Rich.
So I just wait and the router will automatically pick it up when the profile has settled?
The router doesn't care about profiles, Rich, they're just for BT's convenience. Your router will go as fast as it can, limited by the sync speed and profile. If either change, the router will handle it automatically.
Ah well it looks like another weekend with no gaming then.
My pings are between 60 and 120 what can be done about them then while I wait for my (mates) router to do it's biz? It was around a tolerable 45ms before all this happened so my increase doesn't seem to be related to the 8ms increase you are experiencing.
The pings thing may be the same issue as some others have been experiencing, but that doesn't get away from the fact that there is something wrong with your line, and imo, that needs to be sorted first. :)
BT claim the line has no issues and IDnet say they have done all they can do (well that's what the last one said at least ::) - I have learnt over he past few days that it does depend upon who you get when you call). I'm totally out of my depth here. I wish I knew what to do. :dunno:
I'm a musician - in my world dB means something else. :blush:
(edited for spelling)
The other day when you posted your BT speedtest result, it was clear that there's something wrong with your line as the profile of 350k suggested that there had been some significant instability.
Get onto IDNet anyway, as your ping issue may be what others are experiencing.
Ok. I'll try again.
Cheers for listening Sebby.
Here's my latest...
Test1 comprises of Best Effort Test: -provides background information.
Your DSL connection rate: 7424 kbps(DOWN-STREAM), 448 kbps(UP-STREAM)
IP profile for your line is - 350 kbps
Actual IP throughput achieved during the test was - 316 kbps
That's a certain sign of instability, Rich, the profile is for a sync speed of 416-575k. Has IDNet asked you to report the line to BT as a voice fault? If you do a quiet line test (17070 option 2) do you hear any noise?
Nope. Dialled 17070 option 2 and it sounds crystal clear.
Essentially, then, you need to talk to support and get an engineer out, risking the callout charge if no fault is found. :(
That's scary.
But I have the router connected directly to the test socket with a brand new phone cable and a new cat5 from that to the PC so I should be ok yeah?
You should, but no-one can guarantee how BT will play it. From what I know, there's clearly a line fault, but BT have to be able to identify it.
That's where the tea and snacks come in. ;)
Indeed. :)
I won a 2700 HGV on ebay last night - £5.50
h/ware Version: 2701-1--589-005
s/ware Ver: 5.29.107.19
(http://i33.photobucket.com/albums/d67/ou7shined/IDNet/WirelessHub2700HGV.jpg)
Nice. :thumb:
Cool! :)
Plug it in, that will soon change. :whistle: ;D
I'm syncing at about 5megs today - it's obviously shy of the 6.5+ I was getting before all this happened but at least it's working again. I'm not gonna mess about with it until the 2700 arrives.
Spoke to James at IDNet and he has suggested switching off interleaving to try and bring my pings back down to double figures again.
Things are looking up at last. :thumb:
:fingers:
Glad to hear you're making progress, Rich.
Quote from: Rik on Jun 08, 2009, 15:45:40
:fingers:
Glad to hear you're making progress, Rich.
Yup. That's a very appropriate smiley there Rik. :)
It's been well used this past week... :)
The 2700 came today - it's big init! :eek4:
Turns out to be a dual SSID. Thank you. :pray:
I had some trouble initially as the "home" in the address bar doesn't work for it but I found "http://192.168.1.254/" is the key.
I'm in a bit of a panic just now as this is my first wireless and I don't know how to make it secure also I don't want it to self upgrade to v6 while I'm faffing about with it. :red:
Also.. it says...
Connection Speed:
• Incoming: 7392 kbps
• Outgoing: 448 kbps
Is this real or my profile?
Regarding my pings, they have returned to around what they were before all this happened although rather than being as stable as they used to be they are very variable - tried gaming (before the 2700 arrived) and it is still very jerky.
7392/448 looks real enough to me, your profile will be 6.5M. Read the 2700 thread on setting up, that should preserve you from v6. As to wireless, just disable it if you don't need it.
http://192.168.1.254/xslt?PAGE=C01&THISPAGE=B02&NEXTPAGE=C01
on mine.
Thanks Rik - saved the day again. :blush:
I have disabled it for now but I'd like to get it going for my mobile connection also the Mrs wants it for Wii stuff.
In that case:
http://home/xslt?PAGE=C01&THISPAGE=A02_POST&NEXTPAGE=C01
Click on Wireless settings > Edit settings and turn on WPA there, setting a strong key.
Thanks. (had to edit http://192.168.1.254 into the address but I've got the hang of it now)
You knew this was coming.... :D
What's the difference between WEP, WPA, WPA2, PSK etc.?
WEP is weak and hardly worth using, WPA is stronger and pretty secure, WPA2 is stronger yet and compatible with most modern machines. PSK just refers to the fact you use a shared key to access the router.
Sorted! Everything's back to normal again. :thumb:
Having said that, interleaving off has taken me from a very jumpy 70~120ms back down to 40~60ms, which is a little higher than it was before all this happened with it switched on but still in the same ballpark - so presumably something's still not quite right. :dunno: I would appreciate if someone could comment on this.
My connection is syncing around the 7.2~7.4 mark (been doing a few on and offs while configuring my 2700 so presumably it hasn't settled fully) which I am over the moon about.
And I am now fairly au fait with the world of wireless. I'm glad to have taken the plunge (or been pushed into the deep end by you guys :)) It's like one of those things where you know you should just come out and ask about it but everyone else seems to take it for granted so you quietly get by without it. I do have a couple of 2700 questions but I'll air them over in the 2700 thread.
Many thanks peeps.
Hi Rich, glad you're getting there. The ping time may just indicate there's more congestion at the exchange than normal. Is the 2700 indicating it's on fast path?
Is that this bit?
DSL Connection Details
DSL Line (Wire Pair): Line 1 (inner pair)
Protocol: G.DMT Annex A
Downstream Rate: 7264 kbps
Upstream Rate: 448 kbps
Channel: Fast
Current Noise Margin: 12.0 dB (Downstream) 22.0 dB (Upstream)
Current Attenuation: 31.7 dB (Downstream) 17.5 dB (Upstream)
Current Output Power: 19.8 dBm (Downstream) 12.3 dBm (Upstream)
DSLAM Vendor Information: Country: {0xB5} Vendor: {TSTC} Specific: {0x00}
PVC Info: 0/38
Internet Connection Details
Connection Type: PPPoA
Username: ********@uk.idnet.dsl4
Internet Address: 212.69.xxx.xxx
Subnet Mask: 255.255.255.255
Default Gateway: 212.69.63.55
Primary Domain Name Server: 212.69.36.3
Secondary Domain Name Server: 212.69.40.3
Domain:
Maximum Transmission Unit (MTU): 1500
Gateway Ping: Successful
DNS Communication: Successful
Configuration Server Post: Waiting for DNS information
I've just removed your IP address, Rich. Yup, that's it, you're on fast path. I would have hoped for a better ping than 40ms. Can you try a tracert, please, ie Start > Run > CMD <enter> then type tracert www.idnet.net. Paste the result back if you would. :)
Whoops cheers. :blush:
I did 2 for you...
(http://i33.photobucket.com/albums/d67/ou7shined/IDNet/trace1.jpg)
(http://i33.photobucket.com/albums/d67/ou7shined/IDNet/trace2.jpg)
There's very little delay once you hit the IDNet network, Rich, it all seems to be in that first hop. Keep an eye on it, if it doesn't improve, have a word with support.
Incidentally, the quick way to cut'paste' from the CMD window it to right-click on the title bar, then Edit > Select All then <enter>. That's the cut done and you can paste the results as text, rather than having to go through an image editor. :)
For comparison, I've just done a tracert. My line is interleaved, btw.
tracert www.idnet.net
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms home [192.168.1.254]
2 120 ms 37 ms 23 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 24 ms 23 ms 23 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 26 ms 23 ms 23 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 24 ms 25 ms 21 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 24 ms 23 ms 25 ms www.idnet.net [212.69.36.10]
Trace complete.
Nice tip thanks. :thumb:
So it does looks a bit iffy then? What should I be looking out for? I take it the 307 and 73 are bad.
I did a few more and this one came out fairly even...
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms home [192.168.1.254]
2 40 ms 45 ms 39 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 39 ms 41 ms 39 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 41 ms 41 ms 41 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 41 ms 41 ms 41 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 39 ms 39 ms 39 ms www.idnet.net [212.69.36.10]
Trace complete.
Sorry for not keeping up with you.... I'm making the tea while doing this. :D
They are just peak values, Rich, the third column is the average, which is pretty static. What you see in a tracert is a ping to each step of the journey, rather than a simple end to end ping. It can help identify where delays are occurring along the way, but ping traffic is usually given a low priority by the routers it passes through, so if they are busy, you'll see the high values. Hence, you need to collect them over a longish period, eg hours or a day, to see if there are any patterns developing. ATM, my best guess would be you have a fairly busy VP at the exchange, when I was running on a business package, which has priority at the exchange, my pings improved by an average of 4ms on the 24ms I normally see, and when my line was not interleaved, I saw pings of 13ms.
You're also a lot nearer my favourite butcher than my favourite ISP, so that extra distance will have an impact (ping a USA site and you'll see what I mean).
Quote from: ou7shined on Jun 12, 2009, 18:50:42
Sorry for not keeping up with you.... I'm making the tea while doing this. :D
NP. I stopped to go and do my daily penance on the exercise bike. ;D
Quote from: Rik on Jun 12, 2009, 18:53:40...You're also a lot nearer my favourite butcher than my favourite ISP...
:hehe:
My pings are dear to me as a weekend gamer. I wonder if I'll ever get my 23~24ms that I was getting when I 1st joined here. Maybe as you say my exchange is just too busy now. I'll have a look at the business packs but I'm probably paying too much for the one I have as it is. :(
Have a word with IDNet first, Rich, especially of you're on GW6.
I think I'm on dsl4.
The last few characters of your login will tell you. If it's dsl4, it's the same central as gw5, so that's not an issue.
That's reassuring. It's good to eliminate it as the culprit.
Do you think I should give them a bell this morning to see if there's anything else they can do?
No point, Rich, it's not an emergency and would not be dealt with until Monday.
Righto :thumb:
suffering myself today
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.3.2
2 113 ms 129 ms 96 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 172 ms 137 ms 133 ms telehouse-gw3-g0-1-400.idnet.net
[212.69.63.243]
4 50 ms 49 ms 52 ms redbus-gw2-g0-1-331.idnet.net
[212.69.63.5]
5 175 ms 173 ms 51 ms redbus-gw1-fa2-0-300.idnet.net
[212.69.63.225]
6 326 ms 244 ms 188 ms www.idnet.net [212.69.36.10]
Trace complete.
Here's me today......
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms home [192.168.1.254]
2 51 ms 53 ms 203 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 62 ms 43 ms 98 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 39 ms 66 ms 41 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 39 ms 39 ms 43 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 39 ms 41 ms 41 ms www.idnet.net [212.69.36.10]
Trace complete.
Mine are quite good today: -
Tracing route to idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 86 ms 99 ms 99 ms router [192.168.1.254]
2 25 ms 18 ms 19 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 21 ms 20 ms 19 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 20 ms 20 ms 19 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 19 ms 20 ms 19 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 21 ms 18 ms 21 ms www.idnet.net [212.69.36.10]
Trace complete.
It's not universal:
tracert www.idnet.net
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms home [192.168.1.254]
2 27 ms 52 ms 23 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 25 ms 23 ms 23 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 31 ms 27 ms 25 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 23 ms 23 ms 25 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 25 ms 25 ms 25 ms www.idnet.net [212.69.36.10]
Trace complete.
Are you on gw5 or gw6, Jim?
Heres mine tonight :(
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 313 ms 1 ms 1 ms homeportal [192.168.0.1]
2 2 ms 21 ms 19 ms telehouse-gw4-lo2.idnet.net [212.69.63.99]
3 166 ms 32 ms 21 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 270 ms 4294967251 ms 208 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 22 ms 21 ms 21 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 22 ms 21 ms 21 ms www.idnet.net [212.69.36.10]
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 311 ms 311 ms 310 ms homeportal [192.168.0.1]
2 22 ms 330 ms 330 ms telehouse-gw4-lo2.idnet.net [212.69.63.99]
3 331 ms 330 ms 330 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 331 ms 330 ms 330 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 330 ms 332 ms 331 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 331 ms 330 ms 330 ms www.idnet.net [212.69.36.10]
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 311 ms 1 ms 1 ms homeportal [192.168.0.1]
2 21 ms 330 ms 21 ms telehouse-gw4-lo2.idnet.net [212.69.63.99]
3 21 ms 21 ms 21 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 20 ms 21 ms 21 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 20 ms 21 ms 330 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 21 ms 21 ms 21 ms www.idnet.net [212.69.36.10]
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 311 ms 311 ms 311 ms homeportal [192.168.0.1]
2 330 ms 330 ms 330 ms telehouse-gw4-lo2.idnet.net [212.69.63.99]
3 331 ms 330 ms 330 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 331 ms 330 ms 330 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 330 ms 330 ms 21 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 20 ms 330 ms 330 ms www.idnet.net [212.69.36.10]
That's very sluggish. :(
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
tracert www.idnet.net
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms home [192.168.1.254]
2 374 ms 21 ms 23 ms telehouse-gw2-lo2.idnet.net [212.69.63.55]
3 26 ms 23 ms 23 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 26 ms 23 ms 23 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 24 ms 23 ms 23 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 24 ms 25 ms 23 ms www.idnet.net [212.69.36.10]
Trace complete.
Yes, Seems to be better today
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 1 ms <1 ms 1 ms homeportal [192.168.0.1]
2 19 ms 19 ms 19 ms telehouse-gw4-lo2.idnet.net [212.69.63.99]
3 21 ms 19 ms 21 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 22 ms 19 ms 20 ms redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
5 20 ms 21 ms 20 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 19 ms 19 ms 21 ms www.idnet.net [212.69.36.10]
Trace complete.
That suggests an exchange issue, then.
Probably as my SNR has continued its rise and my connection speed is now lower than before I swapped over.
:(
Do you happen to know what make of MSAN you're connected to?
Protocol: G.DMT2+ Annex A
Channel: Fast
DSLAM Vendor Information Country: {46336} Vendor: {TSTC} Specific: {5 }
ATM PVC: 0/38
which I understand is Texas Instruments
Correct. :)
One less suspect...