Hey all,

I am running internet connection sharing on my little LAN, and it works fine w/windows. However when I reboot one of my client machines into BeOSpe, it never seems to respond to the DHCP and I get 0.0.0.0 as an ip and can't ping anything. Any ideas?

Thanx,
Joey

Yes--dig through this forum for any of my posts regarding BeOS and DHCP. There's one post in particular in which I provided a lot of detailed information explaining revisions to DHCP and the possibility for compatibility issues. I also posted a link to a new third party DHCP client for BeOS.

Give us some information about your DHCP server. (Operating system, DHCP version and/or software providing the DHCP service, etc.)

Here’s that post:
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/

This was originally written addressing a different issue, but it may shed some light on DHCP peculiarities--and it looks (for the moment, at least) as if you're having a DHCP-related issue.

I hope this helps. If not, give us more information about your DHCP server and your network logical configuration.

Thanx for the info, I'm running ICS with a win2k professional machine that has 2 NICs in it. The BeOS machine is a client, and when I choose to obtain network settings automatically (or however they word it), I get the 0.0.0.0 . However, when I specify an IP addr. like 192.168.0.22, It work okay. Only problem now is that I can't resolve DNS names...

The link to Bluedot's 3rd party dhcp client brings me to their webpage, but they seem to have lost their ftp server as the files cannot be downloaded.

I'll keep playing around, but thanx for the info, much appreciated!

Joey

Make sure that you included the DNS server name and or IP into your beos
settings that are provided by your ISP at the network preferences. You may
also need to look for a file to edit and move to tell your box where to look.
I need to find it and repost. I thought it was something like network list or
something like that. lemme look again.

Are you talking about the hosts file?

That is it I think! Thanks Andrew.

I reread the info to and the answer may also be to just use a static ip and point the browser to the correct IP. Since the win box extra nic should be a static IP, one would need to have a port address along with the IP to the local lan Nic in the winbox?

I wouldn't use ICS. I would get a program from analogx called proxy and run it on the winbox whenever I wanted access on my beos machine. Go to cnet.com and get a free version of proxy. Config your beos browser to use proxy IP of the winbox and like port 6588.