Cannot login - No response from server - Firewall

First Riot Post
Comment below rating threshold, click here to show it.

Kristix

Junior Member

03-19-2013

Plz do share how you fixed it, I'm really wanting to solo queue right now


Comment below rating threshold, click here to show it.

TheBlindSpawt

Junior Member

03-19-2013

Alright here were my results:

http://n3.netalyzr.icsi.berkeley.edu...6-4b78-82ee/rd


Comment below rating threshold, click here to show it.

TheBlindSpawt

Junior Member

03-19-2013

**UPDATE**

I just logged in successfully. Whatever you guys did, fixed the problem...


Comment below rating threshold, click here to show it.

Kristix

Junior Member

03-19-2013

Well have fun playing I'll be here waiting for hopefully the same


Comment below rating threshold, click here to show it.

Nawtrandom

Junior Member

Comment below rating threshold, click here to show it.

Nunchucker

Junior Member

Comment below rating threshold, click here to show it.

Earthly

Senior Member

Comment below rating threshold, click here to show it.

Bloody C O C K

This user has referred a friend to League of Legends, click for more information

Junior Member

Comment below rating threshold, click here to show it.

Kristix

Junior Member

03-19-2013

Quote:

how did you get the other link on there? I cant find where to get that


Comment below rating threshold, click here to show it.

TheOctipus

Junior Member

03-19-2013

Please help
Minor Aberrations –
Certain TCP protocols are blocked in outbound traffic
Network packet buffering may be excessive
Some DNS resolvers appear to be down
Address-based Tests + –
NAT detection (?): NAT Detected +
Local Network Interfaces (?): OK +
DNS-based host information (?): OK +
NAT support for Universal Plug and Play (UPnP) (?): Not found +
Reachability Tests + –
TCP connectivity (?): Note –
Direct TCP connections to remote FTP servers (port 21) succeed, but do not receive the expected content.
This is most likely due to the way a NAT or firewall handles FTP traffic, as FTP causes unique problems when developing NATs and firewalls. This is most likely benign.
The client received an empty response instead of our normal banner. This suggests that a firewall, proxy, or filter initially allowed the connection and then terminated it, either because it did not understand our server's reply or decided to block the service.
Direct TCP access to remote SSH servers (port 22) is allowed.
Direct TCP access to remote SMTP servers (port 25) is prohibited.
This means you cannot send email via SMTP to arbitrary mail servers. Such blocking is a common countermeasure against malware abusing infected machines for generating spam. Your ISP likely provides a specific mail server that is permitted. Also, webmail services remain unaffected.
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 +
Traceroute (?): OK +
Path MTU (?): OK +
Hidden Proxy Detection (?): OK +
Network Access Link Properties + –
Network performance (?): Latency: 29 ms, Loss: 0.0% +
TCP connection setup latency (?): 30ms +
Background measurement of network health (?): no transient outages +
Network bandwidth (?): Upload 1.1 Mbit/s, Download 6.2 Mbit/s +
Network buffer measurements (?): Uplink 480 ms, Downlink 110 ms –
We estimate your uplink as having 480 ms of buffering. This level can in some situations prove somewhat high, and you may experience degraded performance when performing interactive tasks such as web-surfing while simultaneously conducting large uploads. Real-time applications, such as games or audio chat, may also work poorly when conducting large uploads at the same time.
We estimate your downlink as having 110 ms of buffering. This level may serve well for maximizing speed while minimizing the impact of large transfers on other traffic.
HTTP Tests + –
Address-based HTTP proxy detection (?): OK +
Content-based HTTP proxy detection (?): OK +
HTTP proxy detection via malformed requests (?): OK +
Filetype-based filtering (?): OK +
HTTP caching behavior (?): OK +
JavaScript-based tests (?): OK +
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 120 ms +
Direct probing of DNS resolvers (?) –
Your system is configured to use 2 DNS resolver(s).
The resolver at 10.0.1.1 can process all tested types. Requests from this resolver come from 68.87.75.203. This resolver requries 117 ms to fetch a result from our server and 3 ms to return a result from its cache. It validates DNSSEC. It does not wildcard NXDOMAIN errors.
The resolver at 100.100.10.24 is not responding to requests.
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 +
Direct probing of DNS roots (?): +
IPv6 Tests + –
DNS support for IPv6 (?): OK +
IPv4, IPv6, and your web browser (?): No IPv6 support +
IPv6 connectivity (?): No IPv6 support +
Host Properties + –
System clock accuracy (?): OK +
Browser properties (?): OK +
Uploaded data (?): OK