Page 1 of 1
Dropping conection..
Posted: 22 Apr 2010 16:43
by Tarax the Terrible
Had this a few times now.
Laggy then drops connection and I have to reconnect.
Might be a while before I can.
Last time tried others on messenger and they were okay.
Had it where they lost connection and i was okay..
Odd.
Currently kicked out & can't reconnect..
Pinging 82.80.226.92 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 82.80.226.92:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Guess .91 is another machine nearby..
Pinging 82.80.226.91 with 32 bytes of data:
Reply from 82.80.226.91: bytes=32 time=113ms TTL=243
Reply from 82.80.226.91: bytes=32 time=108ms TTL=243
Reply from 82.80.226.91: bytes=32 time=119ms TTL=243
Reply from 82.80.226.91: bytes=32 time=112ms TTL=243
Ping statistics for 82.80.226.91:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 108ms, Maximum = 119ms, Average = 113ms
Ok back now..
about 6 minutes of lost connection where my char was still in the game..
Sucks. Glad hes not dead.
Re: Dropping conection..
Posted: 22 Apr 2010 17:10
by Creed
I tried that too..
And to make things worse, I was trying to see if I could best Agkula.
Which is not very easy, when you don't have any specials going.
Am glad I have noticed that behavior from the server before, that it goes dead from time to time, for no apparent reason.
So I had put a wimpy, and luckily found myself alive in the next room.
But I sure wasn't happy. And I think its quite annoying that it just goes dead now and then.
Fine enough if you browse webpages, but doesn't really work for us who plays.
Re: Dropping conection..
Posted: 22 Apr 2010 17:41
by Knuffel
Tarax, doing a tracert in addition will show where the problem kicks in (or at least narrow it down).
Code: Select all
C:\>tracert 82.80.226.92
Tracing route to genesis.genesismud.org [82.80.226.92]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 2 ms <1 ms 1 ms gw2-no66.tbcn.telia.com []
3 2 ms <1 ms <1 ms s-b1-link.telia.net [213.248.77.45]
4 2 ms 1 ms 1 ms s-bb2-link.telia.net [80.91.252.126]
5 7 ms 4 ms 4 ms kbn-bb2-link.telia.net [80.91.247.163]
6 6 ms 3 ms 2 ms kbn-b3-link.telia.net [80.91.253.204]
7 3 ms 4 ms 9 ms xe-0-3-0.cph10.ip4.tinet.net [77.67.73.113]
8 9 ms 22 ms 9 ms xe-1-3-0.fra21.ip4.tinet.net [89.149.186.37]
9 35 ms 35 ms 4 ms bezeq-gw.ip4.tinet.net [77.67.66.10]
10 13 ms 41 ms 24 ms bzq-179-124-25.static.bezeqint.net [212.179.124.25]
11 19 ms 16 ms 17 ms bzq-179-124-149.static.bezeqint.net [212.179.124.149]
12 54 ms 99 ms 34 ms bzq-179-124-186.static.bezeqint.net [212.179.124.186]
13 9 ms 12 ms 18 ms bzq-25-116-226.static.bezeqint.net [212.25.116.226]
14 25 ms 27 ms 90 ms genesis.genesismud.org [82.80.226.92]
Trace complete.
Especially since 91 and 92 do follow a different route as of hop 9 as you can see below
Code: Select all
C:\>tracert 82.80.226.91
Tracing route to bzq-82-80-226-91.cablep.bezeqint.net [82.80.226.91]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 <1 ms <1 ms 2 ms gw2-no66.tbcn.telia.com []
3 5 ms 1 ms 1 ms s-b2-link.telia.net [80.91.248.199]
4 <1 ms <1 ms <1 ms s-bb1-link.telia.net [213.248.66.5]
5 1 ms 1 ms 1 ms kbn-bb1-link.telia.net [80.91.247.161]
6 18 ms 17 ms 18 ms kbn-b1-link.telia.net [80.91.253.237]
7 68 ms 6 ms 1 ms xe-0-3-0.cph10.ip4.tinet.net [77.67.73.113]
8 31 ms 31 ms 28 ms xe-10-0-0.fra21.ip4.tinet.net [89.149.184.85]
9 34 ms 34 ms 20 ms bezeq-gw.ip4.tinet.net [77.67.66.10]
10 98 ms 35 ms 13 ms bzq-219-189-13.cablep.bezeqint.net [62.219.189.13]
11 4 ms 10 ms 9 ms bzq-219-189-161.cablep.bezeqint.net [62.219.189.161]
12 5 ms 4 ms 12 ms bzq-219-189-154.cablep.bezeqint.net [62.219.189.154]
13 7 ms 96 ms 31 ms bzq-25-116-226.static.bezeqint.net [212.25.116.226]
14 9 ms 18 ms 14 ms bzq-82-80-226-91.cablep.bezeqint.net [82.80.226.91]
Trace complete.
C:\>tracert 82.80.226.92
Tracing route to genesis.genesismud.org [82.80.226.92]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 7 ms 7 ms 6 ms gw2-no66.tbcn.telia.com []
3 <1 ms <1 ms <1 ms s-b1-link.telia.net [213.248.77.45]
4 9 ms 1 ms 1 ms s-bb1-link.telia.net [80.91.254.118]
5 2 ms 3 ms 1 ms kbn-bb1-link.telia.net [213.248.65.142]
6 1 ms 1 ms 1 ms kbn-b3-link.telia.net [80.91.253.204]
7 2 ms 1 ms 1 ms xe-0-3-0.cph10.ip4.tinet.net [77.67.73.113]
8 2 ms 2 ms 6 ms xe-1-3-0.fra21.ip4.tinet.net [89.149.186.37]
9 3 ms 2 ms 1 ms bezeq-gw.ip4.tinet.net [77.67.66.10]
10 4 ms 10 ms 10 ms bzq-179-124-25.static.bezeqint.net [212.179.124.25]
11 7 ms 6 ms 6 ms bzq-179-124-149.static.bezeqint.net [212.179.124.149]
12 9 ms 8 ms 8 ms bzq-179-124-186.static.bezeqint.net [212.179.124.186]
13 28 ms 101 ms 8 ms bzq-25-116-226.static.bezeqint.net [212.25.116.226]
14 80 ms 3 ms 5 ms genesis.genesismud.org [82.80.226.92]
Trace complete.
And once you are down, doing a
ping -t will show you immediate when you are connected, so that could give a few seconds faster reaction as waiting for your MUD client to try.
K.