Windows Server 2000/2003 Thread, IP Range - does it matter? in Technical; I'm playing with Windows Server 2003 R2 in a virtual machine and one of the first things I need to ...
5th July 2009, 02:52 PM #1
IP Range - does it matter?
I'm playing with Windows Server 2003 R2 in a virtual machine and one of the first things I need to configure for the DHCP role is an address range. I'm using a virtual internal network so I'm not worried about conflicts with anything but...what should I choose for a range and subnet mask?
I'm more of a programmer so subnet masks are lost on me - what's a good value?
IDG Tech News
5th July 2009, 02:58 PM #2
Use this to help - Online IP Subnet Calculator
You pick the subnet mask depending on how many addresses you would like. As long as your IP range is in the private range you can use just about anything.
2 Thanks to FN-GM:
bizzel (5th July 2009), nephilim (5th July 2009)
5th July 2009, 10:59 PM #3
It doesn't really matter, apart from the fact that it must be one of the three RFC1918 private ranges: 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16. I'd use 192.168, but make the mask a /24 (255.255.255.0) which you'll find is the Windows default anyway, then create a subnet by changing the third octet of the network: 192.168.x.0 so that you avoid colliding with your own network.
http://www.troutman.org/tech/linux_guides/subnet.html, taken with a pinch of salt now that CIDR is much more common that just simple subnetting.
Thanks to powdarrmonkey from:
5th July 2009, 11:40 PM #4
If its not going to connect to the internet you can use any network addres you want and any subnet mask you want, the only time it could affect you is if you later connected it to the internet and tried to connect to a host with an IP within the subnet you've chosen.
It is however good practice to stick with the designated private ranges.
6th July 2009, 08:32 AM #5
IF you are going to create a lab with a DHCP role and you are using VMware Workstation you should make sure to disable the VMware DHCP Server before proceding. This can be done in Manage Virtual Networks. Should save you some frustrations
6th July 2009, 10:28 AM #6
- Rep Power
One thing to take into account is VPN routing. e.g if you have a 192.168.10.0/24 you won't be able to VPN to another network with the same subnet. This can be an issue for remote users using VPN's.
By localzuk in forum Windows Server 2000/2003
Last Post: 10th June 2009, 01:31 AM
By techie08 in forum Windows Server 2000/2003
Last Post: 21st May 2009, 12:11 AM
By z4ydi in forum Network and Classroom Management
Last Post: 19th April 2008, 01:24 PM
By FN-GM in forum Courses and Training
Last Post: 29th August 2007, 01:21 PM
By FN-GM in forum General Chat
Last Post: 19th June 2007, 06:48 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)