Jump to content

Connection Time Out Issue

AudaciousGnome

Hi,

 

Recently I have been having an issue with my desktop PC. My wireless internet works perfectly on my Macbook Pro, iPhone and PS4 but on my Windows 8 PC I constantly get this message:

"this webpage is not avaliable. ERR_CONNECTION _TIMED_OUT" (using Chrome)

 

Things will work fine for maybe a minute or two but then I get this error, continuously across all sites.

 

I have tried restarting my modem, disabling and re-enabling my wireless adapter, restarting my PC multiple times, tried using Internet Explorer/FireFox/Chrome. I don't have any antivirus software(I do have adblock not sure if that makes a difference?), I have tried turning my firewall on and off. But nothing helps. 


The wireless adapter I have is a Gigabyte WIFI Wireless 802.11AC Dual Band+Bluetooth4.0 PCI-E X1 Expa
My PC specs are: i7-4790k, 16GB RAM, GTX 980 SC

Under Wifi Status my IPV4 Connectivity says Internet and the IPV6 Connectivity says No Network Access. 
My signal strength is full and my normal speed is 30 down and 10 up. 

Can someone please help me with this?

Link to comment
Share on other sites

Link to post
Share on other sites

Have you attempted to plug in a ethernet cable instead of using WiFi?

Link to comment
Share on other sites

Link to post
Share on other sites

Have you attempted to plug in a ethernet cable instead of using WiFi?

Unfortuantely that is not an option as my modem is upstairs and can't be shifted and I don't have a 20m cable. 

 

As a last resort I might just have to shift my whole PC upstairs and try but I really don't want to do that if I can help it. 

Link to comment
Share on other sites

Link to post
Share on other sites

Unfortuantely that is not an option as my modem is upstairs and can't be shifted and I don't have a 20m cable. 

 

As a last resort I might just have to shift my whole PC upstairs and try but I really don't want to do that if I can help it. 

 

Update/reinstall network drivers, update bios, scan for malware with malwarebytes, change router channel (Try 1, 3, 6, 8, 11).

blackshades on

 

 

Link to comment
Share on other sites

Link to post
Share on other sites

Update/reinstall network drivers, update bios, scan for malware with malwarebytes, change router channel (Try 1, 3, 6, 8, 11).

Up to date/done, Up to date, Scanned no issues, tried numerous channels still getting the same time out error.

