Re: eth1 Fights eth0

Top Page
Attachments:
Message as email
+ (text/plain)
Delete this message
Reply to this message
Author: Jim
Date:  
To: PLUG
Subject: Re: eth1 Fights eth0
The biggest problem I have seen that could cause what you are describing
is when you have 2 default routes

when you type "route" on the console how many lines do you have that say
default under Destination if you have more than 1 it will cause problems

To remove the unwanted route: and fill in a different eth if it is not
eth0
"route delete default eth0"


A good way to test how your box is going to get to a destination is to
use

"ip route get ip.of.destination"
and see what interface is going to be used.


Jim



On Tue, 2004-04-06 at 13:13, George Gambill wrote:
> I installed (and configured) a second nic card (eth1) in my RH 8.0 Samba 3.0 Server (linuxws055).
>
> eht0 is configured (static) as a member of the corporate domain (10.1.xxx.xxx).
>
> eth1 is configured (static) as 192.167.1.1.
>
> When eth1 is physically installed, my win2K box can't see linuxws055.
>
> When eth1 is physically removed (leaving the configurations alone) things are good.
>
> ifcfg-eth1 looks good
>
> An interesting side bar, when booting, the systems shows bringing up both eth0 and eth1 as OK when eth1 is not physically there.
>
> Any ideas?
>
> George
> ---------------------------------------------------
> PLUG-discuss mailing list -
> To subscribe, unsubscribe, or to change you mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss


---------------------------------------------------
PLUG-discuss mailing list -
To subscribe, unsubscribe, or to change you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss