n00b0101
asked on
Site inaccessible to me, accessible to others?
Not sure if this is the right spot to be asking this, but would love someone who could point me in the right direction or, at least, give me some ideas as to why this would happen...
I have a site that I can't get to. Via Safari or FF, the server "takes too long to respond" and won't render. Via Terminal (I'm on a Mac), attempting to SSH in to either the IP or the domain results in a Connection timeout. If I ping the ip (or domain), from Terminal, it results in a 100% packet loss. However, if I go to networktools.com and ping the ip, it seems to work just fine.
The site is hosted by a company that says they pull it up, but I've even driven to another city to attempt to access it and it still didn't work for me. Not sure what to check, or whether this is something happening on my end or theirs, and not sure where to start looking?
I'm hoping some people here can give me some ideas?
I have a site that I can't get to. Via Safari or FF, the server "takes too long to respond" and won't render. Via Terminal (I'm on a Mac), attempting to SSH in to either the IP or the domain results in a Connection timeout. If I ping the ip (or domain), from Terminal, it results in a 100% packet loss. However, if I go to networktools.com and ping the ip, it seems to work just fine.
The site is hosted by a company that says they pull it up, but I've even driven to another city to attempt to access it and it still didn't work for me. Not sure what to check, or whether this is something happening on my end or theirs, and not sure where to start looking?
I'm hoping some people here can give me some ideas?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Ok, well that zeros in on your particular client having the problem if a colleague can access the site from your network. Are you using Windows 7? Try temporarily disabling the adv. firewall and recheck.
ASKER
No, I'm on a Mac... Checking my Linksys Router configuration to see if there's something there, but, not sure what I'm supposed to be looking for... Just madly stabbing in the dark...
In that case, temporarily turn off the firewall. System Preferences / Security and Privacy / Click the Stop button.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I'm not on a PC, I'm on a Mac. And, my firewall is currently off. It's a web site, hosted elsewhere. But, I have SSH access as well. The client, who is on a PC, *can* access the site via browser.
I'm attaching some screenshots of my wireless router setup, just in case they're relevant somehow... I'm not sure what else to check?
I'm attaching some screenshots of my wireless router setup, just in case they're relevant somehow... I'm not sure what else to check?
When you try to access this in a browser are you going to https or http? If https, and ssh also fails, then it might be possible that either the destination site is using old (SSL1) security, or, it is using newer (TLS1) and your mac cannot handle it. If you mac is reasonably new, and the browsers are up to date, then the latter is not likely. It might be more the case that it is SSL1, which is now normally rejected by current browser and ssh. Again, this is a shot in the dark, but is the destination site a commercial site that you would not expect to be using old security software?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It's strange... Ping via terminal results in a 100% packet loss. Traceroute via terminal results in:
Ping via network-tools.com results in:
Also, I'm accessing via http, but I did try https as well and there's no difference at all...
1 192.168.1.1 (192.168.1.1) 1.106 ms 0.744 ms 0.681 ms
2 c-69-181-224-1.hsd1.ca.comcast.net (69.181.224.1) 41.306 ms 20.015 ms 36.323 ms
3 te-7-1-ur02.dalycity.ca.sfba.comcast.net (68.87.197.53) 11.678 ms 18.272 ms 11.211 ms
4 te-1-3-0-0-ar01.oakland.ca.sfba.comcast.net (69.139.198.114) 16.549 ms 18.467 ms 13.253 ms
5 pos-2-5-0-0-cr01.sacramento.ca.ibone.comcast.net (68.86.90.9) 15.907 ms 24.247 ms 16.298 ms
6 pos-0-4-0-0-cr01.sanjose.ca.ibone.comcast.net (68.86.85.50) 19.421 ms 18.784 ms 18.820 ms
7 pos-0-0-0-0-pe01.11greatoaks.ca.ibone.comcast.net (68.86.86.54) 28.415 ms 25.206 ms 23.623 ms
8 tenge13-3.br02.sjo01.pccwbtn.net (63.218.179.25) 28.399 ms 21.467 ms 144.702 ms
9 gnax.ge2-14.br01.atl01.pccwbtn.net (63.216.31.138) 160.940 ms 95.844 ms 326.322 ms
10 atl-core-g-g1-6.gnax.net (63.247.69.178) 325.526 ms 345.799 ms 337.539 ms
11 core-gi1-1.nocdirect.com (209.51.131.90) 611.540 ms 351.620 ms 632.074 ms
12 deeja.nocdirect.com (209.217.237.150) 671.304 ms 84.494 ms 82.946 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
Ping via network-tools.com results in:
Ping 69.73.168.145
Round trip time to 69.73.168.145: 21 ms
Round trip time to 69.73.168.145: 21 ms
Round trip time to 69.73.168.145: 21 ms
Round trip time to 69.73.168.145: 21 ms
Round trip time to 69.73.168.145: 21 ms
Round trip time to 69.73.168.145: 21 ms
Round trip time to 69.73.168.145: 21 ms
Round trip time to 69.73.168.145: 21 ms
Round trip time to 69.73.168.145: 21 ms
Round trip time to 69.73.168.145: 21 ms
Average time over 10 pings: 21 ms
Also, I'm accessing via http, but I did try https as well and there's no difference at all...
ASKER
Well, went to http://www.downforeveryoneorjustme.com/
and typed in the domain... According to the site, it's definitely just me... I'm out of things to think to check... I even tried using OpenDNS to reconfigure my linksys router, but it still won't come up for me...
and typed in the domain... According to the site, it's definitely just me... I'm out of things to think to check... I even tried using OpenDNS to reconfigure my linksys router, but it still won't come up for me...
On the traceroute you posted, did you do it by ip or URL? If by ip, does nslookup resolve the domain name on your MAC?
The traceroute you have posted is only 1 hop away from the destination ip. Also, I observed that the page will only display if you use http and not https. This appears to be a hosting site with cpanel.
Have you contacted this site and asked if they could be blocking your ISP? I am assuming you don't have a fixed ip address at your site.
The traceroute you have posted is only 1 hop away from the destination ip. Also, I observed that the page will only display if you use http and not https. This appears to be a hosting site with cpanel.
Have you contacted this site and asked if they could be blocking your ISP? I am assuming you don't have a fixed ip address at your site.
ASKER
Ok... So, after a long and exhausting back-and-forth, turns out Comcast blocks ips if they detect "malicious data flows", but don't indicate anywhere that they do this or that it's been done... So... Thanks for trying to help, but, in the end... Comcast sucks.
ASKER
points for trying to help and giving me lots of stuff for future reference...
ASKER