2 eth cards and DA installation

[netforce]

Hi,

We do have a somewhat ... "special" problem with our DA installed server. That machine runs under Fedora Core 3, and has two ethernet cards, the first (eth0) is NATed and through NAT, has 6 IPs available for our customers, for serving their ... web needs.

The second (eth1) has only one IP, and it's being used since DA can't accept NATed IPs for its licencing and updating, only for the updates and various DA-related issues.

Both cards have different gateways thus the eth0 has a gateway of 10.0.x.x and the eth1 a gateway of 84.33.x.x with all the network realted details being set up correctly.

Our porblem. Services in the NATed IPs are inaccessible from the net, even though the router is being setup correctly. We have used a second machine on the same 10.0.x.x range (and netmask of course), and all services where accessible (e.g FTP, or DNS) but not from the NATed IPs outside.

Any help would be appreciated.

Thanks and happy new year

[fusionictnl]

Originally posted by netforce
Hi,

We do have a somewhat ... "special" problem with our DA installed server. That machine runs under Fedora Core 3, and has two ethernet cards, the first (eth0) is NATed and through NAT, has 6 IPs available for our customers, for serving their ... web needs.

The second (eth1) has only one IP, and it's being used since DA can't accept NATed IPs for its licencing and updating, only for the updates and various DA-related issues.

Both cards have different gateways thus the eth0 has a gateway of 10.0.x.x and the eth1 a gateway of 84.33.x.x with all the network realted details being set up correctly.

Our porblem. Services in the NATed IPs are inaccessible from the net, even though the router is being setup correctly. We have used a second machine on the same 10.0.x.x range (and netmask of course), and all services where accessible (e.g FTP, or DNS) but not from the NATed IPs outside.

Any help would be appreciated.

Thanks and happy new year

Well first of all try doing a traceroute from outside to one of the IP's and check where it hits off. If it is on you're router than double check it's settings that it is pushing it through.

Somehow I would recommend that you check you're routing table on you're server as using 2 eth's and using one for NAT is somewhat hard to setup.

Mostly the problems reside in the routing tables or the router's routing tables. Traceroute will help you out with this. (If you're router accepts it ;) )