Click here for important information about

static IP for a network

Seagate Barracuda ata iv 80gb hard drive
March 23, 2010 at 20:02:01
Specs: Windows XP

I got a network of one server (using server 2003) and 2 workstations (winXP). The modem is Linksys (also wireless router). Do I need to manually set static IP for all PCs or let the DHCP of router does it automatically? Any idea of which solution is better?


See More: static IP for a network

March 23, 2010 at 22:11:05

Since you are using just a simple setup set the server a static ip address, define the it in the TCP/IP properties of your NIC. Then allow the router to assign IP's to the workstations. If you are looking to expand in the future install DHCP as a server role in server 2003 and go though and configure that then disable the DHCP on the router, but since your set up if small I would keep it at the router level, because if you ever restarted the server with the DHCP being managed on server side it will loose all connectivity to the workstations even internet, even know the modem is hooked to router. Due to the simple fact that the workstation with out an IP will not know where to talk to, to get out onto the net. via Default Gateway.

Any questions e-mail me

Report •

March 24, 2010 at 07:36:02
Anything that's going to be providing a service should have a static IP. This includes servers as well as network printers. So yes, statically assign your server an IP.

Check the DHCP configuration on your router and pick an IP that is outside of your DHCP Scope. The default scope on most SOHO Routers is something like .100 to .199 so you should have plenty of IP's to choose from.

I would recommend using DHCP on the clients. I would leave DHCP running on your router. There's no need to move it to your server now or later. You definitely don't want to try and use DHCP on both at the same time.

I'm not sure why ddennis02 would advise moving the DHCP role to your server but here's why I say not to bother.

DHCP is DHCP and there's no advantage to running it on the server over running it on the router. Any roles your server isn't performing means it has that much more (in terms of performance) to offer to the ones it is.


If you don't mind me saying, your post is confusing. You tell the OP to move it and then say don't. Better you hadn't brought it up at all as you're just making a simple thing complex and it's been my experience in 15+ years of working in IT that one should always apply the KISS principle.

Report •

March 25, 2010 at 04:11:22
Thanks very much, curt R

Report •
Related Solutions

Ask Question