Random disconnects from ICO lobby

Ok, here's my problem.

I have polish retail version installed with english language and updated through Impulse to 1.05.028

I've got only windows firewall runing with sins added to exceptions, no router on the way from ISP.

My computer IP is the one I get directly from ISP.

I can login to ICO (but 50% I can't - seems random). I can get to lobby and see users / send messages,

then after a minute or more I stop getting feedback from ICO and after that I get 'disconnected from ironclad online'

It happens every time.

If I'm lucky, right after loggin in, I can quickly find and join to a game and it plays fine. I'm only having trouble with ICO.

Any ideas anyone?

2,308 views 7 replies
Reply #1 Top
How is your internet connection's stability, do you have any issues with other online games? Also, does your ISP have any record of interfering with peer-to-peer traffic?
Reply #2 Top
Try performing a "trace" to ICO from your location.

At the command-prompt, type "tracert" and the IP of ICO (I haven't played the game in a while but I seem to remember this as ICO's IP) 38.98.152.153.

To open the command-prompt, go to START >> RUN >> cmd (enter "cmd" in the RUN box) and hit enter.


eg.

c:\tracert 38.98.152.153

(it doesn't matter if your "prompt" isn't at the same location as in my example, the "tracert" command is covered by the system's "path" statement and can therefore be entered at the command-prompt at any location)


Running said "trace" to ICO, especially immediately after being disconnected should shed some light as to the location of a "bad hop" along the route to ICO.


Another thing to try would be to run a ping-test to your ISP's local gateway IP. (running IPCONFIG from the same command-prompt will show you a "default gateway" and since your computer's IP comes directly from the ISP with no router involved you can ping-test the "default gateway" like this:)

ping -t xxx.xxx.xxx.xxx (that is the default gateway's IP) > pingtest.txt

The above command will start a ping-test to your ISP's router in your area (recording the info in the pingtest.txt file it's being piped to) and will keep going until you kill it by hitting CTRL-C.

I would recommend letting the ping-test run for at least 3-4 minutes after an ICO disconnection in order to get some solid data. This ping-test will help shed light on whether the connection drops are occuring close to home and need to be looked at by your ISP.



thanks,

the Monk
Reply #3 Top
Ok, I did a clean Win XP SP2 install.
I have only Windows firewall at the moment.
I run ping -t to ICO server the_Monk mentioned with ping ranging 130-250ms, no timeouts
Logged in to ICO (had to try several times).
In lobby I tried constantly to get info on myself (latency info / games played)
Ater several attempts my info showed 'not logged in'
Instantly I run tracert:

1 6 ms 8 ms 7 ms 10.152.128.1
2 * * * Upłynął limit czasu żądania.
3 * * * Upłynął limit czasu żądania.
4 12 ms 10 ms 11 ms pl-waw01a-rd1-g-2-0-0.aorta.net [213.46.178.13]
5 42 ms 44 ms 44 ms uk-lon01a-rd3-s-13-0.aorta.net [213.46.160.137]
6 41 ms 41 ms 41 ms uk-lon01a-ri3-s-0-1.aorta.net [213.46.174.162]
7 43 ms 45 ms 45 ms 213.46.174.134
8 43 ms 52 ms 42 ms te2-1.3493.mpd02.lon01.atlas.cogentco.com [130.117.2.18]
9 115 ms 113 ms 123 ms te4-1.ccr04.jfk02.atlas.cogentco.com [66.28.4.253]
10 124 ms 114 ms 116 ms te2-2.ccr02.bos01.atlas.cogentco.com [154.54.5.242]
11 116 ms 143 ms 132 ms gi11-0-0.core01.bos01.atlas.cogentco.com [154.54.5.21]
12 130 ms 131 ms 131 ms po6-0.core01.cle01.atlas.cogentco.com [66.28.4.158]
13 136 ms 140 ms 132 ms po6-0.core01.tol01.atlas.cogentco.com [66.28.4.222]
14 134 ms 151 ms 134 ms po6-0.core01.dtw04.atlas.cogentco.com [154.54.25.110]
15 132 ms 136 ms 135 ms po4-0.core01.dtw03.atlas.cogentco.com [154.54.25.61]
16 135 ms 138 ms 136 ms vl3504.na01.b015487-0.dtw03.atlas.cogentco.com [38.20.36.214]
17 143 ms 137 ms 137 ms stardock-corporation.demarc.cogentco.com [38.99.219.166]
18 138 ms 150 ms 139 ms 38.98.152.153


I was pinging ICO all the time and got 130-250ms and no timeouts

Other MP games are working fine. Torrents, emule, hamachi - no problem.
For some reason ICO server is dropping my client, and if I'm not mistaken ICO lobby is not P2P based ...
Reply #4 Top

A latency between 130 and 250 might be too high for ICO to "see" you as logged-in?

Now that you've got the data (and it seems like your connection is fine on your end) I'd suggest contacting [email protected] in order to find out if there is anything they can tell you. Their server may have a shorter "timeout".

BTW, the "latency" reported on the player-tab while connected to ICO is wildly inaccurate (in my experience).

thanks,

the Monk
Reply #5 Top
Well , I contacted support. Let wait and see if they come up with something
Reply #6 Top
I think I found the solution
In the end I guess it's ISP related.
I gave it a shot and defined a new route using 'route' command to ICO server.
Well, it's working now - over an hour in lobby without a disconnect.

Monk, kryo, any explanations?
Reply #7 Top

By the looks of your trace, IC/SD might want to look into the routes to ICO as defined by cogentco. Seems like these routes might be causing problems for others as well.

the Monk