• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

kinda a networking question

DIRTsquirt

Senior member
I am not able to access a website from my home computer.. I thought it went down and then that they went out of business. Iwas talking to a buddy oneday and he said he was just there.. so I borrowed his dialup and sure enough I was able to visit the site.
I called my IP and told em of my problem.
The werent able to access the site either but said that they confirmed that they could access it from another provider.. They say it isnt a problem betweem me and them rather a problem between them and the target destination.... I thought the inet was confiured in an endless loop os it one path is broken another will be used?
neway they arent gonna help me. what can I do to access this site can I do something to reroute the signal myself.
So my comp tries to use a path that works?
Whos responsibility is it to enure I get full access to the net? where do I turn?
 
Can you get to your website using the IP address? Did you ever have your site hosted by your ISP?

I have seen problems where people host their site with their ISP but move it later on... The ISP usually forgets to remove the DNS entry for the
domain name of the site and everyone using the ISPs nameservers goes to the invalid IP for the site.
 
Sounds like it could be one of two problems:

Problem 1: DNS isn't resolving to the correct IP address (or any IP address). You can check this by using the command line to try to ping the domain name of the site. If the command line spits back an IP, but the ping times out, this is not the problem. If the command line says that it cannot find this particular domain, that it possibly is the problem.

Problem 2: DNS may or may not resolve to the site. However, there may be a routing issue between your ISP and the ISP hosting the site. (i.e. you have connectivity to most other sites but not this one, and maybe a few others). This happens occasionally, and usually clears itself up. I have heard of horror stories where Above.net has blacklisted entire subnets, but unfortunately I don't have a quick link handy to back up that statement. Try doing a traceroute to see who drops the packet.

-j
 
Back
Top