Networking Problem...read the posts here

[GridX]

I cant get networking to work with FC5 64bit for my AMD 64 Athlon X2 3800+, it has an nVidia MCP5 Ethernet adapter.... which FC5 detects and lists in the network configuration.

I get a Determining IP information for eth0 Failed.

So I cant dhcp, so I try to staticly assign the IP and Ido that and I get status: active, and a status OK.

I do a service network restart and eth0 comes up as OK

ifconfig looks fine no erros, I see my staticly inet addr (I also see an inet6 addr-- I thought I turned it off...does that make a diff?)

I can ping my staticaly machine IP and loopback, I cant ping my gateway (192.168.0.2--which is my router) nor any other machine on the network, I cant ping this Fedora machine from other pcs on the network either.

I have dual booted XP and FC5 on the same machine and the router is supposed to dhcp an address for the dual boot machine...windows gets an ip and network works fine, just not the FC5 part of the machine.

I dont know what I am doing wrong, is it my router? or my NIC?


I am ready to try another NIC, cause this is driving me crazy.



help me

GridX

[3 legged cat]

Just wondering, is it possible your firewall (iptables) is blocking your pings?

[GridX]

I disabled all firewalls and SElinux , I think its a problem with nvidia network driver, and I cant install the network driver it says unable to find the kernel source tree, and I cant find the kernel-devel package for me to install either, this is way too much work just to get networking up.

[Seve]

Hello:
I am no expert, but I suspect you need to look at your router based on what you have posted.
Assuming it does the dns and assignment of IP's? just a thought
Seve

plz check ur firewall configuration, there might b some problem with it.

Also what's the ip that u r giving to the card?
R u using more than one card on the same machine? if yes, what are the ip addresses u r assigning to them...

[GridX]

I turned off all firewalls inside FC5, everything, on my router it does supply DNS ..but I cant even ping my router at all...which is the gateway, I did have it set to dhcp, but FC5 wouldnt dhcp, so I statically assigned an IP in FC5... no go, couldnt ping my router..I also turned of dhcp in the router and statically assigned an IP in FC5 and still could not ping my gateway (router at 192.168.0.2) I assigned everything correctly.....

I think its the nvidia network card, I cant install the nvidia drivers cause it says I need the kernel source installed.... dont know how do to that nor where to find the kernel source rpm.... can anyone lead me in the right direction? if this doesnt work, I am getting a new NIC, if that doesnt work , a new distro.... cause I am really tired of all this troubleshooting... I am too busy to screw around with this.... Sorry if this sounds arrogant, but I am really annoyed.


so much Googling and so little time


GridX

[Kees-de-Graaf]

You should not blame it on your NIC. This problem shows some similarity with wat my E-tech modem-router does to my network. I bought it secondhand, from someone who switched to another ISP, so there was his previous ISP's 'firmware' in it. Initially both fc5 (desktop) and Ubuntu (laptop) did not connect. I changed the modem-router (speedtouch) and all worked fine. Next thing I did, was a firmware upgrade on the E-tech, and now Linux gets connected, but at a very low speed, especially loading a webpage takes like forever. I'm not sure about downloading files. I don't get anything from the Livna repo's, just to mention something.
E-tech's response to the problem is: "Must be something bad in your OS". So, after visiting dozens of fora and fiddling around with all kinds of settings I'm beginning to believe that some DSL, ethernet and other 'intelligent' networking-peripherials have taken some 'shortcuts' in their programming, which are no problem to Windows, but do expose their bugs to Linux by not establishing proper connections.
For further testing purposes I downloaded Damn Small Linux and PuppyLinux. (DSL doesn't seem to cope very well with my MoBo -- AsRock P4VT+ --, Puppy works fine) They can both be ran from a usb-pendrive or CD-rom. Puppy gets connected to the network and to the WWW, but still not at full speed.
I do not know how to diagnose the E-tech. Stuff like PING and Traceroute don't show anything suspicious. All values I read from other network tools & logs are looking OK, so what the ***ck is going on out there?

[GridX]

I disabled the nvidia network adapter and installed a linksys card and now everything works. No more hassles, I couldnt install the drivers for the nvidia network card no matter what I tried. But the linksys card worked as soon as I booted into FC5 all is good now.

[lobobravo]

I'm having the exact same problems, except my NIC is integrated on the ASUS motherboard.
This system worked fine under FC4 (X86), so I am inclined to blame FC5 (x86_64) not my NIC.
I am also unable to install my motherboard's NIC driver because the kernel source tree is not there.
I have seen postings that say not to use the third party drivers, so I have held off on installing the kernel source.

Anyone else having these problems?
Anyone know how to make this work under FC5?

[lobobravo]

Well, unless something comes up in the next few hours it looks like I'm on my way back to FC4.
Is it just me, or is there a problem when the new release breaks something that worked in the old?
I found the x86_64 distribution for FC4 - which was not indexed under the FC downloads page, but can be manually entered in the address string - why that is so hard to find I don't know.
The site posts a broken release and hides the old one - not a big confidence builder.
Next I'll find out it's the 64-bit mods that are breaking the networking and have to go back to x86 FC4.

[wintersm]

DId you cold-boot the computer into linux - there has been some threads on these nvidia network adaptors here before - Its appears that just a reboot from windows to the linux box will cause the network to "not work"..

What appears to be happening, is that most of these nvidia adaptors have some sort of firewall that is activated by the windows drivers, and it remains active on soft-reboots, which means that booting into linux tends to mean the network stops working..

Try ensuing the computer is totally powered down before booting into linux (skip windoz entirely) and see what happens.. I have g-force 4 chipset with builtin ethernet that has the "firewall" but as i have never run windows directly (only under vmware) on it, the network adaptor has performed flawlessly..

[lobobravo]

This is a new, stand-alone system.
It has an integrated NIC on the ASUS motherboard.
(Not exactly the same as the original post - but all of the same problems getting networking up.)