Hey, my computer seems to have some problem connecting to some websites, such as managed.com and ***********.net how come? Can anyone tell me why? i got some support from Comcast, they told me to delete cookies, check for XP firewall, my own firewall, to delete temp internet files, etc. Non of this stuff has worked, can anyone tell me why? I am really frustrated, i haven't been able to see these websites in 3 days and i am really mad! Can anyone help me?:kaioken:

u n i t h o s t i n g . n e t


How come it won't show up? Anyways, that one will fill up for the *************.net

If it has **** that means its a website that has been BANNED from WHT, and you are not allowed to post it. Read the rules for more info.

ok, sorry.

I have had the same problem. I suspect it may be the browser you are using, try using Mozilla, IE or opera.

Originally posted by sergio7889
Hey, my computer seems to have some problem connecting to some websites

I hate to sound patronising, but how do you know that those sites either are down or just don't exist at all? Try running a traceroute to the sites that you can't connect to, that will explain where the link is breaking. It may also be a problem with the DNS server you're using.

To run a traceroute:

1. Click on the Start icon in the bottom left hand corner of your computer
2. Click Run
3. Type cmd
4. Type tracert websitethatyoucan'tvisithere.com (replacing that with the actual website)
5. Watch the results, if it doesn't even resolve then you know the problem is that either the site's DNS servers are dead or there is a problem with yours. If it successfully connects to the website, then maybe you do have a firewall which is blocking your access. The firewall may be a transparent proxy server running on your ISP's servers though, if that was the case then there's not really much you can do about it.

Paste the traceroute results here so we can examine them. :)

Originally posted by stephenM
I hate to sound patronising, but how do you know that those sites either are down or just don't exist at all?

I know they are up, because i asked a couple of other friends to check them out, and they said that they were working.

Ok, here are the results i got when i did tracert managed.com:
------------------------------------------------------------------------------------

C:\Documents and Settings\Sergio Diaz>tracert managed.com

Tracing route to managed.com [66.79.160.10]
over a maximum of 30 hops:

1 12 ms * 11 ms c-24-2-208-1.client.comcast.net [24.2.208.1]
2 12 ms * 13 ms 12.244.127.49
3 10 ms * 9 ms 12.244.70.154
4 15 ms * 14 ms 12.244.73.98
5 14 ms * 11 ms gbr1-p20.n54ny.ip.att.net [12.123.1.130]
6 14 ms * 11 ms tbr2-p013801.n54ny.ip.att.net [12.122.11.17]
7 13 ms * 14 ms ggr1-p320.n54ny.ip.att.net [12.122.12.54]
8 92 ms * 92 ms pos8-3.pr1.lga1.us.above.net [64.125.12.105]
9 93 ms * 91 ms so-4-3-0.cr2.lga1.us.above.net [64.125.30.189]
10 90 ms * 89 ms so-1-0-0.cr2.iad1.us.above.net [208.184.233.65]

11 93 ms * 91 ms so-1-0-0.cr2.dca2.us.above.net [208.184.233.129]

12 93 ms * 92 ms so-2-3-0.cr2.dfw2.us.above.net [64.125.29.13]
13 92 ms * 92 ms so-0-0-0.cr1.dfw2.us.above.net [216.200.127.209]

14 92 ms * 90 ms so-4-1-0.mpr4.sjc2.us.above.net [64.125.29.57]
15 93 ms * 94 ms so-0-0-0.er10a.sjc2.us.above.net [64.125.30.94]

16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
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 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

It looks like possibly an above.net problem? I ran a trace and it got there fine, but didn't use above.net:

Last login: Mon Feb 16 23:16:50 on ttyp1
Welcome to Darwin!
Panther:~ main$ traceroute managed.com
traceroute to managed.com (66.79.160.10), 30 hops max, 40 byte packets
1 192.168.11.1 (192.168.11.1) 6.512 ms 1.638 ms 1.532 ms
2 172.25.119.254 (172.25.119.254) 9.167 ms 12.709 ms 12.371 ms
3 glfd-t2cam1-a-ge-wan41-103.inet.ntl.com (80.4.30.13) 9.416 ms 10.996 ms 20.279 ms
4 gfd-t2core-a-ge-wan61.inet.ntl.com (62.254.207.37) 20.276 ms 14.885 ms 16.127 ms
5 gfd-bb-a-so-300-0.inet.ntl.com (62.253.185.25) 11.094 ms 11.523 ms 13.412 ms
6 tele-ic-1-so-100-0.inet.ntl.com (62.253.185.78) 17.158 ms 16.858 ms 13.237 ms
7 cr02.ldn01.pccwbtn.net (195.66.224.167) 12.092 ms 12.672 ms 11.002 ms
8 pos3-0.cr02.sjo01.pccwbtn.net (63.218.6.66) 205.216 ms 201.963 ms 202.145 ms
9 63.218.7.6 (63.218.7.6) 186.954 ms 177.407 ms 184.876 ms
10 f0-0.core1.eqx.layer42.net (69.36.239.46) 182.962 ms 183.803 ms 178.681 ms
11 f2-0-1.core1.sjc.layer42.net (69.36.239.61) 185.45 ms 184.538 ms 182.397 ms
12 f0-0.core2.sjc.layer42.net (69.36.239.57) 188.405 ms 190.88 ms 185.574 ms
13 bungi-gw1.layer42.net (69.36.239.131) 176.936 ms 208.561 ms 179.366 ms
14 66-154-102-41.assertivenetworks.net (66.154.102.41) 175.859 ms 175.734 ms 178.205 ms
15 66-154-102-52.assertivenetworks.net (66.154.102.52) 177.282 ms 175.33 ms 175.003 ms
16 www.managed.com (66.79.160.10) 175.741 ms 177.412 ms 180.924 ms
Panther:~ main$

what does above.net have to do with me though?

you're being routed through it. It looks like either an above.net router is down or the next hop after above.net is.