none
DHCP options are not sent RRS feed

  • Question

  • Hi

    I am trying to set DHCP options on our SBS 2003 R2. I manually added the new option 150 as well as tried to configure option 66. However, the options are not sent. If I sniff the packets with wireshark all of the newly configured options are not in the DHCP Offer nor in the DHCP ACK.

    Any idea what I am doing wrong. I tried to restart the service, to no avail.

    Thanks
    McL


    • Edited by F. McLion Thursday, February 20, 2014 10:27 AM
    Thursday, February 20, 2014 10:06 AM

Answers

  • Robert, Thanks.

    We found that the server works as supposed. The problem is that Windows clients can not be set (AFAIK) to request options, option 150 for instance.
    We have tried with one of our own hardware with an MCU and have set up DHCP client to request the option 150 from the DHCP Server. The option is not (!) a special user or vendor class option, it is within the default options. If the DHCP request has the option 150 listed, the DHCP Server returns the option as supposed.

    Since we need to use this option with our embedded devices which are not running Windows, this works for us.
    What I miss is some kind of a documentation of MS that clears up these facts regarding the server DHCP as as well as regarding the client DHCP.

    Thanks for trying to help.
    Franz

    • Marked as answer by F. McLion Monday, March 3, 2014 12:22 PM
    Monday, March 3, 2014 12:22 PM

