The EU servers

Tactical advice, How-to, Post-mortem, etc.
peet
Posts: 4972
Joined: Sun Jul 16, 2006 6:57 pm
Location: Holland

Post by peet »

Not much problems here /smile.gif" style="vertical-align:middle" emoid=":)" border="0" alt="smile.gif" />

CODEH:\Documents and Settings\Alleg_X>tracert 84.243.253.94

Bezig met het traceren van de route naar 84.243.253.94 via maximaal 30 hops

1 <1 ms <1 ms <1 ms 192.168.2.1
2 8 ms 7 ms 5 ms ubr33-bu3.dbsch1.nb.home.nl [10.193.0.1]
3 6 ms 5 ms 6 ms csw1-vlan201.dbsch1.nb.home.nl [213.51.152.193]

4 6 ms 5 ms 5 ms bb1-ge10-0-0.dbsch1.nb.home.nl [213.51.158.92]
5 * * * Time-out bij opdracht.
6 9 ms 10 ms 9 ms bb1-ge0-1-0-0.amsix-nikhef.home.nl [213.51.158.
49]
7 10 ms 12 ms 9 ms grafix.telecity2.nl-ix.net [193.239.116.70]
8 12 ms 11 ms 11 ms rtr-1.rtd-kub.grafix.nl [217.67.247.5]
9 14 ms 13 ms 14 ms 84.243.253.94

De trace is voltooid.
Last edited by peet on Fri Jan 19, 2007 9:57 pm, edited 1 time in total.
Image
KofiMan
Posts: 414
Joined: Fri Mar 24, 2006 8:00 am

Post by KofiMan »

C:\>tracert 84.243.253.94

Tracing route to 84.243.253.94 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 13 ms 7 ms 7 ms d154-20-240-254.bchsia.telus.net [154.20.240.254
]
3 7 ms 7 ms 7 ms PGRGBC01DR02.bb.telus.com [208.181.240.14]
4 18 ms 18 ms 18 ms PGRGBC01DR01.bb.telus.com [154.11.10.29]
5 65 ms 65 ms 69 ms toroonnlbr00.bb.telus.com [154.11.11.66]
6 65 ms 65 ms 65 ms so-4-3-2.cr1.ord2.us.above.net [216.200.254.30]

7 85 ms 85 ms 86 ms so-1-1-0.mpr3.lga1.us.above.net [64.125.27.170]

8 171 ms 179 ms 171 ms so-7-0-0.mpr3.ams1.nl.above.net [64.125.27.186]

9 171 ms 171 ms 172 ms grafix.ams4.nl.above.net [82.98.253.68]
10 173 ms 173 ms 173 ms rtr-1.rtd-kub.grafix.nl [217.67.247.5]
11 176 ms 176 ms 176 ms 84.243.253.94

Trace complete.

C:\>

Seems pretty regular, considering that I'm in the arse end of nowhere.. I am suprised I'm only 11 hops away though.
ImmortalZ
Posts: 5048
Joined: Mon Sep 08, 2003 7:00 am
Location: India
Contact:

Post by ImmortalZ »

I got a reply from grafix.nl today.

It amounted to "You're not our customer. Please go away.".

/mad.gif" style="vertical-align:middle" emoid=":mad:" border="0" alt="mad.gif" />
Grimmwolf_GB
Posts: 3711
Joined: Wed Jul 02, 2003 7:00 am
Location: Germany
Contact:

Post by Grimmwolf_GB »

But, but... ask pkk, he is their customer and you want to connect to his stuff.
madpeople
Posts: 4787
Joined: Tue Dec 16, 2003 8:00 am
Location: England

Post by madpeople »

Code: Select all

trace powa!>tracert 84.243.253.94

