streeter

Looks like your driver is probably ok - you wouldn't get anything under eth0 from ifconfig if it wasn't loading. You have not got an IPv4 address assigned to eth0. Do you NEED a dynamic (dhcp) address? You may not even have a DHCP server running - this would explain a lot... If this is your own internal private network, try static addresses. To test your card/driver: As root: (see below) # mv /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth0.old # ifconfig eth0 192.168.0.2 up (you should check the IP address of your router, and assign a number in the same range) # ifconfig eth0 You should then get an ip address (192.168.0.2) in the output. If this works, there's probably nothing wrong with your card/driver. To be root in a console, type su then your password. You need to read the help files a little to learn how to edit files/use the console - an easyish way of file manipulation under a console is to use a file manager called mc - type mc at the command line. If it doesn't start, you will need to install it - type urpmi mc (as root). Chris

Why are you connecting to the internet with an insecure OS when you have a Linux box ? : ) You need to change your wired LAN IP addresses to say, 192.168.7.x . The two networks (wired and wireless) must have different network addresses (first three numbers in this case - class C - net mask 255.255.255.0) Then XP will be able to route packets between the two networks with internet connection sharing. Chris

Not much to go on... First, can you ping your ethernet card? Then can you ping the router? If not, is the driver loaded for your network card, what is the output of ifconfig, and contents of /etc/sysconfig/network-scripts/ifcfg-eth0? Are you running a DHCP server on your router/elsewhere? Can you connect from any of the other PCs? Should do for now : )

Hi Don't start messing with other drivers yet... (I use the SIS900 driver on mdk9.1 and 10.0) Your driver is loading (because you get output from ifconfig eth0), you are just not getting an IP address. Do you NEED a dynamic address? If this is your own internal private network, use static addresses. Several people have suggested you try a static address - have you yet? To test your card/driver: As root: # mv /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth0.old # ifconfig eth0 192.168.0.2 up # ifconfig eth0 You should then get an ip address (192.168.0.2) in the output. If this works, there's nothing wrong with your card/driver. It is normal for a card to 'hang' foir 30 seconds or so when looking for a dynamic address and it cannot find one. Let us know how you get on... Chris

>> I have no idea how to check if my computer is blocking ports as root: iptables -nL Try connecting to your smtp server using telnet with ' telnet smtp.yourisp.com 25 ' - what message do you get?

The Asus web site says your motherboard has a built in network port - have you, or is this a model without? If it has got one, try unplugging one of the PCI cards and using the built in one (you may have to enable it in the BIOS). Just a thought, in case you are having a problem with both cards being the same, or Linux seeing 3 network cards... What is the output of typing ifconfig in a terminal? (you have to be root)

As root: # ifconfig eth0 192.168.2.20 up (or some other IP address not used elsewhere on your LAN) This will set up a static address for your NIC. # ifconfig eth0 should show the IP address ping 192.168.2.1 To test it If that works, there's nothing wrong with your NIC, just your settings... Or post the results here :)

What network card have you got? To check if the driver is loaded do a 'lsmod' at the command line (you must be root). If the driver is not loaded, try loading it first with 'modprobe <drivername>', then running 'service network restart'. If this works, put the driver name in /etc/modules and 'alias eth0 <drivername>' in /etc/modules.conf Or perhaps you already tried....