ifup eth1 gives me Network error how can I troubleshoot this?

It sounds like there's an /etc/sysconfig/network-scripts/ifcfg-eth1 file that /etc/init.d/network used to try to bring up the interface at boot (RTNETLINK answers: File exists), but that failed for some reason. Quite possibly there's no link carrier being detected (SIOCADDRT: Network is unreachable). That might be as a result of a bad NIC, bad cable, bad hub/switch port, improper network configuration, etc.

The first thing to do is to verify that there's a usable network connection to eth1. You should also verify that the network config for eth1 is correct for the network it will connect to.

The hardware is good. This server is functioning. However, there is a slow response for certain functions.

> However, there is a slow response for certain functions.

Could you elaborate on that?

When this server connects to a remote host to have data computed, it takes about ten seconds.

I was hoping the error I get when i up the adaptor would help me find out why.

If the system has a working network link why would you be trying to bring up eth1 and what would expect to gain by doing so?

When I first configured the network, I remember getting this error. But it appeared as though everything was working okay. When the slow response was detected, I thought the error might help determine the cause of the problem so I put it down and then up to get the exact error message.

"Linux 7.3" - can you elaborate on that?

Also, if you have "eth1", you must also have "eth0". Please post output of "ifconfig -a" and the contents of /etc/resolv.conf

Thank you for your help. It turned out to be a daemon that was not running. Not a network problem. Still wonder about that error with the adapter though.

If you'll show me the contents of the files above I can probably tell you what's wrong or where to look for the source of the problem.

For sake of documentation, I ran into this today as well and never did find anyone else with the same resolution.  I'm thinking mine may have been caused by a recent fedora update.  Anyway, the cause of mine was because the device eth0 was configured to be managed by the"network manager".  I went into the device from the GUI and deselected the checkbox entitled "Controlled by NetworkManager".  The network manager must be conflicting with the eth0 configuration.  This problem also had the symptom of losing the DNS server entries in the NIC.