DHCP configuration required

[solvent]

I have 300 users in my company then how should i configure the DHCP server.
Should i create two scopes and merge the two scopes as superscope?
What should i do? Please help me.
Any suggestions would be appreciated

Thanks,

[Milton.J]

Use a Different IP Address Scheme with Subnetting, that might help you. Say you want to build a network with 300 users so you will need to use 300 ip address for user, 1 ip address for DHCP server, 2 ip address would be unusable i.e total 303 ip address of which 2 are unusasble [first is the network address and the last address would be the broadcast address]. using the subnet mask 255.255.255.0 will give the usable ip x.x.x.0 to x.x.x.255 from which you can use only 1 to 254. so you still need 46 ip addresses more. instead of splitting the network into two and using a router you can use a different subnet.
You can do as follows:

change your subnet [on DHCP server] to to 255.255.254.0. this subnet can has 512 ip address [single network] from x.x.0.0 to x.x.1.255 out of which you cannot use x.x.0.0, x.x.1.0, x.x.0.255 and x.x.1.255. so total you can use 508 IP address. problem solved. Give your DHCP server the first ip x.x.0.1 and subnet 255.255.254.0. thats all...!
all the best!

[SecRecy]

Configuring the DHCP Service Active Directory domain in Windows 2000

After you install and start the DHCP service, you must create a scope (a range of valid IP addresses that are available for lease to the DHCP clients). Each DHCP server in your environment should have at least one scope that does not overlap with any other DHCP server scope in your environment. In Windows 2000, DHCP servers within an Active Directory domain environment must be authorized to prevent rogue DHCP servers from coming online and authorizing a DHCP Server.

When you install and configure the DHCP service on a domain controller, the server is typically authorized the first time that you add the server to the DHCP console. However, when you install and configure the DHCP service on a member server, you need to authorize the DHCP server.

Note A stand-alone DHCP server cannot be authorized against an existing Windows Active Directory.

To authorize a DHCP server:

1. Click Start, click Programs, click Administrative Tools, and then click DHCP.

Note You must be logged on to the server with an account that is a member of the Enterprise Administrators group.

2. In the console tree of the DHCP snap-in, select the new DHCP server. If there is a red arrow in the bottom-right corner of the server object, the server has not yet been authorized.

3. Right-click the server, and then click Authorize.

4. After a few moments, right-click the server again and then click Refresh. The server should display a green arrow in the bottom-right corner to indicate that the server has been authorized.

To create a new scope:


1. Click Start, click Programs, point to Administrative Tools, and then click DHCP.


Note In the console tree, select the DHCP server on which you want to create the new DHCP scope.

2. Right-click the server, and then click New Scope. In the New Scope Wizard, click Next, and then type a name and description for the scope. This can be any name that you choose, but it should be descriptive enough to identify the purpose of the scope on your network. For example, you might use Administration Building Client Addresses.

3. Type the range of addresses that can be leased as part of this scope, for example, a starting IP address of 192.168.100.1 to an ending address of 192.168.100.100. Because these addresses are given to clients, they should all be valid addresses for your network and not currently in use. If you want to use a different subnet mask, type the new subnet mask. Click Next.

4. Type any IP addresses that you want to exclude from the range you entered. This includes any addresses that may have already been statically assigned to various computers in your organization. Click Next.

5. Type the number of days, hours, and minutes before an IP address lease from this scope expires. This determines the length of time that a client can hold a leased address without renewing it. Click Next to select Yes, I want to configure these options now, and then extend the wizard to include settings for the most common DHCP options. Click Next.

6. Type the IP address for the default gateway that should be used by clients that obtain an IP address from this scope. Click Add to place the default gateway address into the list, and then click Next.

Note When DNS servers already exist on your network, type your organization's domain name in Parent domain. Type the name of your DNS server, and then click Resolve to ensure that your DHCP server can contact the DNS server and determine its address. Then click Add to include that server in the list of DNS servers that are assigned to the DHCP clients. Click Next.
7. Click Yes, I want to activate this scope now, to activate the scope and allow clients to obtain leases from it, and then click Next. Click Finish.

[SecRecy]

Configure a DHCP Server in a Workgroup in Windows Server 2003

