RE: Xbox 360 online LAG

DEADLY-TDG- — Fri, 30 May 2008 16:23:14 GMT

Sounds fine to me, try a different ISP. Do a couple of tests first though:

(Copied from another site, got no link for it though)

The best way to measure packet loss using ping is to send a large number of pings to an IP address, and then look for failed responses to those pings. For instance, if you ping something 50 times in a rapid fashion, you can measure the number of failed responses and use this as an estimate of "packet loss." Anything over five percent is probably something to be concerned about.

On a Windows machine, this can be accomplished by using the following command at the command prompt:

Ping -n 50 (IP Address or domain name [www.website.com])>

The "–n" tells ping to send a set number of pings, and "50" is the number to send.

Afterwards, you will get a summary of the test that includes the number lost and a percentage:

Ping statistics for 199.181.132.250:

Packets: Sent = 6, Received = 6, Lost = 0 (0%)

Approximate round trip times in milliseconds:

Minimum = 26ms, Maximum = 29ms, Average = 27ms

If you see a very high average roundtrip time (greater then 100ms), this will also cause you to experience slow network downloads.

One way to try to eliminate certain parts of the network that may be the cause of packet loss is to do the ping test along various segments along the path. The first place I normally start testing is the local "default gateway." This is the first router that all your data is transmitted to on the network. If there is high packet loss on this segment, then the problem is localized to your service provider's network.

You can find the IP address of your default router by typing in the "ipconfig" command at your Windows command prompt. This will display the following:

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix_: domainname.com
IP Address. . . . . . . . . . . . : 192.168.2.189
Subnet Mask . . . . . . . . . . . : 255.255.252.0
Default Gateway . . . . . . . . . : 10.10.0.1

What you are looking for is the default gateway IP address. In the example above, it is 10.10.0.1.

Using Trace route

Trace routes can be run by using the trace route command at the Windows command prompt. On Windows XP this is:

tracert (IP Address or Hostname)

While the output doesn't show you packet loss, it will show you if there are slow-responding routers along the path.

The output will show you the response time of all the routers. The following is an example:

1. 5 ms 2 ms 3 ms malibu.domain.com [10.10.0.1]
2. 10 ms 6 ms 7 ms 10.60.0.6
3. 9 ms 7 ms 7 ms 10.20.0.1
4. 6 ms 7 ms 7 ms x130.cd9e68.sj.concentric.net [205.158.104.130]
5. 7 ms 7 ms 8 ms ge9-0.dcr2.dc-fremont-ca.us.xo.net [205.158.60.169]
6. 7 ms 7 ms 7 ms ge2-0.dcr1.dc-fremont-ca.us.xo.net [65.106.2.205]
7. 10 ms 7 ms 8 ms p5-1-0-2.rar2.sanjose-ca.us.xo.net [65.106.2.153]
8. 10 ms 9 ms 11 ms p1-0.ir1.paloalto-ca.us.xo.net [65.106.5.178]
9. 9 ms 10 ms 15 ms 206.111.12.114.ptr.us.xo.net [206.111.12.114]
10. 9 ms 10 ms 10 ms svl-core-03.inet.qwest.net [205.171.205.29]
11. 29 ms 28 ms 29 ms stl-core-02.inet.qwest.net [205.171.5.85]
12. 30 ms 29 ms 29 ms sea-edge-03.inet.qwest.net [205.171.26.42]
13. * * * Request timed out.
14. * * * Request timed out.
15. 28 ms 28 ms 29 ms sam.abcnews.go.com [199.181.132.250]

If you see trace route roundtrip times along the path greater than 100ms (1/10th of a second), this can cause slow transfer times over the network.

From the above, you can see that data travels along lots of different networks (XO, Qwest, ABC). This is part of the beauty of the Internet. The downside is that it places the ability to resolve slow response times out of the hands of individual users. The best place to start is to make sure that there is not packet loss between yourself and your service provider.

Xbox 360 online LAG

TW Steimy — Fri, 25 Apr 2008 10:21:32 GMT

Just wanted to see what my best course of action may be. First i will lay out all the specs:

Computer running Windows XP Pro

2GB RAM

2.13GHz Core2Duo processor overclocked to 2.4GHz

Linksys WRT54GS Router

Linksys WGA54G Wireless adapter

I have the connection currently set up as DHCP, with both Xbox 360 ports forwarded and the DMZ open to the Xbox 360 IP address.

I was considering a change to a static IP but am not sure if any of this is doing me any good as far as hosting games (Rainbow Six Vegas 2 to be exact)

My connection is an 8MB cable connection, last test i ran i was roughly 7890 down and 492 up. But i still get lag at about 13-14 people in a room. Although i do understand this could be due to thier bad connection as much as it is mine.

so any thoughts and ideas would be great.

EndLagNow.org Forums / EndLagNow.org Forums / How to Fight Lag / Xbox 360 online LAG / Latest Posts

RE: Xbox 360 online LAG

Xbox 360 online LAG