Vaag Internet

[Wvg97]

Hallo,

Ik heb sinds eergister een probleem met mijn Internet. Internet explorer, Origin (Game programma) en Utorrent werkten allemaal nog goed. Op een of andere manier deden de programma's steam, xfire en minecraft servers het niet meer. Nou ben ik niet zo'n techneut, maar ik heb van alles uit de troubleshooters gebruikt. Mijn firewall stond het toe, en er waren geen achtergrond programma's. Ik besloot toen de computer met een Medion recovery disk op te schonen zoals ik eerder al had gedaan (Niet dat dit probleem zich eerder heeft voor gedaan), maar helaas werkte het deze keer ook niet. Nu doet een nieuwere versie van Utorrent het ook al niet meer. Ik heb toen zo'n test gedaan met de volgende uitslag:

Result Summary + – (help)

* Hier stond mij IP *

Recorded at 10:44 EDT (14:44 UTC), Sep 02 2013. Permalink. Client/server transcript.
Summary of Noteworthy Events +   –
Minor Aberrations –
Certain TCP protocols are blocked in outbound traffic 
Certain UDP protocols are blocked in outbound traffic 
Not all DNS types were correctly processed 
Address-based Tests +   –
NAT detection (?): NAT Detected +
Local Network Interfaces (?): OK +
DNS-based host information (?): OK +
Reachability Tests +   –
TCP connectivity (?): Note –
Direct TCP connections to remote FTP servers (port 21) failed.
This is commonly due to how a NAT or firewall handles FTP traffic, as FTP causes unique problems when developing NATs and firewalls.
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 allowed.
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 (?): Note –
We are unable to deliver non-DNS UDP datagrams to our servers. Possible reasons include a restrictive Java security policy, a blocking rule imposed by your firewall or personal firewall configuration, or filtering performed by your ISP. Although it means we cannot conduct the latency and bandwidth tests, it does not necessarily indicate a problem with your network.
Traceroute (?): Not executed +
Path MTU (?): Not executed +
Hidden Proxy Detection (?): OK +
Network Access Link Properties +   –
Network performance (?): Prohibited +
TCP connection setup latency (?): 110ms +
Background measurement of network health (?): Not executed +
Network bandwidth (?): Not executed +
Network buffer measurements (?): Not executed +
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 170 ms +
Direct probing of DNS resolvers (?) –
Your system is configured to use 2 DNS resolver(s).
The resolver at 212.54.40.25 (Ik+ben+Ziggo) could not process the following tested types:
Large (~3000B) TXT records fetched with EDNS0
Requests from this resolver come from 212.54.41.235. This resolver requries 168 ms to fetch a result from our server and 14 ms to return a result from its cache. It does not validate DNSSEC. It provides DNSSEC records upon request. It does not wildcard NXDOMAIN errors. The resolver reports a number of additional properties. Show them.
The resolver at 212.54.35.25 (Ik+ben+Ziggo) can process all tested types. Requests from this resolver come from 212.54.35.232. This resolver requries 172 ms to fetch a result from our server and 17 ms to return a result from its cache. It does not validate DNSSEC. It provides DNSSEC records upon request. 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 (?): Not executed +
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 Support from the DNS Roots (?): OK +
Host Properties +   –
System clock accuracy (?): Not executed +
Browser properties (?): OK +
Uploaded data (?): OK

Kan iemand mij verder helpen?

 

[gast0225]

Systeemherstel naar een dag of 3 geleden al geprobeerd?

 

[Wvg97]

Ja dat heb ik gedaan.

Windows problemen vast stellen geeft dit:
De verbinding tussen uw toegangspunt, router of kabelmodem en internet is defect Gedetecteerd

De netwerkgateway is toegankelijk, maar er kan geen netwerkverkeer van internet worden ontvangen.

 

[gast0225]

Ik moet passen. Je kan door je diverse acties al zoveel hebben 'gedaan', dat op normale wijze de boel herstellen lastig wordt. Misschien iemand anders?

 

[toscana99]

Wwg97, beb je al geprobeerd om de programmas steam, xfire en minecraft"" te deinstalleren en opnieuw te installeren? Waarschijnlijk gebruiken deze programmas (die ik trouwens niet ken) bepaalde TCP/UDP poorten , die in je Firewall enabled moeten zijn. Dit wordt meestal tijdens installatie van het desbetreffende programma automatisch gedaan.
groet, toscana99

 

[Wvg97]

Opgelost. Mijn vader had via Ziggo iets ingevoerd en was dit vergeten <_<

 

[toscana99]

Wvg97, nu zijn wij allen natuurlijk geïnteresseerd wat dat "iets" was

 

[Wvg97]

Hij deed er nog al raar over. laten we hopen dat het niet inzagen van internet historie is haha

 

[coenraad]

Opgelost.

Op de blauwe balk bovenin wordt anders het tegendeel beweerd:shocked: