Setting up a domain on a server

Hi

Some things to consider first: by no means an exhaustive list

What's your old domain running on ie which server operating system and what's the os on your new server?
Do you want your new server to be part of the existing domain and why ie what do you want it do do?
Is the new server a replacement of the old server? Will it be at the same site?
Do you want to create a new and separate domain independent of the old one?
How many users do you have and have you considered how this will affect them,

Usually I think it's best to run dhcp from a server - os's like 2000 server and 2003 server have dhcp servers that are very configurable,

Let us know

Deb :))

Old Server: Windows Server 2000
New Server: Windows Server 2003

The new server is replacing the old server that is slow and is running out of room.  I just want the new server to function the same way the old on did.  What type of router do I need in order for the server to act as the DCHP server?  Is a linkys router ie ok?
There will be about 16 users for the new server.

Hi

I would have thought your router should be fine, although routers aren't my thing particularly. Are you running any applications on your old server ie exchange or other mail server/ web server /apps etc? Is it file serving or print serving or both?

It's always best with these things to come up with a researched plan, particularly if you need your users to keep working in the meantime with minimum disruption. Are you running dhcp itself on your 2000 server (sounds like it's maybe on your router and not working)? The whole point of dhcp is that you shouldn't have to do anything else - the dhcp should hand out all the necessary info to the clients ie IP, DNS/WiNS server addresses, gateway address etc. What are you using your linksys router to do?

This is a big question really that you're asking - you might need to break it down a bit,

Deb :))

Ok, the server will be a mail, print, exchange, and file server.  The old server has an Asante router and everytime you need to add a computer onto the network to gain access to the internet. I don't think the old server is handling the DHCP, I think the router is.  You have to manually enter the IP and DNS numbers.   I was wondering for the NEW server, if I could just buy a Linkys router and that way the IP and DNS would just configure automatically.  

So you're running exchange server? Which version and are you wanting to move this across? This makes a big difference depending on what you're trying to achieve. Also is any of this lot sbs - small business server?

In relation to dhcp you can configure it to run from either your router if supported on it, or from your server. I'd choose the server every time - it integrates much better and isn't that hard to set up. Nothing really configures automatically - you always have to give it the info at some point - much better if it's just once though!

You can setup dhcp on your server so that every client or even device that requires it will automatically get it's own unique IP address, default gateway ie router ip, dns servers, wins server automatically. You shouldn't then even have to add these when adding a new pc for example to the domain. Default tcp/ip settings on new 2000 or XP Pro installs are usually set for dhcp, which will be pulled automatically from your server once it's setup.

Deb :))

The new server will have Microsoft Exchange 2003 on it, the old sever doesn't have exchange server.  How do I set up dhcp on my new server, can I use a simple linkys wireless router? We have a DSL connection.