I had this problem back when I was running red hat 7.3 . I worked at it a lot and no matter what it did it refused to activate eth0 for the home network. This problem was very common among the people I knew who were running 7.3. When I upgraded to 8.0 the problem had been rectified. Even though it should not have been a problem, for some reason 7.3 had odd quirks when run on a dual boot with windows, but when it was running on the box by itself it didnt experience any problems. For me, the inability to activate eth0 on a home network was one of those problems. I wish I had an easier answer for you but I am at a loss, I would suggest upgrading to Fedora Core 1.

Ok, I have the workstation with Redhat on connected directly to my PC running w2k. I don't need a special connection, I just need to be able to ftp files back and forth. The workstation is dual bootable the other OS being w2k again. The connection when both computers are running w2k is fine, I've mapped the partion as a network drive. When it is booted into redhat the eth0 will only go active when I fix the IP address and although the Connection icon appears on my w2k computer I cannot make an ftp connection as it tells me there is an error( although not what the error is!). I set the IP address on the w2k computer to see if this would help but get the same problem. I've just used the command prompt to ping the workstation and this appears to function just fine. I then ftp'd to the same address and the message says connection refused. Same when I use the console to ping the w2k computer. There must be some setting I haven't yet activated or some sort of permission I have to set but that's all I can tell you

As said, try upgrade to a more recent of Red Hat. There seems to be a consensus that RH 7.3 does not properly support some newer interface cards. I think your problem should then go away by upgrading. I fixed my problem this way.

No, there isn't any other special configuration quirks needed I know of. If the network interface is supported, then it should be able to be activated right away and no extra tweaks needed.

Of course, it is a good idea to disable your firewall before doing your tests.

hello all,
I also have a problem with network connection on Linux..

I just installed Fedora Core 3. and I am trying to connect to my computer on command prompt like :
$ telnet mycomputer_name
Trying xxx.xxx.x.xxx...
telnet: connect to address xxx.xxx.x.xxx: Connection refused
telnet: Unable to connect to remote host: Connection refused

And I am getting the above message back... But ssh works fine. How can anyone on the same LAN connect to my linux box by typing "telnet" on their command prompt(or whatever)?

Telnet is an insecure means of logging into your box. It is disabled for security reasons. If SSH works for you, then you should just use it. If there are any reasons why you need to use Telnet and SSH does not work for you, then consider the security risks involved in using Telnet over the limitations; if any, of SSH in your decision.

If you must enable Telnet, enable it in your /etc/inetd.conf file.
Read through the manual; man telnet

thanks for your reply locustfurnace, but there's no inetd.conf file in the system(in Fedora).

I am having the same problem in Windows OS, too. No one in our LAN can can connect to my computer using telnet from their computer. Even I can't telnet to my computer from my computer. The reason I am asking telnet is, because MS-Dos does not support ssh command. I found inetd.conf in Windows(using cygwin) but I don't really know what to do inside that file.

Hi to all, I have a simmilar problem like Mace had, so i have installed a Slackware 9.0 distribution on one PC.I have win2k on a second PC, and i connect to the internet wia dsl with the computer running with win2k.I want to enable the slackware machine to connect to the internet through the win2k PC.I've enabled the sharing option in windows so that there actually such a connection can be made, but on the slackware PC i still don't have internet.It has a local network, when i ping to the win2k PC everything is ok, the eth connection is also ok but the slackware PC cannot get out from the local network to the internet.I'm not really sure what to do next, in windows the local area connection is with static IP 192.168.0.1 because it needs this address to share the internet connection.I've tried with different addresses on the linux machin but no success, it just stays in the local network behind the win2k PC.Can someone help me?thanks