Allods Online Forum

Erm, NA and EU playerbases are downloading the game at the same time, this is quite server heavy.

2gb?

first dowloaded the 6mb+ installer.
installed and it started to download 1gb+ patch
and than downloaded350mb+ patch
and now still downloading 7,6gb patch!

i think im doing something wrong!

p.s: i dont want to mention about cant even login to my account!

i just tried to log in via game client. it was 3700/7600mb. and now it shows 33mb/7600mb.

turned off the client and everything.
its time to find some game different. maybe later i can try again. gl all...

Hello,

In order to investigate the download issues, we kindly ask you to run a ping test.

To do so, please follow these steps:

1. Open the command prompt.
For Windows XP: From the Start menu, select Run... . In the "Open:" box, type cmd , and then press Enter.
For Windows Vista and Windows 7: From the Start menu, in the search field, type cmd , and then press Enter.

2. At the command prompt, please write

Citation

ping 213.128.132.250

and then press Enter.

3. Copy the results by right clicking on the window and choose 'Select All'.

4. Please enter your data into your next reply with either CTRL+V or right click -> paste, so that we can analyze them.

5. Please do step 2 to 4 for IP 178.63.38.148, too.

Thank you for your assistance!

Kind regards,
Fayne

Pinging 178.63.38.148 with 32 bytes of data:

Reply from 178.63.38.148: bytes=32 time=260ms TTL=47
Reply from 178.63.38.148: bytes=32 time=260ms TTL=47
Reply from 178.63.38.148: bytes=32 time=262ms TTL=47
Reply from 178.63.38.148: bytes=32 time=262ms TTL=47

Ping statistics for 178.63.38.148:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 260ms, Maximum = 262ms, Average = 261ms


Pinging 213.128.132.250 with 32 bytes of data:


Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 213.128.132.250:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Pinging 213.128.132.250 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 213.128.132.250:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)



Pinging 178.63.38.148 with 32 bytes of data:
Reply from 178.63.38.148: bytes=32 time=147ms TTL=42
Reply from 178.63.38.148: bytes=32 time=147ms TTL=42
Reply from 178.63.38.148: bytes=32 time=148ms TTL=42
Reply from 178.63.38.148: bytes=32 time=147ms TTL=42

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

Citation de "Nethon"

Pinging 213.128.132.250 with 32 bytes of data:


Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 213.128.132.250:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Same here.

im patched already, i simply cant login like many others.i get connection not established.

coz the server is down....looks like they are working on the problems

Pinging 213.128.132.250 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 213.128.132.250:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Pinging 178.63.38.148 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 178.63.38.148:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

pinging 213.128.132.250
Request timed out
Request timed out
Request timed out
Request timed out

Ping statistics for 213.128.132.250
Packets: Sent=4 Received=0 Lost=4 (100% loss)

Pinging 178.63.38.148
Reply from 178.63.38.148: Bytes=32 time=137ms TTL=45
Reply from 178.63.38.148: Bytes=32 time=131ms TTL=45
Reply from 178.63.38.148: Bytes=32 time=130ms TTL=45
Reply from 178.63.38.148: Bytes=32 time=130ms TTL=45

Ping statistics for 178.63.38.148:
packets: sent=4 received =4 lost =0 (0% lost)

approximate round trip times in ms
min=130ms max=137ms ave 132ms

Emmm, my progresive download was over and it's downloading it again from ~50%. Should that be happening?

ping 213.128.132.250

Pinging 213.128.132.250 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 213.128.132.250:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

ping 178.63.38.148

Pinging 178.63.38.148 with 32 bytes of data:
Reply from 178.63.38.148: bytes=32 time=348ms TTL=46
Reply from 178.63.38.148: bytes=32 time=352ms TTL=46
Reply from 178.63.38.148: bytes=32 time=347ms TTL=46
Reply from 178.63.38.148: bytes=32 time=606ms TTL=46

Ping statistics for 178.63.38.148:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 347ms, Maximum = 606ms, Average = 413ms

I assume 213.128.132.250 is rejecting ping requests to avoid smurfing.

Can I also recommend everyone runs the command "tracert" followed by both IP addresses?

Still not working for me... any new?

C:\Users\Stefano>ping 213.128.132.250

Esecuzione di Ping 213.128.132.250 con 32 byte di dati:
Richiesta scaduta.
Richiesta scaduta.
Richiesta scaduta.
Richiesta scaduta.

Statistiche Ping per 213.128.132.250:
Pacchetti: Trasmessi = 4, Ricevuti = 0,
Persi = 4 (100% persi),

C:\Users\Stefano>ping 178.63.38.148

Esecuzione di Ping 178.63.38.148 con 32 byte di dati:
Risposta da 178.63.38.148: byte=32 durata=21ms TTL=46
Risposta da 178.63.38.148: byte=32 durata=21ms TTL=46
Risposta da 178.63.38.148: byte=32 durata=21ms TTL=46
Risposta da 178.63.38.148: byte=32 durata=21ms TTL=46

Statistiche Ping per 178.63.38.148:
Pacchetti: Trasmessi = 4, Ricevuti = 4,
Persi = 0 (0% persi),
Tempo approssimativo percorsi andata/ritorno in millisecondi:
Minimo = 21ms, Massimo = 21ms, Medio = 21ms



C:\Users\Stefano>tracert 213.128.132.250

Traccia instradamento verso 213.128.132.250 su un massimo di 30 punti di passaggio

1 <1 ms <1 ms <1 ms 192.168.1.250
2 1 ms <1 ms <1 ms xxxxxxxxxxxxxxx

3 3 ms 1 ms 1 ms 10.0.214.45
4 1 ms 1 ms 1 ms 10.0.214.253
5 1 ms 1 ms 1 ms xe-0-0-2-vi-0.pop-ronca01-02.ascotlc.net [188.125.113.180]

6 2 ms 1 ms 1 ms xe-0-0-3-vi-0.pop-casie01-02.ascotlc.net [188.125.113.177]

7 2 ms 1 ms 1 ms gi-0-0-1.bgr-casie01-01.ascotlc.net [188.125.113.69]
8 2 ms 1 ms 1 ms gi-0-0-0.bgr-casie01-02.ascotlc.net [188.125.113.53]
9 6 ms 5 ms 6 ms 217.19.158.169
10 15 ms 5 ms 5 ms lag1.mivivxmr02.retelit.it [217.19.144.93]
11 16 ms 16 ms 16 ms ge0-0-3-br2.frankfurt1.iphh.net [80.81.192.27]
12 28 ms 29 ms 29 ms ae1-11-br3.hamburg2.iphh.net [213.128.159.101]
13 28 ms 28 ms 28 ms te4-3-cr1.hamburg2.iphh.net [213.128.159.14]
14 * * * Richiesta scaduta.
15 * * * Richiesta scaduta.
16 * * * Richiesta scaduta.
17 * * * Richiesta scaduta.
18 * * * Richiesta scaduta.
19 * * * Richiesta scaduta.
20 * * * Richiesta scaduta.
21 * * * Richiesta scaduta.
22 * * * Richiesta scaduta.
23 * * * Richiesta scaduta.
24 * * * Richiesta scaduta.
25 * * * Richiesta scaduta.
26 * * * Richiesta scaduta.
27 * * * Richiesta scaduta.
28 * * * Richiesta scaduta.
29 * * * Richiesta scaduta.
30 * * * Richiesta scaduta.

Traccia completata.