DHCP server wont assign IP addresses

December 14, 2010 at 05:30:44
Specs: Windows 2003 R2 SP2, Intel Pentium 4 384MB RAM

I have a Windows 2003 R2 SP2 server that is running DHCP. The problem is that the DHCP server will only give IP addresses to some clients but not to all of them. When I try DHCP on some of the clients it doesnt work however when I put in the IP address i gave to them in the reservations section it works staticly but not dynamically. I have all the clients in the IP reservation table with the scope active and set to 192.168.2.2 to .100 and the server is set to static 192.168.2.14. How do i fix this?

See More: DHCP server wont assign IP addresses

Report •


#1
December 14, 2010 at 06:43:38

Why did you give the server a static IP within the DHCP range?

How do you know when a politician is lying? His mouth is moving.


Report •

#2
December 14, 2010 at 06:56:19

Well I tried to get a IP address using DHCP but it didnt work so i switched over to Static until i can get the DHCP issue fixed

Report •

#3
December 14, 2010 at 07:04:45

You missed my point. The server is supposed to be static but outside the DHCP range. For example: 192.168.2.101

How do you know when a politician is lying? His mouth is moving.


Report •

Related Solutions

#4
December 14, 2010 at 07:50:02

What guapo said!

Any device in the network that provides a service users will need regularly should have a static IP assigned manually by the admin.

Such devices would include any/all servers, printers, managed switches etc.

As pointed out, you assigned an IP within the DHCP scope. If you consider this, you'll understand why that could become a problem. It's a bad idea because that leaves the possibilty of DHCP trying to assign the same IP to another client causing a duplicate IP error. What if you reboot your server and while that's happening, DHCP assigns that same IP to another client? Suddenly nobody can find the server because that IP is in use on a client PC.

If you've never heard of the KISS principle you should google that acronym.

In keeping with the KISS principle I prefer not to mess with reservations or exclusions within DHCP. If you think about it, they're not necessary.

If you want a specific device to always get the same IP, statically assign it on the device.

What I do when setting up DHCP is define a scope for DHCP clients and then use IP's outside the scope for static assignments. Simple, neat and no chance of duplicate IP's.

As to your problem, you must have something misconfigured in your DHCP. I would recommend you wipe it out and start over. Here's how I like to setup DHCP:

Scope of IP's for clients: 192.168.2.100 to 192.168.2.199

The range of IP's from 192.168.2.99 I would keep for static assignments such as the server you mentioned. Now you could give it 192.168.2.14 and never have to worry about duplicate IP's.

I would keep the range 192.168.2.200 to 250 for use with network appliances and such.

Don't bother with exclusions or reservations. Set it up like I've described and reboot your DHCP clients and see if they don't get proper IP's now.

Report back with your results.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***


Report •


Ask Question