1. Welcome Guest! In order to create a new topic or reply to an existing one, you must register first. It is easy and free. Click here to sign up now!.
    Dismiss Notice

DHCP Vendor classes not working help!

Discussion in 'Windows Home Server' started by UselessUser, Sep 10, 2009.

  1. UselessUser

    UselessUser Guest

    Hi,

    Brand new Server 2003 R2 SP2 32bit server install giving out DHCP...

    I need it to give a specific option to a client application...

    This application works by sending DHCP inform packets with option tag 60 set
    to "PDDBE"... and it then expects an option 43 tag back with various info
    in...

    I have created a new vendor class in the DHCP console and set the predefined
    attributes to option tag 43... I then configure it at either the scope or
    server level and it does not work!!

    I am literally pulling my hair out with this... the option 60 tag which is
    used in the vendor class is exactly as read off a wireshark trace, and I can
    enter it in ASCII or binary and it comes up the same as the wireshark trace...

    It just seems like the server is not interested as it just returns a DHCP
    ack with the server id tag 54 and the subnet id tag 1...

    I have tested it against a user class using an xp client desktop and that
    works fine... any ideas? Very frustrating...
     
  2. Shouldn't you configure user class instead of vendor class?

    "UselessUser" <UselessUser@discussions.microsoft.com> wrote in message
    news:8C4A47EC-C575-4801-9993-1E64645D69B8@microsoft.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Hi,
    >
    > Brand new Server 2003 R2 SP2 32bit server install giving out DHCP...
    >
    > I need it to give a specific option to a client application...
    >
    > This application works by sending DHCP inform packets with option tag 60
    > set
    > to "PDDBE"... and it then expects an option 43 tag back with various info
    > in...
    >
    > I have created a new vendor class in the DHCP console and set the
    > predefined
    > attributes to option tag 43... I then configure it at either the scope or
    > server level and it does not work!!
    >
    > I am literally pulling my hair out with this... the option 60 tag which is
    > used in the vendor class is exactly as read off a wireshark trace, and I
    > can
    > enter it in ASCII or binary and it comes up the same as the wireshark
    > trace...
    >
    > It just seems like the server is not interested as it just returns a DHCP
    > ack with the server id tag 54 and the subnet id tag 1...
    >
    > I have tested it against a user class using an xp client desktop and that
    > works fine... any ideas? Very frustrating... <!--colorc--><!--/colorc-->
     

Share This Page