Networking Problems

Red Hat 6.1 on a custom built Pentium 166.  Everything seems to work fine, except the Network adapter - which is an SMC 10BaseT PCI NIC (DEC 21040-AA chip).  When the system boots it fails to start networking.  But, if I run netconfig from the console (before I go into X) I can successfully get an IP address (through DHCP).  I have tried a 3c509 card as well, but that doesn't seem to work at all.
LVL 97
Lee W, MVPTechnology and Business Process AdvisorAsked:
Who is Participating?
 
jlevieConnect With a Mentor Commented:
In what way does the network fail to start at boot. Does the NIC driver get loaded (shows up in "ifconfig -a)? Which rev of the 3c509 did you try? Who is providing the DHCP service (a server on a local LAN, DSL modem to an ISP, or cable modem)?
0
 
jyu_88Commented:
I will try to see if network is enabled by checking /etc/sysconfig/network.
To change those configuration, use 'netcfg' under X and make sure to DHCP is chosen for interface protocol at the bottom of 'interface eth0 editing' window.
 
0
 
barreroCommented:
A simple question.. but why not... everithing is possible:

Are network services up and running?

when you run later netconf from the console it starts automatically the network services...

0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
Lee W, MVPTechnology and Business Process AdvisorAuthor Commented:
During the Red Hat boot, every service that starts displays a green "[    OK    ]" - when eth0 (SMC) and eth2 (3c509) are started (or rather asked to start) the system "pauses" or times-out after about 10-15 seconds and each one says "[FAILED]"  Then, after I log in as root, I run netconfig and the SMC adapter gets an IP and works just fine.

DHCP is coming from a Win2K server and works fine on my other linux box and windows clients and even for Be when I had that briefly installed.  I'd like both NICs to work as I would ultimately want this to act as a backup gateway for my other systems (currently, my Win2K server is the gateway for all systems).  If I succeed in getting both NICs working, one will obtain an IP from a cable modem, the other from the Win2K box.
0
 
jlevieCommented:
And the big question still is, did the ether cards get recognized during boot and before you manually start the network? The output of "ifconfig -a" well tell. Also I still need to know which 3c509 you've got (and I think the answer may be significant for both problems).
0
 
Lee W, MVPTechnology and Business Process AdvisorAuthor Commented:
I'm accepting this as an answer because if was the command ifconfig that helped me figure out what was wrong - that and comparing the 3c509 config in another linux box I have.  First, I had specified the IO address and not the IRQ of the 3c509 card.  Second the SMC PCI card was being assigned IRQ 10 by the system.  As a plug-and-play PCI device, I went into my bios and set IRQ 10 to be used by ISA card.  After doing this it has worked fine since.  ifconfig is what first showed me the SMC card was on IRQ 10 and therefore conflicting with the 3COM card.
0
 
jlevieCommented:
Sorry, it wasn't until just now that I realized that what I had meant to be a comment had been set as a proposed answer.

But, the card status was what I was trying to get you to look at. From the first I suspected an IRQ conflict, with the additional gottcha that the later 3c509b-TX cards come with PnP enabled. PnP can cause all kinds of grief, especially when there are other NIC's in the system.

Anyways, I'm glad you were able to figure it out and get it working.
0
 
Lee W, MVPTechnology and Business Process AdvisorAuthor Commented:
No, it was a comment - I accepted it as an answer.
0
 
jlevieCommented:
Huh, I didn't realize they'd changed the process...
0
All Courses

From novice to tech pro — start learning today.