Constant disconnecting when me and my brother play together

Comment below rating threshold, click here to show it.

keanex

Senior Member

01-21-2013

Me and my brother live together and while the game sometimes lags up when only one of us is playing it is impossible for us both to play together. Pando Media Booster is uninstalled and the ports are forwarded for LoL. I found the Server IP Addresses site and did a tracert to them and they all came back like this: #1, #2, and #3. It's timing out when it gets to Riot servers. I have no firewall on. Any ideas?


Comment below rating threshold, click here to show it.

keanex

Senior Member

01-21-2013

Bump, he can't even log in while I'm logged in currently. Also I ran the ICSI Netalyzer, here's the results.

Summary of Noteworthy Events + –
Minor Aberrations –
Certain TCP protocols are blocked in outbound traffic
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 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 +
Traceroute (?): OK +
Path MTU (?): OK +
Network Access Link Properties + –
Network latency measurements (?): Latency: 30ms Loss: 0.0% +
TCP connection setup latency (?): 190ms +
Network background health measurement (?): no transient outages +
Network bandwidth (?): Upload 3.4 Mbit/sec, Download 12 Mbit/sec +
Network buffer measurements (?): Uplink 160 ms, Downlink 140 ms +
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 110ms +
Direct probing of DNS resolvers (?) –
Your system is configured to use 2 DNS resolver(s).
The resolver at 75.75.75.75 can process all tested types. It validates DNSSEC. It does not wildcard NXDOMAIN errors. The resolver reports a number of additional properties. Show them.
The resolver at 76.76.76.76 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


Comment below rating threshold, click here to show it.

keanex

Senior Member

01-21-2013

Bump.


Comment below rating threshold, click here to show it.

keanex

Senior Member

01-22-2013

Bump. Do mods ever post around here?


Comment below rating threshold, click here to show it.

keanex

Senior Member

01-22-2013

Guess not.


Comment below rating threshold, click here to show it.

Cyclone Janna

Member

01-22-2013

Same issue here. My internet is still on but it says I lost it. VERY frustrating to watch your enemy kill you while u cant move.