Quote from antman2006 :

I am also having same problems I can bearly play on any servers. Kind of sucks since I bought LFS to play online also with my new wheel but I can't stay in servers for 5 - 15min. The bars down the bottom left (Net graph?), one of them would rise untill it his top then I would get D/Cd. I would also get errors like "Can't get track info" etc and I would try again and i will be like "Can't get guest info" then I would try once more and I would get in for 15min or so. Really frustrating.

I hope someone cause sort out the problem as judging by this thread its a big one.

that's exactly the same problem that I'm having... if you can, try find some Australia and NZ server to join, because everything should be sweet if we join those servers. (actually bump into a few other players yesterday who said the same thing)

I wonder if that's because we got crap connection~? or something gone wrong with the system itself~?

I think it has to do with how our data is routed throughout the world. A lot of the time i can't even connect to the master server. Here is a tracert to the lfs site. 330 is unusually high. It should be similar to servers in america which are between 220 and 280 usually.

1 <1 ms <1 ms <1 ms
2 1 ms 1 ms 1 ms RTA1320.home
3 57 ms 56 ms 56 ms lo0.akl-grafton-bba2.ihug.net
4 57 ms 57 ms 58 ms gi1-24.akl-grafton-bdr1.ihug.net
5 59 ms 56 ms 58 ms ip-static-202-147-45-73.asianetcom.net[202.147.45.73]
6 186 ms 183 ms 181 ms unknown.Level3.net [64.152.102.129]
7 181 ms 182 ms 182 ms unknown.Level3.net [64.152.102.129]
8 216 ms 209 ms 211 ms ae-1-53.bbr1.SanJose1.Level3.net [4.68.123.65]
9 330 ms 333 ms 332 ms so-2-0-0.mp1.Manchesteruk1.Level3.net [4.68.128.77]
10 363 ms 362 ms 419 ms so-10-0.hsa2.Manchesteruk1.Level3.net [4.68.113.106]
11 335 ms 330 ms 335 ms 212.187.136.158
12 * * * Request timed out.
13 336 ms 354 ms 334 ms cyclone.core.netline.net.uk [213.40.192.249]
14 364 ms 369 ms 365 ms liveforspeed.net [213.40.196.93]

This is to a german server i see hosts some lfs games.

1 <1 ms <1 ms <1 ms
2 1 ms 1 ms 1 ms RTA1320.home
3 70 ms 71 ms 70 ms lo0.akl-grafton-bba2.ihug.net
4 69 ms 67 ms 82 ms gi1-24.akl-grafton-bdr1.ihug.net
5 66 ms 67 ms 59 ms ip-static-202-147-45-73.asianetcom.net [202.147.45.73]
6 375 ms 257 ms 190 ms po0-0.gw1.sjc1.asianetcom.net [202.147.50.129]
7 223 ms 232 ms 235 ms po0-2.gw1.lax1.asianetcom.net [202.147.61.137]
8 395 ms 219 ms 224 ms [4.78.192.25]
9 201 ms 206 ms 192 ms ae-1-51.bbr1.LosAngeles1.Level3.net [4.68.102.1]
10 391 ms 418 ms 355 ms ae-1-0.bbr1.Frankfurt1.Level3.net [212.187.128.30]
11 349 ms 389 ms 388 ms ge-10-2.ipcolo2.Frankfurt1.Level3.net [4.68.118.138]
12 352 ms 363 ms 355 ms ge-4-0.edge1.fra3.de.inetbone.net [62.67.32.140]
13 395 ms 387 ms 389 ms decix.bellaxa.net [80.81.192.21]
14 388 ms 391 ms 381 ms ge-1-1-991.core2.rb.mainlab.net [80.242.131.18]
15 380 ms 395 ms 387 ms goodserver.de [193.221.121.11]

Pings of over 300 are far too high for any country.

Yeah on CSS etc US servers usually 200 - 250 ping same if you ping to google.com etc.

I just got my mate to do the same and his pings were around 320.

to all kiwis in here, should we try our luck contacting our ISP and see if the port LFS uses have been blocked~?
although I don't quite know if the port is the problem if we can access the OZ server, or perhaps they're on a different port~?

Wouldn't the port being blocked meaning we can't connect at all? Not play fine for 5 - 15 min then get D/Cd ?

Do LFS Devs looks at these topics? (also this one http://www.lfsforum.net/showthread.php?t=6940)