:(

Link to comment
Share on other sites

Link to post
Share on other sites

Hi,

Recently I have been having an issue with my desktop PC. My wireless internet works perfectly on my Macbook Pro, iPhone and PS4 but on my Windows 8 PC I constantly get this message:

"this webpage is not avaliable. ERR_CONNECTION _TIMED_OUT" (using Chrome)

Things will work fine for maybe a minute or two but then I get this error, continuously across all sites.

I have tried restarting my modem, disabling and re-enabling my wireless adapter, restarting my PC multiple times, tried using Internet Explorer/FireFox/Chrome. I don't have any antivirus software(I do have adblock not sure if that makes a difference?), I have tried turning my firewall on and off. But nothing helps.

The wireless adapter I have is a Gigabyte WIFI Wireless 802.11AC Dual Band+Bluetooth4.0 PCI-E X1 Expa

My PC specs are: i7-4790k, 16GB RAM, GTX 980 SC

Under Wifi Status my IPV4 Connectivity says Internet and the IPV6 Connectivity says No Network Access.

My signal strength is full and my normal speed is 30 down and 10 up.

Can someone please help me with this?

Press the start menu button, type in CMD, and then type into the CMD, ipconfig /all and paste the information on the forum.

CPU: AMD Ryzen 5 5600X | CPU Cooler: Stock AMD Cooler | Motherboard: Asus ROG STRIX B550-F GAMING (WI-FI) | RAM: Corsair Vengeance LPX 16 GB (2 x 8 GB) DDR4-3000 CL16 | GPU: Nvidia GTX 1060 6GB Zotac Mini | Case: K280 Case | PSU: Cooler Master B600 Power supply | SSD: 1TB  | HDDs: 1x 250GB & 1x 1TB WD Blue | Monitors: 24" Acer S240HLBID + 24" Samsung  | OS: Win 10 Pro

 

Audio: Behringer Q802USB Xenyx 8 Input Mixer |  U-PHORIA UMC204HD | Behringer XM8500 Dynamic Cardioid Vocal Microphone | Sound Blaster Audigy Fx PCI-E card.

 

Home Lab:  Lenovo ThinkCenter M82 ESXi 6.7 | Lenovo M93 Tiny Exchange 2019 | TP-LINK TL-SG1024D 24-Port Gigabit | Cisco ASA 5506 firewall  | Cisco Catalyst 3750 Gigabit Switch | Cisco 2960C-LL | HP MicroServer G8 NAS | Custom built SCCM Server.

 

 

Link to comment
Share on other sites

Link to post
Share on other sites

Weird thing with this is I am still able to download games from Steam, albeit extremely slowly(100KB/s) compared to 4-5MB/s before. So the wireless still seems to be connecting(barely).....but I literally cannot use the internet, not even to open google, without getting the time out message. 

Link to comment
Share on other sites

Link to post
Share on other sites

I would recommend a fresh install as it doesn't appear to be a card issue nor a browser issue. Could you have installed something recently, could you revert back to a restore point from before the issues? I am only saying do a fresh install as I personally don't care about reinstalling applications. I fresh install all my computer every 3 months anyways.

Link to comment
Share on other sites

Link to post
Share on other sites

Press the start menu button, type in CMD, and then type into the CMD, ipconfig /all and paste the information on the forum.

Microsoft Windows [Version 6.3.9600]

© 2013 Microsoft Corporation. All rights reserved.

 

C:\Users\user>ipconfig/all

 

Windows IP Configuration

 

   Host Name . . . . . . . . . . . . : user-pc

   Primary Dns Suffix  . . . . . . . :

   Node Type . . . . . . . . . . . . : Hybrid

   IP Routing Enabled. . . . . . . . : No

   WINS Proxy Enabled. . . . . . . . : No

   DNS Suffix Search List. . . . . . : lan

 

Ethernet adapter Ethernet:

 

   Media State . . . . . . . . . . . : Media disconnected

   Connection-specific DNS Suffix  . :

   Description . . . . . . . . . . . : Intel® Ethernet Connection (2) I218-V

   Physical Address. . . . . . . . . : 78-24-AF-37-DB-81

   DHCP Enabled. . . . . . . . . . . : Yes

   Autoconfiguration Enabled . . . . : Yes

 

Wireless LAN adapter Local Area Connection* 3:

 

   Media State . . . . . . . . . . . : Media disconnected

   Connection-specific DNS Suffix  . :

   Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter

   Physical Address. . . . . . . . . : A0-A8-CD-26-FA-DF

   DHCP Enabled. . . . . . . . . . . : Yes

   Autoconfiguration Enabled . . . . : Yes

 

Ethernet adapter Bluetooth Network Connection:

 

   Media State . . . . . . . . . . . : Media disconnected

   Connection-specific DNS Suffix  . :

   Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)

   Physical Address. . . . . . . . . : A0-A8-CD-26-FA-E2

   DHCP Enabled. . . . . . . . . . . : Yes

   Autoconfiguration Enabled . . . . : Yes

 

Wireless LAN adapter WiFi:

 

   Connection-specific DNS Suffix  . : lan

   Description . . . . . . . . . . . : Intel® Dual Band Wireless-AC 7260

   Physical Address. . . . . . . . . : A0-A8-CD-26-FA-DE

   DHCP Enabled. . . . . . . . . . . : Yes

   Autoconfiguration Enabled . . . . : Yes

   Link-local IPv6 Address . . . . . : fe80::81b4:5e97:86f:a4e1%3(Preferred)

   IPv4 Address. . . . . . . . . . . : 192.168.1.103(Preferred)

   Subnet Mask . . . . . . . . . . . : 255.255.255.0

   Lease Obtained. . . . . . . . . . : Monday, 27 April 2015 4:08:20 p.m.

   Lease Expires . . . . . . . . . . : Tuesday, 28 April 2015 8:33:15 p.m.

   Default Gateway . . . . . . . . . : Don't think you need to see this

   DHCP Server . . . . . . . . . . . : Don't think you need to see this

   DHCPv6 IAID . . . . . . . . . . . : 60860621

   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1C-0D-13-B9-78-24-AF-37-DB-81

 

   DNS Servers . . . . . . . . . . . : 192.168.1.254

   NetBIOS over Tcpip. . . . . . . . : Enabled

 

