Yes it's mostly anoying . i've finaly got my Compaq armada up'n running with BeOS but now the only thing i cant get right is the network , I have a "Apollo 10/100M Fast ethernet card" pcmcia , should be NE2000 compatible ,, ohh and yes i'm connected to the internet via a broadband connection that supplyes a dhcp for the ip's and so on .. so i put in my card and Be seams to find it right away , i try the dhcp-option .. but No! .. wont work , Well well i think and checks my other computers gateway/dns and so on .. so i give the armada a static ip. Now i can ping myself + all the other computers in the apartment and also use simple things like ftp/telnet and so on .. but here comes the strange thing ,, it only works in my apartment not if i try on an external ip like for example my neighbor. and the only thing thats betwean us is my switch in the apartment and the main-switch in the house.. Cant figure out what to do so please help!! :/

If you ping youself that ain't much but since you can ping with a static IP you are working so far.\ Set up an static IP at your neighbors and then I feel sure it will work. (warn that it may screw up his computer though,,, ya never know so don't do it) You are not getting DCHP services from your ISP. Some just don't work with beos for many reasons. We would need to learn more about your gateway. Did you fill in all the blanks on you network setup? Fill in every block you can including name servers and host name. Use

If you ping youself that ain't much but since you can ping with a static IP you are working so far.\ Set up an static IP at your neighbors and then I feel sure it will work. (warn that it may screw up his computer though,,, ya never know so don't do it) You are not getting DCHP services from your ISP. Some just don't work with beos for many reasons. We would need to learn more about your gateway. Did you fill in all the blanks on you network setup? Fill in every block you can including name servers and host name. Use any name if you don't know it.

Be aware that the BeOS DHCP client does not support some of the newer features defined in RFC2131--in particular, features that request certain client information. (Several older DHCP clients, written to conform to RFC 1541 standards, don't support some of these newer options. Windows NT's DHCP client wasn't even fully RFC2131 compliant until Service Pack 5.) Many ISPs use an optional feature added in RFC2131 to try to verify that the system making the DHCP request actually has an account provisioned. Their DHCP servers are configured to refuse to fulfill a DHCP request if your DHCP client doesn't support this. AT&T Broadband used to do this, before they started using MAC addresses to verify subscriptions. You might never get networking to work under BeOS using DHCP with your particular ISP if they're requiring your machine to respond to a query before fulfilling a DHCP request. If that happens to be the case, you'll have to assign your IP address manually. There is a company called Blue Dot that has a DHCP client for BeOS that's supposed to be almost completely RFC2131 compliant. In case you're interested, here's the URL: http://www.bluedot.68k.org/bluedot/dhcp/