Well...the problem is that, despite the inability to do a ping or traceroute to these two sites, they can be reached through Netscape if Netscape is run outside of the firewall but cannot be reached from inside the firewall, and the firewall is just masquerading. Other sites work perfectly from either inside or outside the firewall, so the problem seems to be related to these sites, unless I'm totally nuts (a distinct probability). FWIW we have to use Passive FTP from inside the firewall, so I was wondering (in my newbie-like manner) if some http sites behave in a similar fashion and are failing because they cannot communicate directly with the requesting box. Ed Jaeger, CFO, Bohlender Graebener Corporation [EMAIL PROTECTED] http://www.bgcorp.com ---------- >Try doing a traceroute with the name resolution disabled -- just a hunch... >(traceroute -n) > >Also, is it possible, although unlikely, that your address block has been blocked >at some point in the route? I have had a few "competitors" block anything coming >from my site. Sounds kind of strange for both of those sites, BUT somewhere >down the line you may be blocked... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For daily digest info, email [EMAIL PROTECTED]