Tunnel adapter isatap.lan:

 

   Media State . . . . . . . . . . . : Media disconnected

   Connection-specific DNS Suffix  . : lan

   Description . . . . . . . . . . . : Microsoft ISATAP Adapter

   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

   DHCP Enabled. . . . . . . . . . . : No

   Autoconfiguration Enabled . . . . : Yes

 

Tunnel adapter Teredo Tunneling Pseudo-Interface:

 

   Connection-specific DNS Suffix  . :

   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface

   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

   DHCP Enabled. . . . . . . . . . . : No

   Autoconfiguration Enabled . . . . : Yes

   IPv6 Address. . . . . . . . . . . : 2001:0:9d38:6ab8:1829:2c22:3f57:fe98(Pref

erred)

   Link-local IPv6 Address . . . . . : fe80::1829:2c22:3f57:fe98%9(Preferred)

   Default Gateway . . . . . . . . . : ::

   DHCPv6 IAID . . . . . . . . . . . : 352321536

   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1C-0D-13-B9-78-24-AF-37-DB-81

 

   NetBIOS over Tcpip. . . . . . . . : Disabled

Link to comment
Share on other sites

Link to post
Share on other sites

I would recommend a fresh install as it doesn't appear to be a card issue nor a browser issue. Could you have installed something recently, could you revert back to a restore point from before the issues? I am only saying do a fresh install as I personally don't care about reinstalling applications. I fresh install all my computer every 3 months anyways.

Honestly I haven't installed anything new for at least a month or two. All I do is play games on Steam.

Link to comment
Share on other sites

Link to post
Share on other sites

Default Gateway . . . . . . . . . : Don't think you need to see this

   DHCP Server . . . . . . . . . . . : Don't think you need to see this

 

It is a private IP address. You should be giving that information if it helps. 

My Gateway is 192.168.1.254. Doesn't mean you can now DDOS or hack me.

 

ping your gateway with the -t arg, then reproduce the issue, if the ping shows nothing changing, the you can ignore (for the most part) everything behind your gateway.

 

Also tracert can help if your being pointed through a route that doesn't exist anymore.

 

could also look at flushing DNS cache.

Link to comment
Share on other sites

Link to post
Share on other sites

Wireless LAN adapter WiFi:

 

   Connection-specific DNS Suffix  . : lan

   Description . . . . . . . . . . . : Intel® Dual Band Wireless-AC 7260

   Physical Address. . . . . . . . . : A0-A8-CD-26-FA-DE

   DHCP Enabled. . . . . . . . . . . : Yes

   Autoconfiguration Enabled . . . . : Yes

   Link-local IPv6 Address . . . . . : fe80::81b4:5e97:86f:a4e1%3(Preferred)

   IPv4 Address. . . . . . . . . . . : 192.168.1.103(Preferred)

   Subnet Mask . . . . . . . . . . . : 255.255.255.0

   Lease Obtained. . . . . . . . . . : Monday, 27 April 2015 4:08:20 p.m.

   Lease Expires . . . . . . . . . . : Tuesday, 28 April 2015 8:33:15 p.m.

   Default Gateway . . . . . . . . . : Don't think you need to see this

   DHCP Server . . . . . . . . . . . : Don't think you need to see this

   DHCPv6 IAID . . . . . . . . . . . : 60860621

   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1C-0D-13-B9-78-24-AF-37-DB-81

 

   DNS Servers . . . . . . . . . . . : 192.168.1.254

   NetBIOS over Tcpip. . . . . . . . : Enabled

