The lag depends on the path between you and the servers/the people you play against. Try this:
Start -> Run -> Type "cmd" and hit enter. In the command window type "tracert ico.stardock.com". If there's any hops that don't respond or that have really high numbers (>200ms) that's the problem. Note that you probably will start timing out once you hit our firewall, but that's normal.
when the box opens in the area that allows for text type cmd and then hit enter
In the command window type "tracert ico.stardock.com". without the "
below is what it should be like with a cable connection (I get complates about lag from people when I host with these numbers)
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Mike>tracert ico.stardock.com
Tracing route to ico.stardock.com [38.98.152.153]
over a maximum of 30 hops:
1 * * * Request timed out.
2 7 ms 6 ms 6 ms ge-8-23-ur01.christianst.pa.panjde.comcast.net [68.85.195.81]
3 7 ms 6 ms 6 ms po-10-ur01.columbsblvd.pa.panjde.comcast.net [68.86.208.57]
4 11 ms 11 ms 6 ms po-10-ur02.greenwayave.pa.panjde.comcast.net [68.86.208.53]
5 8 ms 6 ms 7 ms po-10-ur01.greenwayave.pa.panjde.comcast.net [68.85.192.121]
6 8 ms 8 ms 6 ms po-20-ar01.wallingford.pa.panjde.comcast.net [68.86.208.49]
7 11 ms 15 ms 28 ms te-8-3-ar01.401nbroadst.pa.panjde.comcast.net [68.86.90.10]
8 10 ms 9 ms 9 ms pos-0-7-0-0-cr01.philadelphia.pa.ibone.comcast.net [68.86.85.13]
9 11 ms 13 ms 12 ms COMCAST-IP.edge1.NewYork2.Level3.net [4.71.186.22]
10 13 ms 12 ms 11 ms xe-8-2-0.edge1.NewYork2.Level3.net [4.71.186.21]
11 13 ms 11 ms 11 ms ae-1-69.edge1.NewYork1.Level3.net [4.68.16.14]
12 * 17 ms * COGENT-COMM.car2.NewYork1.Level3.net [4.68.111.46]
13 16 ms 23 ms 16 ms te9-2.mpd03.jfk02.atlas.cogentco.com [154.54.5.209]
14 16 ms 15 ms 16 ms te8-1.ccr04.jfk02.atlas.cogentco.com [154.54.24.138]
15 42 ms 44 ms 43 ms te4-3.ccr02.ord01.atlas.cogentco.com [154.54.1.190]
16 43 ms 42 ms 42 ms vl3499.ccr02.ord03.atlas.cogentco.com [154.54.5.10]
17 43 ms 42 ms 43 ms gi15-0-0.core01.ord03.atlas.cogentco.com [154.54.3.245]
18 53 ms 52 ms 52 ms po2-0.core01.dtw03.atlas.cogentco.com [154.54.2.246]
19 53 ms 53 ms 52 ms vl3504.na01.b015487-0.dtw03.atlas.cogentco.com [38.20.36.214]
20 55 ms 55 ms 54 ms stardock-corporation.demarc.cogentco.com [38.99.219.166]
21 54 ms 57 ms 54 ms 38.98.152.153
Trace complete.
C:\Documents and Settings\Mike>
Tracing route to ico.stardock.com [38.98.152.153]
over a maximum of 30 hops:
1 11 ms 25 ms 26 ms d-65-175-202-1.metrocast.net [65.175.202.1]
2 11 ms 12 ms 12 ms core-65-175-142-18.metrocast.net [65.175.142.18]
3 11 ms 11 ms 12 ms blmtnh-vrf-02.metrocast.net [65.175.142.250]
4 11 ms 12 ms 11 ms pos-1-3.gsr.4-3.mnchnhcohba.seg.NET [216.107.222
.185]
5 13 ms 15 ms 15 ms POS4-1.GW8.BOS4.ALTER.NET [157.130.0.93]
6 12 ms 12 ms 16 ms 0.so-4-3-0.XL2.BOS4.ALTER.NET [152.63.17.18]
7 18 ms 19 ms 20 ms 0.so-6-3-0.XL4.NYC4.ALTER.NET [152.63.0.73]
8 23 ms 20 ms 22 ms 0.ge-5-1-0.BR3.NYC4.ALTER.NET [152.63.3.118]
9 49 ms 51 ms 51 ms po15-3.core01.jfk05.atlas.cogentco.com [154.54.1
2.181]
10 * * 49 ms te9-1.mpd01.jfk05.atlas.cogentco.com [154.54.24.
33]
11 48 ms 52 ms 48 ms te9-2.ccr04.jfk02.atlas.cogentco.com [130.117.0.
53]
12 47 ms 48 ms 64 ms te8-3.ccr02.ord01.atlas.cogentco.com [154.54.7.2
06]
13 48 ms 50 ms 47 ms vl3491.ccr02.ord03.atlas.cogentco.com [154.54.6.
210]
14 59 ms 48 ms 47 ms gi9-0-0.core01.ord03.atlas.cogentco.com [154.54.
3.237]
15 56 ms 59 ms 59 ms po2-0.core01.dtw03.atlas.cogentco.com [154.54.2.
246]
16 59 ms 57 ms 59 ms vl3504.na01.b015487-0.dtw03.atlas.cogentco.com [
38.20.36.214]
17 62 ms 87 ms 58 ms stardock-corporation.demarc.cogentco.com [38.99.
219.166]
18 60 ms 61 ms 60 ms 38.98.152.153
Trace complete.
whats your advertised internet connection speed?
maybe that will help us get some insight into your problem
Oh and I said I think other wise all i know is I have cable.
@ dracula7899
Firewalls, especially those SPI-type firewalls on some crappy cable/dsl modem/router combo's or soho routers (dlink, netgear, linksys, etc.) fragment game-data (especially for p2p connections). DISABLE them.
Other firewall software (other than the Windows Firewall which works fine with SINS) also costs network transport "overhead" which means it will increase latency.
Disable all (except for the windows firewall) firewalls and try again.
Also, If your cable/dsl mode isn't JUST a modem and also happens to be acting as a router you will see increased latency in p2p gaming due to "stricter" NAT controls.
Please read my newest guide linked-to from the bottom of the "Technical FAQ" in the sticky in the "Technical" forum.
thanks,
the Monk
Hop 10 had issues, but yeah, overall it's not bad looking and once you get a game going your connection to ICO doesn't really matter. We'll see if we can improve this in some way, though.
8600 cards should be fine. You can play at pretty nice settings (High). That's what I have here at the office. ![]()
Welcome Guest! Please take the time to register with us.
- Richer content, access to many features that are disabled for guests like commenting and posting on the forums.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!