I'm All by myself Noone is connecting.. All by myself

[HaBiTaT]

ok here is the deal: Want to be able to access home network.

The home server is just 4 computers linked up to a netgear 8 port hub with an uplink switch so everyone can connect to a horrible dsl modem provided by AOL::face turns sour because of the horrible service they provide::

anyways i'm having problems talking to the network itself... i can do it on the other 4 windows machines but not with my linux box.
it keeps saying : could not connect to localhost
Local Host

I'm using a Linksys Etherfast NC100 card. Installed properly i hope.

do i need to setup a sever to be able to do this???

[SuperHornet]

Ok, sigh

What Distro and version are you using?

When the box boots up do any of the interfaces start (eth0, eth1, lo) with no errors?

Should find that in /var/log/boot.log

Do you have to staticaly assign a IP or is provided for you?
You can see this using ifconfig.

[HaBiTaT]

By distro you mean what type of linux and version right????
Mandrake v 8.2....

Now that i think of it when my box does start up my eth0 does fail....

because it is aol the IPs are static.

[fancypiper]

Since when can Linux connect to AOL? I thought it took a Windows program to use AOL. :confused:

[HaBiTaT]

well that was gonna be my next question.... am i able to use wine to run aol... so i can connect to the world????

[fancypiper]

Let us know. :D

[HaBiTaT]

The only problem is that my ethernet card is failing when linux loads how do i fix this???

[DMR]

OK, here we go- from the bottom up:

Post the make and model of your NIC; knowing that will help us help you.

1. Turn off Plug-n-Play support in your BIOS; doing so can eliminate resource (IRQ and I/O address) conflicts on the PCI bus.

2. Use the following command to make sure that your card is at least basically identifying itself correctly to the system:

lspci |grep Ethernet

You should see your card's chipset correctly identified in the resulting "Ethernet controller" output.

3. Run the ifconfig command; verify that your NIC is recognized in the resulting output (if you only have one NIC, it will be listed as eth0; you should also always see stats for the loopback device 127.0.0.1). Verify that the IP info (inet addr, Bcast, Mask) is correct, and note the Interrupt and Base address values. Also check for RX/TX errors and collisions. If eth0 is not listed when you run ifconfig, try "ifconfig -a"; the "-a" option forces ifconfig to report all network interfaces, active or not. If eth0 appears only when you run ifconfig with the -a option, it is definitely not running correctly.

4. Run the following two commands:

cat /proc/interrupts |less
cat /proc/ioports |less

For the first command, note the IRQ assigned to eth0; verify that it matches the Interrupt value listed when you ran the ifconfig command, and note if the assigned interrupt is being shared with another device. If so, this doesn't necessarily indicate a problem, but it can.
For the second command, make sure that the address range of your Eternet controller doesn't conflict with/overlap that of another device. Also make sure that the start of the address range corresponds to the Base address value given for eth0 when you ran ifconfig.


6. If the above steps yield errors or indicate conflicts even after you've turned off P-N-P support in the BIOS, you can try physically rearranging the slot order of your cards on the PCI bus to allieviate those conflicts.


7. Verify that the correct module is being loaded for your ethernet card by issuing the "lsmod" command; you should see the module name in the resulting list of loaded modules. If not, issue the following two commands and try again:

depmod -ae
modprobe <name of your NIC's module>

If the module appears as loaded after that, check your /etc/modules.conf file to make sure that it has an entry for the module (this will load the module automagically each time you boot). The line will look like this:

alias eth0 <name of your NIC's module>

If the line doesn't exist, add it by editing the file with your favorite text editor.

8. Once you're sure that the NIC is correctly configured and the module is properly loaded, you can try to bring the card up with the following command:

ifconfig eth0 <the NIC's IP address> netmask <the appropriate netmask> up


If you get no errors, you should at least be able to ping the IP address of the NIC.


Give the above a shot, let us know what you get (be specific), and we'll take it from there.

:)

[HaBiTaT]

ok i typed : lspci | grep ethernet

Nothing happened sent me to the
root@localhost root prompt

[fancypiper]

Typo. It should have been:ls pci | grep ethernet

Trycat /proc/pciand post the results of the line that looks similar to mine: Bus 2, device 1, function 0:
Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (rev 16).
IRQ 11.
Master Capable. Latency=32. Min Gnt=32.Max Lat=64.
I/O at 0xc000 [0xc0ff].
Non-prefetchable 32 bit memory at 0xef000000 [0xef0000ff].

