Loading...

Solved Can't connect to realm

Discussion in 'Help Desk' started by -Papo-, Nov 13, 2016.

  1. -Papo-

    -Papo- Member

    Joined:
    Nov 13, 2016
    Messages:
    3
    Likes Received:
    1
    Trophy Points:
    3
    Hi,
    I installed D2 Lord of destruction and I followed the install guide to connect to d2.europebattle.net server.
    I can start my game and select Battle.net, I can login with my credentials but my game can't connect to the realm.
    I disabled Windows Firewall, Windows Defender, DEP and I checked if my PC can contact d2.europebattle.net server on TCP 6112 port and TCP 4000 port.
    I can see only International realm but for me is always offline.
    Can you help me please.
    thanks
     
    -Papo-, Nov 13, 2016
    #1
  2. inayat

    inayat Head Game Master Moderator

    Joined:
    Sep 12, 2016
    Messages:
    24,455
    Likes Received:
    6,142
    Trophy Points:
    113

    Hey there,
    try this and let me know.
    You have failed installing the Diablo II client correctly or you have failed adding the realm gateways. Follow our manual connect guide from here or here and don't forget to apply our realm patch as well.
     
    inayat, Nov 13, 2016
    #2
  3. Gix

    Gix Founder

    Joined:
    Jan 1, 2005
    Messages:
    54,770
    Likes Received:
    5,769
    Trophy Points:
    113

    Gix, Nov 13, 2016
    #3
  4. -Papo-

    -Papo- Member

    Joined:
    Nov 13, 2016
    Messages:
    3
    Likes Received:
    1
    Trophy Points:
    3
    @Gix, I used tcpdump on my firewall to verify if something block communication from my PC and the server and you can find below the result:

    17:52:55.145702 IP 192.168.26.11.62189 > 188.165.54.9.6112: Flags , seq 4196810516, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
    17:52:55.239353 IP 188.165.54.9.6112 > 192.168.26.11.62189: Flags [S.], seq 1757329794, ack 4196810517, win 8192, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
    17:52:55.240345 IP 192.168.26.11.62189 > 188.165.54.9.6112: Flags [.], ack 1, win 64, length 0
    17:52:55.258999 IP 192.168.26.11.62189 > 188.165.54.9.6112: Flags [P.], seq 1:2, ack 1, win 64, length 1
    17:52:55.259487 IP 192.168.26.11.62189 > 188.165.54.9.6112: Flags [P.], seq 2:52, ack 1, win 64, length 50
    17:52:55.333192 IP 188.165.54.9.6112 > 192.168.26.11.62189: Flags [.], ack 52, win 256, length 0
    17:52:55.335677 IP 188.165.54.9.6112 > 192.168.26.11.62189: Flags [P.], seq 1:9, ack 52, win 256, length 8
    17:52:55.336505 IP 192.168.26.11.62189 > 188.165.54.9.6112: Flags [P.], seq 52:60, ack 9, win 64, length 8
    17:52:55.404163 IP 188.165.54.9.6112 > 192.168.26.11.62189: Flags [P.], seq 9:110, ack 60, win 256, length 101
    17:52:55.460562 IP 192.168.26.11.62189 > 188.165.54.9.6112: Flags [.], ack 110, win 64, length 0
    17:52:55.522781 IP 192.168.26.11.62189 > 188.165.54.9.6112: Flags [P.], seq 60:194, ack 110, win 64, length 134
    17:52:55.598760 IP 188.165.54.9.6112 > 192.168.26.11.62189: Flags [P.], seq 110:119, ack 194, win 256, length 9
    17:52:55.602530 IP 192.168.26.11.62189 > 188.165.54.9.6112: Flags [P.], seq 194:224, ack 119, win 64, length 30
    17:52:55.705476 IP 188.165.54.9.6112 > 192.168.26.11.62189: Flags [P.], seq 119:157, ack 224, win 255, length 38
    17:52:55.755109 IP 192.168.26.11.62189 > 188.165.54.9.6112: Flags [.], ack 157, win 64, length 0
    17:52:59.957997 IP 192.168.26.11.62189 > 188.165.54.9.6112: Flags [P.], seq 224:263, ack 157, win 64, length 39
    17:53:00.026485 IP 188.165.54.9.6112 > 192.168.26.11.62189: Flags [P.], seq 157:165, ack 263, win 255, length 8
    17:53:00.082893 IP 192.168.26.11.62189 > 188.165.54.9.6112: Flags [.], ack 165, win 64, length 0
    17:53:00.102063 IP 192.168.26.11.62189 > 188.165.54.9.6112: Flags [P.], seq 263:267, ack 165, win 64, length 4
    17:53:00.175323 IP 188.165.54.9.6112 > 192.168.26.11.62189: Flags [P.], seq 165:214, ack 267, win 255, length 49
    17:53:00.183983 IP 192.168.26.11.62189 > 188.165.54.9.6112: Flags [P.], seq 267:309, ack 214, win 64, length 42
    17:53:00.253687 IP 188.165.54.9.6112 > 192.168.26.11.62189: Flags [P.], seq 214:297, ack 309, win 255, length 83
    17:53:00.295334 IP 192.168.26.11.62189 > 188.165.54.9.6112: Flags [.], ack 297, win 63, length 0
    17:53:03.130789 IP 192.168.26.11.62189 > 188.165.54.9.6112: Flags [F.], seq 309, ack 297, win 63, length 0
    17:53:03.200637 IP 188.165.54.9.6112 > 192.168.26.11.62189: Flags [.], ack 310, win 255, length 0
    17:53:03.206783 IP 188.165.54.9.6112 > 192.168.26.11.62189: Flags [F.], seq 297, ack 310, win 255, length 0
    17:53:03.207703 IP 192.168.26.11.62189 > 188.165.54.9.6112: Flags [.], ack 298, win 63, length 0

    My client on my LAN has IP 192.168.26.11.6 and the capture shows that the communication on TCP port 6112 is active but I have the message that you posted on your previuos message.
     
    -Papo-, Nov 13, 2016
    #4
  5. Gix

    Gix Founder

    Joined:
    Jan 1, 2005
    Messages:
    54,770
    Likes Received:
    5,769
    Trophy Points:
    113

    Login inside your router panel and forward 6112 and 4000 ports. That error shows up when those ports are blocked or in use.

    PS: Are you using Windows or Linux?
     
    Gix, Nov 13, 2016
    #5
  6. -Papo-

    -Papo- Member

    Joined:
    Nov 13, 2016
    Messages:
    3
    Likes Received:
    1
    Trophy Points:
    3
    I'm using Windows.
    I resolved my issue.
    It was not a problem with port but I try to connect with my username:
    -Papo-
    I think that the system did not like the character - at the beginning of my account.
    When I created a new account that starts with a alphabetical character I was able to connect to the realm.
    Thanks
     
    -Papo-, Nov 17, 2016
    #6
    Gix likes this.
  7. Gix

    Gix Founder

    Joined:
    Jan 1, 2005
    Messages:
    54,770
    Likes Received:
    5,769
    Trophy Points:
    113

    Thanks for letting us know, @-Papo-. Although some signs are allowed to be used inside the account and character name, I'll make sure to test your issue and see if it happens regardless of the used sign.
    Welcome aboard and enjoy your stay!
     
    Gix, Nov 17, 2016
    #7
    • Draft saved Draft deleted
    Loading...
    Similar Threads - Can't connect realm
    1. pvdptje

      Solved Can't connect to server anymore

      pvdptje, Sep 16, 2018, in forum: Help Desk
      Replies:
      2
      Views:
      1,411
      pvdptje
      Sep 16, 2018
    2. darkspider64

      Solved can't connect to bnet

      darkspider64, Feb 24, 2017, in forum: Help Desk
      Replies:
      5
      Views:
      3,272
      Gix
      Feb 24, 2017
    3. Xploiterx

      Solved Can't connect :(

      Xploiterx, Jun 8, 2016, in forum: Help Desk
      Replies:
      3
      Views:
      1,764
      Gix
      Jun 10, 2016
    4. kiflata

      Can't connect after installing windows 10

      kiflata, Aug 2, 2015, in forum: Help Desk
      Replies:
      5
      Views:
      1,741
      Gix
      Aug 4, 2015
    5. Vaasu

      Can't connect to server

      Vaasu, Dec 3, 2014, in forum: Help Desk
      Replies:
      5
      Views:
      2,068
      Vaasu
      Dec 4, 2014
    Loading...