How to kick a DHCP user form Mountain Lion Server App?

I have a ghost dynamic DHCP client on my Mountain LIon server app DHCP which conflicts with the actual server IP. How do I kick this DHCP user? I am trying to create a static IP mapped to the server so this doesn't happen again, but it will not let me because the conflicting static IP is persisting.
Jeremy LeysTechnical LeadAsked:
Who is Participating?
 
nappy_dConnect With a Mentor Commented:
Please try the following:

1.

disconnect the Ethernet cable from your server

2.

configure the server to have the static IP address

3.

adjust your dhcp scope. As am example, if you want the server to have the ip 192.168.1.10, adjust your dhcp server

4.

scope to be 192.168.1.50-150. This will make all machines get an ip and not use your server's IP.

5.

it is probably a good idea to also reboot all computers to force them to request a new IP address.
0
 
Jeremy LeysTechnical LeadAuthor Commented:
How do I kick dynamic DHCP user + os x mountain lion server app DHCP.

Persisting after, restarting router, resetting PRAM and restarting server. I even powered off the server and turned it back on.

I turned off all WiFi access points, but still persisting GHOST session.
0
 
Jeremy LeysTechnical LeadAuthor Commented:
Or is there a way to renew DHCP leases of all clients from the Mountain Lion DHCP Server App?
0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
nappy_dCommented:
Are you saying there is a computer in your network that has the same IP of your DHCP server?

If this is the case, it means the machine has a static IP or you have configured you DHCP scope whic may include your server's IP address.
0
 
Jeremy LeysTechnical LeadAuthor Commented:
I have attached a screen shot; not a computer, an Android phone, I have since disconnected all WiFi access points to the network and the DHCP client list still shows the Android phone with conflicting IP address 192.168.1.56.

I think the reason that this happened was that the server was manually assigned an IP address that was not static assigned in DHCP in the Server App.

The issue I now have is that I can setup a static address for the server in DHCP but when I restart the server the static entry for the server is not retained. It seems that the DHCP lease has not expired for the Android device. Which is why I refer to it as a ghost session. Is there a way to force DHCP lease for all clients to expire or kick individual devices from the server?
Screen-Shot-2014-08-01-at-7.45.24-am.png
0
 
Jeremy LeysTechnical LeadAuthor Commented:
Thanks very good solution, solved my problem.
0
All Courses

From novice to tech pro — start learning today.