[HaBiTaT]

when i typed in ls pci | grep ethernet
i get an error messege..... I don't think i am properly setting up my ethernet card how do i manually set it up to use the tulip driver????

[DMR]

fancypiper:

That wasn't a typo- the command is lspci (although your suggestion of using "cat /proc/pci" will work as well).


HaBiTaT:

Linux is case-sensitive; when issuing "lspci |grep Ethernet", the first "E" in Ethernet needs to be capitalized in order for the command to work. Try it again using proper case and let us know what you get. If it doesn't work for some reason, try fancypiper's advice about using "cat /proc/pci" and look for some indication of your NIC in the resulting output.

Also try the other tests I posted and let us know the results of those as well. Concerning the tulip module, where I indicated "<name of your NIC's module>" in my suggestions, just replace that with "tulip" (omit the quotes) instead.

[HaBiTaT]

everything corresponds to your long post DMR:

1. PnP is off
2. 00:09.0 Ethernet controller: Linksys Network Everywhere Fast Ethernet 10/100 model NC100 (rev. 11)
3. Eth0 Link encap: Ethernet HWadder 00:04:5A:80:E9:5B
Broadcast Multicast MTU:1500 Metric 1
Rx Packets: 0 errors: 0 Dropped: 0 Overruns: 0 Frames
Tx Packets: 0 errors: 4 Dropped: 0 Overruns: 0 carrier: 8 Collisions: 0 Txqueuelen: 100
Rxbytes:0 Txbytes:0
Interupt 11 Base address:0xdc00
4. cat /proc/interrupts |less
cat /proc/ioports |less = dc00-dcff

7. lsmod does load the tulip driver.

[HaBiTaT]

^bump^

[DMR]

My looong post indeed; it took 3 cups of coffee to write that tome. This will a little shorter, I promise...

:D

Originally posted by HaBiTaT
3. Eth0 Link encap: Ethernet HWadder 00:04:5A:80:E9:5B
Broadcast Multicast MTU:1500 Metric 1
Rx Packets: 0 errors: 0 Dropped: 0 Overruns: 0 Frames
Tx Packets: 0 errors: 4 Dropped: 0 Overruns: 0 carrier: 8 Collisions: 0 Txqueuelen: 100
Rxbytes:0 Txbytes:0
Interupt 11 Base address:0xdc00Hmm, ifconfig is not showing an IP address assigned to eth0, which either means that you haven't properly assigned it, or it is actually being assigned via DHCP. The output of ifconfig for a NIC with a statically assigned IP would look like this:eth0 Link encap:Ethernet HWaddr 00:E0:29:5F:B9:29
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:35926 errors:0 dropped:0 overruns:0 frame:0
TX packets:39621 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:27848568 (26.5 Mb) TX bytes:7643831 (7.2 Mb)
Interrupt:10 Base address:0x5000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:4540 errors:0 dropped:0 overruns:0 frame:0
TX packets:4540 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:444728 (434.3 Kb) TX bytes:444728 (434.3 Kb)Note the inet, Bcast, and Mask entries for eth0; you will see something similar when using a statically assigned IP.

A couple of thoughts:

-What is the exact error message when eth0 fails at bootup? If it says something similar to "determining IP information for eth0: FAILED", it's likely that the card is tring to use DHCP. If the message is more like "Bringing up device eth0: FAILED", then you probably have a static IP assigned but have other problems.

-If you are not using DHCP, your /etc/sysconfig/network file should contain the following (substitute your HOSTNAME, DOMAINNAME,and GATEWAY info obviously):[root@penguinbox~]# less /etc/sysconfig/network

NETWORKING=yes
FORWARD_IPV4="no"
HOSTNAME="penguinbox.localdomain"
DOMAINNAME=localdomain
GATEWAY="192.168.0.1"
GATEWAYDEV="eth0"

- To verify eth0's particular IP, netmask, broadcast address, etc., check /etc/sysconfig/network-scripts/ifcfg-eth0:
[root@penguinbox~]# less /etc/sysconfig/network-scripts/ifcfg-eth0

DEVICE="eth0"
BOOTPROTO="none"
IPADDR="192.168.0.2"
NETMASK="255.255.255.0"
NETWORK=192.168.0.0
BROADCAST=192.168.0.255
ONBOOT="yes"If you are using DHCP, "BOOTPROTO" will be "dhcp". If you are statically assigning, the information should appear similar to the above (again, with your IP information instead).

-Can you ping the NIC by the IP you assigned it?