Really newb question for networking

This is a discussion about Really newb question for networking in the Everything Linux category; Hello, I currently have RedHat 9. 0 Installed on my 2 servers. Both are acting really bizarre at system restarts. I can only setup my network manually, anything else fails AND when I reboot, all the configuration I have went through is ignored and my eth0 isn't brought up.

Everything Linux 1800 This topic was started by dppls, 2003-12-04 16:23. Last reply by frequencydrive, 2004-03-15 02:50

Discussion 4

dppls

2 Posts
Location -
Joined 2003-12-04

#118376

2003-12-04 17:23

Hello,

I currently have RedHat 9.0 Installed on my 2 servers.
Both are acting really bizarre at system restarts.
I can only setup my network manually, anything else fails AND when I reboot, all the configuration I have went through is ignored and my eth0 isn't brought up.

I am a newb with RedHat so, I don't know what logs are okay or not...
I will post all logs needed when asked.

I do now that I have these messages in /var/log/messages
Dec 4 09:40:37 ns1 kernel: Intel

PRO/1000 Network Driver - version 5.0.43-k1
Dec 4 09:40:37 ns1 kernel: Copyright

1999-2003 Intel Corporation.
Dec 4 09:40:37 ns1 kernel: eth0: Intel

PRO/1000 Network Connection
Dec 4 09:40:37 ns1 kernel: ip_tables:

2000-2002 Netfilter core team
Dec 4 09:40:37 ns1 kernel: e1000: eth0 NIC Link is Up 100 Mbps Full Duplex
...
Dec 4 09:40:37 ns1 ifup: failed.
Dec 4 09:40:37 ns1 network: Bringing up interface eth0: failed

And if I try a services iptables save i get:
Dec 4 10:31:31 ns1 vsftpd: warning: can't get client address: Bad file descriptor

Thank you very much.

REVERSES - New free wav samples (or Reason refill)

bootp: Server w.x.y.z not responding, timed out

Participate in our website and join the conversation

You already have an account on our website? To log in, use the link provided below.

Create a new user account. Registration is free and takes only a few seconds.

This subject has been archived. New comments and votes cannot be submitted.

Dec 4

Created

Mar 15

Last Response

0

Likes

2 minutes

Read Time

Users

Responses to this topic

chrispope

29 Posts
Location -
Joined 2003-12-09

#118377

2003-12-09 21:14

Try typing dmesg at the command prompt and sift through the "wreckage" of you system startup to find any errors that occured that the system did not tell you about.