Tracing route to 84.243.253.94 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  we250a.halls.manchester.ac.uk [130.88.183.250]
  2    <1 ms    <1 ms    <1 ms  gw-uom.mcc.ac.uk [130.88.250.54]
  3    <1 ms    <1 ms     1 ms  gw-man.netnw.net.uk [194.66.21.242]
  4    <1 ms    <1 ms    <1 ms  gw-nnw.core.netnw.net.uk [194.66.25.97]
  5     1 ms    <1 ms    <1 ms  gw-man-rh.netnw.net.uk [194.66.25.149]
  6    15 ms     1 ms     1 ms  so-0-1-0.warr-sbr1.ja.net [146.97.42.169]
  7     5 ms     5 ms     5 ms  so-0-2-0.read-sbr1.ja.net [146.97.33.109]
  8     6 ms     6 ms     6 ms  lond-scr3.ja.net [146.97.33.142]
  9     6 ms     6 ms     6 ms  146.97.35.158
  10    6 ms     6 ms     6 ms  ge-0-2-0-0.lonth-inter-2.interoute.net [195.66.226.53]
  11    6 ms     6 ms     6 ms  Gi4-0.lon-wal-core-1.interoute.net [84.233.152.181]
  12   12 ms    12 ms    12 ms  PO1-2.rtm-vla-access-1.interoute.net [212.23.41.205]
  13   17 ms    16 ms    16 ms  217.118.121.134
  14   18 ms    18 ms    18 ms  84.243.253.94

Trace complete.

trace powa!>
all is well /smile.gif" style="vertical-align:middle" emoid=":)" border="0" alt="smile.gif" />

problems in GB squad game

CODEMicrosoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.

>tracert 84.243.253.94

Tracing route to 84.243.253.94 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms we250a.halls.manchester.ac.uk [130.88.183.250]
2 6 ms 7 ms 7 ms gw-uom.mcc.ac.uk [130.88.250.54]
3 35 ms 24 ms 21 ms gw-man.netnw.net.uk [194.66.21.242]
4 12 ms 14 ms 37 ms gw-nnw.core.netnw.net.uk [194.66.25.97]
5 14 ms 11 ms 11 ms gw-man-rh.netnw.net.uk [194.66.25.149]
6 10 ms 11 ms 12 ms so-0-1-0.warr-sbr1.ja.net [146.97.42.169]
7 24 ms 21 ms 20 ms so-0-2-0.read-sbr1.ja.net [146.97.33.109]
8 18 ms 19 ms 18 ms lond-scr3.ja.net [146.97.33.142]
9 13 ms 13 ms 11 ms 146.97.35.158
10 18 ms 18 ms 19 ms ge-0-2-0-0.lonth-inter-2.interoute.net [195.66.2
26.53]
11 108 ms 240 ms 37 ms Gi4-0.lon-wal-core-1.interoute.net [84.233.152.1
81]
12 21 ms 22 ms 22 ms PO1-2.rtm-vla-access-1.interoute.net [212.23.41.
205]
13 28 ms 33 ms 26 ms 217.118.121.134
14 36 ms 34 ms * 84.243.253.94
15 38 ms 30 ms 30 ms 84.243.253.94

Trace complete.

>tracert 84.243.253.94

Tracing route to 84.243.253.94 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms we250a.halls.manchester.ac.uk [130.88.183.250]
2 13 ms 13 ms 13 ms gw-uom.mcc.ac.uk [130.88.250.54]
3 216 ms 206 ms 136 ms gw-man.netnw.net.uk [194.66.21.242]
4 9 ms 8 ms 8 ms gw-nnw.core.netnw.net.uk [194.66.25.97]
5 107 ms 11 ms 9 ms gw-man-rh.netnw.net.uk [194.66.25.149]
6 10 ms 12 ms 11 ms so-0-1-0.warr-sbr1.ja.net [146.97.42.169]
7 19 ms 18 ms 15 ms so-0-2-0.read-sbr1.ja.net [146.97.33.109]
8 27 ms 25 ms 23 ms lond-scr3.ja.net [146.97.33.142]
9 17 ms 14 ms 15 ms 146.97.35.158
10 16 ms 18 ms 16 ms ge-0-2-0-0.lonth-inter-2.interoute.net [195.66.2
26.53]
11 28 ms 35 ms 30 ms Gi4-0.lon-wal-core-1.interoute.net [84.233.152.1
81]
12 22 ms 23 ms 23 ms PO1-2.rtm-vla-access-1.interoute.net [212.23.41.
205]
13 24 ms 27 ms 89 ms 217.118.121.134
14 52 ms 39 ms 39 ms 84.243.253.94

Trace complete.

>tracert

Usage: tracert [-d] [-h maximum_hops] [-j host-list] [-w timeout] target_name

Options:
-d Do not resolve addresses to hostnames.
-h maximum_hops Maximum number of hops to search for target.
-j host-list Loose source route along host-list.
-w timeout Wait timeout milliseconds for each reply.

>ping

