Cannot login - No response from server - Firewall

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

2stepping

Junior Member

03-20-2013

I just tried logging in today after patch have the same message someone help


Comment below rating threshold, click here to show it.

marblegargler42

Junior Member

03-20-2013

Played a few games today after patch, a couple minutes ago tried to log in and got the same error as the OP.
Here's my link: http://n3.netalyzr.icsi.berkeley.edu...d70d-4b32-8caa
Thanks for your time!


Comment below rating threshold, click here to show it.

LittleJimmy

Junior Member

03-21-2013

i restarted my router and it worked fine. just wanted to let u guys know. it might help your problems


Comment below rating threshold, click here to show it.

IDidYourMom12

Junior Member

03-21-2013

Hey I got the same message too, no response from server. From the link posted by http://netalyzr.icsi.berkeley.edu/ I have no idea what to do there


Comment below rating threshold, click here to show it.

Yippyx

Junior Member

03-21-2013

Ok guys the fix is disconnect from you're internet then reconnect to it, for some odd reason...

Your welcome.


Comment below rating threshold, click here to show it.

Fabiank2

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

Junior Member

03-21-2013

Similar problem.

I cant login.

When i do, my chat service wont connect and afater i choose my champion the screen turns black.

I´ve been demoted because of this.

Thx Riot.


Comment below rating threshold, click here to show it.

DeadWyrm

Junior Member

03-21-2013

Same problem, managed to get to "Logging on" window but after some long waiting period i only get a "Connection Error - Connection Failure: Unable to connect to the PVP.net server. ..." after i press OK the client closes.
Tried the Internet Explorer thing, didn't work (as expected õ_o), restarting router, pc, desabling firewall/anti-virus, tracing routes, flushing dns, resetting ip config...
Nothing works so far, any Riot response about this issue?


Comment below rating threshold, click here to show it.

Psiche

Junior Member

03-21-2013

Hellos Morgageddon, i have the same problme here D:... this is my test tahtn u post 2 days ago...

http://n3.netalyzr.icsi.berkeley.edu...5436-4eae-a6d6

i dont know if u can read it on ur computer, but well u.u.. i will post the same results below

Result Summary + – (help)
190-176-85-107.speedy.com.ar / 190.176.85.107
Recorded at 00:52 EDT (04:52 UTC), Mar 22 2013. Permalink. Client/server transcript.
Summary of Noteworthy Events + –
Major Abnormalities –
Your DNS resolver returns IP addresses for names that do not exist
Minor Aberrations –
Network packet buffering may be excessive
Not all DNS types were correctly processed
Your computer's clock is slightly slow
Address-based Tests + –
NAT detection (?): NAT Detected +
Local Network Interfaces (?): OK +
DNS-based host information (?): OK +
NAT support for Universal Plug and Play (UPnP) (?): Yes +
Reachability Tests + –
TCP connectivity (?): OK +
UDP connectivity (?): OK +
Traceroute (?): OK +
Path MTU (?): OK +
Hidden Proxy Detection (?): OK +
Network Access Link Properties + –
Network performance (?): Latency: 220 ms, Loss: 2.0% +
TCP connection setup latency (?): 229ms +
Background measurement of network health (?): no transient outages +
Network bandwidth (?): Upload 520 Kbit/s, Download 990 Kbit/s +
Network buffer measurements (?): Uplink 780 ms, Downlink 1500 ms –
We estimate your uplink as having 780 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 1500 ms of buffering. This is quite high, and you may experience substantial disruption to your network performance when performing interactive tasks such as web-surfing while simultaneously conducting large downloads. With such a buffer, real-time applications such as games or audio chat can work quite poorly when conducting large downloads at the same time.
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 +
DNS resolver address (?): OK +
DNS resolver properties (?): Lookup latency 280 ms +
Direct probing of DNS resolvers (?) –
Your system is configured to use 1 DNS resolver(s).
The resolver at 192.168.2.1 (DnsCuy07) could not process the following tested types:
Medium (~1300B) TXT records
Large (~3000B) TXT records
Large (~3000B) TXT records fetched with EDNS0
RTYPE=1169 (deliberately unknown) records
Requests from this resolver come from 200.63.128.173. This resolver requries 392 ms to fetch a result from our server and 670 ms to return a result from its cache. It does not validate DNSSEC. It wildcards NXDOMAIN errors. Instead of an error it returns the following IP address(es): 192.150.42.169. The resolver reports a number of additional properties. Show them.
DNS glue policy (?): OK +
DNS resolver port randomization (?): OK +
DNS lookups of popular domains (?): OK +
DNS external proxy (?): OK +
DNS results wildcarding (?): Warning –
Your ISP's DNS server returns IP addresses even for domain names which should not resolve. Instead of an error, the DNS server returns an address of 208.70.188.15, which resolves to smartbrowsebr-mx.terra.com. You can inspect the resulting HTML content here.
There are several possible explanations for this behavior. The most likely cause is that the ISP is attempting to profit from customer's typos by presenting advertisements in response to bad requests, but it could also be due to an error or misconfiguration in the DNS server.
The big problem with this behavior is that it can potentially break any network application which relies on DNS properly returning an error when a name does not exist.
The following lists your DNS server's behavior in more detail.
www.{random}.com is mapped to 208.70.188.15.
www.{random}.org is mapped to 208.70.188.15.
fubar.{random}.com is mapped to 208.70.188.15.
www.yahoo.cmo [sic] is mapped to 208.70.188.15.
nxdomain.{random}.netalyzr.icsi.berkeley.edu is correctly reported as an error.
DNS-level redirection of specific sites (?): OK +
Direct probing of DNS roots (?): OK +
IPv6 Tests + –
DNS support for IPv6 (?): OK +
IPv4, IPv6, and your web browser (?): No IPv6 support +
IPv6 connectivity (?): No IPv6 support +
Network Security Protocols + –
DNSSEC Network Transport Tests (?): OK +
DNSSEC Support from the DNS Roots (?): OK +
Host Properties + –
System clock accuracy (?): Warning –
Your computer's clock is 8 seconds slow.
Browser properties (?): OK +
Uploaded data (?): OK


