Unable to connect to the server

Тема в разделе "Архив", создана пользователем LooQuePasso, 20 май 2011.

  1. LooQuePasso

    LooQuePasso Новичок

    Доброе время суток!
    Возникла проблема и длится уже на протяжении 3 дней. Захожу в игру, выбираю чемпиона, игра начинает грузиться и выскакивает ошибка...

    Unable to connect to the server. If you have a firewall, it may be blocking the connection. Please refer to your firewall's documentation. Would you like to retry the connection?
    Две кнопки - Повтор Отмена

    Жмешь повтор, все снова повторяется...

    2-3 месяца играл, проблем не было. Файрволл отключил и антивирус тоже, но не помогает. Переустановил игру, толку ноль!

    Как решить проблему?
    На форуме полазил, ничего подобного не нашел.

    US server.
     
    1 человеку нравится это.
  2. LooQuePasso

    LooQuePasso Новичок

    Вот текст:

    Summary of Noteworthy Events –
    Minor Aberrations
    Certain TCP protocols are blocked in outbound traffic
    The network path does not reply when it needs to fragment traffic
    Virus filtering appears to be present on your host or network
    Address-based Tests +
    NAT detection (?): No NAT Detected
    Local Network Interfaces (?): OK
    DNS-based host information (?): OK
    Reachability Tests –
    TCP connectivity (?): Note
    Direct TCP access to remote FTP servers (port 21) is allowed.
    Direct TCP access to remote SSH servers (port 22) is allowed.
    Direct TCP access to remote SMTP servers (port 25) is allowed.
    Direct TCP access to remote DNS servers (port 53) is allowed.
    Direct TCP access to remote HTTP servers (port 80) is allowed.
    Direct TCP access to remote POP3 servers (port 110) is allowed.
    Direct TCP access to remote RPC servers (port 135) is blocked.
    This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
    Direct TCP access to remote NetBIOS servers (port 139) is blocked.
    This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
    Direct TCP access to remote IMAP servers (port 143) is allowed.
    Direct TCP access to remote SNMP servers (port 161) is allowed.
    Direct TCP access to remote HTTPS servers (port 443) is allowed.
    Direct TCP access to remote SMB servers (port 445) is blocked.
    This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
    Direct TCP access to remote SMTP/SSL servers (port 465) is allowed.
    Direct TCP access to remote secure IMAP servers (port 585) is allowed.
    Direct TCP access to remote authenticated SMTP servers (port 587) is allowed.
    Direct TCP access to remote IMAP/SSL servers (port 993) is allowed.
    Direct TCP access to remote POP/SSL servers (port 995) is allowed.
    Direct TCP access to remote OpenVPN servers (port 1194) is allowed.
    Direct TCP access to remote PPTP Control servers (port 1723) is allowed.
    Direct TCP access to remote SIP servers (port 5060) is allowed.
    Direct TCP access to remote BitTorrent servers (port 6881) is allowed.
    Direct TCP access to remote TOR servers (port 9001) is allowed.
    UDP connectivity (?): OK
    Basic UDP access is available.
    The applet was able to send fragmented UDP traffic.
    The applet was able to receive fragmented UDP traffic.
    Direct UDP access to remote DNS servers (port 53) is allowed.
    Direct UDP access to remote NTP servers (port 123) is allowed.
    Direct UDP access to remote OpenVPN servers (port 1194) is allowed.
    Direct UDP access to remote MSSQL servers (port 1434) is allowed.
    Traceroute (?): OK
    It takes 16 network hops for traffic to pass from our server to your system, as shown below. For each hop, the time it takes to traverse it is shown in parentheses.
    10.209.112.3 (0 ms)
    ec2-75-101-160-190.compute-1.amazonaws.com (0 ms)
    216.182.232.66 (0 ms)
    *
    *
    *
    xe-0-3-0.was12.ip4.tinet.net (1 ms)
    xe-9-0-0.was12.ip4.tinet.net (1 ms)
    te0-6-0-5.mpd22.iad02.atlas.cogentco.com (1 ms)
    te0-1-0-5.mpd22.dca01.atlas.cogentco.com (2 ms)
    *
    *
    msk-m9-b1-xe1-0-0.fiord.ru (137 ms)
    msk-m9-b1-xe1-0-0.fiord.ru (141 ms)
    *
    *
    Path MTU (?): Warning
    The path between your network and our system supports an MTU of at least 1500 bytes, and the path between our system and your network has an MTU of 1400 bytes. The path MTU bottleneck that fails to properly report the ICMP "too big" is between * and *. The path between our system and your network does not appear to report properly when the sender needs to fragment traffic.
    Network Access Link Properties +
    Network latency measurements (?): Latency: 130ms Loss: 0.5%
    TCP connection setup latency (?): 140ms
    Network background health measurement (?): no transient outages
    Network bandwidth measurements (?): Upload 1.9 Mbit/sec, Download 3.8 Mbit/sec
    Network buffer measurements (?): Uplink 409 ms, Downlink 120 ms
    HTTP Tests –
    Address-based HTTP proxy detection (?): OK
    We detected no explicit sign of HTTP proxy via IP address changes.
    Content-based HTTP proxy detection (?): OK
    No HTTP header or content changes hint at the presence of a proxy.
    HTTP proxy detection via malformed requests (?): OK
    Deliberately malformed HTTP requests arrive at our server unchanged. We are not able to detect a proxy along the path to our server using this method.
    Filetype-based filtering (?): Note
    Files of type exe remain unmodified by the network.
    Files of type mp3 remain unmodified by the network.
    Files of type torrent remain unmodified by the network.
    A test "virus" (the benign EICAR test file that antivirus vendors recognize as a test) was blocked or modified in transit.
    HTTP caching behavior (?): OK
    We detected no signs of a transparent HTTP cache in your network path.
    JavaScript-based tests (?): OK
    The applet did not execute within a frame.
    Your web browser reports the following cookies for our web page:
    lang = en (set by our server)
    netAlizEd = BaR (set by our server)
    netalyzrStatus = running (set by our server)
    Your web browser was unable to fetch an image using IPv6.
    DNS Tests +
    Restricted domain DNS lookup (?): OK
    Unrestricted domain DNS lookup (?): OK
    Direct DNS support (?): OK
    Direct EDNS support (?): OK
    DNS resolver address (?): OK
    DNS resolver properties (?): Lookup latency 260ms
    Direct probing of DNS resolvers (?): Not Executed
    DNS glue policy (?): OK
    DNS resolver port randomization (?): OK
    DNS lookups of popular domains (?): OK
    DNS external proxy (?): OK
    DNS results wildcarding (?): OK
    DNS-level redirection of specific sites (?): OK
    IPv6 Tests +
    DNS support for IPv6 (?): OK
    IPv4, IPv6, and Your Web Browser (?): IPv6 Connectivity Problem
    IPv6 Connectivity (?): No IPv6 Support
    Host Properties +
    System clock accuracy (?): OK
    Browser properties (?): OK
    Uploaded Data (?): OK
     
  3. капля боли

    капля боли Пользователь

    таже трабла, тока на EU, помагите кто знает де собака зарыта.