Usage: ping [-t] [-a] [-n count] [-l size] [-f] [-i TTL] [-v TOS]
[-r count] [-s count] [[-j host-list] | [-k host-list]]
[-w timeout] target_name

Options:
-t Ping the specified host until stopped.
To see statistics and continue - type Control-Break;
To stop - type Control-C.
-a Resolve addresses to hostnames.
-n count Number of echo requests to send.
-l size Send buffer size.
-f Set Don't Fragment flag in packet.
-i TTL Time To Live.
-v TOS Type Of Service.
-r count Record route for count hops.
-s count Timestamp for count hops.
-j host-list Loose source route along host-list.
-k host-list Strict source route along host-list.
-w timeout Timeout in milliseconds to wait for each reply.


>ping 84.243.253.94

Pinging 84.243.253.94 with 32 bytes of data:

Reply from 84.243.253.94: bytes=32 time=37ms TTL=115
Reply from 84.243.253.94: bytes=32 time=31ms TTL=115
Reply from 84.243.253.94: bytes=32 time=74ms TTL=115
Reply from 84.243.253.94: bytes=32 time=26ms TTL=115

Ping statistics for 84.243.253.94:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 74ms, Average = 42ms

>ping 84.243.253.94 -l 1024

Pinging 84.243.253.94 with 1024 bytes of data:

Reply from 84.243.253.94: bytes=1024 time=47ms TTL=115
Reply from 84.243.253.94: bytes=1024 time=33ms TTL=115
Request timed out.
Reply from 84.243.253.94: bytes=1024 time=34ms TTL=115

Ping statistics for 84.243.253.94:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 47ms, Average = 38ms

>ping 84.243.253.94 -n 10

Pinging 84.243.253.94 with 32 bytes of data:

Reply from 84.243.253.94: bytes=32 time=39ms TTL=115
Reply from 84.243.253.94: bytes=32 time=27ms TTL=115
Reply from 84.243.253.94: bytes=32 time=39ms TTL=115
Reply from 84.243.253.94: bytes=32 time=29ms TTL=115
Reply from 84.243.253.94: bytes=32 time=26ms TTL=115
Reply from 84.243.253.94: bytes=32 time=27ms TTL=115
Reply from 84.243.253.94: bytes=32 time=29ms TTL=115
Reply from 84.243.253.94: bytes=32 time=30ms TTL=115
Reply from 84.243.253.94: bytes=32 time=27ms TTL=115
Reply from 84.243.253.94: bytes=32 time=40ms TTL=115

Ping statistics for 84.243.253.94:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 40ms, Average = 31ms

>ping 84.243.253.94 -n 10 -l 1024

Pinging 84.243.253.94 with 1024 bytes of data:

Reply from 84.243.253.94: bytes=1024 time=38ms TTL=115
Reply from 84.243.253.94: bytes=1024 time=32ms TTL=115
Reply from 84.243.253.94: bytes=1024 time=44ms TTL=115
Reply from 84.243.253.94: bytes=1024 time=28ms TTL=115
Reply from 84.243.253.94: bytes=1024 time=50ms TTL=115
Reply from 84.243.253.94: bytes=1024 time=32ms TTL=115
Reply from 84.243.253.94: bytes=1024 time=40ms TTL=115
Reply from 84.243.253.94: bytes=1024 time=32ms TTL=115
Reply from 84.243.253.94: bytes=1024 time=37ms TTL=115
Reply from 84.243.253.94: bytes=1024 time=29ms TTL=115

Ping statistics for 84.243.253.94:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 50ms, Average = 36ms

>ping 84.243.253.94 -n 10 -l 1500

Pinging 84.243.253.94 with 1500 bytes of data:

Reply from 84.243.253.94: bytes=1500 time=32ms TTL=115
Reply from 84.243.253.94: bytes=1500 time=33ms TTL=115
Request timed out.
Reply from 84.243.253.94: bytes=1500 time=38ms TTL=115
Request timed out.
Reply from 84.243.253.94: bytes=1500 time=32ms TTL=115
Reply from 84.243.253.94: bytes=1500 time=35ms TTL=115
Reply from 84.243.253.94: bytes=1500 time=36ms TTL=115
Reply from 84.243.253.94: bytes=1500 time=34ms TTL=115
Reply from 84.243.253.94: bytes=1500 time=34ms TTL=115

