Skip navigation

problem DHCP Server and windows

2799 Views 14 Replies Latest reply: Mar 18, 2014 8:12 AM by billflu2 RSS
elfigu Level 1 Level 1 (0 points)
Currently Being Moderated
Dec 13, 2012 3:55 PM

hello,

i have a mac mini 10.8.2 with server 2.2. I configurated dhcd server in my net and i have a problem with windows clients, these do not work, do not get ip.
But, mac clients work correctly.
What could be the problem?

 

Thanks

Xserve, OS X Mountain Lion (10.8.2)
  • FromOZ Level 2 Level 2 (400 points)
    Currently Being Moderated
    Dec 26, 2012 5:36 AM (in response to elfigu)

    Hmmm — that sort of reply is not necessarily going to get you any support is it. This is a self-help forum you know, no-one has to help you.

     

    It's a bit difficult with the brief information you have provided to be able to advise anything....

     

    • Is this a home network or a business environment?
    • Are there any other DHCP servers in the network? If it is a business network are you 'in control' of it? Is there another systems administrator who looks after network (and perhaps has put another DHCP server in)
    • It is assumed that both the Mac and Win machines are in the same subnet?
    • If you give the Windows machines a static IP can they ping the Mac DHCP machine?
    • This is obvious - but I'll ask it - but does the Mac mini server have a static IP address?

     

    You see that there can be many many factors - if you want help you should provide more detailed information.

  • FromOZ Level 2 Level 2 (400 points)
    Currently Being Moderated
    Jan 2, 2013 12:17 PM (in response to elfigu)

    Life's tough... when one considers that it costs $ 6000 per year for a the lowest support package from Apple (10 incidents / year) that covers OS X Server then free sounds pretty good — whatever response one gets.

     

    To your problem...

     

    If the Mac mini running OS X Server has a static IP and if Mac machines are successfully getting IP addresses then the thing to do is check various points

     

    This website

     

    http://krypted.com/mac-os-x/running-dhcp-on-mountain-lion-server/

     

    has information on setup of DHCP on OS X Server. You'll note that he says that Apple has taken management of DHCP out of the Server app, that was the case but they put it back in in version 2.1 I believe (you will be on OS X Server App 2.2 I take it). The point is he gives some information about config files if you want to check them. You don't need to manually change the config files as you can do (basic) config in the GUI.

     

    To check the Windows clients I would:

     

    1. Give them a temp static IP address in the same netrange of the server and make sure they can ping it (I'm assuming they are in the same physical network i.e. plugged into the same switch)
    2. Make sure that the Windows clients can get to UDP port 67 on your server and that the server is listening on port 67 (see below)
    3. Change the connection settings on the Windows machine to get all IP settings automatically, IP address and DNS settings to make the Windows machine try to get an IP address from DHCP server.
    4. Note down the MAC address of the Windows machine
    5. Go to the OS X server and in Server | Logs | System Log and filter (not search) for the string 'bootpd'. You should then see requests and traffic related to DHCP from the Windows machine. If you see nothing then get one of your Macs and get it to renew its DHCP lease.
    6. Try searching for the MAC address of the Windows machine (MAC address will be in format like in red colour below)
    7. If you see Mac machines communicating and connecting to the Mac server but Windows machines not even attempting to then you need to start looking at the Windows machines.
    8. For a more low level investigation you can run a free packet sniffer like Wireshark on the Windows machine to see what it is doing when it tries to find a DHCP server.

     

    See what you find... again though if the Windows machines don't even try to talk to the OS X server on port 67 then the issue is with the Windows machines.

     

     

     

     

    Check that server is listening on port 67, in Terminal run these commands, second one shows port as number

    ================================

    $ netstat -a -p udp

    udp4       0      0  *.bootps               *.* 

     

    $ netstat -an -p udp

    udp4       0      0  *.67                   *.*

     

     

    Example filtered log output of System Log

    ================================

    Jan  2 20:23:59 server.example.com bootpd[24959]: server name server.example.com

    Jan  2 20:23:59 server.example.com bootpd[24959]: interface en0: ip 192.168.1.2 mask 255.255.255.0

    Jan  2 20:23:59 server.example.com bootpd[24959]: DHCP REQUEST [en0]: 1,c7:2b:21:24:6d:6e <Fred's-iMac>

    Jan  2 20:23:59 server.example.com bootpd[24959]: ACK sent Fred's-iMac 192.168.1.100 pktsize 312

    Mac mini, OS X Server
  • JAGUK Level 1 Level 1 (10 points)
    Currently Being Moderated
    Jan 26, 2013 11:20 AM (in response to FromOZ)

    Hey FromOz,

     

    Nice post mate, very thorough - I've been searching for some help on the very same issue!

     

    Every windows machine that we try to connect to our work network, whether by wireless or ethernet, fails to get an IP. I've worked out, with the help of Wireshark, that it is failing accept the IP that the server is offering.

     

    I'm not that sure how to interpret all of the imformation from Wireshark really but I will give your advise a go and hope that I can spot the issue...

     

    We do have a second "guest" wireless network which I want to fully disable to eliminate it from the equation.

     

    If I'm still struggling I'll post back on here and hope that you can give any advise.

     

    Thanks, Justin

     

    (Mac Mini, OS X Server Mountain Lion)

  • JAGUK Level 1 Level 1 (10 points)
    Currently Being Moderated
    Jan 28, 2013 7:02 AM (in response to FromOZ)

    Hi FromOz (or anyone else who could kindly help!),

     

    I seem to have got somewhere this morning but not 100% why...

     

    I established that we have no secondary source of DHCP on our network.

     

    From Wireshark, on the Windows laptop, I could see it sending REQUEST & DISCOVER to port 67

     

    On the server system log I could see this:

     

    Jan 28 10:01:55 our.server.com bootpd[33319]: DHCP DISCOVER [en0]: 1,0:2:3f:d2:48:6e <justin-laptop>

    Jan 28 10:01:55 our.server.com bootpd[33319]: OFFER sent <no hostname> 10.0.1.152 pktsize 300

     

    At this point we started to get a seperate error on the server and lost internet and had to reboot the server.

     

    After the server had restarted i then saw the Windows laptop suddenly get assigned an IP and saw this type of subsequent entry in the system logs:

     

    Jan 28 13:17:38 our.server.com bootpd[293]: DHCP INFORM [en0]: 1,0:2:3f:d2:48:6e <justin-laptop>

    Jan 28 13:17:38 our.server.com bootpd[293]: ACK sent justin-laptop 10.0.1.40 pktsize 300

     

    Jan 28 13:31:46 our.server.com bootpd[293]: DHCP REQUEST [en0]: 1,0:2:3f:d2:48:6e <justin-laptop>

    Jan 28 13:31:46 our.server.com bootpd[293]: ACK sent justin-laptop 10.0.1.40 pktsize 304

     

    The only issue I can see before the server restart was that the server was not sending out its OFFER with the client hostname.

     

    One other thing I should point out is that I did not set up the server personally, one of my collegues did.

     

    Thanks in advance,

     

    Justin

  • FromOZ Level 2 Level 2 (400 points)
    Currently Being Moderated
    Jan 28, 2013 7:17 AM (in response to JAGUK)

    IT'S HEALED! REJOICE.

     

    Seriously, when is the last time the server rebooted? It could be as simple as that.

     

    Next what version of OS X Server is it running and on what base OS.

     

    Next was the DHCP initially setup on an older version of OS X server (pre-Lion) and then migrated to Lion/Mountain Lion? Reason for that question is the older versions of DHCP setup had more functionality exposed via the Server app GUI and perhaps something was configured that you can't see easily now.

     

    You can also run this command in the terminal to see what all DHCP settings are:

     

    sudo serveradmin settings dhcp

  • JAGUK Level 1 Level 1 (10 points)
    Currently Being Moderated
    Jan 28, 2013 8:02 AM (in response to FromOZ)

    Thanks for such a quick response

     

    The server was rebooted not that long ago to be honest so it's probably not that...

     

    The server is running version 2.2 of Mountain Lion.

     

    This was definiteyl a freshly setup DHCP

     

    I have just tested a Windows 7 netbook too and this also got an IP fine over both ethernet and wireless

     

    Not really sure what else to look at now that the issue seems to have magically resolved itself after the server reboot...

     

    Did you want ot see the server DHCP settings?

  • FromOZ Level 2 Level 2 (400 points)
    Currently Being Moderated
    Jan 28, 2013 8:06 AM (in response to JAGUK)

    Not really sure what else to look at now that the issue seems to have magically resolved itself after the server reboot...

     

    As the man says "if it ain't broke then don't touch it" I would leave it if you have definitely confirmed that all clients are working now.

     

     

    Did you want ot see the server DHCP settings?

     

    Sure, no probs. You will want to anonymise the output though before you post it.

    Mac mini, OS X Server
  • JAGUK Level 1 Level 1 (10 points)
    Currently Being Moderated
    Jan 28, 2013 8:50 AM (in response to FromOZ)

    right enough - I'll let it ride for now and see how we get on with some other Windows clients...

     

    strangely we have had the odd Macbook Pro that has thrown a wobbly and would not connect but most OS X clients are now fixed IPs anyway.


    I won't bother boring you with our DHCP settings unless this problem re-emerges sometime soon.

     

    Thanks FromOz, you have been most helpful.

     

    Justin

  • calfaro2 Level 1 Level 1 (0 points)
    Currently Being Moderated
    Feb 17, 2014 11:59 AM (in response to JAGUK)

    Hi this same issue is happening to us. We cannot get any windows machines ips on a mavricks dhcp server..any ideas ?

  • JAGUK Level 1 Level 1 (10 points)
    Currently Being Moderated
    Feb 19, 2014 4:42 AM (in response to calfaro2)

    same situation for me again... the only way to get the windows machines on the network / internet is by giving them fixed IPs within DHCP in Server app

     

    this is fine if the machines are static but when freelancers/clients come in with Windows machines it's really awkward

     

    if I follow FromOz's guide, in the server logs i can see the following:

     

    Feb 19 12:33:02 my.server.com bootpd[97863]: DHCP DISCOVER [en0]: 1,0:2:3f:d2:48:6e <justin-laptop>

    Feb 19 12:33:02 my.server.com bootpd[97863]: OFFER sent <no hostname> 10.0.1.3 pktsize 300

     

    So the server is sending the OFFER of an IP address but the Windows machine doesn't seem to respond / accept - my knowledge in this area is pretty limited so I'm not sure what should follow the OFFER

     

    Any help would be appreciated ;-)

  • Antonio Rocco Level 6 Level 6 (10,100 points)
    Currently Being Moderated
    Feb 19, 2014 6:34 AM (in response to JAGUK)

    DORA is the acronym used.

     

    D = Discover

    O = Offer

    R = Receive

    A = Acknowledge

  • billflu2 Level 1 Level 1 (0 points)
    Currently Being Moderated
    Mar 18, 2014 8:12 AM (in response to elfigu)

    One thing to check is if the DHCP scope has a search domain. I ran into this issue today where Windows computers wouldn't work until I added a fake search domain instead of having nothing (this is guest wifi). I hope this helps someone.

Actions

More Like This

  • Retrieving data ...

Bookmarked By (1)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.