All replies

  • Did you add them as server options or scope options?

    Robert Pearman SBS MVP
    itauthority.co.uk | Title(Required)
    Facebook | Twitter | Linked in | Google+

    Thursday, February 20, 2014 10:55 AM
    Moderator
  • I tried both.
    Thursday, February 20, 2014 12:39 PM
  • Google told me that I am not the first to encounter this. Unfortunately, it did nod find an answer for me.
    So, if anybody who faced the same issues has found a solution I'd highly appreciate!

    Thursday, February 20, 2014 5:39 PM
  • I have not seen it myself.

    Do you have a screen shot of your scope options?


    Robert Pearman SBS MVP
    itauthority.co.uk | Title(Required)
    Facebook | Twitter | Linked in | Google+

    Friday, February 21, 2014 8:42 AM
    Moderator
  • I have removed the domain name blabla.local in the screen shot.

    Friday, February 21, 2014 8:49 AM
  • Hi,

    Have you configured two DHCP servers to manage the network subnet? Regarding the current issue, I suggest you could try to install the following hotfix to see if it works.

    A Windows Server 2003-based DHCP server that has a single deactivated scope still responds to DHCP INFORM packets from clients, and therefore network access problems occur

    http://support.microsoft.com/kb/944200/en-us

    Best Regards,

    Andy Qi


    Andy Qi
    TechNet Community Support

    Saturday, February 22, 2014 8:55 AM
    Moderator
  • Hi,

    I have only the one DHCP server on the SBS.
    Anyhow, I'll try with this hotfix installed and post back afterwards.

    Thanks and best regards,
    Franz

    Monday, February 24, 2014 7:34 AM
  • The hotfix did not solve the issue.
    Any other idea?

    Monday, February 24, 2014 5:33 PM
  • Nobody an idea how to get this up and running as supposed?
    Tuesday, February 25, 2014 7:41 AM
  • Are _any_ DHCP options sent out?

    Robert Pearman SBS MVP
    itauthority.co.uk | Title(Required)
    Facebook | Twitter | Linked in | Google+

    Tuesday, February 25, 2014 2:17 PM
    Moderator
  • All the other set are sent, see this Wireshark snip of an ACK:

    Tuesday, February 25, 2014 2:22 PM
  • bump
    Thursday, February 27, 2014 5:26 PM
  • Have you considered a reinstall of DHCP?

    Robert Pearman SBS MVP
    itauthority.co.uk | Title(Required)
    Facebook | Twitter | Linked in | Google+

    Thursday, February 27, 2014 8:26 PM
    Moderator
  • Actually, I thought about that.
    Since the server is in use I did not just quickly do it. I also may try to delete the current and create a new scope.

    Friday, February 28, 2014 7:37 AM
  • I think a new scope is probably a good start.

    Robert Pearman SBS MVP
    itauthority.co.uk | Title(Required)
    Facebook | Twitter | Linked in | Google+

    Friday, February 28, 2014 10:58 AM
    Moderator
  • New scope is best to start with. Does the server have 1 NIC or 2? SBS 2003 is a stickler about only using 1 NIC, it is best that you run 2. 1 Will connect to your internet connection/firewall, the other to a switch with the rest of the network devices. Rerun CEICW wizard
    Friday, February 28, 2014 4:23 PM
  • I have a configuration with only one NIC because the router to the wild is not near the SBS. I am aware of the other configuration option with 2 NIC's.
    However, in regards of the DHCP, I don't see how this would be related.
    Anyhow, I'll start with a new DHCP scope over the weekend. Maybe it helps.

    Thank you guys.

    Friday, February 28, 2014 4:39 PM
  • The new scope did not help.
    I found that the client (MS W7, for testing purpose) does send a Parameter Request List on the Discover as well as on the Request for an address.
    Does the DHCP Server in Server 2003 send out all options anyway or only the requested ones?

    Monday, March 3, 2014 7:36 AM
  • The scope options should form part of the 'Offer' i believe.

    http://support.microsoft.com/kb/169289

    DHCPOFFER

    The DHCP server responds by sending a DHCPOFFER packet. In the IP section of the capture excerpt below, the Source address is now the DHCP server IP address, and the Destination address is the broadcast address 255.255.255.255. The DHCP section identifies the packet as an Offer. The YIADDR field is populated with the IP address the server is offering the client. Note the CHADDR field still contains the physical address of the requesting client. Also, we see in the DHCP Option Field section the various options being sent by the server along with the IP address. In this case the server is sending the Subnet Mask, Default Gateway (Router), Lease Time, WINS server address (NetBIOS Name Service), and the NetBIOS Node Type.
    IP: ID = 0x3C30; Proto = UDP; Len: 328
        IP: Version = 4 (0x4)
        IP: Header Length = 20 (0x14)
        IP: Service Type = 0 (0x0)
            IP: Precedence = Routine
            IP: ...0.... = Normal Delay
            IP: ....0... = Normal Throughput
            IP: .....0.. = Normal Reliability
        IP: Total Length = 328 (0x148)
        IP: Identification = 15408 (0x3C30)
        IP: Flags Summary = 0 (0x0)
            IP: .......0 = Last fragment in datagram
            IP: ......0. = May fragment datagram if necessary
        IP: Fragment Offset = 0 (0x0) bytes
        IP: Time to Live = 128 (0x80)
        IP: Protocol = UDP - User Datagram
        IP: Checksum = 0x2FA8
        IP: Source Address = 157.54.48.151
        IP: Destination Address = 255.255.255.255
        IP: Data: Number of data bytes remaining = 308 (0x0134)
    
    DHCP: Offer              (xid=21274A1D)
        DHCP: Op Code           (op)     = 2 (0x2)
        DHCP: Hardware Type     (htype)  = 1 (0x1) 10Mb Ethernet
        DHCP: Hardware Address Length (hlen) = 6 (0x6)
        DHCP: Hops              (hops)   = 0 (0x0)
        DHCP: Transaction ID    (xid)    = 556223005 (0x21274A1D)
        DHCP: Seconds           (secs)   = 0 (0x0)
        DHCP: Flags             (flags)  = 0 (0x0)
            DHCP: 0............... = No Broadcast
        DHCP: Client IP Address (ciaddr) = 0.0.0.0
        DHCP: Your   IP Address (yiaddr) = 157.54.50.5
        DHCP: Server IP Address (siaddr) = 0.0.0.0
        DHCP: Relay  IP Address (giaddr) = 0.0.0.0
        DHCP: Client Ethernet Address (chaddr) = 08002B2ED85E
        DHCP: Server Host Name  (sname)  = <Blank>
        DHCP: Boot File Name    (file)   = <Blank>
        DHCP: Magic Cookie = [OK]
        DHCP: Option Field      (options)
            DHCP: DHCP Message Type      = DHCP Offer
            DHCP: Subnet Mask            = 255.255.240.0
            DHCP: Renewal Time Value (T1) = 8 Days,  0:00:00
            DHCP: Rebinding Time Value (T2) = 14 Days,  0:00:00
            DHCP: IP Address Lease Time  = 16 Days,  0:00:00
            DHCP: Server Identifier      = 157.54.48.151
            DHCP: Router                 = 157.54.48.1
            DHCP: NetBIOS Name Service   = 157.54.16.154
            DHCP: NetBIOS Node Type      = (Length: 1) 04
            DHCP: End of this option field
    				


    Robert Pearman SBS MVP
    itauthority.co.uk | Title(Required)
    Facebook | Twitter | Linked in | Google+

    Monday, March 3, 2014 10:55 AM
    Moderator
  • Robert, Thanks.

    We found that the server works as supposed. The problem is that Windows clients can not be set (AFAIK) to request options, option 150 for instance.
    We have tried with one of our own hardware with an MCU and have set up DHCP client to request the option 150 from the DHCP Server. The option is not (!) a special user or vendor class option, it is within the default options. If the DHCP request has the option 150 listed, the DHCP Server returns the option as supposed.

    Since we need to use this option with our embedded devices which are not running Windows, this works for us.
    What I miss is some kind of a documentation of MS that clears up these facts regarding the server DHCP as as well as regarding the client DHCP.

    Thanks for trying to help.
    Franz

    • Marked as answer by F. McLion Monday, March 3, 2014 12:22 PM
    Monday, March 3, 2014 12:22 PM
  • Ah so you don't want that option for the client PCs, just want to see if it is properly offered by the server?

    Robert Pearman SBS MVP
    itauthority.co.uk | Title(Required)
    Facebook | Twitter | Linked in | Google+


    Monday, March 3, 2014 1:09 PM
    Moderator
  • I tried with the added registry entry in the option section, to no avail (or I did something wrong).

    I got the task to set this up since I am the IT-Admin (beside my job as HW/SW developer). Of course, I wanted to test this before telling the users that the setting ready to be used, and that was where I got stuck. The Win7 PC was just to test things out, in the end we need this option on our embedded devices where it - surprisingly and thankfully - works.

    Monday, March 3, 2014 2:23 PM
  • If the device already has an IP assigned by the DHCP server it will not look again until the lease has expired. You could either force a an ipconfig /renew  or better still, delete the devices in DHCP on your server which should force the devices to look for a new address and pick up your new rules.

    https://community.spiceworks.com/topic/1529483-microsoft-dhcp-option-change-not-reflected-on-client


    Wednesday, July 10, 2019 9:30 AM