View Full Version : Wick BB
The Angel Of Death
30-Jun-04, 13:05
Anyone been activated yet ???
I heard that BT are about a week behind schedule, that came from a BT Engineer.
The BT website says that the exchange has been enabled but over at the Pipex site the order tracker says that my order is on 'Hold' while they wait for BT to enable the exchange, so god knows who is telling the truth.
Giz
The Angel Of Death
30-Jun-04, 13:55
Eclipse told me that my account cant be created untill bt confirm the exchange has gone live will check my equipment later on today and see if my dsl light is solid if it is then the exchange must be enabled
The BT Website probably goes by the predetermined schedule and isn't updated with any slip from the published date.
You can phone here: 0845 601 2949 (option 9)
to find out if you have broadband already.
They said I have the service on my line so my order via Plusnet is moving along. Normal lead time for ADSL orders is 7-10 working days, usually a bit longer for new exchanges.
Colin Manson
30-Jun-04, 14:22
You could always try logging on to the BT test account.
Username "bt_test@startup_domain" and no password.
Then at least you will know if your line has been activated.
Cheers
Colin
The Angel Of Death
30-Jun-04, 14:33
either that or check to see if your equipment has a solid dsl light
The Angel Of Death
01-Jul-04, 10:02
Anyone got any more information on whats happening my line still wasnt active as of this morning
tommy1979
01-Jul-04, 11:50
my dsl light was still flashing when i checked it this morning.....cant say i expected any less from BT
Tom
Disgruntled BT customer [mad] [mad] [mad] [mad]
Colin Manson
01-Jul-04, 12:59
It's very rare that anyone gets connected on the RFS date, sometimes it can take up to 3 days before they start connecting people.
Cheers
Colin
tommy1979
01-Jul-04, 13:18
fair do's, just after waiting for so long i want it NOW ;)
The Angel Of Death
01-Jul-04, 13:28
Snap i though the whole point of the rfs date was that it would be "ready for service" on tha date given not a few days / weeks after the date if we had a date set in stone that everything was ready to go it would be a lot better than having to wait
Colin Manson
01-Jul-04, 14:05
Yup I know what you mean; I was under the same impression because I know someone that had BB on the RFS date in Thurso.
I asked about this and I was told that it was highly unusual and that sometimes campaigners got BB within a day of the RFS date but for normal folk it was a few days after.
Maybe it's different on these smaller exchanges and I hope you get it ASAP, I however have to wait to next Wednesday because I have to get an engineered upgrade from ISDN, at least I will know exactly when I will have ADSL and I don't have to wait and "light watch" like you guys ;)
I've just been told the 8th of July (after 12pm) iis when I'll be fully activated. The wait is killing me! [mad]
I too have been told that i will be "live" on the 8th of July!!!!
never mind i suppose tis something to look forward to! :D
At the moment i am using Onspeed to speed up my connection(7 day trial takes me up to my activation date ;)) so i can get ready for the high speeds that i will get on BB!!! :lol:
Cmon BT get your finger oot!!!!
The Angel Of Death
01-Jul-04, 20:43
My line is fully active been connected for hours on the bt test details and can access the test page as well (http://193.113.211.125/digitaldemo)
Chased up eclipse they said there was nothing they could do about it until bt inform them that they have finished on the line due to be chasing this up tomorrow so hopefully once thye have that i can get some details to get online with
Got a reply from Pipex and they confirmed that my ADSL service will go live on the 8th :D
Dunno what you lot are moaning about. I live 3.5 miles from the exchange and it's too far to get it.
I'm depressed. [evil]
tommy1979
01-Jul-04, 23:53
WOOHOO Thats me now online with eclipse, so much for having to wail till the 7th of july.........
:lol: :lol: :lol:
The Angel Of Death
02-Jul-04, 13:13
Snap (almost) as well i got my details to connect when i get home from work
Colin Manson
02-Jul-04, 14:58
Dunno what you lot are moaning about. I live 3.5 miles from the exchange and it's too far to get it.
I'm depressed. [evil]
Have you tried to order it from anyone?
Cheers
Colin
Dunno what you lot are moaning about. I live 3.5 miles from the exchange and it's too far to get it.
I'm depressed. [evil]
Have you tried to order it from anyone?
Cheers
Colin
No I haven't. The BT postcode thing says that I was too far away from the exchange so I presumed that was that. Is it not? :roll:
Colin Manson
03-Jul-04, 16:04
The postcode checker is an estimate, it isn't always correct; you need to get your line tested to find out for sure.
This is usually done by placing a manual order with an ISP, not all ISPs do manual orders. A few I remember offhand are Zen, Nildram and Vispa. You can always phone any ISP that you like and ask them if they can help you.
Cheers
Colin
hi all am to waiting for isdn to been done with BT but aint recived anything like the welcome pack all i get is that my order has been placed and waiting on bt to comfim the exchange as been acivted but the exchange as been actived on tuesday nite.anyone else the same as me?
This is really frustrating, i got my Modem from Pipex today and i have a 'Solid' green adsl light, but i have no connection details from Pipex yet.......arrggghhhh!!!
Giz
bummer when u done the order u do it online?> if so once order was placed when they sent u an email saying it was ordered didnt u get an service agreement of them which contants ur username and password.I did :) but i didnt sign up with pipex i signed up with nilly.
The postcode checker is an estimate, it isn't always correct; you need to get your line tested to find out for sure.
Surely a Phone Number Checker will be accurate. Right? :confused
Colin Manson
04-Jul-04, 22:33
No, it is all based upon estimates. Sometimes lines that are within the distance fail and others that are at the extremes pass.
It's always better to try a manual order, I know Vispa will do these and they will get detailed info from BT and tell you about your line. If you read forums such as ADSLguides you will read about people that have only been able to get BB via a manual order. You will of course find people that are on the limit but they still can't get it.
Hopefully BT will increase the line distance limit to 10km and lots more people will be able to get it. Trials seem to be giving good results.
Cheers
Colin
I will be broadband enabled on the 8th.
BUT i have found something seriously strange!!!!
While downloading on Imesh i noticed that i was receiving my Download at......wait for it.........23Kbps!!, BUT i havent even got my broadband modem yet!!!!
:roll:
Im still on a 56k modem and average out at 2.5kbps sometimes 3 but im receiving at 10 times my normal rate, maybe i'll cancel broadband!!!! :D
Any1 else have this "problem" ????
Sweet, a quick phone call to Pipex for my login details and hey presto!!....i have Broadband....and Wow!! it's everything i'd hoped for, after 5 years of connecting at somewhere between 45/48 kbps what a joy it is to now be connecting at 576 kbps :)
Giz
well got my date today its tomrrow between 10.30 and 12.30 hope everything goes well. :D :D
WOW!
BB installed today - amazing....
What a superb service now. Just downloaded a 371 Mb file in just over 1h hour 20 mins. Wouldn't have evn tried that before.
Well chuffed.
Also got my wireless set up woking and able to surf the net from the garden, kitchen , toilet ;) etc.
online games hey peeps wots yer pings like in game servers like jolt?
My ping on both jolt and multiplay servers is between 43 - 47. (That is for Counter strike)
Well chuffed.
Not made me any better though - still kak. :lol:
ye its a bit harder now coz it so damn fast when playing but i get used to it :)
Colin Manson
12-Jul-04, 19:05
I'd like to find out if there is much difference between the connections that we have from different ISPs.
Could you do a couple of things and post the results here, along with the ISP you are with and the type of modem/router that you are using. (Ping & Trace)
Go to the run box in the start menu, type
cmd.exe and press Ok
A black box will appear on the screen, at the prompt > type this
ping 217.169.20.18
This will 'ping' the server 4 time and print the Minimum, Maximum and Average pings on the last row. If you could post those 3 figures and also do this
at the same prompt type
tracert 217.169.20.18 >c:\trace.txt
This will trace the connections from your PC to the server, it will output the results in a text file in the root of your C drive, open the text file and paste the results here. It would be a good idea to highlight the text and press the code button above to format the text.
It is also very important that you are not doing anything else on your internet connection at the time, this would give you a much higher result.
All of this info will help us gamers choose the ISP with the best ping :D
Cheers
Colin
Silverback
14-Jul-04, 00:16
I don't know if anyones interested but heres my results for various tests, bearing in mind that I have optimised my connection for downloading / file sharing and not for games. I have the Pipex 512 unlimited download service.
Incidently, I recommend you all check out http://www.dslreports.com/ its a site with various tools and guides to optimise your connection.
Ping tests of various packet size
Pinging 217.169.20.18 with 32 bytes of data:
Reply from 217.169.20.18: bytes=32 time=50ms TTL=61
Reply from 217.169.20.18: bytes=32 time=50ms TTL=61
Reply from 217.169.20.18: bytes=32 time=50ms TTL=61
Reply from 217.169.20.18: bytes=32 time=50ms TTL=61
Reply from 217.169.20.18: bytes=32 time=40ms TTL=61
Reply from 217.169.20.18: bytes=32 time=50ms TTL=61
Reply from 217.169.20.18: bytes=32 time=50ms TTL=61
Reply from 217.169.20.18: bytes=32 time=60ms TTL=61
Reply from 217.169.20.18: bytes=32 time=50ms TTL=61
Reply from 217.169.20.18: bytes=32 time=50ms TTL=61
Reply from 217.169.20.18: bytes=32 time=50ms TTL=61
Reply from 217.169.20.18: bytes=32 time=40ms TTL=61
Reply from 217.169.20.18: bytes=32 time=50ms TTL=61
Reply from 217.169.20.18: bytes=32 time=50ms TTL=61
Reply from 217.169.20.18: bytes=32 time=40ms TTL=61
Reply from 217.169.20.18: bytes=32 time=50ms TTL=61
Reply from 217.169.20.18: bytes=32 time=50ms TTL=61
Reply from 217.169.20.18: bytes=32 time=50ms TTL=61
Reply from 217.169.20.18: bytes=32 time=50ms TTL=61
Reply from 217.169.20.18: bytes=32 time=50ms TTL=61
Ping statistics for 217.169.20.18:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 60ms, Average = 50ms
------------------------------------------------------------
Pinging 217.169.20.18 with 320 bytes of data:
Reply from 217.169.20.18: bytes=320 time=61ms TTL=61
Reply from 217.169.20.18: bytes=320 time=59ms TTL=61
Reply from 217.169.20.18: bytes=320 time=59ms TTL=61
Reply from 217.169.20.18: bytes=320 time=59ms TTL=61
Reply from 217.169.20.18: bytes=320 time=59ms TTL=61
Reply from 217.169.20.18: bytes=320 time=59ms TTL=61
Reply from 217.169.20.18: bytes=320 time=59ms TTL=61
Reply from 217.169.20.18: bytes=320 time=59ms TTL=61
Reply from 217.169.20.18: bytes=320 time=69ms TTL=61
Reply from 217.169.20.18: bytes=320 time=59ms TTL=61
Reply from 217.169.20.18: bytes=320 time=59ms TTL=61
Reply from 217.169.20.18: bytes=320 time=59ms TTL=61
Reply from 217.169.20.18: bytes=320 time=59ms TTL=61
Reply from 217.169.20.18: bytes=320 time=59ms TTL=61
Reply from 217.169.20.18: bytes=320 time=59ms TTL=61
Reply from 217.169.20.18: bytes=320 time=59ms TTL=61
Reply from 217.169.20.18: bytes=320 time=59ms TTL=61
Reply from 217.169.20.18: bytes=320 time=59ms TTL=61
Reply from 217.169.20.18: bytes=320 time=69ms TTL=61
Reply from 217.169.20.18: bytes=320 time=59ms TTL=61
Ping statistics for 217.169.20.18:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 59ms, Maximum = 69ms, Average = 60ms
------------------------------------------------------------
Pinging 217.169.20.18 with 3200 bytes of data:
Reply from 217.169.20.18: bytes=3200 time=199ms TTL=61
Reply from 217.169.20.18: bytes=3200 time=200ms TTL=61
Reply from 217.169.20.18: bytes=3200 time=200ms TTL=61
Reply from 217.169.20.18: bytes=3200 time=200ms TTL=61
Reply from 217.169.20.18: bytes=3200 time=200ms TTL=61
Reply from 217.169.20.18: bytes=3200 time=200ms TTL=61
Reply from 217.169.20.18: bytes=3200 time=200ms TTL=61
Reply from 217.169.20.18: bytes=3200 time=200ms TTL=61
Reply from 217.169.20.18: bytes=3200 time=200ms TTL=61
Reply from 217.169.20.18: bytes=3200 time=200ms TTL=61
Reply from 217.169.20.18: bytes=3200 time=200ms TTL=61
Reply from 217.169.20.18: bytes=3200 time=200ms TTL=61
Reply from 217.169.20.18: bytes=3200 time=200ms TTL=61
Reply from 217.169.20.18: bytes=3200 time=200ms TTL=61
Reply from 217.169.20.18: bytes=3200 time=200ms TTL=61
Reply from 217.169.20.18: bytes=3200 time=200ms TTL=61
Reply from 217.169.20.18: bytes=3200 time=200ms TTL=61
Reply from 217.169.20.18: bytes=3200 time=200ms TTL=61
Reply from 217.169.20.18: bytes=3200 time=200ms TTL=61
Reply from 217.169.20.18: bytes=3200 time=200ms TTL=61
Ping statistics for 217.169.20.18:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 199ms, Maximum = 210ms, Average = 200ms
------------------------------------------------------------
Trace Route
Tracing route to 217.169.20.18 over a maximum of 30 hops
1 48 ms 49 ms 49 ms loopback1.ar1.gs1.systems.pipex.net [62.241.161.247]
2 50 ms 49 ms 49 ms ge-0-0-0.cr1.gs1.systems.pipex.net [62.241.161.90]
3 49 ms 49 ms 49 ms xp.aimless.aaisp.net.uk [217.79.160.86]
4 49 ms 49 ms 49 ms 217.169.20.18
------------------------------------------------------------
ADSL Guide speedtest
Direction Actual Speed True Speed (estimated)
Downstream 460 Kbps (57.5 KB/sec) 496 Kbps (inc. overheads)
Upstream 243 Kbps (30.4 KB/sec) 262 Kbps (inc. overheads)
------------------------------------------------------------
Speakeasy Test 1 Washington, D.C. - Baltimore, MD
Your download speed : 441291 bps, or 430 kbps.
A 53.8 KB/sec transfer rate.
Your upload speed : 248416 bps, or 242 kbps.
Speakeasy Test 2 New York City, NY - Boston, MA
Your download speed : 441248 bps, or 430 kbps.
A 53.8 KB/sec transfer rate.
Your upload speed : 248077 bps, or 242 kbps.
FTP File download test 57.4 KB/Sec
-----------------------------------------------------------
Receive Window (RWIN): 11680
Window Scaling: off
Path MTU Discovery: ON
RFC1323 Window Scaling: OFF
RFC1323 Time Stamping: OFF
Selective Acks: ON
MSS requested: 1460
TTL: 131
TTL remaining: 115
Actual data bytes sent: 146000
Actual data packets: 100
Max packet sent (MTU): 1500
Max packet recd (MTU): 1500
Retransmitted data packets: 0
sacks you sent: 0
pushed data pkts: 20
data transmit time: 2.801 secs
our max idletime: 179.8 ms
transfer rate: 43956 bytes/sec
transfer rate: 351 kbits/sec!
transfer efficiency: 100%
ICMP (ping) check
Minimum ping: 121 ms
Maximum ping: 134 ms
Ping stability:
122 121 122 122 123 134 124 125 134 124
mysophales
15-Jul-04, 03:12
only the first part of the test worked with me
min = 41 max = 44 average = 42
thats with bt/yahoo
wot do u get colin think most peeple up here will get about the same ping no matter wot isp u with shame i was hoping for a 20 odd ping in jolt servers as am with nilly but i get 50 - 55 which sucks tbh have this it about the same ping i was getting with isdn and when doing a trace route with isdn to jolt gave me better results than am getting with broadband, am using a netgear 834 router so atm am not that happy with pings for me i was looking foward to those very low pings and am sitting with a very fast pc still struggle with the low ping people in england with slower pc than me are getting way better ping 20 - 30 werid eh as any gamer will tell u online games and ping has a lot to do with pc and how fps u get in ur games thus lowering ur ping if u have say about 150fps than if u used 30fps and u will see that ur ping will jump at least 70 or 80 higher ping than with the higher fps. :)
Colin Manson
16-Jul-04, 10:47
I get about 50, the server is one that my team rents for playing quake. 40 seems to be a normal ping for those ISPs that terminate in London, the company I am with terminates in Manchester atm but they are moving the connections to London by the end of the year.
I'm on a 1 month contract so I could move but 10ms isn't really a problem and I'd rather stay with a company that isn't likely to give me any problems.
The ping isn't much different from ISDN but the gaming is much better, I think the ping isn't that much of an issue as long as it's stays the same. I'm very pleased with my Vigor 2600+ it does everything I want and it's really stable :)
I've been playing online since Doom 2 and I can't say that I've ever heard anyone saying that FPS makes a difference to the ping but maybe it depends on the game you play. I have 3 computers and they give between 80FPS to over 300FPS and the ping is the same on all of them. It's just easier to hit targets when your PC is running smoothly. The ping will always be lower the closer the person is to the server, as long as the IPS have good routing and have their routers set correctly.
Cheers
Colin
Colin,
here are my results;
http://www.djross.co.uk/example_photos/image1.jpg
AND
Tracing route to 217.169.20.18 over a maximum of 30 hops
1 45 ms 42 ms 42 ms loopback1.ar2.gs1.systems.pipex.net [62.241.161.244]
2 47 ms 44 ms 41 ms ge-0-1-0.cr1.gs1.systems.pipex.net [62.241.161.106]
3 43 ms 43 ms 43 ms abovenet.aimless.aaisp.net.uk [213.161.69.150]
4 43 ms 45 ms 43 ms 217.169.20.18
Trace complete.
What are your thoughts on this?
ATHRoss
As I have said in a previous post, average pings in Counter Strike Servers (Jolt and Multiplay is ~40 - 45)
Mine are with 64 bytes of data
Pinging 217.169.20.18 with 64 bytes of data:
Reply from 217.169.20.18: bytes=64 time=28ms TTL=52
Reply from 217.169.20.18: bytes=64 time=29ms TTL=52
Reply from 217.169.20.18: bytes=64 time=30ms TTL=52
Reply from 217.169.20.18: bytes=64 time=32ms TTL=52
Ping statistics for 217.169.20.18:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 32ms, Average = 29ms
.................................................. ........................................
Pinging 217.169.20.18 with 32 bytes of data:
Reply from 217.169.20.18: bytes=32 time=31ms TTL=52
Reply from 217.169.20.18: bytes=32 time=28ms TTL=52
Reply from 217.169.20.18: bytes=32 time=34ms TTL=52
Reply from 217.169.20.18: bytes=32 time=30ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=28ms TTL=52
Reply from 217.169.20.18: bytes=32 time=30ms TTL=52
Reply from 217.169.20.18: bytes=32 time=28ms TTL=52
Reply from 217.169.20.18: bytes=32 time=30ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=28ms TTL=52
Reply from 217.169.20.18: bytes=32 time=28ms TTL=52
Reply from 217.169.20.18: bytes=32 time=33ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=30ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=33ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=30ms TTL=52
Reply from 217.169.20.18: bytes=32 time=30ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=30ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=33ms TTL=52
Reply from 217.169.20.18: bytes=32 time=35ms TTL=52
Reply from 217.169.20.18: bytes=32 time=28ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=30ms TTL=52
Reply from 217.169.20.18: bytes=32 time=32ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=30ms TTL=52
Reply from 217.169.20.18: bytes=32 time=31ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=31ms TTL=52
Reply from 217.169.20.18: bytes=32 time=30ms TTL=52
Reply from 217.169.20.18: bytes=32 time=28ms TTL=52
Reply from 217.169.20.18: bytes=32 time=30ms TTL=52
Reply from 217.169.20.18: bytes=32 time=28ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=28ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=30ms TTL=52
Reply from 217.169.20.18: bytes=32 time=28ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=27ms TTL=52
Reply from 217.169.20.18: bytes=32 time=30ms TTL=52
Reply from 217.169.20.18: bytes=32 time=31ms TTL=52
Reply from 217.169.20.18: bytes=32 time=31ms TTL=52
Reply from 217.169.20.18: bytes=32 time=28ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=28ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=30ms TTL=52
Reply from 217.169.20.18: bytes=32 time=32ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=30ms TTL=52
Reply from 217.169.20.18: bytes=32 time=28ms TTL=52
Reply from 217.169.20.18: bytes=32 time=28ms TTL=52
Reply from 217.169.20.18: bytes=32 time=31ms TTL=52
Reply from 217.169.20.18: bytes=32 time=28ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=31ms TTL=52
Reply from 217.169.20.18: bytes=32 time=30ms TTL=52
Reply from 217.169.20.18: bytes=32 time=31ms TTL=52
Reply from 217.169.20.18: bytes=32 time=30ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=30ms TTL=52
Reply from 217.169.20.18: bytes=32 time=28ms TTL=52
Reply from 217.169.20.18: bytes=32 time=30ms TTL=52
Reply from 217.169.20.18: bytes=32 time=31ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=31ms TTL=52
Reply from 217.169.20.18: bytes=32 time=30ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=28ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=29ms TTL=52
Reply from 217.169.20.18: bytes=32 time=27ms TTL=52
Reply from 217.169.20.18: bytes=32 time=32ms TTL=52
Reply from 217.169.20.18: bytes=32 time=30ms TTL=52
Reply from 217.169.20.18: bytes=32 time=28ms TTL=52
Ping statistics for 217.169.20.18:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 35ms, Average = 29ms
wot isp are u with and are you in wick?
I am with BT Broadband in Thurso but also get the same results in Wick with BT Business broadband
simian sally
23-Jul-04, 02:17
Lo All!
It is important to remember that your ping times will depend on whether you are using a direct or wireless connection, and where you are located geographically.
I get consistent 22ms average ping times for 32 byte packets when connected directly to my router via ethernet. Individual times are rarely outwith the range 21-23ms.
Over wireless, average ping times are roughly 39ms, again for 32 byte packets, but the fluctuations are quite large, and individual ping times can easily vary between 25ms and 55ms for a sequence of about 100 packets.
Yes, wireless adds roughly 17ms to my ping times. As far as I can ascertain, this is not atypical, although it will be router and wireless card dependent.
I am using 576K Pipex in Edinburgh, so I would expect my ping times to be lower than Caithness users', but I don't know how much lower.
newlabeluk
03-Aug-04, 10:05
at least you guys will be getting BB,think of the poor unfortunates that are on the JOG exchange but live 7miles from it.they are outside the exchange distance according to BT...Or and this was a good one! it depends on how the cable is laid,if it goes up the left hand side of the road crosses over and comes back down the person nearest the exchange may not get BB because the cable goes too far.....this told to a 77yr old BT customer. [mad]
hey all any1 else having problems with their broadband in wick with high pings and there download speeds dropping on the speedtest i have 512 when it runs ok my download is 59.8 and upload 31.8 but when ping goes high my download speed goes down to 34.7 but the upload stays the same.Just wondered if anyone else having problems. u can check ur speed here www.adslguide.org then speedtest. :)
Colin Manson
15-Aug-04, 22:10
Lo,
aaisp seem to be having problems.
They are having a few issues with routers this weekend which probably caused the problem.
I noticed a few people on usenet are also reporting issues at aaisp.
I'm with Vispa and I've had bad pings and my download is only 45.8 and it should be about 115.
Cheers
Colin
yes colin but this being going on now for few weeks.
Colin Manson
17-Aug-04, 06:45
Lo,
Spoke to a guy from my ISP yesterday and he thinks there must be a problem at our exchange, something that affects only some of the people on it. I know a coupld of guys that don't see this problem so it isn't affecting everyone.
They are going to test my connection today and hopefully it will be reported to BT, the only problem is that the average ping has to be over 100 before BT will accept it as a fault. I think they run a test that does 1000 pings.
Will let you know what happens when I get the results.
Cheers
Colin
I know that Pipex were having some troubles earlier this month and lost a major connection therefore routing users through spare capacity on other major pipes.
See http://bbs.adslguide.org.uk/showflat.php?Cat=&Board=pipex&Number=1345561&page=0&view=collapsed&sb=5&o=0&fpart=
May explain things a little.
ATHRoss
Colin Manson
19-Aug-04, 13:18
Lo m8,
Shouldn't make any difference to us, I think thegame said he was with nilly and I'm with Vispa. Pipex issues wouldn't affect us.
Cheers
Colin
http://www.hie.co.uk/default.aspx?locid=0finewk9b
Will this apply to Wick and Thurso etc exchanges?
New line noise limit standards just announced by BT for exchange-based broadband means an extra 14,000 people in the Highlands and Islands will now be able to get high speed connections from September 6.
As reported here last week, the extended reach trials in Fort William and Dingwall have been so successful BT can now confidently widen availability from broadband-enabled local exchanges.
Previously broadband services were generally restricted to homes and businesses located within 5.5km of an upgraded exchange. But now the tests have shown the distance limits can be withdrawn completely for 512kb/sec ADSL services. It is estimated that more than 99.8 per cent of lines connected to a broadband exchange should be able to get a 512kb/sec ADSL service by August next year.
The findings of the trials have also allowed the reach limit for 1mb/sec premium services to be increased from 4km to approximately 6km - making 1 mb/sec ADSL available to 97 per cent of Scottish homes and businesses connected to a broadband exchange.
Brendan Dick, general manager for BT Scotland, said: “This is a great step forward for the ongoing development of broadband in Scotland.
“Trial data and feedback from the testers in Fort William and Dingwall has played a major part in making it possible. Their interest and commitment to work with BT has helped bring about a significant milestone in the development of British communications.
“Broadband is fundamental to the future in so many ways, and now it will be available to a million more homes and businesses - including many in the trialists’ own areas. Around 12 per cent of customers in Dingwall and 14 per cent in Fort William are currently out of reach, so this development could make a big difference to many more rural farms, businesses and consumers there - and elsewhere across the country.”
BT says the new coverage footprint for broadband is now on par with the percentage of homes that can get good quality analogue TV signals for the four main terrestrial channels.......
Colin Manson
19-Aug-04, 21:16
Yes it will apply to all exchanges.
Yes it will apply to all exchanges.
Good news for all us country bumpkins then. :)
Colin Manson
19-Aug-04, 21:44
Yes it will apply to all exchanges.
Good news for all us country bumpkins then. :)
Yup it should make a big difference to lots of people.
BT is confident that 512kbit/s products can now be provided to the majority of people and the current planning limit of 60dB (6km) will be removed.
Also a BT guy told me that the quality of the telephones up here is pretty good, I know that my line has a very good SNR Margin and Loop Att. So that should help more people get ADSL.
Cheers
Colin
any1 still having problems with there bb in wick i am still the same old problems,wot about you colin ?
Anyone had any success with the new extended limts? My line is being activated on September 14th with pipex, yays!
tides of pentland firth
11-Sep-04, 23:07
We've had it for about two months now and it has got slower and slower since the day it was installed. Also, Ive never had a problem with the internet until now but now im always in contact with BT bb over minor things every week nearly. Might be due to my computer by I wouldnt have thought so.
Colin Manson
12-Sep-04, 00:46
any1 still having problems with there bb in wick i am still the same old problems,wot about you colin ?
Problems wont clear up until the 22nd when they upgrade the Virtual Paths, they are still showing up as Red on the exchange checker.
Hopefully everything will be fine after the upgrade.
Cheers
Colin
Powered by vBulletin® Copyright © 2024 vBulletin Solutions, Inc. All rights reserved.