2 interface cards

[TMcB]

I have 2 network cards installed on my server -1000Base-SX and an ethernet card.
The 1000Base-SX is the only one currently connected.
Within SAM I have disabled the ethernet card, although it still knows the ip address, etc configured on it.

Meanwhile, on the console, I am receiving the error message- telnetd :connection reset by peer.
The only noticable thing from NETFMT is a problem with the interface card - check cable.

Is it possible that even though this card is disabled, that it is still trying to do something?
Can I remove this card altogether from system?

Thanks for any help

[Rainer von Bongartz · Accepted solution]

look at /etc/rc.config.d/netconf and delete the entries for your undesired lan card.

the do an /sbin/init.d/net stop and /sbin/init.d/net start and all configuration will ge gone

regards
Rainer

[Ravi_8]

Hi,
find the lan number(x) for the ethernet using 'lanscan' command and make it down "netconfig lanx down". and also delete all the entries for ethernet in /etc/rc.config.d/netconf and do "/sbin/init.d/net stop/start"

[TMcB]

Hi folks

lan0 is the unused card and lan1 is the Gigabit card.

Within netconf, interface_name[0] refers to lan0.
When I delete all the configurations marked [0]
should I leave the other one as lan1 and [1]
or do I change all entries for it to [0].

Thanks for your advice

[MANOJ SRIVASTAVA]

Hi Terry

You should not change the entries to lan[0].
Also do a lanscan to confirm which card is lan[0] and which one is lan [1]

Manoj Srivastava

[John Palmer]

Hi Terry,

You should remove all your [1] entries and amend your [0] entries to reference lan1 and its settings. You'll end up with something like:-

INTERFACE_NAME[0]=lan1
IP_ADDRESS[0]=
SUBNET_MASK[0]=
BROADCAST_ADDRESS[0]=
LANCONFIG_ARGS[0]=
DHCP_ENABLE[0]=

Regards,
John

[rick jones]

i suppose that some sort of wierd interaction could result in the telnet connections being reset by the remotes, but i find it a bit unlikely.

if the remotes are PC's, many PC apps erroneously use abortive TCP closes - setting SO_LINGER settings such that a RST is used instead of a FIN . that could result in the telnetd reporting connection aborted by peer.