RE: Ethernet weirdness

2000-12-20 Thread Mobeen Azhar
Of Chad W. Skinner Sent: Monday, December 18, 2000 2056 To: [EMAIL PROTECTED] Subject: RE: Ethernet weirdness Does anyone know if this situation would occur if the card was set to auto-negotiate. It may not be able to start do to settings. I am reaching here as I am not very familiar

Re: Ethernet weirdness

2000-12-18 Thread Micah Yoder
Funky NIC? I would swap the cards to try and isolate the problem. If the Aaargh. Now that you mention that, I bet you're right. I'll try that at some point... being a hardware clutz I'm not up to it right now... I just thought of a couple other things to try... 1. putting a hub between

Re: Ethernet weirdness

2000-12-18 Thread Statux
usually the SIO errors happen when you try to do address/other config stuff on an improperly initialized piece of hardware or if the actions trying to be performed are illegal (including not possible)... could be a bad NIC (mind you I didn't read the whole original post) or just a bad config file

Re: Ethernet weirdness

2000-12-18 Thread Charles Galpin
My bet is on the cards. I've seen this happen with a friend's setup like this - win98 -- crossover cable-- linux The win98 box wouldn't boot without the linux box being up. I don't recall about visa versa. they were dead cheap nics, but don't recall the brand. charles On Mon, 18 Dec 2000,

Re: Ethernet weirdness

2000-12-17 Thread Bret Hughes
Micah Yoder wrote: Hi, I have two RH6.2 boxes connected to each other by Ethernet, a crossover cable. Both have 3Com 905 cards. The names are eclipse and nova. The weird thing is that nova MUST come up first, or they won't talk to each other. If I boot eclipse when nova is not on,