OS X server, DHCP Server and random blocked IPs

Question

Hello !
I use a Mac Mini as a DHCP server for my wireless network. It is connected to internet through a wired modem and gives an IP (through Airport) to the computers that ask for it.
Everything works quite fine... Unless, sometimes, clients obtain an adress but cannot browse the web nor connect to local network. The ip is just "blocked".
If i try to use it on an other computer (manually), it just doens't work.
So, I must change the ip, by changing the DHCP Name of the computer (otherwise, the server always give the same adress), to fix the problem.
What is strange, is that a few time after, the incriminated ip works new ! Until it is down again...
My bootpd config file is the fallowing;
<?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>NetBoot</key>
<dict/>
<key>Subnets</key>
<array>
<dict>
<key>allocate</key>
<true/>
<key>dhcpdomainname</key>
<string>antoine.maille.priv</string>
<key>dhcpdomain_nameserver</key>
<array>
<string>81.253.149.1</string>
<string>80.10.246.3</string>
<string>10.0.0.1</string>
</array>
<key>dhcpldapurl</key>
<array>
<string>ldaps://Mac Mini/</string>
</array>
<key>dhcp_router</key>
<string>10.0.0.1</string>
<key>lease_max</key>
<integer>604800</integer>
<key>leasetimesecs</key>
<string>86400</string>
<key>name</key>
<string>DHCP WiFi</string>
<key>net_address</key>
<string>10.0.0.0</string>
<key>net_mask</key>
<string>255.255.255.0</string>
<key>net_range</key>
<array>
<string>10.0.0.10</string>
<string>10.0.0.100</string>
</array>
<key>selectedportname</key>
<string>en1</string>
<key>uuid</key>
<string>FEB30FD5-3749-480E-9FEB-BD2C20206431</string>
</dict>
</array>
<key>allow</key>
<array/>
<key>bootp_enabled</key>
<true/>
<key>deny</key>
<array/>
<key>detectother_dhcpserver</key>
<true/>
<key>dhcp_enabled</key>
<true/>
<key>oldnetbootenabled</key>
<false/>
<key>relay_enabled</key>
<true/>
<key>relayiplist</key>
<array/>
<key>timeServiceStarted</key>
<string>2008-11-26 22:59:19 +0100</string>
</dict>
</plist>
Do you have any idea of what I should do to fix that problem ?
Thanks !
alex

Answer 1

Brandon Macinnis wrote:
Dnar,
Thanks for the follow up bit about using the smbutil statshares command.  I used that and could confirm that I am also able to force it to connect with smb2.  Oddly though, in the stat share info it still says "AUTO_NEGOTIATE"
                              SMB_NEGOTIATE                 AUTO_NEGOTIATE
                              SMB_VERSION                   SMB_2.1
But maybe that just means something else and not the fact that it did not auto negotiate to SMB.  I guess for now this will be what I have to do to use smb2.
I think in this case the AUTO_NEGOTIATE merely means it will auto negotiate a connection between SMB1, SMB2, and (from your data) also SMB2.1 this would have nothing to do with auto negotiating between SMB2 and AFP, which from this thread appears broken.
I also would like to thank Brandon for the tip about smbutil statshares, I had been looking for a simple way to tell what version of SMB was being used to test my NAS.
For everyone's benefit, it would appear from the above that whilst Apple advertise Mavericks as using SMB2 they have gone as far as implementing SMB2.1 and merely list it only as SMB2 for simplicity and due to the fact there is not a huge different between SMB2 and SMB2.1
See http://en.wikipedia.org/wiki/Server_Message_Block#SMB_2_and_3