Ping statistics for 84.243.253.94:
Packets: Sent = 10, Received = 8, Lost = 2 (20% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 38ms, Average = 34ms

>

again, towards the end
CODE>ping 84.243.253.94 -n 20 -l 1500

Pinging 84.243.253.94 with 1500 bytes of data:

Reply from 84.243.253.94: bytes=1500 time=38ms TTL=115
Reply from 84.243.253.94: bytes=1500 time=40ms TTL=115
Reply from 84.243.253.94: bytes=1500 time=37ms TTL=115
Reply from 84.243.253.94: bytes=1500 time=39ms TTL=115
Reply from 84.243.253.94: bytes=1500 time=70ms TTL=115
Reply from 84.243.253.94: bytes=1500 time=43ms TTL=115
Reply from 84.243.253.94: bytes=1500 time=65ms TTL=115
Reply from 84.243.253.94: bytes=1500 time=37ms TTL=115
Reply from 84.243.253.94: bytes=1500 time=42ms TTL=115
Reply from 84.243.253.94: bytes=1500 time=89ms TTL=115
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 84.243.253.94: bytes=1500 time=65ms TTL=115
Reply from 84.243.253.94: bytes=1500 time=38ms TTL=115
Reply from 84.243.253.94: bytes=1500 time=62ms TTL=115
Reply from 84.243.253.94: bytes=1500 time=36ms TTL=115
Request timed out.
Reply from 84.243.253.94: bytes=1500 time=41ms TTL=115

Ping statistics for 84.243.253.94:
Packets: Sent = 20, Received = 15, Lost = 5 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 89ms, Average = 49ms

>
Last edited by madpeople on Sun Jan 21, 2007 9:19 pm, edited 1 time in total.
Ion
Posts: 178
Joined: Wed Nov 09, 2005 8:00 am
Location: England

Post by Ion »

same prob for me on the GoD core sever the others seem fine for me atm kept freezing up my fps
Image
Image
Raveen
Posts: 9104
Joined: Wed Mar 16, 2005 8:00 am
Location: Birmingham, UK
Contact:

Post by Raveen »

Most days I can connect fine to the EU servers but occasionally I get bad packet loss to the point where I can't play. I've had the same thing on ThalServe from time to time too.

Chalk it up to experience and go play something else is the only solution I've come across.
ImageImage
Spidey: Can't think of a reason I'd need to know anything
Rand0m_Numb3r
Posts: 1338
Joined: Mon Apr 18, 2005 7:00 am
Location: Madison, Wisconsin

Post by Rand0m_Numb3r »

Same thing here rav i tend to play DoW or something or hang with larry on the DN servers
Beyond the clock tower.
Puggle
Posts: 80
Joined: Wed Aug 02, 2006 10:50 am
Location: Sahf Lahnden
Contact:

Post by Puggle »

I haven't played for a few weeks, I come back and find that I have warpy-type lag to the extent that I can't really play. I guess it might be the Euroserver, but I'm in the UK and my lag is low (about 50-100 in game). Still here is a tracert as requested:


Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Dave>tracert 84.243.253.94

Tracing route to 84.243.253.94 over a maximum of 30 hops

1 42 ms 42 ms 44 ms ge0-1.lns6-c13.telh.planet.net.uk [62.25.196.202
]
2 39 ms 38 ms 35 ms ge2-2.pbr-1.telh.as5388.net [62.25.196.194]
3 41 ms 38 ms 38 ms pos1-0.ber-1.r18.telh.as5388.net [195.92.55.160]

4 42 ms 38 ms 42 ms ge-0-2-0-0.lonth-inter-2.interoute.net [195.66.22653]
5 43 ms 44 ms 44 ms Gi4-0.lon-wal-core-1.interoute.net [84.233.152.181]
6 41 ms 40 ms 42 ms PO1-2.rtm-vla-access-1.interoute.net [212.23.41.205]
7 49 ms 52 ms 48 ms 217.118.121.134
8 51 ms 54 ms 91 ms 84.243.253.94

Trace complete.

~Puggle
Adaven
Posts: 1959
Joined: Sat Oct 25, 2003 7:00 am
Location: Greater Ozarks

Post by Adaven »

You are probably having trouble with packet loss or somesuch. Check you pings in alleg (alt f, right next to lag). The should reset around 5-6, the higher it goes the bigger warps you experience.
Post Reply