I use wireless to my laptop yes. The router is a Thomson Alcatel ST780. And i have to say that it is a peice of crap. The strange thing is that i have no connection or speed problems eccept for this game.
Can it be a port forwarding problem or something? its really strange that some pings is correct but most is lost.
I feel like sending a small package of anthrax to my ISP...
connection error...
I have a similar problem with connecting to servers. With my old computer and old ISP LFS ran perfectly.
Now i have updated both comp and ISP, and moved to a new apartment.
Im running LFS on a 2x2.4ghz intel with 4 gig ram and Geforce 9600M GT.
I have a 24mbit ADSL Line, so bandwidth is no broblem.
When trying to connect to a server i almost never get a connection. It fails at different points of the access to.
Did not recieve guest info.
Fails to load skins,
Did not recieve OK from server.
When i finally get connected to a server it runs perfectly though. No lag och disconnections. Its only connecting to servers that almost always fails.
And if a connection is successful the connection process is really slow... takes almost 2 min to get connected.
When i run the tests i see i have major packet loss. I really miss LFS and need help to get it running.
Pinging master.liveforspeed.net [213.40.20.2] with 32 bytes of data:
Reply from 213.40.20.2: bytes=32 time=82ms TTL=48
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 213.40.20.2:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 82ms, Maximum = 82ms, Average = 82ms
Tracing route to master.liveforspeed.net [213.40.20.2]
over a maximum of 30 hops:
1 38 ms 99 ms 99 ms dsldevice.lan [192.168.1.254]
2 * * 4180 ms 10.244.129.33
3 59 ms 99 ms * 195.54.125.45
4 36 ms 100 ms * ti3006d320-ge3-0-0.ti.telenor.net [146.172.109.1
3]
5 * * * Request timed out.
6 * * * Request timed out.
7 * 2391 ms 64 ms ti3004b300-ae0-0.ti.telenor.net [146.172.105.42]
8 88 ms 45 ms 55 ms 212.162.10.9
9 133 ms 144 ms 87 ms ae-31-51.ebr1.Berlin1.Level3.net [4.68.108.30]
10 212 ms * * ae-1-100.ebr2.Berlin1.Level3.net [4.69.133.174]
11 78 ms 90 ms 107 ms ae-3.ebr2.Dusseldorf1.Level3.net [4.69.133.146]
12 2671 ms 689 ms * ae-2.ebr1.Amsterdam1.Level3.net [4.69.133.89]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * 3611 ms 75 ms lfs4.hosted.netline.net.uk [213.40.20.2]
Trace complete.
# Copyright (c) 1993-1999 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
127.0.0.1 localhost
im in big need of help!
Now i have updated both comp and ISP, and moved to a new apartment.
Im running LFS on a 2x2.4ghz intel with 4 gig ram and Geforce 9600M GT.
I have a 24mbit ADSL Line, so bandwidth is no broblem.
When trying to connect to a server i almost never get a connection. It fails at different points of the access to.
Did not recieve guest info.
Fails to load skins,
Did not recieve OK from server.
When i finally get connected to a server it runs perfectly though. No lag och disconnections. Its only connecting to servers that almost always fails.
And if a connection is successful the connection process is really slow... takes almost 2 min to get connected.
When i run the tests i see i have major packet loss. I really miss LFS and need help to get it running.
Pinging master.liveforspeed.net [213.40.20.2] with 32 bytes of data:
Reply from 213.40.20.2: bytes=32 time=82ms TTL=48
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 213.40.20.2:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 82ms, Maximum = 82ms, Average = 82ms
Tracing route to master.liveforspeed.net [213.40.20.2]
over a maximum of 30 hops:
1 38 ms 99 ms 99 ms dsldevice.lan [192.168.1.254]
2 * * 4180 ms 10.244.129.33
3 59 ms 99 ms * 195.54.125.45
4 36 ms 100 ms * ti3006d320-ge3-0-0.ti.telenor.net [146.172.109.1
3]
5 * * * Request timed out.
6 * * * Request timed out.
7 * 2391 ms 64 ms ti3004b300-ae0-0.ti.telenor.net [146.172.105.42]
8 88 ms 45 ms 55 ms 212.162.10.9
9 133 ms 144 ms 87 ms ae-31-51.ebr1.Berlin1.Level3.net [4.68.108.30]
10 212 ms * * ae-1-100.ebr2.Berlin1.Level3.net [4.69.133.174]
11 78 ms 90 ms 107 ms ae-3.ebr2.Dusseldorf1.Level3.net [4.69.133.146]
12 2671 ms 689 ms * ae-2.ebr1.Amsterdam1.Level3.net [4.69.133.89]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * 3611 ms 75 ms lfs4.hosted.netline.net.uk [213.40.20.2]
Trace complete.
# Copyright (c) 1993-1999 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
127.0.0.1 localhost
im in big need of help!
FGED GREDG RDFGDR GSFDG