|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.