Setting options in DHCP client ...

Hi everyone, ...
Im having problems connecting to my corporate intranet DHCP network and investigating I realize the DHCP server requires a fixed DHCP Option 60 (vendor-class-identifier) with the value "MSFT 5.0".
Please, How can I configure this option in my osx DHCP client?
Regards,
Raul.

So you Mac is supporting Windows 2000 or older Microsoft operating systems? That is what Microsoft DHCP Vendor and User Classes. The 10.6.x system shouldn't need and changing.

Similar Messages

  • Win7 dhcp client: sending options

    I am trying to change dhcp option 60 and 43 on my Windows 7 Cleint PC.
    The standard option 60 - vendor class identifier is set to "MSFT 5.0" and I would like to change it to a different value of "Siemens". Similarly I want to send a Vendor Specific ID using option 43.
    I have tried to add:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DHCP\Parameters\Options\DhcpSendOptions
    "60"=hex:3c,07,53,69,65,6d,65,6e,73
    but try as I will, it will not send anything modified in the DHCP client request to the server.
    Do I need to put the registry entry somewhere else or in a different format?
    Thanks.

    Hi,
    After research, I found this registry key was supported by Windows CE and may not be supported in Windows 7. Otherwise, I have not found any documents that mentioned this.
    Juke Chou
    TechNet Community Support

  • DHCP client to send option 60

    Hi,
    I am running Yosemite 10.10.2 and I would like to enrich DHCP discover message sent by the mac os client with option 60 vendor-class-identifier.
    After various reading on the support web site, I tried to update this file: /System/Library/SystemConfiguration/IPConfiguration.bundle/Contents/Info.plist like this :
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
    <dict>
            <key>BuildMachineOSBuild</key>
            <string>14C92</string>
            <key>CFBundleDevelopmentRegion</key>
            <string>English</string>
            <key>CFBundleIdentifier</key>
            <string>com.apple.SystemConfiguration.IPConfiguration</string>
            <key>CFBundleName</key>
            <string>SystemConfiguration</string>
            <key>CFBundleShortVersionString</key>
            <string>14.0.0</string>
            <key>DTCompiler</key>
            <string>com.apple.compilers.llvm.clang.1_0</string>
            <key>DTPlatformBuild</key>
            <string>6D97u</string>
            <key>DTPlatformVersion</key>
            <string>GM</string>
            <key>DTSDKBuild</key>
            <string>14C75a</string>
            <key>DTSDKName</key>
            <string>macosx10.10internal</string>
            <key>DTXcode</key>
            <string>0630</string>
            <key>DTXcodeBuild</key>
            <string>6D97u</string>
            <key>IPConfiguration</key>
            <dict>
                    <key>ARPConflictRetryCount</key>
                    <integer>2</integer>
                    <key>ARPConflictRetryDelaySeconds</key>
                    <real>0.75</real>
                    <key>ARPDetectCount</key>
                    <integer>3</integer>
                    <key>ARPDetectRetryTimeSeconds</key>
                    <real>0.014999999999999999</real>
                    <key>ARPGratuitousCount</key>
                    <integer>2</integer>
                    <key>ARPProbeCount</key>
                    <integer>3</integer>
                    <key>ARPResolveRetryTimeSeconds</key>
                    <real>0.32000000000000001</real>
                    <key>ARPRetryTimeSeconds</key>
                    <real>0.32000000000000001</real>
                    <key>ConfigureIPv6</key>
                    <true/>
                    <key>DHCPAcceptsBOOTP</key>
                    <false/>
                    <key>DHCPAllocateLinkLocalAtRetryCount</key>
                    <integer>4</integer>
                    <key>DHCPFailureConfiguresLinkLocal</key>
                    <true/>
                    <key>DHCPInitRebootRetryCount</key>
                    <integer>2</integer>
                    <key>DHCPLeaseWriteT1ThresholdSeconds</key>
                    <integer>3600</integer>
                    <key>DHCPLocalHostNameLengthMax</key>
                    <integer>15</integer>
                    <key>DHCPRequestedParameterList</key>
                    <array>
                            <integer>1</integer>
                            <integer>3</integer>
                            <integer>6</integer>
                            <integer>15</integer>
                            <integer>119</integer>
                            <integer>95</integer>
                            <integer>252</integer>
                            <integer>44</integer>
                            <integer>46</integer>
                    </array>
                    <key>dhcpoption60</key>
                    <string>MSFT 5.0</string>
                    <key>DHCPRouterARPAtRetryCount</key>
                    <integer>7</integer>
                    <key>DHCPSelectRetryCount</key>
                    <integer>3</integer>
                    <key>DHCPSuccessDeconfiguresLinkLocal</key>
                    <true/>
                    <key>DHCPv6Enabled</key>
                    <true/>
                    <key>DHCPv6RequestedOptions</key>
                    <array>
                            <integer>23</integer>
                            <integer>24</integer>
                    </array>
                    <key>DefendIPAddressCount</key>
                    <integer>5</integer>
                    <key>DefendIPAddressIntervalSeconds</key>
                    <integer>10</integer>
                    <key>DiscoverAndPublishRouterMACAddress</key>
                    <true/>
                    <key>DiscoverRouterMACAddressTimeSeconds</key>
                    <integer>60</integer>
                    <key>GatherTimeSeconds</key>
                    <integer>1</integer>
                    <key>InitialRetryTimeSeconds</key>
                    <integer>1</integer>
                    <key>LinkInactiveWaitTimeSeconds</key>
                    <real>0.10000000000000001</real>
                    <key>ManualConflictRetryIntervalSeconds</key>
                    <integer>300</integer>
                    <key>MaximumRetryTimeSeconds</key>
                    <integer>8</integer>
                    <key>MinimumShortWakeIntervalSeconds</key>
                    <integer>60</integer>
                    <key>MinimumWakeIntervalSeconds</key>
                    <integer>900</integer>
                    <key>MustBroadcast</key>
                    <false/>
                    <key>RetryCount</key>
                    <integer>9</integer>
                    <key>RouterARPEnabled</key>
                    <true/>
                    <key>RouterARPWiFiLeaseStartThresholdSeconds</key>
                    <integer>86400</integer>
                    <key>UseMaintenanceWake</key>
                    <true/>
                    <key>WakeSkewSeconds</key>
                    <integer>30</integer>
            </dict>
            <key>MachServices</key>
            <dict>
                    <key>com.apple.network.IPConfiguration</key>
                    <true/>
            </dict>
            <key>Requires</key>
            <array>
                    <string>com.apple.SystemConfiguration.InterfaceNamer</string>
                    <string>com.apple.SystemConfiguration.KernelEventMonitor</string>
                    <string>com.apple.SystemConfiguration.PreferencesMonitor</string>
            </array>
    </dict>
    </plist>
    Unfortunately no joy ... nothing has changed.
    Does anybody have a solution to this problem or is it just no fixable ?
    Thanks,
    Matt.

    found a solution : install dhcp (for example with darwinport , i.e. sudo port install dhcp) and use the dhclient command with a specific /etc/dhclient.conf
    send dhcp-client-identifier "Guile";
    send vendor-class-identifier "msft";
    send host-name "GuileMac";

  • I want to reserve a static IP address on my Airport extreme.  What is the difference between reserving by MAC Address and DHCP Client ID?

    I want to understand the differences in the way you can reserve a static address for a device on the network.  I had previously set the device itself to an address and then reserved it with DHCP Client ID, which I thought was just the devices static addresss.  I'm not sure if this was in fact correct or just happend to work.  I know what a MAC address is, but I'm not really sure what the DHCP Client ID is. So it would be great if someone could clarify it, and the difference between reserving address by MAC Address or DHCP Client ID.

    A MAC address is a unique identification consisting of letters and numbers in a form that looks like this:
    xx:xx:xx:xx:xx:xx
    Every network device has a MAC address, which can be found on a label on the bottom or back of the device. Apple calls this the Ethernet ID.
    A DHCP Client ID is an optional name that you can assign to a device. For example, on your Mac....
    Open System Preferences (gear icon on the dock)
    Open Network
    Click on Ethernet
    Click Advanced at the lower right
    You may be able to edit the DHCP Client  ID here....for example.....you could enter MJ500's MacBook in the space provided. That would be the Client ID of your Mac.

  • How to setup default gateway in a DHCP client. The default gateway will be the Ip address of the server that has RRAS installed, hence routing cabalities.

    How to setup default gateway in a DHCP client. The default gateway will be the Ip address of the server that has RRAS installed, hence routing cabalities.

    Hi Bill,
    Thank you for replying back...Yes, I was actually asking how do you set the default gateway address on the DHCP server?,
    I believe I got the answer below:
    To configure the DHCP default gateway option Click Start, point to Administrative Tools and then click DHCP. In the console tree, expand the applicable DHCP server, expand IPv4, and then right-click Scope Options Click Configure Options, check 003
    Router, type the applicable Server name and IP address, and then click OK.
    Thank you

  • Macs show up as "unknown" on my router's DHCP Client Table

    Both of my Macs, an Intel Mac Mini running Snow Leopard and a G4 iMac running Tiger show up as "unknown" in my router's DHCP client table.
    All of my Windows PCs all show up with their computer names.
    Is there a way to get my Macs' computer names to show up in the DHCP client table? The router is a Linksys RTP300.

    Open Network System Preferences, click on the service you are using to connect to the network (airport, ethernet, etc), click on Advanced and go to the TCP/IP tab. There is a field for DHCP client ID. This may pass a name to the router and it may use it. I don't know.
    Another option is the WINS tab. You can set the Netbios name (other than the default) and workgroup (and any WINS servers, if you know their addresses).

  • Management of a DHCP client in a remote unknown network

    Dear all,
    Here is my problem :
    I have the network A with a DHCP Server.
    Network A knows the network B only with its NATed addresses
    In DHCP Server (which is on a Solaris machine) the remote client is configured with NATed informations.
    In network B I have a client.
    Network B knows the network A only with its NATed addresses
    The ip helper-adress is set to NATed address of the DHCP Server.
    At the client power up, all works fine but the client receive all its NATed informations so it's IP, netmask and gateway addresses are wrong.
    I would like to know if the DHCP relay can modify some information in the DHCP-OFFER packets.
    Thanks for your help.
    Br,
    Jean-Yves ANDREOLETTI

    Hi Jean-Yves,
    can I add some options on my clients from the DHCP master server.
    This is, in general, impossible. DHCP protocol essentially lacks any features in which DHCP servers can cooperate, share the address leases or synchronize the configuration options handed out to clients. Indeed, the entire DHCP protocol focuses exclusively on the client-server communication, and there are no provisions for server-server information exchange.
    If your router was obtaining an IP address from the DHCP server itself (i.e. if one of its interface was configured with ip address dhcp) then you could use the import all command in the DHCP pool on the router, causing the router to obtain all DHCP options not explicitly specified in the pool from the DHCP server. However, this scenario is more applicable to dialout solutions, and I do not think it is suited to your network.
    Apart from this, I am not aware of any method that would allow you to merge a selected set of settings on a local DHCP server with another settings from a master DHCP server. I am sorry to disappoint you.
    Best regards,
    Peter

  • CNR DHCP Client-class

    We are using CNR with multiple scopes to provide ip addressing for both computers and IPTV set top boxes. The STB's require boot params in dhcp option-131 and option-240. I have set up a client-class-policy that contains the two options and when I set up a client with an exact mac address, then the information is provided correctly.
    The problem is we have hundreds of STB's. How do I get CNR to generalize the client mac address to just the first 3 bytes?
    I have tried creating a client with 00:00:00 for the last three bytes and then altering the dhcp-client-identifier to match, but it doesn't work.
    The docs state that you can create a client-lookup-id expression but shows no examples.
    Thanks.

    Reread the docs closer and found that the environment parameter 'default-client-class-name' is only visible in the pre-client-lookup extension. So in the post-packet-decode extension I check the request parameter 'dhcp-class-identifier' and then set a environment parameter stb-type to a class name.
    In the pre-client-lookup I check to see if the stb-type is in the environment dictionary. If it is then I set 'default-client-class-name' to that value. This forces the DHCP to use the client-class of the same name as the default for this DHCP request. Since I set the option 131 in the appropriate client-class-policy then it all works. Don't even need a client set up at all.
    Thanks for the response on expressions. Looks like I may have been able to do it that way too.

  • WDS PXE DHCP, Clients on different subnet

    Hello,
    We are having a lot of trouble trying to get pxe imaging working from our WDS server on different subnets.  We have an existing Zenworking imaging setup working as of right now, but WDS is causing more issues than I care to troubleshoot.  I have read
    blog after blog, forum post after forum post and everyone says just install it and it works!  I guess we have run into some sort of problem that nobody else has.
    Enviroment:
    2x DC's, Server 2012 R2, both run DNS, 10.5.0.101, 10.5.0.102
    1x DHCP Server, 2012 R2, 10.5.0.105
    1x WDS Server, 2012 R2, 10.5.0.41
    If I put a client on the same subnet as all of the servers it seems to work, except for the fact that it takes a while for the client to get an IP and continue to load wdsnbp.com.  I would say around 20-30 seconds.  In our zenworks enviroment it takes
    no more than 1 second to get an IP.  As for the dhcp server itself, clients receive normal dhcp offers instantly.  So that part is working properly.
    Now when I try an access the WDS pxe server from a different subnet other than the one that all of the servers are on, noting that I do have the ip helper address setup on our layer 3 switch:
    interface Vlan2025
     ip address 10.200.20.1 255.255.255.0
     ip helper-address 10.5.0.105
     ip helper-address 10.5.0.41
    It always says failed to receive boot file.  But as I said earlier, clients in windows receive dhcp leases from 10.5.0.105 without issue.
    Setting the client options in the DHCP server with options 66 and 67 works sortof, but we found that it was unreliable and often finicky.  Like having the system repeatedly ask to press f12, and even if you did press f12 it would still ask to press f12
    again.
    So I continued to do a wirehark packet capture on the port where the device was trying to get the dhcp/pxe info from the DHCP / WDS servers.  The first packet here is from the DHCP server and the second is from the WDS server.
    Bootstrap Protocol
        Message type: Boot Reply (2)
        Hardware type: Ethernet (0x01)
        Hardware address length: 6
        Hops: 0
        Transaction ID: 0xd6c565d2
        Seconds elapsed: 0
        Bootp flags: 0x8000 (Broadcast)
        Client IP address: 0.0.0.0 (0.0.0.0)
        Your (client) IP address: 10.200.20.117 (10.200.20.117)
        Next server IP address: 10.5.0.105 (10.5.0.105)
        Relay agent IP address: 10.200.20.1 (10.200.20.1)
        Client MAC address: Hewlett-_c5:65:d2 (78:e7:d1:c5:65:d2)
        Client hardware address padding: 00000000000000000000
        Server host name not given
        Boot file name not given
        Magic cookie: DHCP
        Option: (53) DHCP Message Type
            Length: 1
            DHCP: Offer (2)
        Option: (1) Subnet Mask
            Length: 4
            Subnet Mask: 255.255.255.0 (255.255.255.0)
        Option: (58) Renewal Time Value
            Length: 4
            Renewal Time Value: (21600s) 6 hours
        Option: (59) Rebinding Time Value
            Length: 4
            Rebinding Time Value: (37800s) 10 hours, 30 minutes
        Option: (51) IP Address Lease Time
            Length: 4
            IP Address Lease Time: (43200s) 12 hours
        Option: (54) DHCP Server Identifier
            Length: 4
            DHCP Server Identifier: 10.5.0.105 (10.5.0.105)
        Option: (3) Router
            Length: 4
            Router: 10.200.20.1 (10.200.20.1)
        Option: (6) Domain Name Server
            Length: 8
            Domain Name Server: 10.5.0.101 (10.5.0.101)
            Domain Name Server: 10.5.0.102 (10.5.0.102)
        Option: (15) Domain Name
            Length: 8
            Domain Name: domain.com
        Option: (255) End
            Option End: 255
    Bootstrap Protocol
        Message type: Boot Reply (2)
        Hardware type: Ethernet (0x01)
        Hardware address length: 6
        Hops: 0
        Transaction ID: 0xd2c565d2
        Seconds elapsed: 4
        Bootp flags: 0x8000 (Broadcast)
        Client IP address: 0.0.0.0 (0.0.0.0)
        Your (client) IP address: 0.0.0.0 (0.0.0.0)
        Next server IP address: 10.5.0.41 (10.5.0.41)
        Relay agent IP address: 10.200.20.1 (10.200.20.1)
        Client MAC address: Hewlett-_c5:65:d2 (78:e7:d1:c5:65:d2)
        Client hardware address padding: 00000000000000000000
        Server host name: wds1.domain.com
        Boot file name not given
        Magic cookie: DHCP
        Option: (54) DHCP Server Identifier
            Length: 4
            DHCP Server Identifier: 10.5.0.41 (10.5.0.41)
        Option: (97) UUID/GUID-based Client Identifier
            Length: 17
            Client Identifier (UUID): eb8daa31-8e62-11df-bbd8-d1c565d278e7
        Option: (60) Vendor class identifier
            Length: 9
            Vendor class identifier: PXEClient
        Option: (53) DHCP Message Type
            Length: 1
            DHCP: Offer (2)
        Option: (255) End
            Option End: 255
    What I find interesting is that the WDS server is not handing out a boot file name:
    "Boot file name not given"
    Could this be the reason why we receive the no boot file received error when trying to boot a client into pxe?
    The other thing that I noticed was that the WDS server is also responding with the:
    "    Option: (60) Vendor class identifier
            Length: 9
            Vendor class identifier: PXEClient
    Why would it be responding with this, when the dhcp is on a separate server.  Is this option only if you have DHCP and WDS on the same server?
    Any help would be appreciated as there has been too much time already spent on getting nowhere.
    Thanks,
    Dan.

    Dan,
    10 months later and not one reply...  I'm having the same issue, did you ever figure this out?  DHCP server is my Cisco Switch, WDS/PXE is on another network.  The WDS and PXE is working fine as I can do so from the same network as the WDS/PXE
    server.  I can also get the WDS/PXE to work if I have a MS DHCP server on a different network and populate the option 66 and option 67.  I cannot get this to work using Cisco ip helper-address for some reason.
    Thanks,

  • Cisco ASA 5505 and DHCP Client Problems

    Hi, i have a problem. I've connected my ASA appliance to an ADSL modem, and i dont get an DHCP address on the outside interface (e0/0). I use the asa-722-19.bin firmware.
    I turned on the debugging for the DHCP client and could see that the ASA device was sending out broadcasts but a reply never came. Instead I connected the device to my internal network where the ASA got an address instantly.
    I read somewhere that if I was to use ?ip address dhcp client-id fastethernet 0″, then I got an address from the ISP.
    I tried looking for a similar command on the ASA5505 but I couldn?t find anything. I did however find a page on the Cisco site confirming my suspicions. It said some ISP?s require the client-id field of the DHCPDISCOVER request to be filled.
    I've also read that this issue has beed fixed since a few weeks, now they have released version 7.2(2).22 where you can define ?dhcp-client client-id interface outside? in global configuration mode. Im running 7.2(2).19 and i cannot find any command like that in my appaiance. How do i fix my problem ? Or how do i get about recieving the 7.2(2).22 firmware update.
    Regards !
    Leif

    Hi again! I thought I should share the solution that worked for me. I use software version 7.2(2) on this device. ASDM 5.2(2). In ASDM open configuration / Interfaces. Click in outside (my case 0/0) and press Edit. Then open the tab Advanced and set the correct Active Mac address. Fore some reason its empty by default and the ISP/modem don't like that. You will find the correct MAC address under the help menu / "About ASA". Im sure there is some another way to do this but this is a simple "how-to" that works with Swedens biggest ISP and their standard DSL modem.
    When I used a Linksys DSL modem in bridge mode without the MAC address set I got an inside IP adress (192.168.x.x) from the modem to the ASA. After setting the MAC address I just had to do a renew and got the outside address right away. /Bjorn
    (future users searchwords: no ip from isp, ASA 5505 and cable modem).

  • Have to regularly restart DHCP Client - HP Pavilion 500-205 DT - Windows 7

    HP Pavilion 500-205 DT - Windows 7 Home Premium 64-bit SP1
    Realtek PCIe GBE Family Controller - Driver 7.67.1226.2012
    Bought 3 identical machines for our childcare center. Set them up the same. All work fine except ONE of them becomes inaccessible periodically (daily more-or-less) to the other Windows computers on our little peer-to-peer LAN. You can see it, but cannot access any shared folder. There is NO problem accessing the OTHER computers on the LAN from this one. All 3 machines have the same sharing profile, workgroup, permissions, AV, firewall settings, everything. I realized restarting the computer in question solved the problem immediately but temporarily. I narrowed it down to restarting the DHCP Client service. Do that, everything works fine immediately but temporarily.
    Things I tried:
    Calling HP support - not helpful at all. It is under warranty.
    Disabled IPv6
    Disabled wireless
    Disabled power-saving shutoff of network adapter
    Setting DHCP CLIENT recovery to:
      First Failure = Restart the the Service
     Second Failure = Restart the the Service
     Subsequent Failures = Restart the the Service
     Reset Fail count After = 120
     Restart Service after = 0
    But again, this isn't happening to the other machines with default settings. Nothing works except restarting the DHCP Client service. The loss of access happens with or without someone logged or using it. It has happened since it was first set up.
    I don't know if the HP warranty covers factory-loaded OS. I don't want to restore the thing and start over. I am not an IT professional, just the guy in the office who does these things, but it seems like the network adapter could be defective. I don't know if I can convince a first-level phone support person to have me bring the machine to an authorized service place.
    Any help greatly appreciated,
    Larry
    This question was solved.
    View Solution.

    You're very welcome.
    I would tend to agree, but I wanted to offer you that driver as a last resort.
    This is a consumer to consumer forum.  I don't work for HP, and if you suspect it is a hardware issue, you will need to contact HP technical support and submit a support case under the warranty.
    The warranty covers hardware, and support for the HP software and operating system installed (as long as it is the original factory image that came with the PC and not an operating system you installed).

  • WRT54G v7 WAN DHCP client problem

    I've recently started having a strange problem with my WRT54G. Internet access is via a Cable modem and has been working fine for months, and the cable modem works fine so I suspect the problem is with the router. However the router is also working, mostly, so I figured I'd see if anyone here has any suggestions. Here are the details of the problem:
    The router WAN configuration was set to DHCP.
    It used to happily pick up a new IP address from the cable modem whenever necessary.
    One night the router stopped picking up an IP on the WAN side. (nothing was changed. I'm the only one in the house who goes anywhere near the router)
    Connecting the modem directly to a PC works fine (suggesting the modem's DHCP server is fine).
    Copying the WAN IP config from the PC to the router, as a Static IP, also allows it to work when the modem is plugged back into the router and the router to a PC (which is how it's setup now, but it's a pain to have to mess with the physical connections and manually reconfigure the router every time the modem drops a connection (which is another issue, but not one for this forum...)).
    So both the modem and the router seem to work except for the router's DHCP client. It works fine as a DHCP server for the LAN.
    The firmware was already upgraded (and working), I've followed the standard power-cycle procedure, I've released and renewed the IP via the Status tab in the web interface, and I've tried resetting the router using both the button on the unit and via the web interface to revert to factory defaults.
    Any suggestions?
    Solved!
    Go to Solution.

    I also had this problem which occurred after >2 years of the router working fine.  After changing MTU to 1300, cloning the PC MAC address, and power cycling the router and modem fixed the problem.  But I was curious to see which change did the trick, so I changed both back to the default (MTU = auto and not cloning the MAC address) and it worked fine!  I think the router problem is intermittant and may appear to be fixed by changing setting, but I fully expect it to reoccur. 

  • Router reports garbage characters for Mac's DHCP client hostname

    I've got a Linksys wifi router giving nice wireless access to my 17" powerbook (OSX 10.3.9). But when I look at the DHCP active IP table, this one (and another Mac I have on the network) both show up with garbage characters on the "client hostname" even though I have the "DHCP client Id" field filled in in the Network, TCP/IP system preference pane. How do I get the router to see my client's name?
    Mike

    Might help if you told us what the "garbage" was. It
    might help indentify what it relates to because it's
    highly unlikely to be truly random. It's more likely
    to be based on the client's MAC address.
    ok. It is, exactly: ¸#Єª
    In any case, DHCP client ID and hostname are not
    related, so you might be out of luck depending on
    what the Linksys is doing.
    ah! Sorry - I thought that's what it wanted. So, where on my machine do I set the client hostname? Where does a router grab this info from? I've got a PC connected to this thing which does report its name correctly.
    Thanks,
    Mike

  • DHCP Client does not send host name to DHCP Server

    Hello,
    I installed Solaris 10 on VirtualBox and I cannot ping/ssh/telnet the virtual machine by its host name (even from the host computer) but only by it's ip.
    I tried everything I could find on internet with no success (I don't want to add the hostname in every hosts file on every computer because it's not really professionnal)
    I followed what said here: http://docs.oracle.com/cd/E26505_01/html/E27061/eyhuv.html#scrolltoc
    Can someone has an idea of what I can do or why this does not work.
    I installed a virtual Windows7 and an Ubuntu, and it worked perfectly.
    Any help would be grantly appreciated.
    Thank you
    Here is my current configuration:
    Oracle VM VirtualBox 4.3.8 (I choose "Oracle 10 10/09 and later (64 bit))
    Oracle Solaris 10 1/13
    Network: bridge with RealTek interface
    NB: I don't have access to dhcp server on my netgear router (access is disabled by my ISP)
    Files in /etc:
    dhcp.e1000g0 (empty)
    nodename (contains "thorgal")
    nsswitch.conf has following lines:
    hosts: files dns # Added by DHCP
    ipnodes: files dns # Added by DHCP
    networks:   files
    protocols:  files
    rpc:        files
    ethers:     files
    netmasks:   files
    bootparams: files
    hostname.e1000g0 (contains "inet thorgal")
    /etc/inet/hosts:
    ::1             localhost
    127.0.0.1       localhost loghost
    192.168.0.17    thorgal # Added by DHCP
    /etc/default/dhcpagent:
    REQUEST_HOSTNAME=yes
    PARAM_REQUEST_LIST=1,3,6,12,15,28,43
    .v6.PARAM_REQUEST_LIST=7,12,23,24,27,29
    I also try "ifconfig e1000g0 dhcp release" with no success
    the debugging of dhcpagent:
    # pkill -x dhcpagent
    # /sbin/dhcpagent -d1 -f &
    1088
    # ifconfig e1000g0 dhcp start
    /sbin/dhcpagent: debug: insert_pif: e1000g0: sdumax 1500, hwtype 1, hwlen 6
    /sbin/dhcpagent: debug: set_packet_filter: set filter 805869f (DHCP filter)
    /sbin/dhcpagent: debug: get_smach_cid: getting default client-id property on e1000g0
    /sbin/dhcpagent: debug: in state INIT; allowing start command on e1000g0
    /sbin/dhcpagent: debug: ipc_action_start: started start (command 4) on e1000g0
    /sbin/dhcpagent: debug: set_smach_state: changing from INIT to INIT_REBOOT on e1000g0
    /sbin/dhcpagent: debug: dhcp_selecting: host thorgal
    /sbin/dhcpagent: info: configure_v4_lease: setting IP netmask to 255.255.255.0 on e1000g0
    /sbin/dhcpagent: info: configure_v4_lease: setting IP address to 192.168.0.17 on e1000g0
    /sbin/dhcpagent: warning: configure_v4_lease: no IP broadcast specified for e1000g0, making best guess
    /sbin/dhcpagent: info: configure_v4_lease: using broadcast address 192.168.0.255 on e1000g0
    /sbin/dhcpagent: info: configure_v4_timers: e1000g0 acquired lease, expires Fri Mar 21 21:33:05 2014
    /sbin/dhcpagent: info: configure_v4_timers: e1000g0 begins renewal at Fri Mar 21 09:33:05 2014
    /sbin/dhcpagent: info: configure_v4_timers: e1000g0 begins rebinding at Fri Mar 21 18:33:05 2014
    /sbin/dhcpagent: debug: set_smach_state: changing from INIT_REBOOT to PRE_BOUND on e1000g0
    /sbin/dhcpagent: info: added default router 192.168.0.1 on e1000g0
    /sbin/dhcpagent: debug: set_smach_state: changing from PRE_BOUND to BOUND on e1000g0
    /sbin/dhcpagent: debug: configure_bound: bound e1000g0
    /sbin/dhcpagent: debug: ipc_action_finish: finished start (command 4) on e1000g0: 0

    During the Solaris installation process, you told it what the hostname was going to be and that you wanted that environment to exist with a dynamic IP address instead of a specific address that you desired.
    When Solaris boots it broadcasts that hostname and waits for a DHCP server to be quasi-intelligent enough to award an IP address based upon a pre-configured list inside that DHCP server.   Hostname ABC would always get IP address 123 on subnet rst, hostname DEF would always get IP address 456 on subnet xyz, and so on and so on.
    That's the fundamental process for proper (and thus secure) DHCP.
    All your other environments (Windows, Debian, Ubuntu) are what might be thought of as "hacked for convenience" to get around that sort of network configuration.  They take the lazy way to exist.  That partial networking setup is good enough for a home network but would be miserably insecure in a corporate environment.  Those choices are operating environments that are nice for end-user desktops but aren't Enterprise Class.
    My suggestion?
    Review the IP address range in your Netgear router's setup.
    It is likely something like 192.169.0.1 through 192.168.0.50 and can be customized.
    You probably don't have 50 devices on your network and probably will never have 50 simultaneous devices on your network.
    ... just do a reconfigure reboot and set your Solaris to use a static IP of 192.068.0.45
    Then reboot and I predict your issue that prompted this forum thread will be gone.
    That's how I've done it at home for many years, even when installing Solaris to bare metal (no virtualization).

  • How get the RVS4000's DHCP server to assign another IP address other than its own as the default gateway to its DHCP clients?

    Hi,
    I have a RVS4000 router with DHCP enabled and in router mode. 
    The LAN is 192.168.2.x.  The RVS4000 static IP address is 192.168.2.8
    The router is not the RVS4000 and is at 192.168.2.1
    The RVS4000 dhcp is assigning it's clients a default gateway of 192.168.2.8 instead of what I want 192.168.2.1.
    How can I get the RVS4000's DHCP server to assign another IP address other than its own as the default gateway to its DHCP clients?
    Thanks

    Hi Gail, you cannot do this. The router, as the DHCP server will only assign a default gateway of what IP interface the DHCP server runs on. If you have the default IP, the gateway is 192.168.1.1. If you create a second vlan, by default it would be 192.168.2.1.
    There are not configuration options for the built-in DHCP server. If you'd like to expand this functionality, you would need an external dhcp server.
    -Tom
    Please mark answered for helpful posts

Maybe you are looking for