IP Address for Small Office Server

Microsoft Windows server standard 2008 -...
June 16, 2010 at 17:36:51
Specs: Windows XP
We have an old server running 7 stations and Windows Server 2000. I bought a new Dell T110 with Server Foundations 2008 and want to just recreate the network from scratch. I really don't want to close down the old server until I get the new one at least configured. Hope to move over the seven stations during a weekend.

I ran DCPROMO to detup the new domain controller, but I am stumped on a simple question about the TCP/IP address for the new server. I cannot use the existing IP address of the server, since it is still running. I also plan to change the FQDN.

Do I need to talk to our ISP and reserve a small block of IPs? Just not sure how to do this. I don't see any other problems in getting the new network going.

See More: IP Address for Small Office Server

Report •

June 16, 2010 at 20:43:29
first of all you should be behind a router which means you use private ip not public ip [like from your isp]

Your lan [the private side of the router] typically uses a 192.168.x.y ip range
x=1 or 0

Lets start with what your present server is using for an ip address. Do you know how to get this?

Report •

June 16, 2010 at 22:11:08
Yes, I can get the IP address of the server by going to the CMD prompt and run IPCONFIG /ALL.

I have a SMC8014W-G "Broadband Wireless Gateway" that Time Warner Provided. It is listed at 4 port cable modem.

Current setup is:
IP Address
Subnet Mask
Defalt Gatway

Doman name is abc.local, where abc is the domain. The new Server 2008 domain will be def.local, where def is the new domain name.

I am thinking that I will be able to use this same configuration numbers on the new server because it has a different Domain Name. Is this correct?

Honestly, I don't see how the server actually finds the router, since there is no where to actually put the ip address of the router (public address) in the setup. Or is there?

I also noticed that IPCONFIG shows:
IP Routing enabled.....NO.

Does this setting need attention?

Report •

June 17, 2010 at 06:59:16
routing = no is correct.

servers should have a static ip. You can not give the same ip address to a different server. In your case I would suggest you use for the new server. This is at the far end of the range and should not cause a ip conflict if the workstations/printers are getting dhcp ips.

Report •

Related Solutions

June 17, 2010 at 07:21:39
Sounds like good advice on setting the the new server to .254. I did look at the assignments and I saw nothing above .80

I'm not sure I have a static IP address set in the system. So, I am not trying to get that ironed out. I understand the static IP address for the router should be the default gateway.

On last question, if you don't mind. Currently, the SMC router is connected to a Dell 24-port hub, and the server is connected to the Gigabit port on the hub. All work stations and printers are also diretly connected to the hub. Should I have 2 NICs in the server and connect Server NIC#1 directly to the router, and connect server NIC #2 to the Dell hub? I am looking for the best performance I can get in my setup as I have several employees accessing insurance companies on the internet all day long. Thanks.


Report •

June 17, 2010 at 09:08:34
Do not dual home your server. This causes multiple problems if not configured just right. There is no need.

Internet isn't going thru the server so you want to look at optimizing your internet connection not the server connection.

Can you post the results of an ipconfig /all from the server for review. I want to check your DNS settings as these are important for configuring 2008

Servers should have static ips. Your router configuration works so I would leave it alone for now. Might want to web search on ip addressing and using/configuring dhcp. You would be advised to set the routers dhcp scope to something smaller than the entire subnet. Something like 2-100 for expample.

Report •

June 17, 2010 at 16:10:52
Well, making some progress for a novice. Was able to finish configuring the domain controller with the IPs as mentioned above. Can access the internet. Installed printer, file sharing, DHCP, and DNS. Detecting network device settings drove me nuts for a couple hours, but got it set up, and was able to get the brother network printer to function properly. The scope is set pretty big, used 1-250. I can cut that down.

Called Time Warner and I do not have a static IP, it is currently dynamic ... and to upgrade will cost me extra!?? What!?

I have set up workstations on the DC in Server 2000, so I will have to see how it is in Server 2008.

Wanderer, thanks for the feedback. Your input was very helpful. Have to put this project to rest for several days due to a trip... but I'll be back with more results.

Report •

June 18, 2010 at 08:18:35
You are confusing static ip on the lan and static ip on the wan. You do not need static ip on the wan [time warner] unless you are planning on hosting a web site or games.

I suspect your server/workstation dns is not setup correctly and you will have issues with joining the new domain because of it.

Still looking for that post of the servers ipconfig /all for review

Report •

Ask Question