Configuring DHCP on Win2K (exlcuding certain mac-adresses)

Hi all!

we are having some troubles with our dhcp-server on a win2k-dc.
We defined a scope of 12 adresses to be assigend via dhcp.

From time to time people don't get an adress from the server though
there should be enough free adresses (lease duration is set to an extra
short period of 3 hours).

If i check the current leases in the dhcp-admin-interface i see that 6
clients a got an ip. Therefore there should be 6 more adresses free to
be assigned. But the statistics of the dhcp-server say that there are no
free ips left.

Obviously some leases are not shown in the interface.

So i checked the dhcp-logs and found entries like these:

10,10/14/08,08:55:12,Zuweisen,192.76.154.31,,001FF35C0C93
10,10/14/08,09:05:09,Zuweisen,192.76.154.32,,001FF352E923

Is there a way to make these leases (with empty names) show up in the
dhcp-admin-interface too?
And is there way to easily flush all current adress-assignments?

Are there recommended practices for blocking (blacklisting) certain
mac-adresses from receiving an ip?

I further noticed, that a times there a leases for ras/dial-clients.
Does this mean a ras-connection was established or ist 'just' a
reservation by the server?

As we don't use remote access to the server is it safe to deactivate the
ras and routing-service or are there any other applications/services
(DNS, Exchange) relying on it?

Thanks for your help,
Andreas

"Andreas" <(E-Mail Removed)> wrote in message
news:48f70a39$0$11100$(E-Mail Removed)...
> As we don't use remote access to the server is it safe to deactivate the
> ras and routing-service or are there any other applications/services
> (DNS, Exchange) relying on it?

Either uninstall it or reduce the number of PPTP and L2TP Ports in the RRAS
Admin MMC.
RRAS will "collect" all the IP#s it needs to cover all of its ports ahead of
time and holds them in reserve,..that's the way RRAS has always worked. So
either reduce the number that it needs or uninstall it from Add/Remove
Programs--->Windows Components.

DHCP Scopes should include the FULL subnet range (x.x.x.1--x.x.x.254)
Then use Exclusions to limit the amount/range of addresses given out.
Then use Reservations for the few machine where the IP# should never
change,...but if you have a lot of those then forget the Reservations and
just include those in the Exclusions and manually/statically assign the
machine.

I usually do something similar to this,...it tends to be "fire & forget"
because I almost never have to touch it any more after that:

Full Subnet Range: 192.168.1.1 -- 192.168.1.254
Exclusion: 192.168.1.1--192.168.1.24 (Servers, Utility machines, network
devices)
Exclusion: 192.168.1.246 -- 192.168.1.254 (Printers, more network devices)
Reservations: from preferably *none* up to maybe 5 or 10 at most
Actual Host's DHCP Range: 192.168.1.25--192.168.1.245
Scope Options: Only things unique to each Scope
Server Options: Only things common across all Scopes
Superscopes: Never!,..ever, ever, ever. Their true use and need is
*extremely* rare.
Most people that try to use them use them
inappropriately due to
misunderstanding their purpose.