Main Forum > Tweaking.com Support & Help
Website issue - Solved!
jrjr:
--- Quote from: Shane on June 25, 2015, 03:22:28 am ---That is really odd. My program is about 95% registry related repairs. Registering files and such.
I never had any trouble accessing any sites after the repairs, the program doesn't target any sites and such.
Are you able to try a different internet connection as a test? What antivirus do you have installed and firewall software? I have a feeling something else is at play, as my repair program doesnt do anything to accessing sites such as dns other than simply doing a flush dns command.
Using a proxy makes the connection go though another server instead of your ISP, this is how some people can get around blocks their ISp setup, it also could be something as simple as the modem/router needing rebooted so that it can clear itself out. Pull the power cord from both your modem and router (If you have both) wait a full 60 sec and then plug them back in and see how it does. :wink:
The reason for this, is there have been a lot of problems I have seen where a node on the net was having trouble, so the router your connection takes goes through multiple nodes, if one is down or having trouble the connection doesnt complete. Using a proxy and such means you are taking a different route. So sometimes the problem isnt you or your ISP, but instead one of the nodes. They call it the information super highway, and guess what it has road construction as well lol
Shane
--- End quote ---
Thank you both for your time.
I agree it's very odd. I have rebooted the modem and router before, but just did it again for grins after waiting several minutes. No change. I don't have another internet connection available without lugging the desktop to someone's home. I took notes as I went along on things that I tried. Whats really odd is I can ping by IP or domain name successfully and all other computers on the same network are fine with these websites. Even the same desktop works using a VM with the same network interface. Not sure if all my efforts are listed above or not but here they are as complete so far -
--- Quote ---I cannot access three (maybe more I haven’t run into yet) websites from Firefox, Chrome, Opera, Safari or IE running on my desktop. I have checked the host file and it's clean. Checked Internet restricted sites and that has no entries. I have turned off all antivirus programs and turned off Windows firewall. Still no joy. Also have done - ipconfig /flushdns in cmd as admin and reset winsock.
I ran malwarebytes, Panda, Superantispyware, MS security essentials and cleaned whatever they found. Just standard tracking cookie finds. Also ran Malwarebytes rootkit program with no results.
Created a new Windows user profile. Same results in that profile.
Ran msconfig – disable all in startup – reboot with same results
Have powered off the PC, unplugged and held power button to discharge with no results.
Rebooted router and modem
I can successfully ping the website in question via IP and domain. If I enter their IP in the browser address bar it will time out the same as trying their domain name.
tracert finds the unavailable domains without issue
traceroute works fine on the sites too
Tried Google DNS and also hard coding Road Runner DNS servers. Same issues.
I can access these websites from my laptop on the same network, AND if I run virtual box on my desktop in question using a Win 10 or Linux VM I can access the websites without issue.
If I configure a proxy server I can access the sites.
--- End quote ---
Shane:
Lets see what happens if you do a trace route to it and we can see the nodes it is taking. here is the results of my trace route to the site.
--- Quote ---Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Shane>tracert http://www.theprofilebrotherhood.com
Unable to resolve target system name http://www.theprofilebrotherhood.com.
C:\Users\Shane>tracert www.theprofilebrotherhood.com
Tracing route to theprofilebrotherhood.com [174.36.75.246]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 16 ms 8 ms 9 ms dtr04mdfdor-tge-0-5-0-2.mdfd.or.charter.com [96.
34.105.245]
4 19 ms 15 ms 23 ms bbr01mdfdor-bue-2.mdfd.or.charter.com [96.34.105
.82]
5 29 ms 31 ms 23 ms bbr02sttlwa-bue-4.sttl.wa.charter.com [96.34.0.5
6]
6 30 ms 26 ms 32 ms prr01sttlwa-bue-2.sttl.wa.charter.com [96.34.3.3
9]
7 25 ms 18 ms 18 ms te1-5.bbr01.wb01.sea01.networklayer.com [206.81.
80.140]
8 62 ms 71 ms 68 ms ae0.bbr01.cs01.den01.networklayer.com [173.192.1
8.145]
9 63 ms 63 ms 66 ms ae12.bbr02.eq01.dal03.networklayer.com [173.192.
18.138]
10 64 ms 63 ms 63 ms ae1.dar01.sr01.dal01.networklayer.com [173.192.1
8.255]
11 70 ms 70 ms 63 ms po1.fcr02.sr04.dal01.networklayer.com [66.228.11
8.178]
12 68 ms 72 ms 67 ms www.theprofilebrotherhood.com [174.36.75.246]
Trace complete.
C:\Users\Shane>
--- End quote ---
Shane
jrjr:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>traceroute www.theprofilebrotherhood.com
'traceroute' is not recognized as an internal or external command,
operable program or batch file.
C:\Windows\system32>tracert www.theprofilebrotherhood.com
Tracing route to theprofilebrotherhood.com [174.36.75.246]
over a maximum of 30 hops:
1 4 ms <1 ms <1 ms 192.168.1.1
2 37 ms 44 ms 29 ms cpe-66-67-0-1.rochester.res.rr.com [66.67.0.1]
3 33 ms 28 ms 21 ms tge0-0-1.sodsny0302h.northeast.rr.com [24.93.8.1
10]
4 13 ms 12 ms 12 ms agg36.hnrtnyaf02r.northeast.rr.com [24.58.45.88]
5 21 ms 23 ms 19 ms be28.albynyyf01r.northeast.rr.com [24.58.32.70]
6 30 ms 32 ms 31 ms bu-ether16.nycmny837aw-bcr00.tbone.rr.com [66.10
9.6.74]
7 53 ms 29 ms 75 ms 0.ae1.pr1.nyc20.tbone.rr.com [107.14.17.218]
8 29 ms 28 ms 28 ms 66.109.11.126
9 39 ms 38 ms 38 ms ae1.bbr01.eq01.chi01.networklayer.com [173.192.1
8.132]
10 60 ms 59 ms 60 ms ae20.bbr01.eq01.dal03.networklayer.com [173.192.
18.136]
11 59 ms 57 ms 60 ms ae0.dar01.sr01.dal01.networklayer.com [173.192.1
8.211]
12 59 ms 57 ms 60 ms po1.fcr02.sr04.dal01.networklayer.com [66.228.11
8.178]
13 58 ms 60 ms 60 ms www.theprofilebrotherhood.com [174.36.75.246]
Trace complete.
C:\Windows\system32>
Shane:
Ok so ping and tracert can hit the site just fine, which also shows it is getting the right IP from the dns servers. Yet your browsers are not able to hit it, can you a screen shot of the actual message of when it fails?
Ping and tracert hit a different port than the normal port 80 when accessing a site or port 443 for https, so thats something to consider as well, have you tried disabling all AV and firewall software?
Reason why I ask is the fact that ping and tracert can hit it means that it is up, isnt being blocked and the connection to it is fine, dns is working, so it seems like the browsers are being blocked.
All I use is firefox and I do know it keeps its own dns cache, wonder if we just need to make sure the dns cache is clear for the browsers.
Shane
jrjr:
Yea sure. It takes several minutes to time out. 2 of the sites are server connection reset or something similar. 3rd is a financial site and says something like - secure connection failed. Will get them for you.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version