[Cialug] networking problems

[n.d]

browser: firefox (on all machines)
error message: "The connection was refused when attempting to contact *****"
proxy: no thank you.
routing table:

(linux)Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt 
Iface
192.168.123.0   *               255.255.255.0   U         0 0          0 
eth0
169.254.0.0     *               255.255.0.0     U         0 0          0 
eth0
default         192.168.123.1   0.0.0.0         UG        0 0          0 
eth0

(windows routing table. beware its scary.)
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0    192.168.123.1   192.168.123.4       20
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
    192.168.123.0    255.255.255.0    192.168.123.4   192.168.123.4       20
    192.168.123.4  255.255.255.255        127.0.0.1       127.0.0.1       20
  192.168.123.255  255.255.255.255    192.168.123.4   192.168.123.4       20
        224.0.0.0        240.0.0.0    192.168.123.4   192.168.123.4       20
  255.255.255.255  255.255.255.255    192.168.123.4   192.168.123.4       1
Default Gateway:     192.168.123.1

traceroute to www.cnet.com:
traceroute to c10-ssa-xw-lb.cnet.com (216.239.115.141), 30 hops max, 38 
byte packets
 1  192.168.123.1 (192.168.123.1)  5.427 ms  5.171 ms  0.906 ms
 2  10.17.224.1 (10.17.224.1)  14.929 ms  16.012 ms  25.858 ms
 3  12-215-16-169.client.mchsi.com (12.215.16.169)  13.201 ms  20.414 
ms  20.851 ms
 4  12-215-5-6.client.mchsi.com (12.215.5.6)  29.101 ms  25.932 ms  
28.772 ms
 5  tbr1-p011801.cgcil.ip.att.net (12.123.6.58)  69.979 ms  69.100 ms  
74.897 ms
     MPLS Label=32430 CoS=5 TTL=1 S=0
 6  tbr1-cl1.sffca.ip.att.net (12.122.10.6)  69.086 ms  68.957 ms  68.846 ms
     MPLS Label=32441 CoS=5 TTL=1 S=0
 7  gar4-p300.sffca.ip.att.net (12.123.13.174)  66.468 ms  68.680 ms  
79.969 ms
 8  idf22-gsr12-1-pos-6-0.rwc1.attens.net (12.122.255.222)  84.092 ms  
73.723 ms  68.881 ms
 9  mdf3-bi4k-1-eth-1-1.rwc1.attens.net (216.148.209.62)  69.123 ms  
66.730 ms  70.334 ms
10  63.241.72.146 (63.241.72.146)  67.872 ms  73.085 ms  77.695 ms
11  63.241.72.146 (63.241.72.146)  70.027 ms !X *  71.228 ms !X
[root at network config]# traceroute www.us.army.mil
traceroute to www.us.army.mil (143.69.243.36), 30 hops max, 38 byte packets
 1  192.168.123.1 (192.168.123.1)  1.127 ms  4.883 ms  0.864 ms
 2  10.17.224.1 (10.17.224.1)  15.985 ms  23.009 ms  11.821 ms
 3  12-215-16-169.client.mchsi.com (12.215.16.169)  16.088 ms  14.095 
ms  17.577 ms
 4  12-215-5-2.client.mchsi.com (12.215.5.2)  27.920 ms  24.915 ms  
29.009 ms
 5  tbr1-p012301.cgcil.ip.att.net (12.123.6.9)  32.406 ms  37.678 ms  
25.964 ms
     MPLS Label=32479 CoS=5 TTL=1 S=0
 6  ggr2-p300.cgcil.ip.att.net (12.123.6.33)  28.986 ms  24.970 ms  
29.934 ms
 7  att-gw.chi.qwest.net (192.205.32.98)  30.922 ms  23.589 ms  28.645 ms
 8  cer-core-01.inet.qwest.net (205.171.139.57)  30.621 ms  25.643 ms  
23.988 ms
 9  dca-edge-13.inet.qwest.net (205.171.209.74)  50.892 ms  64.519 ms  
57.270 ms
10  67.133.229.126 (67.133.229.126)  48.980 ms  48.064 ms  47.253 ms
11  198.26.76.33 (198.26.76.33)  50.130 ms  49.536 ms  53.938 ms
12  33.1.1.98 (33.1.1.98)  68.983 ms  71.017 ms  80.984 ms
13  198.26.215.114 (198.26.215.114)  102.197 ms  78.949 ms  111.950 ms
14  * * * (etc etc etc to infinity)

this i believe is where the problems arise. whats odd is i just noticed 
that i can access this site from my server but not my other machines. 
the investigation continues.


Kenneth Ristau wrote:

>n.d wrote:
>  
>
>>root at network~# host www.us.army.mil 192.168.123.101
>>Using domain server:
>>Name: 192.168.123.101
>>Address: 192.168.123.101#53
>>
>>www.us.army.mil has address 143.69.243.36
>>
>>    
>>
>--SNIP--
>
>OK, looks like your DNS is working correctly, so we need to look at
>something else.  What browser are you using to access these sites, and
>what error message (if any) do you get when you try to access them?  Are
>you using a proxy?  If so, can you by-pass it for testing, and what
>happens when you do?
>
>If you suspect routing, try doing a traceroute on the IP of each of your
>example sites.  Perhaps include the results of those traceroutes and
>your routing table in your reply.  I don't think it is routing, though.
> If it was, I would expect to see you unable to access any site at all,
>not just a select few.
>
>later,
>kristau
>  
>