This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
This happened once before, a few months back. I was unable to visit a specific website when on the internet via my home WiFi Network. I could access any other website without issue. I could also access the specific website from my cell phone, or from anywhere else...it was only while on my home WiFi that the issue arose. After discussion with both the host of the website, and my ISP, it was decided that I needed a new cable modem, and WiFi Router. I purchased both, and the problem went away. Now it has returned. Since my modem and router are new, seems that cannot be the issue. My ISP has looked into it, and said they have never experienced such an issue, and do not know what else to advise. Has anyone else every experienced this issue? Any guidance would be greatly appreciated as it is annoying not being able to access this one website from home. I am currently turning on the mobile hotspot on my cell phone and accessing it that way without issue. I should also ad that I have tried shutting down both the modem and the router and rebooting with no success. I use a Surface Pro 4 so cannot connect directly to the modem using a LAN connection. I have also attempted connecting to the site using my MacBook Air and have the same issue. It seems clear that the issue has to do with my network.....Thanks in advance!
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Answer accepted by question author
As a test, change the DNS servers in network properties to use Google DNS servers 8.8.8.8 and 8.8.4.4. The instructions at http://www.howtogeek.com/howto/7406/speed-up-your-web-browsing-with-google-public-dns/ look pretty good.
Restart after you do this and run the tracert again and see if you can connect. Let's see if it is a different route to the destination host.
open a cmd prompt and do a tracert to the website in question. if you wanted to
tracert to microsoft. com you would type
tracert microsoft.com
and press enter
tracert to the site in question and copy and paste the TEXT output (not a screen
shot) into a reply.
Thanks for the reply! Yes, my ISP had me run the tracert and said that everything works fine until the request gets to the hos server, then times out. The host server checked and said the site is fully accesible from everywhere else, so the issue has to be with my isp, or my network. Basically, everyone shrugs their shoulders and says the problem is not with them. Frustrating. Not sure i understand your question in relation to accessing via their ip address...dont know how to do that. Unfortunately a good deal of this is above my level of understading. To my knowledge, i have changed nothing in my system, so cannot understand why it would just stop working. Thanks again!
Have you tried accessing the site by it's ip address? You can also perform a tracert at the dos prompt which will indicate where in the network you are failing. The syntax of the trace route command is tracert + name or ip of website (eg... tracert www.google.com)
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Users\avasc>tracert www.avascapes.com
Tracing route to avascapes.com [67.227.214.114]
over a maximum of 30 hops:
1 2 ms 4 ms 2 ms READYSHARE [192.168.1.1]
2 20 ms 15 ms 11 ms 10.102.0.1
3 20 ms 15 ms 13 ms click_dtn_core_10g2/1.click-network.com [131.191.0.4]
4 12 ms 25 ms 13 ms click-cndts7606b_10g2/3.click-network.com [131.191.0.39]
5 13 ms 12 ms 14 ms cr1-tacs-p200.bb.spectrumnet.us [174.127.154.25]
6 16 ms 19 ms 14 ms br1-span-te-0-0-4.bb.spectrumnet.us [174.127.138.134]
7 22 ms 17 ms 19 ms cr1-pdx-t3-1.bb.spectrumnet.us [174.127.138.185]
8 17 ms 17 ms 15 ms te0-0-0-5.rcr21.pdx01.atlas.cogentco.com [38.104.105.73]
9 16 ms 16 ms 21 ms te0-0-1-2.rcr12.pdx02.atlas.cogentco.com [154.24.49.213]
10 28 ms 21 ms 19 ms be2670.ccr22.sea01.atlas.cogentco.com [154.54.42.149]
11 18 ms 18 ms 29 ms be2084.ccr21.sea02.atlas.cogentco.com [154.54.0.254]
12 41 ms 41 ms 43 ms be2085.ccr21.slc01.atlas.cogentco.com [154.54.2.198]
13 50 ms 50 ms 50 ms be3037.ccr21.den01.atlas.cogentco.com [154.54.41.146]
14 89 ms 61 ms 61 ms be3035.ccr21.mci01.atlas.cogentco.com [154.54.5.90]
15 75 ms 81 ms 87 ms be2831.ccr41.ord01.atlas.cogentco.com [154.54.42.166]
16 76 ms 82 ms 73 ms be2765.ccr41.ord03.atlas.cogentco.com [154.54.45.18]
17 84 ms 76 ms 73 ms be2409.rcr11.b002281-5.ord03.atlas.cogentco.com [154.54.29.66]
18 75 ms 75 ms 77 ms cogent-chi.liquidweb.com [38.104.103.166]
19 91 ms 82 ms 103 ms lw-dc3-core2-te8-16.rtr.liquidweb.com [209.59.157.229]
20 82 ms 81 ms 84 ms lw-dc3-dist16-po6.rtr.liquidweb.com [69.167.128.95]
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 *
