Windows

From what you've said above your server is addressed within the range specified to be handed out. Now I'm not 100% certain here, but I'd make the range of addresses run from 200.150.170.250 to 200.150.170.254 as my first approach. I do know that NT support s subnetting, they'd have to. Besides the info handed out by DHCP should go out automatically. I think because you've included the server's address in your assigned ranges that you've managed to perplex the DHCP server.

Unless you have more than 254 devices (PC's, Servers, Network Printers, etc.), there's no need to subnet. Simply set the scope for the entire range (200.150.170.1 to 200.150.170.254) with the default subnet mask (255.255.255.0) and exclude the rangeyou don't want to dynamically assign.

Sounds like your node types are not setup for to handle subnetting. Set your Node types to 4 (mixed)in the Global options of your DHCP scope. This makes them cross compatible with all IP network configurations. Very handy when you travel to different offices with different IP configurations. This also works with low speed connections between the DHCP client and DHCP Server. Also Try using SP5. I was unable to subnet with SP3, SP4 but I did not try SP6.

The problem that you have is that you are trying to assign invalid IP Addresses for the Subnet Mask that you are using.

If you set your scope to be:

200.150.170.241 - 200.150.170.246

then it should work. This is your last IP address range with the subnet you are specifying.
If you require a full list of addresses then email me and I'll forward them to you.

Answer #4 is the ONLY correct answer here!!!!!

You can't use a subnet mask lower than the IP address range. You should read a book on subnet masking before you attempt it or hire a professional.

Everyone else that answered this question, fails their TCP/IP exam for today.

D. Stewart MCSE