Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

Wireless random errors


  • Please log in to reply

#1
gauntlet1

gauntlet1

    New Member

  • Member
  • Pip
  • 1 posts

Hello,
I bought a new HP probook (win7 64bit)
and brought it home to use alongside my older laptop (Lenovo, win7 64bit)
 

Both are connected to the same router via Wifi, but the new one is acting up - randomly displaying error screens like ERR_TIMOUT/DNS Related error/no internet etc...


I tried changing DNS to 8.8.8.8 and others, canceled IPV6, tried winsocket and netshell commands, restarting everything and nothing.
Tried disabling firewall and bullguard antivirus.

network adapters are all up to date.

The error screens are usually accompanied by long response time (resolving host, waiting for... establishing secure connection)
and sometimes the webpages upload only partly and I need to refresh in order to keep them going.

The problem is not permanent. It can happen for an hour and then all is good, or just in the morning
regardless of any configuration modification.

 

This is a check I ran with ICSI Netalyzr today (displaying error lines only)-
 

Network performance (?): Latency: 190 ms, Loss: 23.0% –

We recorded a packet loss of 23%. This loss is very significant and will lead to serious performance problems.
It could be due either to very high load on our servers due to a large number of visitors, or problems in your network.
All the packet loss appears to have occurred on the path from our server to your computer.

TCP connection setup latency (?): 1100ms –

Background measurement of network health (?): 23 transient outages, longest: 15.8 seconds –

Network buffer measurements (?): Uplink 620 ms, Downlink is good –

Your ISP's DNS resolver requires 2000 ms to conduct an external lookup. It takes 200 ms for your ISP's DNS resolver to lookup a name on our server.
This is particularly slow, and you may see significant performance degradation as a result.

Only some DNS root server instances returned proper DNSSEC information. The working roots are: A, B, C, E, F, G, H, I, K, L, M


And this one is half hour later -

 

We received UPnP responses from one device: •10.0.0.138: this device provided a valid device description via its UPnP URL.
This description, viewable here, contains the following information about this gateway:◦Name: NETGEAR DG834Nv2 Router
◦Manufacturer: NETGEAR
◦Manufacturer URL: http://www.netgear.com/
◦Model name: NETGEAR DG834Nv2 Router
◦Model number: 1.01.04
◦Model URL: http://www.netgear.com/
◦Model Description: NETGEAR DG834Nv2 Router

This device appears to run "Netgear/1.0 UPnP/1.0 miniupnpd/1.0". This system may be vulnerable to CVE-2013-0230

Direct TCP access to remote SMTP servers (port 25) succeeds, but does not return the expected content.

This suggests that your network enforces a mandatory SMTP proxy which may or may not allow you to send email directly from your system.
This is probably a countermeasure against malware abusing infected machines for generating spam.
You ISP also likely provides a specific mail server that is permitted. Also, webmail services remain unaffected.

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 connections to remote POP3 servers (port 110) succeed, but do not receive the expected content.
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 connections to remote IMAP servers (port 143) succeed, but do not receive the expected content.
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.

 Hidden Proxy Detection (?): Warning –

Netalyzr detected the following proxies:
◦Port: 25 , Response Time: 0 ms
◦Port: 80 (HTTP), Response Time: 0 ms
◦Port: 110 (POP3), Response Time: 0 ms
◦Port: 143 (IMAP), Response Time: 0 ms

So totally different reports on the same configuration.

Again - meantime the other laptop next to it is surfing the web (chrome or IE) just fine.

I know the problem is gonna come back again randomly through the day....
any ideas?
 


  • 0

Advertisements







Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP