workgroup vs domain... ??

Don't change your DHCP setup. The DHCP on the server is a lot more robust than that of the Router/Firewall, but for ease of configuration don't add DHCP to the server. Contiune to use the DHCP on the Router.

I don't have a solution to offer.....but a suggestion. If you want people to answer the questions you ask....maybe you should award some points on the 10,000 questions you have asked!!! I just ignore your questions now.

Let me verify how I think you're presently setup and then give you a (semi-) easy solution.
You have either a DSL or Cable high-speed connection from an ISP providing a single public IP address. This IP address is aasigned to your router/firewall (a Linksys box maybe), which is in turn providing DSN info through DHCP.
The first decision you need to make is how bad do you want to set up a "private" (internal) domain.
In order to create a Win2K DC, you must understand and install Active Directory. An AD server requires a fixed IP address. In order to successfully run AD, AD must have access to a DNS server. Your ISP probably does not want to (or can't) provide the proper (necessary) DNS support for an AD domain.
So what you are left with is that in order to set up your own domain with Win2K (and AD), you will also have to setup a DNS server also. My suggestion is as follows (if you still want to set up your own internal domain:
1. Create a Win2K DC with a domain name along thelines of xyz.local (vs. xyz.com - this will be a "private" domain).
2. Install a DNS server with forward and reverse lookup zones for xyz.local domain. You should also set the DNS server to forward any requests for DNS info it can't answer to your ISP's DNS servers.
3. Install DHCP on the same server and set it up to serve your internal network. Disable the DHCP fnction on your router/firewall. The reason I say this is if the router provides DHCP service it is providing DNS info it is being fed by your ISP, not your internal network. While this wouldn't affect your clients abilities to access the internet, thay would have problems resolving internal DNS lookups.

Okay, I'm reposting this becase this is the 3rd time today the system has dumped my alias on a post.
Let me verify how I think you're presently setup and then give you a (semi-) easy solution.
You have either a DSL or Cable high-speed connection from an ISP providing a single public IP address. This IP address is aasigned to your router/firewall (a Linksys box maybe), which is in turn providing DSN info through DHCP.
The first decision you need to make is how bad do you want to set up a "private" (internal) domain.
In order to create a Win2K DC, you must understand and install Active Directory. An AD server requires a fixed IP address. In order to successfully run AD, AD must have access to a DNS server. Your ISP probably does not want to (or can't) provide the proper (necessary) DNS support for an AD domain.
So what you are left with is that in order to set up your own domain with Win2K (and AD), you will also have to setup a DNS server also. My suggestion is as follows (if you still want to set up your own internal domain:
1. Create a Win2K DC with a domain name along the lines of xyz.local (vs. xyz.com - this will be a "private" domain).
2. Install a DNS server with forward and reverse lookup zones for xyz.local domain. You should also set the DNS server to forward any requests for DNS info it can't answer to your ISP's DNS servers.
3. Install DHCP on the same server and set it up to serve your internal network. Disable the DHCP function on your router/firewall. The reason I say this is if the router provides DHCP service it is providing DNS info it is being fed by your ISP, not your internal network. While this wouldn't affect your clients abilities to access the internet, thay would have problemsresolving internal DNS lookups.