Hi guys , going LD alot lately. Like sometimes 10 times in 15 mins.... I did a trace, i can see the timed out part which cant be good, any ideas ? I have 30 mb Broadband and dont have any other problems with any other games.


Tracing route to host225.ea.com [63.117.29.225]
over a maximum of 30 hops:

1 4294967267 ms 6 ms 4294967267 ms 10.108.132.1
2 1 ms 4294967270 ms 4294967270 ms pete-core-1b-ae1-1335.network.virgin
media.net [81.100.32.209]
3 4294967282 ms <1 ms 5 ms popl-bb-1b-as6-0.network.virginmedia.net [
212.43.163.221]
4 7 ms 38 ms 4294967275 ms popl-bb-1a-ae0-0.network.virginmedia.net [
213.105.174.229]
5 71 ms 4294967281 ms 6 ms 195.50.91.69
6 4294967283 ms 4294967281 ms 5 ms ae-52-52.csw2.London1.Level3.net [4.
69.139.120]
7 5 ms 4294967293 ms 4294967285 ms ae-57-222.ebr2.London1.Level3.net [4
.69.153.133]
8 117 ms 58 ms 71 ms ae-44-44.ebr1.NewYork1.Level3.net [4.69.137.78]

9 58 ms 79 ms 80 ms ae-4-4.ebr1.NewYork2.Level3.net [4.69.141.18]
10 78 ms 88 ms 86 ms ae-1-51.edge2.NewYork2.Level3.net [4.69.138.195]

11 68 ms 82 ms 84 ms 4.68.111.138
12 69 ms 50 ms 53 ms 0.ae3.XT2.NYC4.ALTER.NET [152.63.16.186]
13 68 ms 68 ms 65 ms 0.so-5-2-0.XT2.DCA5.ALTER.NET [152.63.0.185]
14 70 ms 140 ms 66 ms 0.so-6-0-0.UR2.MTC4.ALTER.NET [152.63.38.242]
15 65 ms 67 ms 66 ms 206.112.176.42
16 74 ms 75 ms 62 ms 206.112.184.37
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 *

Do you get the time outs all the time or only when you are unable to connect?

A request time out may not mean there is a problem, many devices will not reply to ICMP requests and you get a time out instead. But normal traffic flows through just fine.

If it's intermittent and sometimes those hops do reply and sometimes they don't. Then it could be a sign of a problem (assuming the traffic is taking the same route).

You'll also want to look for high latency.

Also the tool you are using seems to be giving odd results. "4294967285 ms" is probably not real. It usually times out after 1500 ms I believe. 4294967285 ms I think is about 50 days.

yep always times out... i have played DAOC for years and never had a problem before. I am really at a loss, game is unplayable.

I would not worry about line 17 - 24 saying "* * * Request timed out". 206.112.184.37 is probably the last stop before hitting the game servers and most game servers do not respond to pings/traces. So when the trace hits the game server it will time out.


Ravyn is correct that things seem messed up. 4294967267 ms is 49.7 days.


I googled 4294967267 ms, looking for others that may have the same kind of trouble, and found a link where a person fixed the strange number popping up by restarting their computer.





gl

 

-----signature-----

its been talked about quite a few times, but when Mythic moved over to its new
ISP, and that ISP uses Alter.net, the game became harder to connect to, and issues
all the time with connections.

Its ALTER.NET that is causing the problem.. Wish SPRINT or whatever ISP Mythic is using
would route around that damn ISP..

They went almost 2 weeks a few years ago with Ping requests timing out. That there was a
switch issue, and that it needed to be replaced.

Finally after they replaced the switch, pinging was down to around 50ms.. Amazing.

 

-----signature-----

All its doing is showing the hops. Depending on whos network (ISP) that particular IP falls under, is who you want to contact to fix the issue. The last one that went through fine is who you should contact and give them the IP your trying to reach and they can find it and find out what the issue is. All traceroute (tracert) is doing is showing you the hops from you to the destination server. The first time out is your problem the one before that is who you need to contact. Could talk to your ISP too maybe they an IT guy you can talk to or a network guy.

 

-----signature-----

This isn't entirely accurate. "* * * Request timed out. " simply indicates the router/network you've encountered has ICMP blocked, which isn't indicative of a specific problem.

With intermittent connections it's very difficult to troubleshoot, as the connection works for a while and then stops. The traffic is getting there and back for a period of time, and then stops. It's possible one of the routers/firewalls in the chain is closing the connection or re-routing the traffic for whatever reason. Very difficult to identify the cause from either ends, especially if you're not in the US.

Contact your service provider to see if they can help identify the issue. The game runs on both TCP and UDP (TCP Ports: 1280, 10500-10510, 10622 UDP Ports: 1024-65535 and almost always to the 63.117.29.XXX network)

As a note: I've been having issues for the past month or two with an error of "our client has stopped receiving messages from the server", and I'm still having the issues especially when I open multiple accounts. I've watched my firewall and machine logs, and i can clearly see the traffic go out then simply stop coming back in. Both my ISP and EA were absolutely useless to try and get it resolved.

Good luck to ya and let me know if you get it fixed, as it may help me too.

 

-----signature-----

That first hop is a dsl modem or cable modem or firewall or router sitting in your house or it should be. The address of the first hop is also a private IP address and the address falls in the range of one of the following so that's some confirmation I'm correct...

10.0.0.0 - 10.255.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.255.255

Are you sure you don't have some kind of funky problem with your network equipment? I'd check any firewalls, wireless access points, modems, etc. that you have. You might want to restart your network hardware and then retry the tracert to see if that helps.

 

-----signature-----