Network problems

[RightOn]

Hi im a very new user of linux and for a start i decided to experience the fedora distro.
I´ve instaled everything smothly with a setup made for a worksation, but for some unknow reason to me the network is dead, when i try to use dhcp (wich works fine with my PDA and a laptop) i get a error message saying something like "cant get ip for eth0", so i tought "maybe if i try with a static ip it will work...", but as you can all see if im writing on the forum is becouse that solution didnt work... :confused:

Well i have all my computers linked to a dlink router and everything on my network works fine except the fedora box.

Plz bare with me becouse i dont understand nothing about commands and that sort of stuff for linux, so i move around by the graphical interface.

My question is, i´ve seen people complaining about the same stuff in the forum, is this fixable or should i change for another distro? I´ve seen another user saying that he moved to Debian and all worked fine and he had the same problem im having.

So if some of you guys could tell me the best option i would be very tankfull. If this an know bug plz could someone point me to the right direction in order to fix the problem.

My network config is like this:
Router: 192.168.1.1
other machines range: 192.168.1.50 / 60

[pzeigler]

It might help if you tell us what type of NIC you are using.

[RightOn]

It might help if you tell us what type of NIC you are using.

Hi by NIC i assume type of network card correct? im using a Genius GF100TXR4 a plain simple ethernet 10/100 card

[RightOn]

I have been seing other post and everywhere people always ask these configs, so i wrote then down in case its necessary.

at the moment i have a static adress as you can see, but still no network....
------
resov.comf
search 192.168.1.1
nameserver 192.168.1.1

------
hosts
127.0.0.1 localhost.localdomain localhost

------
ifcfg-eth0
IPV6INIT = no
ONBOOT = yes
USERCTL = no
PEERDNS = yes
GATEWAY = 192.168.1.1
TYPE = Ethernet
DEVICE = eth0
HWADDR = 00:40:f4:b5:64:41
BOOTPROTO = none
NETMASK = 255.255.255.0
IPADDR = 192.168.1.50
-------------------------------

[tresslyn]

I dono maybe try this.

# ifconfig eth0 up

or

# /etc/init.d/network restart

[RightOn]

Hi, i have allready tried that, i assume that is to start my network card, wich has been always active so no problems there i have the card lights all working and the status is showing active.
The problem seems to else where altough i cant really say where.

None the less thanks for the help.

RightOn

[tresslyn]

next question, can you see your router?

[RightOn]

no, for now its the only test i´ve been doing, im writint on firefox my router adress by i cant access it

[tresslyn]

What is the message you receive when you activate eth0 in the network GUI? The reason I ask is when I reinstalled my system I received a error code on my network card.

[RightOn]

I dont get any error if i assigned a static IP, but if i leave it to dhcp then i have to restart the network and i get "determining IP information for eth0... failed"
I guess he cant reach the router to be assingned a IP by dhcp

[Crux]

192.168.1.1 is the router GUI address for most routers. I've 2 NIC's for internet sharing. this is the static I gave the one that is the 'network'
eth1 Link encap:Ethernet HWaddr 00:A0:C9:03:8D:E9
inet addr:192.168.1.200 Bcast:192.168.7.255 Mask:255.255.248.0
inet6 addr: fe80::2a0:c9ff:fe03:8de9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7556 errors:0 dropped:0 overruns:0 frame:0
TX packets:7438 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1194524 (1.1 MiB) TX bytes:8421408 (8.0 MiB)

Try changing the IP, and don't forget to setup the DNS.
You can find the DNS for your box with this

# cat /etc/resolv.conf

Mine looks like this
[root@enigma enigma]# cat /etc/resolv.conf
; generated by /sbin/dhclient-script
search -my isp-
nameserver 24.215.0.11
nameserver 24.215.0.12
nameserver 24.215.0.13
[root@enigma enigma]#

[tresslyn]

I notice another thread with dual nics. Let me see if I can find it again. They seemed to resolve their issue.

[RightOn]

192.168.1.1 is the router GUI address for most routers. I've 2 NIC's for internet sharing. this is the static I gave the one that is the 'network'
eth1 Link encap:Ethernet HWaddr 00:A0:C9:03:8D:E9
inet addr:192.168.1.200 Bcast:192.168.7.255 Mask:255.255.248.0
inet6 addr: fe80::2a0:c9ff:fe03:8de9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7556 errors:0 dropped:0 overruns:0 frame:0
TX packets:7438 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1194524 (1.1 MiB) TX bytes:8421408 (8.0 MiB)

Try changing the IP, and don't forget to setup the DNS.
You can find the DNS for your box with this

# cat /etc/resolv.conf

Mine looks like this
[root@enigma enigma]# cat /etc/resolv.conf
; generated by /sbin/dhclient-script
search -my isp-
nameserver 24.215.0.11
nameserver 24.215.0.12
nameserver 24.215.0.13
[root@enigma enigma]#

Hi can you plz explain to me better, i cant figure out what ip you want me to change? The ip on my router or my fedora box ip?

Another thing, if you have 2 NIC's one is active and the other deactive right? they cant be both active at the same time, and also would that resolve my problem?

[Crux]

