- 227
- 5
- CPU
- i5 3570k cooled by MACHO Hr-02 Rev. A
- Scheda Madre
- Asrock z77 Extreme 4
- HDD
- SSD Samsung 840 250GB & HDD Samsung 1TB
- RAM
- Corsair Vengeance CL-9 8GB (4x2)
- GPU
- MSI R7870 HAWK
- Monitor
- LG Flatron M2362D
- PSU
- EVGA Supernova 750W B2
- Case
- NZXT Phantom 410
- OS
- Windows 7 64bit
Ciao a tutti, dopo aver eseguito un test per la connessione su ICSI Netalyzr ho iscontrato un po' di errorini che però, a causa della mia poca esperienza, non riesco a "tradurre". Qualucno può gentilmente aiutarmi a capire e magari anche a risolvere i miei problemi? Grazie infinite.
Address-based Tests
NAT support for Universal Plug and Play (UPnP) (?): Yes–
We received UPnP responses from one device:
Network Access Link Properties
Network buffer measurements (?): Uplink 2400 ms, Downlink 940 ms–
We estimate your uplink as having 2400 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 uploads. With such a buffer, real-time applications such as games or audio chat can work quite poorly when conducting large uploads at the same time.
DNS Tests
Internal Server Error on Test Report
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 212.48.8.140, which does not resolve. 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.
Questi qui sopra sono gli errori che il test ha riscontrato. Ringrazio anticipatamete per le risposte e gli aiuti che mi darete.
Address-based Tests
NAT support for Universal Plug and Play (UPnP) (?): Yes–
We received UPnP responses from one device:
- 192.168.1.1: this device provided a valid device description via its UPnP URL. This description, viewable here, contains the following information about this gateway:
- Name: LINKSYS WAG200G Gateway
- Manufacturer: LINKSYS
- Manufacturer URL: http://www.linksys.com
- Model name: Wireless-G ADSL Home Gateway
- Model number: WAG200G
- Model URL: http://www.linksys.com
- Model Description: LINKSYS WAG200G Gateway
Network Access Link Properties
Network buffer measurements (?): Uplink 2400 ms, Downlink 940 ms–
We estimate your uplink as having 2400 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 uploads. With such a buffer, real-time applications such as games or audio chat can work quite poorly when conducting large uploads at the same time.
DNS Tests
Internal Server Error on Test Report
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 212.48.8.140, which does not resolve. 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 212.48.8.140.
- www.{random}.org is mapped to 212.48.8.140.
- fubar.{random}.com is mapped to 212.48.8.140.
- www.yahoo.cmo [sic] is mapped to 212.48.8.140.
- nxdomain.{random}.netalyzr.icsi.berkeley.edu is mapped to 212.48.8.140
Questi qui sopra sono gli errori che il test ha riscontrato. Ringrazio anticipatamete per le risposte e gli aiuti che mi darete.