This is my test D:! i hope this help you u.u.. thank you


Comment below rating threshold, click here to show it.

deathmyztare

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

Junior Member

03-22-2013

Mine is still not working, Bump


Comment below rating threshold, click here to show it.

LeonBanx

Junior Member

03-22-2013

The ICSI Netalyzr
Start » Analysis » Results
Result Summary + – (help)
24-119-86-226.cpe.cableone.net / 24.119.86.226
Recorded at 22:32 EDT (02:32 UTC next day), Mar 22 2013. Permalink. Referrer. Client/server transcript.
Summary of Noteworthy Events + –
Minor Aberrations –
Certain TCP protocols are blocked in outbound traffic
Network packet buffering may be excessive
Not all DNS types were correctly processed
Your computer's clock is substantially fast
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 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 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: 91 ms, Loss: 0.0% +
TCP connection setup latency (?): 83ms +
Background measurement of network health (?): no transient outages +
Network bandwidth (?): Upload 550 Kbit/s, Download 5.2 Mbit/s +
Network buffer measurements (?): Uplink 330 ms, Downlink 1900 ms –
We estimate your uplink as having 330 ms of buffering. This level may serve well for maximizing speed while minimizing the impact of large transfers on other traffic.
We estimate your downlink as having 1900 ms of buffering. This is quite high, and you may experience substantial disruption to your network performance when performing interactive tasks such as web-surfing while simultaneously conducting large downloads. With such a buffer, real-time applications such as games or audio chat can work quite poorly when conducting large downloads at the same time.
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 +
DNS resolver address (?): OK +
DNS resolver properties (?): Lookup latency 80 ms +
Direct probing of DNS resolvers (?) –
Your system is configured to use 2 DNS resolver(s).
The resolver at 24.116.2.50 (KansasCityDNS.cableone.net) can process all tested types. Requests from this resolver come from 24.119.5.34. This resolver requries 84 ms to fetch a result from our server and 24 ms to return a result from its cache. It does not validate DNSSEC. It does not wildcard NXDOMAIN errors. The resolver reports a number of additional properties. Show them.
The resolver at 24.116.2.34 (bdns4.cableone.net) could not process the following tested types:
Medium (~1300B) TXT records
Large (~3000B) TXT records
Requests from this resolver come from 24.116.3.58. This resolver requries 73 ms to fetch a result from our server and 73 ms to return a result from its cache. It does not validate DNSSEC. It does not wildcard NXDOMAIN errors. The resolver reports a number of additional properties. Show them.
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 (?): OK +
IPv6 Tests + –
DNS support for IPv6 (?): OK +
IPv4, IPv6, and your web browser (?): No IPv6 support +
IPv6 connectivity (?): No IPv6 support +
Network Security Protocols + –
DNSSEC Network Transport Tests (?): OK +
DNSSEC Support from the DNS Roots (?): OK +
Host Properties + –
System clock accuracy (?): Warning –
Your computer's clock is 7229 seconds fast.
Browser properties (?): OK +
Uploaded data (?): OK +
Feedback + –
User-provided feedback –
Feel free to update your feedback below.
If you'd like to give us a way to contact you at a later time, please provide an email address. We will never share your address with anyone.

How is your machine/device connected to the local network?
Wireless
Wired
Where are you right now?
At home
At work
In a public setting (wifi hotspot, internet cafe, etc)
Other (please describe)

Feel free to leave additional comments here.


ID 43ca253f-32168-b2270fc3-c020-4b5d-a89e FAQs + Blog + Papers + Links + ICSI