I tried to configure my laptop to connect to the network at work.

I have following information from the admin:

IP: w.x.y.a
netmask: 255.255.255.0
gateway w.x.y.b
dns-server: w.x.1.1
w.x.1.5

I edited my /etc/network/interfaces like this:

In the resolv.conf I have:

When I try to connect (ifup eth0) I get no error (no feedback at all - normal?) but I cant ping any IP or domain and the browser gets stuck at "looking up some.domain..."

When I boot into Windows and enter the above values everything works fine.

route -n gives me:
which I find strange but I dont really understand the routing table..

Any ideas?

Stefan

Start with checking if you have an IP with 'ifconfig'
(You should have since there is no message - that is standard in Linux. When a command is succesful there is normally no output.)
With only one NIC you should be fine, but try two things:
1. Check DNS: In browser, don't use name but IP; like 216.109.117.207
This is IP for www.yahoo.com, if it works you have a DNS-problem.
2. In routing-table 0.0.0.0 should be OK for default gateway, but maybe you have to specify it:
# route add default eth0

All I can think of for now.

I tried the yahoo IP.
The browser says "Connection refused when attempting to contact"
and ping says "from <my ip> icmp_seq=2 destination host unreachable"
ifconfig shows my correct IP for eth0

??

I had the same problem with my wifi card. In your interfaces file, change

name Ethernet LAN card

to:

name eth0

As soon as I changed mine from "name Wireless LAN card" to "name ath0", it connected.

I hope this helps.

I just realized that eth1394 takes eth0 (dmesg told me that)! I guess that's the problem.
Now I cant make eth1394 let go eth0!
I tried removing eth1394 with modconf but on reboot it's loaded again!

What is the nice way to get rid of eth1394 or its alliance with eth0. And will eth0 work with my NIC afterwards?

Stefan

Sorry, wrong question answered....

try to set it manualy
ifconfig eth1394 down
ifconfig eth0 w.x.y.z
route add default gw your.gate.way.IP
echo "nameserver your.DNS.I.P" > /etc/resolv.conf
type ifconfig to see the result
if u have intenet try to fill in /etc/network/interfaces like in mine but with your correct data

iface eth0 inet static
address 192.168.0.7
netmask 255.255.255.0
broadcast 192.168.0.255
gateway 192.168.0.1
name Ethernet LAN card
network 192.168.0.0

Now that I know that the eth1394 module was the problem, it works when I do it manually.
But the behavior of the modules upon boot is not consistent. sometimes e100 binds to eth0 and eth1394 to eth1 and sometimes it is the other way round. I would like it to happen the same way on every reboot.
I added eth1394 to /etc/hotplug/blacklist so this one shouldn't load at all now, right? And therefor e100 will always be eth0, like I want it to.

thanks for the help

if you're using the debian 3.1 installer, it should have done the network configuration correctly and automatically. it may have decided to use eth1 as your lan interface. if so, you should have set up your network config for eth1 instead of eth0.