tritium

Windows computer do not assign themselves an IP automatically, that is the job of static IP setting or DHCP. I'm not aware of any other alternatives.

Those Windows XP computers will handle DHCP as a server, but only after adding that admin server from the control panel. Windows 98se will *not* act as a DHCP server. You will only need to setup the DHCP on 1 of your WinXP Pro computers.

In reality, Smackre, setting up a DHCP server will be not useful to your small network of computers. If you were using a leased internet connection line with a limited number of IP addresses and wanted to assign those on a "as needed" basis, then it might be worthwhile. Or, if you had a great need for security on your network and wanted to move computer IPs around to keep hackers on their toes, then sure, DHCP might be for you.

Based on our previous conversations about 802.11b, however, I am going to strongly advise against setting up DHCP on your network unless you achieve your aim via a router with a DHCP server built in. Not only would the setup be challenging for a novice network engineer, but the responsibilities of maintenance and troubleshooting may be more than you want to bite off.

There is nothing wrong with using static IPs and running the network exactly as it is setup now. If it ain't broken...

Edit: One substantial benefit of static IPs is knowing exactly where a problematic PC resides. If you map out your network on paper and write down which IP address cooresponds with which PC, then if your computers are ever hit with a network virus, tracing and locating the PC based on its network traffic will be much easier.

__________________
Blah.