Dennis Myers wrote:
On Thursday 17 February 2005 10:10 am, Dennis Myers wrote:

On Thursday 17 February 2005 08:36 am, Michael Hahn wrote:

From: "Derek Jennings" <[EMAIL PROTECTED]>

Can you try choosing a static address just to eliminate any issue with
the DHCP server?  Pick a unique address on the same subnet as the
router.

There


should not be any need to alter your router configuration. It will not

care


if you use a static address.
With a static address can you 'ping' the router?
(ping xxx.xxx.xxx.xxx  where xxx.xxx.xxx.xxx is the IP address of the

router.


Ctl C will stop the pings)

Ok, setup the static IP address, tried to ping the router, and got this message: connect: Network is unreachable

Double check to make sure shorewall firewall is off in MCC? I.E. "everything " box is checked.

Oh, and also a firewall on any windows machines seems to be a problem for each machine that has it. So temporarily turn them off?


You shouldn't need to turn off any firewalls. Before you get carried away here, lets do some basic troubleshooting.

First, run "lsmod | grep 8139" to see is one of the 8139 modules is loaded and working. With 2 NICs using this driver, you should have seen eth0 and eth1 in ifconfig. But with firewire also showing up as a NIC in some setups, the output of ifconfig does not mean the correct module is loading. The "Network is unreachable" message indicates that the network setup isn't correct. You should always be able to ping the router from any machine connected to it. (It is possible to turn it off on a full router, but the ones used as firewalls for DLS/cable usualy don't offer that.)

Now, there are two drivers that work with the RTL8139 NIC, depending on the one you have. So if the driver isn't working, we can try the other one. They are 8139cp and 8139too. Both will work with DHCP, and that is the preferred way to set up the one connected to the router when it is configured to be a DHCP derver. The one that is not connected will need some special consideration later. Depending on how it will be used, or if it isn't used at all, we may want to configure it with a static IP, and make it not to be enabled.

The other complication with 2 NICs is determining witch one is eth0, and eth1. You can wast a lot of time troubleshooting things when you are working with the one that is not connected to the router, when you thing you are working with the one that is.

Another thing that wil help is to run "ifconfig -a", as this will show the interfaces that are down, as well as the ones that are up.

Mikkel
--

  Do not meddle in the affairs of dragons,
for you are crunchy and taste good with Ketchup!

____________________________________________________
Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com
____________________________________________________

Reply via email to