mac mini server refuses to get DHCP address from router
3 Macbooks and a Mini, Mac OS X (10.6.1)
3 Macbooks and a Mini, Mac OS X (10.6.1)
That 'corrupt' file solved my problem! Thanks for posting that. Every once in awhile my G4 goes 'DHCP' nuts... now I know why! I'm going to keep this one...
Mauricette has a point.
A server function is not designed to accept a floating or dynamic IP address. If that is the case, how do you create firewall rules that prevent those unnnecessary ports being left opened from being attacked by rogue machines in Romania and China on a hourly basis when you announce to the world that your server is available if the server IP address keep changing due to the DHCP lease change? Yes, they do have bots that do this VERY EFFICIENTLY!
By changing the very nature of your firewall rules by working with DHCP, you are opening ports you do not know to accommodate DHCP dynamic addressing, which was the reason why your Mac Mini Server stopped working in the first place. It's ok for a client, since a client isn't serving any files to any one right.
By using client based firewall rules, you are exposing your server to attacks and when they get through your Mini server, which they can if they are persistent, they get into your home network and then whatever file server services you have opened and unprotected at the time WILL BE copied by these people easily.
I have a client once who did just that. She was attacked, the hacker went through her network like a rampaging bull. They were from China. My Synology RAID server gets this attack all the time, but I have a well establish IDS system and the Synology RAID has logs that tracks attacks.
For a server setup. Use static IP and then build a strong firewall around it and protect it and never compromise.
Recently, I just noticed someone somehow hacked and broke my WPA-PSK AES passkey for one of my Wireless N network router. It was not set up with a strong password though, but thankgod I had a firewall around that so my internal networks were safe. So this teaches you that if someone wants in bad, they will get in.
Hope this helps.
This is not a firewall problem and our Mac Mini Server certainly is not running its own DHCP service. (Anyone can check that easily enough, btw, by looking for ports 67 and 68 in the output of sudo netstat -an | grep udp)
Watching the wire from another machine you can also see the DHCPDISCOVER, DHCPOFFER, DHCPREQUEST and DHCPACK packets going back and forth.
In our case we're running a Windows 2008 R2 DHCP server with a MAC reservation for the Mac Mini Server's ethernet MAC (its WiFi is turned off). What I found is that is you specify a DHCP Client ID in the settings it would kybosh the reservation in Windows and send back a dynamic address instead. Don't set the DHCP Client ID and it works OK.
In the DHCPDISCOVER packet it is prefixing the Client ID with a NUL character, so I'm wondering if this is a actually a bug...
===============================================================================
udp/67 2012-05-18 13:04:41
op = BOOTREQUEST
htype = HTYPE_ETHER
hlen = 6
hops = 0
xid = 659fb5a7
secs = 1
flags = 0
ciaddr = 0.0.0.0
yiaddr = 0.0.0.0
siaddr = 0.0.0.0
giaddr = 0.0.0.0
chaddr = 406c8f03e555
sname =
file =
Options :
DHO_DHCP_MESSAGE_TYPE(53) = DHCPDISCOVER
DHO_DHCP_PARAMETER_REQUEST_LIST(55) = 1 3 6 15 119 95 252 44 46
DHO_DHCP_MAX_MESSAGE_SIZE(57) = 1500
DHO_DHCP_CLIENT_IDENTIFIER(61) = \x00cripps
DHO_DHCP_LEASE_TIME(51) = 7776000
DHO_HOST_NAME(12) = cripps
padding [18] = 000000000000000000000000000000000000
===============================================================================
This is the exact same issue ive encountered with my Mac Mini Server.... seems to be a bigger issue than i thought
My advice would be to assign a static IP to a server in the system preferences. The thing is, servers use DNS, and DNS is not going to work well (or at all) if the server IP changes. I honestly have never tried using DHCP for a server's IP, so I can offer no advice as to how to make that work. Maybe I'm missing something, but I can't think of a reason NOT to assign a server a static IP.
mac mini server refuses to get DHCP address from router