Hi,
As indicated above, you need to use virtual hosts or, more specifically, name-based virtual hosts. The following are examples of three different domains (as indicated by the ServerName directive) all of which are running on a single IP address. You would put something like this in your httpd.conf. The DocumentRoot directives define the physical location of the content - obviously you would use your W2K locations but you should get the idea.
NameVirtualHost 172.16.16.1:80
<VirtualHost 172.16.16.1>
UseCanonicalname off
ServerName vhost1.mydomain.com
DocumentRoot /var/
</VirtualHost>
<VirtualHost 172.16.16.1>
UseCanonicalname off
ServerName vhost2.mydomain.com
DocumentRoot /var/
</VirtualHost>
<VirtualHost 172.16.16.1>
UseCanonicalname off
ServerName
DocumentRoot /var/
</VirtualHost>
All you need to do is get all the sites to resolve to you IP address via DNS. (172.16.16.1 above is an example of the internet ip address on which apache is listening - if you prefer you can substitute '*' which is supposed to listen on all interfaces) See -->
Also, if you are going to host lots of sites there is a syntax that can be used to dynamically generate elements of the virtual host (e.g. directory path) based on manipulation of the content of the http header, i.e. mass virtual hosts -->
.
To some extent you can get round the problem RhythmAce described above by setting your default up in a 'dummy' virtual host container that is first in the list - known as the 'primary virtual host'. If a request is received that doesn't match any of the defined vhosts, apache chooses the first one by default.
Hope this helps