Your already "revealed" your Gateway with the DNS server. And it seems you are using the routers DNS service. You should change that.

Did you by any chance tamper with IPv6?

 

You say that you barely connect to the router, I'm guessing that your router is far away or behind a lot of walls?

I'm curious to look at a traceroute, execute this commands as an Administrator (means opening CMD by Run As Administrator).

//If you changed your DNS server, now you should flush your DNS cache:ifconfig /flushdns//Now you should flush your routing tablenetsh interface ip delete destinationcache//And finally do a traceroutetracert google.com//A lot of IP addresses should appear, if you fear for your security, mask the last 2 octets.//So if you get 54.62.89.41 then mask it so it looks like 54.62.xx.xx

 

Link to comment
Share on other sites

Link to post
Share on other sites

 

Your already "revealed" your Gateway with the DNS server. And it seems you are using the routers DNS service. You should change that.

Did you by any chance tamper with IPv6?

 

You say that you barely connect to the router, I'm guessing that your router is far away or behind a lot of walls?

I'm curious to look at a traceroute, execute this commands as an Administrator (means opening CMD by Run As Administrator).

//If you changed your DNS server, now you should flush your DNS cache:ifconfig /flushdns//Now you should flush your routing tablenetsh interface ip delete destinationcache//And finally do a traceroutetracert google.com//A lot of IP addresses should appear, if you fear for your security, mask the last 2 octets.//So if you get 54.62.89.41 then mask it so it looks like 54.62.xx.xx

Hi.

 

I have not tampered with IPV6 and I don't even know how I would go about doing that.

Yes the PC is downstairs but so is my laptop and so is my PS4 and they all have no been affected at all while the PC is constantly getting timeouts. 

I have not changed my DNS. Again don't know how so wouldn't do that.

The trace came back with this:

C:\Windows\system32>tracert google.com

 

Tracing route to google.com [198.18.1.183]

over a maximum of 30 hops:

 

  1     1 ms    <1 ms    <1 ms  dsldevice.lan [192.168.1.254]

  2   577 ms   877 ms   521 ms  125-239-200-1.jetstream.xtra.co.nz [125.239.200.

1]

  3     *        *        *     Request timed out.

  4     *        *        *     Request timed out.

  5     *        *        *     Request timed out.

  6     *        *        *     Request timed out.

  7     *        *        *     Request timed out.

  8     *        *        *     Request timed out.

  9     *        *        *     Request timed out.

 10     *        *        *     Request timed out.

 11     *        *        *     Request timed out.

 12     *        *        *     Request timed out.

 13     *        *        *     Request timed out.

Link to comment
Share on other sites

Link to post
Share on other sites

Check if you can ping google.com versus google's ip address (which is 203.2.228.159 for me).

Link to comment
Share on other sites

Link to post
Share on other sites

snip

 

This is interesting. And you say all other devices are working normally? Did you perform the commands I wrote, except the tracert?

 

The latency to your router is 1ms while from your router to the ISP gateway is 650ms, and after that all your packets get dropped. Could you connect your laptop via ethernet and do the same thing?

Link to comment
Share on other sites

Link to post
Share on other sites

This is interesting. And you say all other devices are working normally? Did you perform the commands I wrote, except the tracert?

 

The latency to your router is 1ms while from your router to the ISP gateway is 650ms, and after that all your packets get dropped. Could you connect your laptop via ethernet and do the same thing?

Any idea what might cause that?

I just did it all again and got these results. The internet worked for 5 minutes and then I got the "time out error" again on my PC.

Microsoft Windows [Version 6.3.9600]

© 2013 Microsoft Corporation. All rights reserved.

 

C:\Windows\system32>ipconfig /flushdns

 

Windows IP Configuration

 

Successfully flushed the DNS Resolver Cache.

 

C:\Windows\system32>netsh interface ip delete destinationcache

Ok.

 

 

C:\Windows\system32>tracert google.com

 

Tracing route to google.com [74.125.237.193]

