The list of DHCP options that Microsoft clients can accept is fairly small:
DNS, WINS (NBNS), Node Type, Router, NetBIOS Scope ID
Any other options sent will generate that error. I am not familiar with
the DHCP server you are using, but I would suggest looking at the config to
see if you can change the way it is offering the options.
--
Jerry Camel
jca...@msn.com
Progression Incorporated
Colorado Springs, CO
(719) 573-4138
Silke Müller <si...@kermit.wiesbaden.ruv.de> wrote in article
<01bc86c5$40bc1ac0$0b22e8c3@rq00099>...
> Hi,
> we have some problems regarding our Unix-based DHCP Server (Cisco
> DNS/DHCP-Manager) and NT4.0-Workstations.
> The DHCP Server locates the appropriate IP-Adress by scanning its data
base
> for the client identifier (first scan) and MAC address (second scan)
> We want it to scan for the MAC address. If the server doesnt't find the
> client identifier, the CID will be sent back to the client (DHCP option
61
> in RFC1533).
> And that's the problem: the IP address the client receives ist correct,
> but the
> Event Monitor shows an alert (' Could not get an IP address', anything
like
> that)
> and some warnings ('Unknown option: 61')
> The client has got all information needed from the DHCP-server (ipconfig
> shows all
> options I wanted the client to get), but I want to avoid these warnings
and
> error messages. Another unknown option is 56, which contains the
> error message the server provides to the client if an request fails.
> If I put the appropriate data in the server side client ID field, there
are
> no
> errors in the Event Monitor. But we don't want to use the CID.
> Has anyone any experience with this? What can I do to prevent those error
> messages?
> IMHO this is a client bug, because these DHCP options are in the standard
> and any DHCP client has to know them.
> Any advice welcome...
> Silke
