|
|
|
Noob
Group: Forum Members
Last Login: 2/16/2008 4:05 PM
Posts: 1,
Visits: 4
|
|
ok so heres the story
i recently swithced from DSL to FIOS
and directly connected to dsl to wirelessly connected to FIOS
i never had problems with being directly connected to fios. and its not the internet seeing as how fios is better then dsl
so heres the problem
im suffering lag in games when i play, i dont know what it is
i mean nothing else is effected by lag like file transfering or downloading
only in games i lag.
i think it maybe with the signal spikes
my signal constantly changes from 54 to 34 to 48 mbps during games.
anyone help me?
|
|
|
|
|
Member
Group: Forum Members
Last Login: 8/16/2008 6:07 PM
Posts: 14,
Visits: 17
|
|
Try these:
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.
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.
|
|
|
|
