If you haven't taken specific measures to set up particular routes for each
NIC using iproute2 utilities, then your computer will only use one NIC
anyway and you are just wasting a NIC. Many people assume that a server will
use the interface bound to the IP address that a request is addressed to,
but it doesn't actually work this way. If the route table has two routes of
equal cost to the same destination, then it will just pick the first
interface every time, which will usually be through the lower numbered NIC.
However, communications should still be working if there was nothing else
wrong.
To help troubleshoot, we would need more information, such as the output of
'/sbin/route -n', '/sbin/ifconfig', the route table on the router, any
access lists on the router or firewall rules on the server.
Also, are there any other problems in communication between the two subnets,
or can the NT/2000 machines all communicate fine across the router?
--
wcardwell at nc dot rr dot com
"Paul Graves" <(E-Mail Removed)> wrote in message
news:4WgSa.44650$(E-Mail Removed)...
> I have two nic's in my linux web server: 150.150.32.104 and
150.150.32.105.
> They are both on the same subnet: 255.255.254.0.
>
> the .105 is set up in DNS... I can not ping or access the web server from
> another subnet across a sysco router.
>
> Am I stupid for having two nic's on the same subnet or what? All client
> pc's are NT 2000.
>
> Thanks,
>
> Frustrated Newbie.
>
>
|