Don't copy paste from here. Just type it in....
1. start command prompt.
2. type "telnet charterone.com 80" [enter]
3. if the command prompt screen goes blank, you were able to connect.
4. type in "GET / HTTP/1.0" & hit the [enter] key twice.
5. Anything come up?
Also try this at the command prompt: "nslookup charterone.com" [enter] if the last line doesn't say:
Name: charterone.com
Addresses: 128.11.152.178, 128.167.128.254
Then you have a DNS problem. 99% of time you (the end-user) need not worry about DNS. The other computer could just be loading the page from the cache.
The purpose of telnet is to see the real TCP connectivity without a browser trying to parse & render it's interpretation.
You could also try "pathping charterone.com" which is just the same as tracert except it pings each router in the path for about 5 minutes nonstop to determine package loss at each router. You should generally get less than 2% package loss (even that's kind of high, 0 is really what you're looking for). You would only worry about the first few and last few hops as the first are ISP-related and the latter are web-site related. The ones in the middle are the big name internet backbone people (like Level3, akadns, and atdn) which would have the least amount of problems.
Does you have a proxy server configured?