mindphlux schrieb:
Ich komm auch irgendwie nicht klar... die Services laufen alle soweit, einen Account konnte ich ebenfalls anlegen, aber dann... eine Nachricht, das zur Zeit keine Welten verfügbar seien. Die realm.list stimmt aber, die Dienste habe ich auch schon öfters neu gestartet - kein Erfolg. Habs mit D2 1.10 ausprobiert. Es geht weder vom Server noch von einem anderen Rechner aus.
Irgendeine Idee, was ich falsch gemacht haben könne?
Dieses Problem habe ich auch....bruache dringend ,wenn möglich noch heute hilfe oder nen kleines tutorial
Hier auszug aus d2closed 2.2 console:
Jul 28 17:12:39 d2dbs_d2ladder_checksum_check: ladder file check pass (checksum=0xDB72C052)
Jul 28 17:12:39 d2dbs_d2ladder_saveladder: backup ladder file
Jul 28 17:12:39 dbs_server_main: waiting for connections...
Jul 28 17:12:39 d2dbs_d2ladder_checksum_check: ladder file check pass (checksum=0xDB72C052)
Jul 28 17:12:39 d2dbs_d2ladder_saveladder: backup ladder file
Jul 28 17:12:40 d2cs_d2ladder_readladder: ladder file loaded successfully (28 types 35 maxtype)
Jul 28 17:12:51 bnetd_check: connection to bnetd s2s timeout
Jul 28 17:12:51 d2cs_conn_destroy: [180] closed connection 1 (0 left)
Jul 28 17:13:03 s2s_create: try make s2s connection to 192.168.123.198:6112
Jul 28 17:13:03 s2s_create: connection to s2s server 192.168.123.198:6112 is in progress
Jul 28 17:13:04 d2cs_conn_create: created session=2 socket=180 (1 current connections)
Jul 28 17:13:25 bnetd_check: connection to bnetd s2s timeout
Jul 28 17:13:25 d2cs_conn_destroy: [180] closed connection 2 (0 left)
Jul 28 17:13:26 server_accept: accept connection from 192.168.123.198
Jul 28 17:13:26 d2cs_conn_create: created session=3 socket=180 (1 current connections)
Jul 28 17:13:26 on_d2gs_initconn: [180] client initiated d2gs connection
Jul 28 17:13:26 d2cs_handle_d2gs_init: sent init packet to d2gs 1 (sessionnum=3)
Jul 28 17:13:36 s2s_create: try make s2s connection to 192.168.123.198:6112
Jul 28 17:13:36 s2s_create: connection to s2s server 192.168.123.198:6112 is in progress
Jul 28 17:13:36 d2cs_conn_create: created session=4 socket=232 (2 current connections)
Jul 28 17:13:47 bnetd_check: connection to bnetd s2s timeout
Jul 28 17:13:47 d2cs_conn_destroy: [232] closed connection 4 (1 left)
Jul 28 17:13:58 s2s_create: try make s2s connection to 192.168.123.198:6112
Jul 28 17:13:58 s2s_create: connection to s2s server 192.168.123.198:6112 is in progress
Jul 28 17:13:58 d2cs_conn_create: created session=5 socket=232 (2 current connections)
Jul 28 17:14:09 bnetd_check: connection to bnetd s2s timeout
Jul 28 17:14:09 d2cs_conn_destroy: [232] closed connection 5 (1 left)
Jul 28 17:14:20 s2s_create: try make s2s connection to 192.168.123.198:6112
Jul 28 17:14:20 s2s_create: connection to s2s server 192.168.123.198:6112 is in progress
Jul 28 17:14:20 d2cs_conn_create: created session=6 socket=232 (2 current connections)
Jul 28 17:14:31 bnetd_check: connection to bnetd s2s timeout
Jul 28 17:14:31 d2cs_conn_destroy: [232] closed connection 6 (1 left)
Jul 28 17:14:42 s2s_create: try make s2s connection to 192.168.123.198:6112
Jul 28 17:14:42 s2s_create: connection to s2s server 192.168.123.198:6112 is in progress
Jul 28 17:14:42 d2cs_conn_create: created session=7 socket=236 (2 current connections)
Jul 28 17:14:54 bnetd_check: connection to bnetd s2s timeout
Jul 28 17:14:54 d2cs_conn_destroy: [236] closed connection 7 (1 left)
Jul 28 17:15:05 s2s_create: try make s2s connection to 192.168.123.198:6112
Jul 28 17:15:05 s2s_create: connection to s2s server 192.168.123.198:6112 is in progress
Jul 28 17:15:05 d2cs_conn_create: created session=8 socket=236 (2 current connections)