The online racing simulator
Keep Losing Connection to CTRA Servers
Hey...I am having problems with CTRA servers like alot of the time i would be in race and then all of a sudden kick saying lost connection to host and this is begining to be a pain in the ass as it seems to happen when i am leading a race or something. Its not my connection because i have a very reliable connection and i race in Masters Of Endurance for years and never had this problem can someone help?
I have the same problem, have not tested this morning, bust last night me and my team mate got dc all the time. Its something with the server I guess.
Better hope it works today
Me too the last two weekends in the evenings, I'm with Tiscali and my bet would be some sort of packet shaping being introduced as the other week there was a major outage and ever since this have encountered problems at certain times.
Have you tested it today, if it`s more stable?
Well i normally have not any issue with CTRA. But recently I have these weird drop outs. Dunno why. This also happens to the ZWR server. I think they are on the same server bcus ZWR and CTRA is hosted by UKCT. I did some cheking but I cant find the fault on mine side. But I seriously dont think your server is the issue but weird conections from other racers. But it does seems to be more frequent now then it used to be.

@ edit, coming to think of it, last night we had several knock outs on our server as well. The normal guys timed out but there were several who timed out aswell. LFS world having probs currently ????
#6 - SamH
I've spent the morning watching connections to the server, and also watching SQL traffic etc. I haven't yet been able to detect any problems. The server's connection to the net seems to be excellent, and everything in the garden smells rosey.

That doesn't mean that there isn't a problem.. just that I haven't found one yet.

If you're having connection problems with the CTRA servers, try opening a CMD window and typing "ping raceauthority.com -t" without the quotes. Keep an eye on the responses over 10 or 15 mins, and note the highest and lowest pings you get. Let me know what they are.

Here are the results I got over a minute or so:

C:\>ping raceauthority.com -t
Pinging raceauthority.com [77.74.194.249] with 32 bytes of data:
Reply from 77.74.194.249: bytes=32 time=27ms TTL=117
Reply from 77.74.194.249: bytes=32 time=16ms TTL=117
Reply from 77.74.194.249: bytes=32 time=15ms TTL=117
Reply from 77.74.194.249: bytes=32 time=15ms TTL=117
Reply from 77.74.194.249: bytes=32 time=16ms TTL=117
Reply from 77.74.194.249: bytes=32 time=15ms TTL=117
Reply from 77.74.194.249: bytes=32 time=14ms TTL=117
Reply from 77.74.194.249: bytes=32 time=17ms TTL=117
Reply from 77.74.194.249: bytes=32 time=16ms TTL=117
Reply from 77.74.194.249: bytes=32 time=14ms TTL=117
Reply from 77.74.194.249: bytes=32 time=15ms TTL=117
Reply from 77.74.194.249: bytes=32 time=14ms TTL=117
Reply from 77.74.194.249: bytes=32 time=15ms TTL=117
Reply from 77.74.194.249: bytes=32 time=16ms TTL=117
Reply from 77.74.194.249: bytes=32 time=16ms TTL=117
Reply from 77.74.194.249: bytes=32 time=15ms TTL=117
Reply from 77.74.194.249: bytes=32 time=14ms TTL=117
Reply from 77.74.194.249: bytes=32 time=19ms TTL=117
Reply from 77.74.194.249: bytes=32 time=14ms TTL=117
Reply from 77.74.194.249: bytes=32 time=17ms TTL=117
Reply from 77.74.194.249: bytes=32 time=15ms TTL=117
Reply from 77.74.194.249: bytes=32 time=15ms TTL=117
Reply from 77.74.194.249: bytes=32 time=15ms TTL=117
Reply from 77.74.194.249: bytes=32 time=15ms TTL=117
Reply from 77.74.194.249: bytes=32 time=15ms TTL=117
Reply from 77.74.194.249: bytes=32 time=15ms TTL=117
Reply from 77.74.194.249: bytes=32 time=16ms TTL=117
Reply from 77.74.194.249: bytes=32 time=15ms TTL=117
Reply from 77.74.194.249: bytes=32 time=14ms TTL=117
Reply from 77.74.194.249: bytes=32 time=16ms TTL=117
Reply from 77.74.194.249: bytes=32 time=16ms TTL=117
Reply from 77.74.194.249: bytes=32 time=16ms TTL=117
Reply from 77.74.194.249: bytes=32 time=14ms TTL=117
Reply from 77.74.194.249: bytes=32 time=16ms TTL=117
Reply from 77.74.194.249: bytes=32 time=16ms TTL=117
Reply from 77.74.194.249: bytes=32 time=14ms TTL=117
Reply from 77.74.194.249: bytes=32 time=24ms TTL=117
Reply from 77.74.194.249: bytes=32 time=17ms TTL=117
Reply from 77.74.194.249: bytes=32 time=15ms TTL=117
Reply from 77.74.194.249: bytes=32 time=15ms TTL=117
Reply from 77.74.194.249: bytes=32 time=15ms TTL=117
Reply from 77.74.194.249: bytes=32 time=14ms TTL=117
Reply from 77.74.194.249: bytes=32 time=15ms TTL=117
Reply from 77.74.194.249: bytes=32 time=14ms TTL=117
Reply from 77.74.194.249: bytes=32 time=14ms TTL=117
Reply from 77.74.194.249: bytes=32 time=17ms TTL=117
Reply from 77.74.194.249: bytes=32 time=16ms TTL=117
Reply from 77.74.194.249: bytes=32 time=18ms TTL=117
Reply from 77.74.194.249: bytes=32 time=17ms TTL=117
Reply from 77.74.194.249: bytes=32 time=15ms TTL=117
Reply from 77.74.194.249: bytes=32 time=17ms TTL=117
Reply from 77.74.194.249: bytes=32 time=15ms TTL=117
Reply from 77.74.194.249: bytes=32 time=16ms TTL=117
Reply from 77.74.194.249: bytes=32 time=17ms TTL=117
Reply from 77.74.194.249: bytes=32 time=17ms TTL=117
Reply from 77.74.194.249: bytes=32 time=14ms TTL=117
Reply from 77.74.194.249: bytes=32 time=25ms TTL=117
Reply from 77.74.194.249: bytes=32 time=15ms TTL=117
Reply from 77.74.194.249: bytes=32 time=16ms TTL=117
Reply from 77.74.194.249: bytes=32 time=15ms TTL=117
Reply from 77.74.194.249: bytes=32 time=15ms TTL=117
Reply from 77.74.194.249: bytes=32 time=15ms TTL=117
Reply from 77.74.194.249: bytes=32 time=16ms TTL=117
Reply from 77.74.194.249: bytes=32 time=15ms TTL=117
Reply from 77.74.194.249: bytes=32 time=15ms TTL=117
Reply from 77.74.194.249: bytes=32 time=15ms TTL=117
Reply from 77.74.194.249: bytes=32 time=14ms TTL=117
Reply from 77.74.194.249: bytes=32 time=19ms TTL=117
Reply from 77.74.194.249: bytes=32 time=14ms TTL=117
Reply from 77.74.194.249: bytes=32 time=37ms TTL=117
Reply from 77.74.194.249: bytes=32 time=16ms TTL=117
Reply from 77.74.194.249: bytes=32 time=15ms TTL=117
Reply from 77.74.194.249: bytes=32 time=16ms TTL=117
Reply from 77.74.194.249: bytes=32 time=17ms TTL=117
Reply from 77.74.194.249: bytes=32 time=15ms TTL=117
Reply from 77.74.194.249: bytes=32 time=15ms TTL=117
Reply from 77.74.194.249: bytes=32 time=16ms TTL=117
Reply from 77.74.194.249: bytes=32 time=16ms TTL=117
Reply from 77.74.194.249: bytes=32 time=16ms TTL=117
Reply from 77.74.194.249: bytes=32 time=17ms TTL=117
Reply from 77.74.194.249: bytes=32 time=22ms TTL=117
Reply from 77.74.194.249: bytes=32 time=15ms TTL=117
Reply from 77.74.194.249: bytes=32 time=15ms TTL=117
Reply from 77.74.194.249: bytes=32 time=15ms TTL=117
Reply from 77.74.194.249: bytes=32 time=16ms TTL=117
Reply from 77.74.194.249: bytes=32 time=14ms TTL=117
Reply from 77.74.194.249: bytes=32 time=18ms TTL=117
Reply from 77.74.194.249: bytes=32 time=16ms TTL=117
Reply from 77.74.194.249: bytes=32 time=16ms TTL=117
Reply from 77.74.194.249: bytes=32 time=14ms TTL=117

Hiya Sam.

NOthing wrong with your ping. Its between 17/33 ms. With a highset of 33 and looking at averag its between19 and 21. Good solid stable connection. But i seriously think it hasnt got to do with UKCT server. It seems when LFS world is giving connection problem then there are these drop outs. Like I said i normally dont drop out at all. Only when I cant get or have a high response time on LFS world.

Last night I noticed the same. High response time from LFS world and people on HR server were timing out big time. I could connect to LFS world but it was very slow. When that is happening I can expect drop outs on servers. Not just HR but others as well.
So you are saying that the problem might be the LFS server itself?
Overload?
I am sure it has something to do with the isp, i have this problem at home on my ADSL line, but at my workplace with the same computer it´s just fine
i know this does not help very much, but i haven´t had any problems with the ctra-servers ever....
Neighter have I, I think I`v DC`d 4-5 times thorugh the last months, but then that night I DC`d all the time Tried other games and downloaded stuff, everything looked fine here too. But it seems to be better now, strange
#12 - Nobo
Last week i experienced some mass disco's on race 1 (6-7 drivers disco'ed). Just 2-3 times, one time i have been affected.
the reason I think it's the ISP packet shaping is it only occurs during weekends with me after 7pm as if someone flicked a switch and it does not matter how busy the server is.

It seems some ISP's are becoming rather aggressive again with regards to this and it's been happening since Tiscali had a rather large outage that lasted the best part of a whole day about two weeks ago, mabe it's just a tactic they have decided to employ until they can sort out their hardware.

FGED GREDG RDFGDR GSFDG