On Wed, 30 May 2001, Mike Colgan wrote:
> >Make sure reverse DNS works for the places you are trying to ping or ping -n
> >ipaddress
>
> We have tried IP address and domain names and they resolve OK, it just
> refuses to do the actual ping.
*Reverse* DNS - dig -x <IP address> or dig <IP in reverse>.in-addr.arpa.
> >That will test ICMP.
> >Also make sure you havent firewalled yourself in.
> >ipchains -L -n
>
> I checked ipchains and it appears that I'm open to the world (input, out
> put and forward all accept). We can also telnet out but can't telnet in.
> The thinking here is that certain deamons aren't up. How does one check
> such a thing? What is meant to be running in a default install. What needs
> to be running to get networked?
The fact you can ping means the network is going - the fact you can't
connect to a Web server means something is intercepting the packets. Make
sure you're not behind a firewall that blocks port 80 (forcing you to use a
caching proxy). That might be the problem.
--
-----------------------------------------------------------------------
#include <disclaimer.h>
Matthew Palmer
[EMAIL PROTECTED]
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
