*** From dhcp-server -- To unsubscribe, see the end of this message. ***
If you look at the client identifier on that client, it starts with:
52:41:53:20, or "RAS ". It's a Microsoft Windows NT Server running
Remote Access Services, which is a dialup modem service. It grabs an
IP address for a dialup modem in advance of actually getting a call,
and never properly releases it, so it's possible for the thing to
consume a lot of addresses if it's rebooted a lot.
If there aren't supposed to be RAS servers on your network, the thing
to do is to go track them down and shut them off. If there are,
there's not much you can do except give them short leases and just
deal with all the log messages.
In 2.0 there's no way to exclude a client based on a pattern in the
MAC address. You could write a host declaration for that particular
client identifier and put "deny booting" in it, but the RAS server
will just choose another.
In 3.0, you can refuse to give addresses to RAS servers with the
following statement:
if substring (option dhcp-client-identifier, 0, 3) = "RAS " {
deny booting;
}
You can also assign RAS servers IP addresses from an unroutable
subnet that you make up, and give them really long leases, and that
will shut them up. This is done with classing and address pools.
It sounds like you aren't in a position to recommend 3.0, though, so
this may not matter to you. :'(
_MelloN_
------------------------------------------------------------------------------
To unsubscribe from this list, please visit http://www.fugue.com/dhcp/lists
If you are without web access, or if you are having trouble with the web page,
please send mail to [EMAIL PROTECTED] Please try to use the web
page first - it will take a long time for your request to be processed by hand.
Archives for this mailing list are available at
http://www.webnology.com/list-archives/dhcp/dhcp-server
------------------------------------------------------------------------------