Hi can you plz explain to me better, i cant figure out what ip you want me to change? The ip on my router or my fedora box ip?

Another thing, if you have 2 NIC's one is active and the other deactive right? they cant be both active at the same time, and also would that resolve my problem?

Change the IP on the NIC in your box. Yes, BOTH of my NIC's are active. One runs the cable modem, the other hooks to the wifes box for internet/file/printer sharing. eth0 get's it's information from the DHCP of the cable modem, and passes it to eth1. You need to know what information your router is trying to send to your NIC if you want to set it up staticly.

Also, did this ever work?
Where did you get the cable?
Is it a cross over cable? or straight through?
Is it perhaps hooked into the aux/dls connection of the router? Try another jack in the router.
Is the router active? aka lights and such.

I know, dumb questions, but since I am not there I've gotta ask.

[RightOn]

Hi by parts:

dis this ever work? = No never

the rest of the question are all tested the cable is a straight trough and the router is on and that sort of stuff, i also thought it could be the cable 2 nights ago, but i tried linking it up to my laptop and everything worked fine.

i have this problem only the fedora box, and i have it since i installed the OS for the first time. really dunno what can it be...

ah, i allready assigned a new ip to the NIC, but nothing... im rebooting just in case also i tried tried to leave the eth0 to dhcp, but still nothing, the only way i cant get the two NIC´s wroking togheter is assigning a static IP for each one, but even so no network.

[Crux]

hhhmmm... only other suggestion is to ensure your NIC is on the hardware compatibility list (https://hardware.redhat.com/hwcert/index.cgi) if not maybe try a generic Tulip driver.

Also, maybe download KnoppixSTD (http://distrowatch.com/table.php?distribution=knoppixstd) or DamnSmall or other diagnostic distro to see if any Nix version can setup that NIC.

Keep us posted.

I googled and found that you are not the only one. Try unplugging the cable, and plugging it back in while the machine is hot/on/
BSD Forum (http://www.bsdports.com/forums/showthread.php?threadid=27998)

[RightOn]

Ok, thanks for the assistance, im gonna try one of those diagnostic distros, or maybe even a ful one to see if i can make it work.
Once again thank you for the help.

RightOn

[affanjavid]

I was stucked in same problem while i was trying by Ehetrnet card (built in my System Board *SIS900) that was not prpperly installed as i resulted.............when i used a new ethernetcard (PCI) every thing was fine.

[Crux]

Ok, thanks for the assistance, im gonna try one of those diagnostic distros, or maybe even a ful one to see if i can make it work.
Once again thank you for the help.

RightOn

No frets. Linux was built on community support. If.. nay.. WHEN you get it rolling, let us know. Also, any further questions you have, please ask. Seems like a driver issue though.

One last question. Was the NIC installed BEFORE the distro was loaded? If so, maybe take it out, then force the OS to find it and set it up. Just a needle in the haystack suggestion. Or do what we used to with the tractor. Beat the piss out of it and wire it back together. :D

[RightOn]

Just a note, i´ve tried unpluging the cable and plugin it again and between i queryed my router and strange enough i get the same response " the connection was refused when trying to contact 192.168.1.1"

Well im not a rocket scientist but it seems that either with the cable on or off the problem is that the fedora core isnt letting me send info, its like the network card was dead. when i installed i said no firewall and no SELinux becouse it was the secound time i was installing becouse of this problem..

Guess nothing i can do, like i said i´ll probably try another distro... ill keep people posted if i found anything more about this matter, altough i think this is a bug on the OS build

[RightOn]

Hi there again, after these few weeks wich i had very few time to resolve my problem, and before like i said changing distro i began wondering it could be a hardware malfunction, well now i have my fedora distro up and running smothly :D

I just went out and asked a old ethernet card from a friend of mine who has a hardware store, and now its all working fine, i guess the real problem is that Fedora core 4 doesnt work with my new ethernet card wich is, for all those interested, a Genius GF100TXR4.

So if you planing on installing Fedora with that card forget about it, i just did :D
Now i have an old 3Com card that works fine.

Well thx a lot for the suport people.


RightOn

[Trek1701]

Hey RightOn!
I have the same problem you had. What 3Com card are you using now? I'm using 3Com 3c905c.

Trek1701

[RightOn]

Hey RightOn!
I have the same problem you had. What 3Com card are you using now? I'm using 3Com 3c905c.

Trek1701


Hi thats exactly the same im using now, and everything is working fine

Sorry for the time i took to reply but i had to step away from the computer for a while

[Trek1701]

Hi thats exactly the same im using now, and everything is working fine

Sorry for the time i took to reply but i had to step away from the computer for a while
Don't worry ;)

Question: are you using it with static IP 192.168.1.1 or not?

Trek1701

[RightOn]

nop, im using dhcp enable ip´s, so i guess the hard part is done using a static ip its easier.

[zhiping_mei]

I did not have problem when used NetworkManager v0.4 after fresh installation. Similar problem happened when I updated to new version of NetworkManager (v0.5). So, all what I did was keep the original version of NetworkManager, and avoid updating NetworkManager. There must be some problem with new version of NetworkManager. Maybe I am wrong.