how do i disable dhcp server in windows 2000 internet connection sharing? in windows 98se there was a registry file on the CD, but i can't find that on the 2k CD. i'm sure there has to be a registry setting for it and i need to find out quickly because i have a running ISC DHCPD (OpenBSD 3.0) that will be doing the dhcp-serving and i don't want any new hosts to get confused so i need to find out quickly... please help!

Right click on the connection, then properties, then select TCP/IP, and set a manual address and subnet mask.

you don't understand. first off, what connection are you talking about? i can't put a manual ip on a ppp link, and there already is a static non-dhcp address on the ehternet. it is listening for dhcp broadcast requests and i need to disable this functionality. if it's on the same network as my other dhcp server than problems bare bound to arise

sterling, you didn't even think about his question. that's not what he asked. david, i don't really know. i heard somewhere that our "wonderful" overseeers at microsoft have decided to remove the ability to disable the DNS/DHCP functionality in Windows 2000 like you could in 98se (seems like something they'd force you to get "server" or "advanced server" or something to disable) and i do not believe that there is a registry hack for this, as that is what it was in 98se after all. i suggest this: get an extra NIC for your OpenBSD machine (or another) and a crossover cable. put the crossover cable directly in between the windows ics and the openbsd machine. the win will be 192.168.0.1 and the openbsd's second NIC will be something else (use "ifconfig -a" to check). then, simply set up a good nat-rules (/etc/nat.conf i think) file to map the connections. there are plenty of good examples on the net and you can modify a pf.conf to get a good clean solid firewall (OpenBSD's is after all the best in the business). this will give all clients on your network access to the network and your windows machine won't even be able to access them :) unless, of course, you decide to allow them access in nat.conf both ways, in which case be careful. when setting up your static and dynamic IPs in the OpenBSD ISC DHCPD i think it would be a good idea to move the addresses over to 172.16.0.x since that windows machine will force itself to 192.168.0.1 and the openbsd will get some 192.168.0.x for its second interface. good luck

After reading the above I decided to work this out because it was affecting my network as well. My only solution that is currently working very well is to install "Zone Alarm", not sure if it matters if you have the 'free' version or not, but this is how I did it: 1) Set up an environment were you have a hub/switch, your gateway and a normal client. 2) Install Zone Alarm on the gateway 3) Set it all up so it works NOTE: when ever a process tries to access the internal/external networks from the gateway it will ask to make sure this is permitted – you either accept/deny it. 4) Now get the client to obtain a new IP address 4a) in NT/win2k/XP Pro use at the command prompt: c:\>ipconfig /release c:\>ipconfig /renew 5) Go back to the gateway and you will see that it has trapped a service that is trying to access the internal network (this is the DHCP service), deny it access. (There is also an option to make it remember this so it will always deny it – select it). 6) Your gateway is now no longer doing DHCP on your internal network 7) Reconnect your gateway to the network and you will be able to use your other DHCP server! This worked for me first time so have fun.