[suse 9.1 Pro] Install

As I'm also a newbie and looked where I could but don't see the solution at this point. Now I know how people feel when they have a Windows related question!#@.
As I installed 9.1 Pro I couldn't connect for updating and have no internet connection at all. I have 2 nic's, 1 DECchip 21041 and 1 8139 from realtek. After installation of the software I configured both nic's with DHCP without any luck, the system recognises the nic's but in the boot log is stated that no interface is active (yet)????
Which steps do I have to take with or after install. I opened port 139 in the firewall, do I have to join more user groups??

At this moment I can't post any logs because of no connection.

Yea, join more user groups. I think I had to join 6 before my network would work in 9.1. In 9.0, it was only 4, so it caused me a lot of problems until I figured it out.

Seriously, in YaST, Network Devices -> Network Card, do the nics show as configured?

Nero,
2 NIC's
You must have some recognition problems.
Start with removing one and test your connection with one.

Now, all depends on your hardware setup
SuSE 9.1 per default thinks you are connection through xDSL (ppoe).
Only one card should connect through ppoe and be dedicated for.
Identifying the card is tricky, so, first test wit only one NIC installed.

Better would be for you to install a hardware router (I suppose so, as if you install 2 NIC's your intention is to use your Linux box as gateway/firewall/DHCP server? Don't.)

Am discussing this (and losing patience ) on
http://forums.suselinuxsupport.de/in...showtopic=4885

I will take out 1 nic in the first place to check what will happen, maybe as you mentioned a conflict. Then I will try again to set-up the network.
Keep you posted

The Realtek card I would say is your best chance first. I have used that card many times and should be the easiest to get working.

Agree on the Realtek.

edited:
no way to configure a NIC under Yast without fisrt configuring the cards. My bad.

I've noticed that after an install, it detects the cards and sets them up for DHCP. Sometimes that works correctly and sometimes it doesn't. Try lvlamb's suggestion and reconfigure the card. Try giving it a static IP, see if that helps.

69, I beg to disagree.
Only use statics on very small networks when yo know what you are doing.
Always use dynamics,
either those provided by your ISP, your router, or the Linux router. Among the pool of Internet reserved private LAN addresses, there still are 3 domains. (RFC 1918)
10.*.*.*
172.16.*.*
192.168.*.*
Enough * (stars) to confuse any protocol.
Let one, and only one DHCP server atrribute an address,
let (most do) setup programs negociate a dynamic address.

Now, if you connect to your ISP, another address comes into play, your Internet (mostly dynamic) address. Which must remain dynamic at most ISP providers.
A card can have several dynamic addresses, each linked to a service.
Unfortunately, when you attribute a static address to a NIC, that NC will only reply when addressed to the static address, which usually is a local address, by design reserved to the local LAN and not addressable from the outside world.
In my case, I have on my NIC, a 192.168.*.* address allocated by my router, my ISP recognises me as 195.*.*.* (his router) whereas the outside world would ping me through the 80.*.*.* pool of my ISP (the router through which he accesses the highway). Don't mess with statics.

Further, would you change a NIC, a static address would not be recognized anymore, (DHCP is a two columns table with an Ethernet address ddd.ddd.ddd.ddd against a MAC address hh:hh:hh:hh:hh:hh).

I keep repeating, best solution is to have a black box (router/firewall/DHCP), some even integrate the modem part and bridge/hub functions. Current prices of that kind of hardware makes the fine tuning any software solution a pure loss of time.

I like static only unless dealing with major companies. I think it is usless to run a DHCP Lan on a home network personally. On top of that my ISP only gives static IP's which makes me even happier.

As for the OP, if there is a router between the broadband modem and the computer, an easy way to tell if you are having DHCP issues is to give the card a static IP.