[TriLUG] apache cable modem woes

r.wheaton ryan.wheaton at attbi.com
Tue Oct 22 15:05:02 EDT 2002


i tried all kinds of different ports, like 3007, 14568, and 82, all with 
the same result (forgot to include that in my email).

and i've noticed this morning that I can't connect to the box at all. 
 all connections time out whether they be telnet, ping, http, ssh, ftp, 
whatever.  a traceroute produces the following:

traceroute to 12.253.103.252 (12.253.103.252), 30 hops max, 38 byte packets
 1  192.168.0.1 (192.168.0.1)  0.503 ms  0.401 ms  0.673 ms
 2  adsl-80-155-1.rdu.bellsouth.net (65.80.155.1)  24.701 ms  14.707 ms  
14.730ms
 3  adsl-215-14-97.rdu.bellsouth.net (209.215.14.97)  15.955 ms  15.308 
ms  17.111 ms
 4  205.152.244.184 (205.152.244.184)  15.802 ms  14.505 ms  15.470 ms
5  500.POS4-2.GW4.RDU1.ALTER.NET (65.208.83.229)  15.704 ms  16.385 ms  
16.951ms
6  176.at-5-0-0.CL1.RDU1.ALTER.NET (152.63.36.2)  16.931 ms  17.334 ms  
16.217ms
7  0.so-5-1-0.XL1.DCA8.ALTER.NET (152.63.42.206)  25.055 ms  24.231 ms  
24.588ms
8  POS6-0.BR3.DCA6.ALTER.NET (152.63.38.117)  24.324 ms  25.238 ms  
23.609 ms
9  uu-gw.wswdc.ip.att.net (192.205.32.161)  26.796 ms  26.675 ms  24.819 ms
10  gbr4-p50.wswdc.ip.att.net (12.123.9.54)  26.308 ms  26.334 ms  25.815 ms
11  gbr4-p10.attga.ip.att.net (12.122.2.161)  40.108 ms  40.655 ms  
41.341 ms
12  gbr3-p10.dlstx.ip.att.net (12.122.3.37)  59.082 ms  57.409 ms  58.585 ms
13  gbr4-p60.dlstx.ip.att.net (12.122.1.138)  57.178 ms  56.700 ms  
58.595 ms
14  gbr4-p50.dvmco.ip.att.net (12.122.2.102)  98.316 ms  97.571 ms  
97.757 ms
15  gbr2-p100.dvmco.ip.att.net (12.122.5.30)  105.960 ms  103.461 ms  
104.424 ms
16  gar1-p370.dvmco.ip.att.net (12.123.36.77)  96.865 ms  98.547 ms  
98.512 ms
17  12.244.73.129 (12.244.73.129)  103.505 ms  104.172 ms  103.683 ms
18  12.244.71.66 (12.244.71.66)  98.073 ms  99.719 ms  98.754 ms
19  12.244.71.70 (12.244.71.70)  104.485 ms  104.899 ms  104.199 ms
20  12.244.71.74 (12.244.71.74)  105.707 ms  105.146 ms  106.410 ms
21  12.244.92.163 (12.244.92.163)  99.776 ms  100.248 ms  98.503 ms
22  * *
23  * *

and it's all timeouts from there...  maybe i should just call AT&T and 
tell them to leave me alone :-)

thanks for y'lls help.

-rtw

Jeremy P wrote:

>On Tue, 22 Oct 2002, r.wheaton wrote:
>
>>Hello,
>>    I recently just moved out to Colorado from north carolina, and have 
>>been taking a lot of pictures with my dig. camera.  I have been posting 
>>them on my delegated 10MB through my AT&T cable modem account.  Well, 
>>that space has run dry.  And, what i'd like to do is just host them 
>>straight off my cable modem.  I've noticed that my IP doesn't change 
>>that much, and with the help of dyndns.org it seems like the best way 
>>for my friends and family back home to see my pics.  Well, I got it all 
>>set up, and I can see it fine, but no one outside of AT&T can.  Is AT&T 
>>blocking this traffic somehow??  I read on their site that they don't 
>>want you to host any type of server, but this seems kind of ridiculous. 
>>
>
>Hi,
>
>When you say that people from outside "cannot get" to your web server, 
>what exactlty does that mean?  You'll need to troubleshoot what the exact 
>problem is.  For example, is DNS working (name resolves to your correct IP 
>address)?  Can the IP address be pinged (this assumes ICMP isn't being 
>blocked somwhere)?  What happens when you attempt a raw HTTP connection 
>("telnet 127.0.0.1 80" where 127.0.0.1 is the IP address) ?  
>
>--Jeremy
>
>_______________________________________________
>TriLUG mailing list
>    http://www.trilug.org/mailman/listinfo/trilug
>TriLUG Organizational FAQ:
>    http://www.trilug.org/~lovelace/faq/TriLUG-faq.html
>





More information about the TriLUG mailing list