over a maximum of 30 hops:

 

  1     1 ms     3 ms     1 ms  dsldevice.lan [192.168.1.254]

  2   506 ms   709 ms   479 ms  125-239-200-1.jetstream.xtra.co.nz [125.239.200.

1]

  3     *        *        *     Request timed out.

  4    31 ms    34 ms    30 ms  ae8-10.akbr6.global-gateway.net.nz [122.56.116.5

]

  5    39 ms    30 ms    30 ms  ae5-2.akbr7.global-gateway.net.nz [210.55.202.21

3]

  6    55 ms    54 ms    54 ms  xe0-0-1.sgbr3.global-gateway.net.nz [202.50.232.

110]

  7    55 ms   210 ms    58 ms  ae2-10.sgbr4.global-gateway.net.nz [202.50.232.2

46]

  8    55 ms    55 ms    59 ms  google-gsw.sgbr4.global-gateway.net.nz [202.50.2

37.198]

  9    57 ms    56 ms    57 ms  209.85.142.122

 10    56 ms    56 ms    56 ms  72.14.236.181

 11    56 ms    55 ms    55 ms  syd01s19-in-f1.1e100.net [74.125.237.193]

 

Trace complete.

 

C:\Windows\system32>

Link to comment
Share on other sites

Link to post
Share on other sites

My laptop(Macbook Pro) which is literally right next to my PC  gives these results when I run a trace to google.com:

Note the wireless internet on my Laptop is working perfectly, in fact I am using it now to post here. It is the PC(results above) who's internet is not working.

traceroute google.com

traceroute to google.com (216.58.220.110), 64 hops max, 52 byte packets

 1  dsldevice (192.168.1.254)  2.096 ms  3.424 ms  1.090 ms

 2  125-239-200-1.jetstream.xtra.co.nz (125.239.200.1)  1014.393 ms  579.234 ms  602.561 ms

 3  * * *

 4  ae8-10.akbr6.global-gateway.net.nz (122.56.116.5)  33.965 ms  33.993 ms  33.050 ms

 5  ae5-2.akbr7.global-gateway.net.nz (210.55.202.213)  31.865 ms  37.549 ms  32.747 ms

 6  xe0-0-4.sgbr3.global-gateway.net.nz (122.56.127.94)  56.107 ms

    xe0-0-1.sgbr3.global-gateway.net.nz (202.50.232.110)  56.964 ms

    xe0-0-6.sgbr3.global-gateway.net.nz (202.50.232.190)  55.908 ms

 7  ae2-10.sgbr4.global-gateway.net.nz (202.50.232.246)  56.881 ms  59.320 ms  55.806 ms

 8  google-gsw.sgbr4.global-gateway.net.nz (202.50.237.198)  56.234 ms  55.719 ms  55.916 ms

 9  209.85.142.122 (209.85.142.122)  57.051 ms  57.204 ms  57.106 ms

10  209.85.142.11 (209.85.142.11)  57.881 ms  58.173 ms  56.378 ms

11  syd10s01-in-f14.1e100.net (216.58.220.110)  58.587 ms  69.761 ms  57.318 ms

Link to comment
Share on other sites

Link to post
Share on other sites

Tracing route to google.com [74.125.237.193]

over a maximum of 30 hops:

 

  1     1 ms     3 ms     1 ms  dsldevice.lan [192.168.1.254]

  2   506 ms   709 ms   479 ms  125-239-200-1.jetstream.xtra.co.nz [125.239.200.

1]

  3     *        *        *     Request timed out.

  4    31 ms    34 ms    30 ms  ae8-10.akbr6.global-gateway.net.nz [122.56.116.5

]

  5    39 ms    30 ms    30 ms  ae5-2.akbr7.global-gateway.net.nz [210.55.202.21

3]

  6    55 ms    54 ms    54 ms  xe0-0-1.sgbr3.global-gateway.net.nz [202.50.232.

110]

  7    55 ms   210 ms    58 ms  ae2-10.sgbr4.global-gateway.net.nz [202.50.232.2

46]

  8    55 ms    55 ms    59 ms  google-gsw.sgbr4.global-gateway.net.nz [202.50.2

37.198]

  9    57 ms    56 ms    57 ms  209.85.142.122

 10    56 ms    56 ms    56 ms  72.14.236.181

 11    56 ms    55 ms    55 ms  syd01s19-in-f1.1e100.net [74.125.237.193]

 

