[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Cannot access Web Page from behind firewall



The Web Page I am trying access is www.columbiahouse.com. I try to
access it from either Netscape or Lynx but both get hung up on waiting
for the host to reply. This is on my machine inside my firewall.

My set up is a two machine network. One is my gateway with a
masquarading firewall with the following rules:

ipfwadm -F -p deny
ipfwadm -F -a m -S 192.168.0.2/255.255.255.0 -D 0.0.0.0/0


I can get to the web site from the gateway using Lynx (can't test
Netscapr. No X.), but it cannot complete a traceroute request to the
site. Seems strange to me.

What I get when I type traceroute www.columbiahouse.com on the firewall
machine:

traceroute to www.columbiahouse.com (206.25.182.132), 30 hops max, 40
byte packets
 1  server11.local.general.dialup.unt.edu (129.120.50.11)  146.731 ms 
135.095 ms  139.239 ms
 2  129.120.50.250 (129.120.50.250)  139.01 ms  136.072 ms  139.295 ms
 3  utd-t1-s5-6.texan.state.tx.us (141.198.234.129)  168.984 ms  156.251
ms  149.173 ms
 4  shb3-h1-0.capnet.state.tx.us (141.198.14.1)  178.957 ms  165.989 ms 
159.252 ms
 5  inet-gw.capnet.state.tx.us (141.198.1.1)  158.974 ms  166.212 ms 
169.248 ms
 6  12.127.180.161 (12.127.180.161)  242.778 ms  205.951 ms  189.294 ms
 7  br1-a350s3.distx.ip.att.net (12.127.2.22)  169.041 ms  185.775 ms 
159.35 ms
 8  br2-h11.n54ny.ip.att.net (12.127.15.229)  248.99 ms  236.03 ms 
209.274 ms
 9  gr1-a3100s1.n54ny.ip.att.net (192.205.31.245)  239.039 ms  195.632
ms  289.295 ms
10  nr1-h11.napny.ip.att.net (192.205.31.218)  228.992 ms  195.716 ms 
209.269 ms
11  2-sprint-nap.internetmci.net (192.157.69.48)  249.062 ms  235.758
ms  259.242 ms
12  core5-hssi0-0-0.WestOrange.cw.net (204.70.10.229)  229.058 ms 
255.061 ms  229.334 ms
13  bordercore2.WestOrange.cw.net (166.48.6.1)  238.954 ms  215.798 ms 
229.326 ms
14  columbia-house.WestOrange.cw.net (166.48.238.6)  258.933 ms  226.294
ms  219.256 ms
15  * * *


Now I have just tried upping my kernel to 2.0.36 to find out it still
uses PPP v2.2.0. But the new kernel does not fix the problem. I have
also tried opening the firewall (default policy of accept.) Again, to no
avail.

Any other suggestions? Thanx in advance.

-- 
Paul Miller
pmiller@jove.acs.unt.edu


Reply to: