#16 Eingetragen von Jarnys vor 1 Jahrzehnt Melden | Zitieren
C:\Users\janlue>nslookup shard.ryzom.comServer: router.luetke.lanAddress: 2001:4dd0:ff00:8b12:6::1Nicht autorisierende Antwort:Name: shard.ryzom.comAddress: 178.33.44.35
luetke@media ~ $ dig su1.ryzom.com; <<>> DiG 9.8.1-P1 <<>> su1.ryzom.com;; global options: +cmd;; Got answer:;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 391;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0;; QUESTION SECTION:;su1.ryzom.com. IN A;; ANSWER SECTION:su1.ryzom.com. 28654 IN A 178.33.44.35;; Query time: 2 msec;; SERVER: 192.168.6.1#53(192.168.6.1);; WHEN: Wed Oct 16 14:16:17 2013;; MSG SIZE rcvd: 47
C:\Users\janlue>ping shard.ryzom.comPing wird ausgeführt für shard.ryzom.com [178.33.44.35] mit 32 Bytes Daten:Antwort von 178.33.44.35: Bytes=32 Zeit=28ms TTL=56Antwort von 178.33.44.35: Bytes=32 Zeit=27ms TTL=56Antwort von 178.33.44.35: Bytes=32 Zeit=27ms TTL=56Antwort von 178.33.44.35: Bytes=32 Zeit=27ms TTL=56Ping-Statistik für 178.33.44.35: Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust),Ca. Zeitangaben in Millisek.: Minimum = 27ms, Maximum = 28ms, Mittelwert = 27ms
luetke@media ~ $ ping -c 4 su1.ryzom.comPING su1.ryzom.com (178.33.44.35) 56(84) bytes of data.64 bytes from 178.33.44.35: icmp_req=1 ttl=56 time=27.2 ms64 bytes from 178.33.44.35: icmp_req=2 ttl=56 time=27.9 ms64 bytes from 178.33.44.35: icmp_req=3 ttl=56 time=27.2 ms64 bytes from 178.33.44.35: icmp_req=4 ttl=56 time=28.0 ms--- su1.ryzom.com ping statistics ---4 packets transmitted, 4 received, 0% packet loss, time 15157msrtt min/avg/max/mdev = 27.215/27.613/28.070/0.436 ms
C:\Users\janlue>tracert shard.ryzom.comRoutenverfolgung zu shard.ryzom.com [178.33.44.35] über maximal 30 Abschnitte: 1 <1 ms <1 ms 4 ms router.luetke.lan [192.168.6.1] 2 11 ms 9 ms 8 ms 62.214.64.52 3 24 ms 10 ms 10 ms 62.214.110.57 4 179 ms 198 ms 204 ms 62.214.106.90 5 19 ms 20 ms 19 ms 62.214.106.65 6 * 20 ms * decix.routers.ovh.net [80.81.192.209] 7 29 ms 28 ms 60 ms rbx-g2-a9.fr.eu [91.121.131.201] 8 29 ms * 27 ms vss-6a-6k.fr.eu [91.121.128.40] 9 27 ms 27 ms 27 ms 178.33.44.35Ablaufverfolgung beendet.
traceroute su1.ryzom.comtraceroute to su1.ryzom.com (178.33.44.35), 30 hops max, 60 byte packets 1 router.luetke.lan (192.168.6.1) 0.733 ms 1.142 ms 1.562 ms 2 62.214.64.52 (62.214.64.52) 11.456 ms 13.551 ms 15.054 ms 3 62.214.110.57 (62.214.110.57) 152.616 ms 152.954 ms 153.113 ms 4 62.214.106.90 (62.214.106.90) 27.540 ms 30.607 ms 62.214.106.94 (62.214.106.94) 31.393 ms 5 62.214.106.69 (62.214.106.69) 41.017 ms 41.354 ms 42.822 ms 6 decix.routers.ovh.net (80.81.192.209) 45.429 ms * * 7 rbx-g2-a9.fr.eu (91.121.131.201) 50.528 ms 28.825 ms 58.231 ms 8 vss-6a-6k.fr.eu (91.121.128.40) 58.618 ms * * 9 * * *...30 * * *
---
#17 Eingetragen von Dawmdt (Gast) vor 1 Jahrzehnt Zitieren
It looks to me like a it could be a random internet routing problem with your ISP provider and the game, this can occur from time to time and is not particularly anyones fault.
Pinging shard.ryzom.com [178.33.44.35] with 32 bytes of data:Reply from 178.33.44.35: bytes=32 time=12ms TTL=57Reply from 178.33.44.35: bytes=32 time=11ms TTL=57Reply from 178.33.44.35: bytes=32 time=10ms TTL=57Reply from 178.33.44.35: bytes=32 time=11ms TTL=57Ping statistics for 178.33.44.35: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 10ms, Maximum = 12ms, Average = 11mstracert shard.ryzom.comTracing route to shard.ryzom.com [178.33.44.35]over a maximum of 30 hops: 1 General failure.Trace complete.ping shard.ryzom.comPinging shard.ryzom.com [178.33.44.35] with 32 bytes of data:Reply from 178.33.44.35: bytes=32 time=11ms TTL=57Reply from 178.33.44.35: bytes=32 time=11ms TTL=57Reply from 178.33.44.35: bytes=32 time=12ms TTL=57Reply from 178.33.44.35: bytes=32 time=11ms TTL=57Ping statistics for 178.33.44.35: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 11ms, Maximum = 12ms, Average = 11mstracert shard.ryzom.comTracing route to shard.ryzom.com [178.33.44.35]over a maximum of 30 hops: 1 General failure.Trace complete.tracert shard.ryzom.comTracing route to shard.ryzom.com [178.33.44.35]over a maximum of 30 hops: 1 5 ms 5 ms 8 ms 10.29.12.1 2 7 ms 8 ms 7 ms bmly-core-2a-ae4-1499.network.virginmedia.net [80.1.227.145] 3 8 ms 7 ms 8 ms popl-bb-1c-ae3-0.network.virginmedia.net [213.105.159.225] 4 6 ms 7 ms 8 ms tele-ic-5-ae0-0.network.virginmedia.net [213.105.159.117] 5 * * * Request timed out. 6 11 ms 11 ms 12 ms rbx-g1-a9.fr.eu [94.23.122.66] 7 General failure.Trace complete.ping shard.ryzom.comPinging shard.ryzom.com [178.33.44.35] with 32 bytes of data:Reply from 178.33.44.35: bytes=32 time=10ms TTL=57Reply from 178.33.44.35: bytes=32 time=12ms TTL=57Reply from 178.33.44.35: bytes=32 time=12ms TTL=57Reply from 178.33.44.35: bytes=32 time=11ms TTL=57Ping statistics for 178.33.44.35: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 10ms, Maximum = 12ms, Average = 11mstracert shard.ryzom.comTracing route to shard.ryzom.com [178.33.44.35]over a maximum of 30 hops: 1 6 ms 6 ms 7 ms 10.29.12.1 2 10 ms 7 ms 7 ms bmly-core-2a-ae4-1499.network.virginmedia.net [80.1.227.145] 3 8 ms 8 ms General failure.Trace complete.
#18 Eingetragen von Jarnys vor 1 Jahrzehnt Melden | Zitieren
#19 Eingetragen von Herlie (Gast) vor 1 Jahrzehnt Zitieren
#20 Eingetragen von Talkirc vor 1 Jahrzehnt Melden | Zitieren
Other games - they give you a cookie whether you succeed or not, in fact you don't even have to participate. Ryzom takes your cookie, eats it in front of you, and slaps you 2 or 3 times for bringing a cookie in the first place.
powered by ryzom-api