routing problem

[atanoli]

I installed RedHat 7.1 with two LAN cards 1 for Internal LAN and 2nd for Internet Public access. My server name is "azamtanoli"

Configured
Apache Server running fine.
NIS server running fine.
DNS server running fine.

I can browse internet from my this server( when i tell to browser that this server is derectly connected to the internet).


But now problems are:

1. when i am typing "ping

http://www.abc.com"

my server can resolve this name but there is no reply from ping command, 100% packet loss, why?

2. When define my server's IP address into netscape browser its not going to internet. Checking my local server and asking that there so no site or URL on this server?

Its seems to me that there is routing problem. (Althoug i add route default gw xx.xx.xx.xx)?

Thanks

 

[ifincham]

Hi,

Well, the fact that you can resolve the IP address simply means that you can talk to a dns server to get that information. If your resolution (/etc/resolv.conf) points to your own dns server then evidently thats talking correctly to other dns servers to resolve external addresses. Accessing the resolved IP address is a function of routing - however, to a large extent, that is down to your ISP. As long as the default gateway is correct (eth1) then you have configured the routing correctly. However, there may be network address translation and firewalling at your router or dsl/cable modem so that adds to the complexity.

On (1), if it's just one address then the server may be down or there may be a routing problem somewhere. Otherwise, it may be that ping (icmp protocol) is being filtered / firewalled somewhere. Some sysadmins block pings for security reasons.

On (2), I'm not sure what you mean here. Do you mean

http://127.0.0.1

or a public IP address ?

Also, how do you connect from the second ethernet card to the internet ?

Regards

 

[marsd]

For your nameserver to resolve names it has to query an
external nameserver so you can be pretty sure that you
are able to "get out"..
It sounds like you have multiple misconfigurations.
Look at your log files, disable FW services and rules
and verify that you have local name resolution in your
hosts file for a start.

 

[atanoli]

1st of all thank you very much.

ifincham i am talking about public IP

 

[marsd]

Check the server name directive in your httpd.conf:
You must have dns configured correctly for external hosts
to connect to the address specified on this line.

That is you must have an A or cname record pointing to
the correctly configured web server name in the zones for
your domain. Otherwise you will need to put the ip address
of the pub interface as your server name, and only be resolved by IP for now.

If a firewall is involved you will have to deal with this
as well.