How to Configure the DHCP Service
After you have installed the DHCP service and started it, you must create a scope, which is a range of valid IP addresses that are available for lease to the DHCP client computers on the network. Microsoft recommends that each DHCP server in your environment have at least one scope that does not overlap with any other DHCP server scope in your environment. In Windows Server 2003, DHCP servers in an Active Directory-based domain must be authorized to prevent rogue DHCP servers from coming online. Any Windows Server 2003 DHCP Server that determines itself to be unauthorized will not manage clients.

How to Create a New Scope

1. Click Start, point to Programs, point to Administrative Tools, and then click DHCP.

2. In the console tree, right-click the DHCP server on which you want to create the new DHCP scope, and then click New Scope.

3. In the New Scope Wizard, click Next, and then type a name and description for the scope. This can be any name that you want, but it should be descriptive enough so that you can identify the purpose of the scope on your network (for example, you can use a name such as "Administration Building Client Addresses"). Click Next.

4. Type the range of addresses that can be leased as part of this scope (for example, use a range of IP addresses from a starting IP address of 192.168.100.1 to an ending address of 192.168.100.100). Because these addresses are given to clients, they must all be valid addresses for your network and not currently in use. If you want to use a different subnet mask, type the new subnet mask. Click Next.

5. Type any IP addresses that you want to exclude from the range that you entered. This includes any addresses in the range described in step 4 that may have already been statically assigned to various computers in your organization. Typically, domain controllers, Web servers, DHCP servers, Domain Name System (DNS) servers, and other servers, have statically assigned IP addresses. Click Next.

6. Type the number of days, hours, and minutes before an IP address lease from this scope expires. This determines how long a client can hold a leased address without renewing it. Click Next, and then click Yes, I want to configure these options now to extend the wizard to include settings for the most common DHCP options. Click Next.

7. Type the IP address for the default gateway that should be used by clients that obtain an IP address from this scope. Click Add to add the default gateway address in the list, and then click Next.

8. If you are using DNS servers on your network, type your organization's domain name in the Parent domain box. Type the name of your DNS server, and then click Resolve to make sure that your DHCP server can contact the DNS server and determine its address. Click Add to include that server in the list of DNS servers that are assigned to the DHCP clients. Click Next, and then follow the same steps if you are using a Windows Internet Naming Service (WINS) server, by adding its name and IP address. Click Next.

9. Click Yes, I want to activate this scope now to activate the scope and allow clients to obtain leases from it, and then click Next.

10. Click Finish.

11. In the console tree, click the server name, and then click Authorize on the Action menu.

Troubleshooting
The following sections explain how to troubleshoot some of the issues that you may experience when you try to install and configure a Windows Server 2003-based DHCP server in a workgroup.

Clients Cannot Obtain an IP Address
If a DHCP client does not have a configured IP address, this typically indicates that the client was not able to contact a DHCP server. This can be caused by a network problem, or because the DHCP server is unavailable. If the DHCP server started and other clients can obtain valid addresses, verify that the client has a valid network connection and that all the related client hardware devices (including cables and network adapters) are working properly.

The DHCP Server Is Unavailable
If a DHCP server does not provide leased addresses to clients, it is frequently because the DHCP service did not start. If this is the case, the server may not be authorized to operate on the network. If you were previously able to start the DHCP service, but it has since stopped, use Event Viewer to check the System log for any entries that may explain why you cannot start the DHCP service.

To restart the DHCP service:

1. Click Start, and then click Run.
2. Type cmd, and then press ENTER.
3. Type net start dhcpserver, and then press ENTER.

[solvent]

Thank you very much Milton.J.

If i do subnetting as you said then don't we require the router?

regards,

[Milton.J]

If we use a larger subnet for a single network as i explained above, we won't require router because the whole larger network would be a one single network. router is used only if we use two different network. all the best!

[solvent]

Ok, thank you Milton .

Milton, If 300 employees are placed in two floors (1st floor 150 and 2nd floor 150).
Than how do i setup the network?

regards,

[Milton.J]

The procedure isn't affected if you use 300 computer on the same floor or on different floor [Physical location]. Configuration is only a logical map. don't worry have fun, stay at peace...!