Trace complete.

 

C:\Windows\system32>

 

 

 

traceroute google.com

traceroute to google.com (216.58.220.110), 64 hops max, 52 byte packets

 1  dsldevice (192.168.1.254)  2.096 ms  3.424 ms  1.090 ms

 2  125-239-200-1.jetstream.xtra.co.nz (125.239.200.1)  1014.393 ms  579.234 ms  602.561 ms

 3  * * *

 4  ae8-10.akbr6.global-gateway.net.nz (122.56.116.5)  33.965 ms  33.993 ms  33.050 ms

 5  ae5-2.akbr7.global-gateway.net.nz (210.55.202.213)  31.865 ms  37.549 ms  32.747 ms

 6  xe0-0-4.sgbr3.global-gateway.net.nz (122.56.127.94)  56.107 ms

    xe0-0-1.sgbr3.global-gateway.net.nz (202.50.232.110)  56.964 ms

    xe0-0-6.sgbr3.global-gateway.net.nz (202.50.232.190)  55.908 ms

 7  ae2-10.sgbr4.global-gateway.net.nz (202.50.232.246)  56.881 ms  59.320 ms  55.806 ms

 8  google-gsw.sgbr4.global-gateway.net.nz (202.50.237.198)  56.234 ms  55.719 ms  55.916 ms

 9  209.85.142.122 (209.85.142.122)  57.051 ms  57.204 ms  57.106 ms

10  209.85.142.11 (209.85.142.11)  57.881 ms  58.173 ms  56.378 ms

11  syd10s01-in-f14.1e100.net (216.58.220.110)  58.587 ms  69.761 ms  57.318 ms

 

 

Yeah, seems like you are running into some routing issues on your PC. I'm not sure but for some reason I suspect IPv6 might be causing the issue, can you disable IPv6, execute all the commands again and see if that solves it? Look up on google how to disable IPv6 only on the PC.

Link to comment
Share on other sites

Link to post
Share on other sites

Okay so updates with this. 

I took my wireless card and dongle to a friends house and it worked. So it is not faulty. 

I moved the computer upstairs and connected via ethernet and the same thing happened. Internet worked great for 2 minutes then got the time out issues again. 

He is the trace over ethernet:

Microsoft Windows [Version 6.3.9600]

© 2013 Microsoft Corporation. All rights reserved.

 

C:\Windows\system32>tracert google.com

 

Tracing route to google.com [198.18.1.58]

over a maximum of 30 hops:

 

  1    <1 ms    <1 ms    <1 ms  dsldevice.lan [192.168.1.254]

  2   706 ms   406 ms   780 ms  125-239-200-1.jetstream.xtra.co.nz [125.239.200.

1]

  3     *        *        *     Request timed out.

  4     *        *        *     Request timed out.

  5     *        *        *     Request timed out.

  6     *        *        *     Request timed out.

  7     *        *        *     Request timed out.

  8     *        *        *     Request timed out.

  9     *        *        *     Request timed out.

 10     *        *        *     Request timed out.

 11     *        *        *     Request timed out.

 12     *        *        *     Request timed out.

 13     *        *        *     Request timed out.

 14     *        *        *     Request timed out.

 15     *        *        *     Request timed out.

 16     *        *        *     Request timed out.

 17     *        *        *     Request timed out.

 18     *        *        *     Request timed out.

 19     *        *        *     Request timed out.

 20     *        *        *     Request timed out.

 21     *        *        *     Request timed out.

 22     *        *        *     Request timed out.

 23     *        *        *     Request timed out.

 24     *        *        *     Request timed out.

 25     *        *        *     Request timed out.

 26     *        *        *     Request timed out.

 27     *        *        *     Request timed out.

 28     *        *        *     Request timed out.

 29     *        *        *     Request timed out.

 30     *        *        *     Request timed out.

 

Trace complete.

 

C:\Windows\system32>

 

 

So I guess it must be a hardware issue? 

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×