*** From dhcp-server -- To unsubscribe, see the end of this message. ***
At 12:08 26.04.99 -0400, Eloy A. Paris wrote:
>----- Forwarded message from Sean Perry <[EMAIL PROTECTED]> -----
> [...] one of the NT servers in the office keeps asking for IPs and dhcp-beta
>assigns one, then another, and so on. What is even more odd is that the MAC
>address shown is not a normal mac address. Below are log snippets.
>
>Apr 24 10:50:34 foo usr/sbin/dhcpd: Internet Software Consortium DHCP Server
>V2.0b1pl26
>Apr 24 10:57:08 foo usr/sbin/dhcpd: DHCPREQUEST for 209.219.162.88 from
>52:41:53:20:90:e6:7f:a0:bb:8d:be:01:01:00:00:00 via eth0
>Apr 24 10:57:08 foo usr/sbin/dhcpd: DHCPACK on 209.219.162.88 to
>52:41:53:20:90:e6:7f:a0:bb:8d:be:01:01:00:00:00 via eth0
>Apr 24 10:59:08 foo usr/sbin/dhcpd: DHCPREQUEST for 209.219.162.89 from
>52:41:53:20:90:e6:7f:a0:bb:8d:be:01:02:00:00:00 via eth0
>Apr 24 10:59:08 foo usr/sbin/dhcpd: DHCPACK on 209.219.162.89 to
>52:41:53:20:90:e6:7f:a0:bb:8d:be:01:02:00:00:00 via eth0
>
>The range is 85-89. I up'ed the lease time to an hour so it would happen less
>frequently (makes sense anyway).
>
>I read the dhcp conf man page and could see no way to say "ignore this
>machine", besides the MAC address is not valid, at least as far as I can see.
That's the well-known "Windows NT RAS Server" problem. If the RAS Server
service is enabled on a Windows NT machine, it will by default request an
IP address lease for each of its RAS ports under a fake MAC address starting
with 52:41:53:20 (that's ASCII for "RAS "). What's worse, at least before
SP4 the server would actually use a different MAC address after each reboot,
thereby eating up your address pool.
You have these options:
a) Grin and bear it. :-)
b) Configure the RAS server to use a fixed address pool instead of
requesting addresses via DHCP.
c) Disable the RAS server service on the NT server. (Should it be
there, anyway?)
d) Patch dhcp-2.0b1 to ignore requests with invalid MAC addresses.
There's a patch for that floating around on this list. The RAS
server will be effectively disabled by this, too, however it will
go on and on nagging your DHCP server for a lease.
e) Use dhcp-3.0-alpha which has very nice new features to handle this
kind of problem, but, as its name says, is still an alpha version.
--
Tilman Schmidt E-Mail: [EMAIL PROTECTED] (office)
Sema Group Koeln, Germany [EMAIL PROTECTED] (private)
"newfs leaves the filesystem in a well known state (empty)."
- Henrik Nordstrom
------------------------------------------------------------------------------
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
------------------------------------------------------------------------------
