I have a "very second hand" Dell PII as a proxy, running SuSE 9.0. Now I want to make it dual homed using the built-in eth as well as the PCI one, in order to use ADSL. I can configure the built-in one, but it doesn't seem to respond (ping doesn't work). According to the LEDs there is contact at both ends, but if I try to make it a DHCP client it won't play. Is there a way to dig a bit deeper to see what's happening (or not as the case may be), or can I safely conclude that it is dud?

An alternative is to use a second PCI eth card, but that leads me to the second stumbing block. I have only two slots with the current smaller PCI footprint, and the other is occupied by the graphics card. (The shops don't carry the older type.) Trying to use the built-in one, guess what, it's dead. I can configure it, but the monitor just says "no signal" and shuts down into power save mode.

Any suggestions most welcome.

Is the onboard nic enabled in the bios? What does lspci -v and dmesg say about the nic? Have you checked all cables, connections, etc. to ensure they are good?
good luck.

The on-board monito output suddenly decided to play, so all is well in this department.

So it's all sorted or just the video?
good luck.

I put another network card in the slot vacated by the video card.

But as shown by another thread under networking I still have problems with the DHCP client.

Are you running a firewall? What is the output of the following commands?

ifconfig -a

route -n

You might try a different client as well.
good luck.

This is the thread: http://www.linuxquestions.org/questi...hreadid=262944

The ifconfig confirms that there is no inet adr. An old laptop with suse 9.0 as well behaves the same way, but connecting (wired) to the router works, it accepts a dhcp address from the router.

This is what ifconfig and route says:

eth0 Link encap:Ethernet HWaddr 00:01:02:9D:18:63
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::201:2ff:fe9d:1863/64 Scope:Link
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9462 errors:0 dropped:0 overruns:0 frame:0
TX packets:9171 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1369302 (1.3 Mb) TX bytes:1606315 (1.5 Mb)
Interrupt:10 Base address:0xdc00

eth1 Link encap:Ethernet HWaddr 00:C0:4F:95:A2:32
inet6 addr: fe80::2c0:4fff:fe95:a232/64 Scope:Link
UP BROADCAST NOTRAILERS MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:2024 errors:0 dropped:0 overruns:0 carrier:2024
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:1130268 (1.0 Mb)
Interrupt:11 Base address:0xdc80

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:493 errors:0 dropped:0 overruns:0 frame:0
TX packets:493 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:50990 (49.7 Kb) TX bytes:50990 (49.7 Kb)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

ft-gw1:/home/squiduser # route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 192.168.1.2 0.0.0.0 UG 0 0 0 eth0

The firewall is stopped for the time being.

I got the laptop to work, and furthermore, dhcp doesn't work on any of the interfaces of the proxy.

I'll continue in the previously mentioned thread though, to keep the topic in the relevant forum.

I'll follow up there, no need to make further posts here.
good luck.

I'm back in this forum

I've tried to configure under Win98, getting generally speaking the same behaviour. So is it a HW or BIOS problem?

I detect all three interfaces, but only one will work. It drives me nuts!

This has gotten a bit hard to follow. I'll make any further posts in the other thread.
good luck.