Is there a trick I need to do to get my windows machines to get and address from my OS X Server?
Sorry I was a bit frazzled when I wrote this. But the windows PC's are running windows 8 and are stuck on unidentified network and will not get and address. But my Macbooks will get and address fine.
Hi
In Server app for the DHCP server settings | Networks | your subnet choose Edit. Then click Edit next to DNS settings and in the 'Provide these search domains to connected clients' entry box type in your domain.
Setting this helped another person with mixed Mac / Windows client environment.
They are all on the same subnet. The OSX lion server was the only DHCP server. I recently turned off DHCP and just using the router for DHCP until I can figure it out.
I am just using a work group for the windows machines. Is there a way I can associate them with my OSX server like a domain? I am sorry I am extremely new to the OSX server system.
All my other devices work fine Ex: iPad's, Xbox 360, PS3, Phones.
DHCP works on a lower level (so to speak) then Windows workgroups or domains or Apple Bonjour (Zero Conf) networking.
Basically when you turn on a machine (either Windows or Mac) which has the setting of get IP address automatically (not manual IP address set) it sends out a 'broadcast' to the network asking for any DHCP server to respond. The system which is setup as a DHCP server should then respond and then there is a communication between the two systems and the client machine is assigned an iP address and is told other info like the gateway address and DNS server.
Did you setup the search domains on the DHCP server on OS X? Some Windows users have said this solved their Windows client DHCP problems.
On the Windows client machines in a command prompt if you type "ipconfig /renew" does the Windows machine complain about not finding DHCP server?
If you give Windows machine temporarily an IP address can you ping the IP address of the OS X Server (running DHCP).
I have been able to ping the server when I give it a Static Address. I have tried the /release /renew for ipconfig. I will add the workgroup to the search domains when I get back to the house and update with some screen shots once I get a chance.
Hello!
Did the search-domain/workgroup fix work? I am having troubble connecting a windows client to my mac-driven network. It's making my head explode so bad...Only apple products work, but try Windows or Android ont hat network and they fail. They don't get an IP and such, they get nothing.
Regards, Ingwie
Sadly, I never did get it to work so I just switched DHCP to my router. 😟
i have had the same issue. Windows clients (XP, 2003, 7) just could not receive an address from the dhcp server.
I think i got it solved by removing an invalid line in my dhcp server config file.
This is what i did:
<key>dhcp_domain_name</key>
<string></string>
alternatively, you can fill the dhcp_domain_name with a valid domain name suffix. Both options seem to have worked just fine for me.
<key>dhcp_domain_name</key>
<string>whatever.mydomain.com</string>
Tips:
also see the official documentation:
https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/ man8/bootpd.8.html
dhcp_domain_name
The default DNS domain name (option code 15). If this property is notpresent, the server will supply its own default domain name (if available).
I was able to get DHCP working by modifying the hostname of my Mac Mini from local to "computername".home.net. Once I did that it updated the services for me. After that I was able to get DHCP on my Windows 7 SP1 computer.
Fuzzylr wrote:
I was able to get DHCP working by modifying the hostname of my Mac Mini from local to "computername".home.net. Once I did that it updated the services for me. After that I was able to get DHCP on my Windows 7 SP1 computer.
OS X Server requires correct local DNS, and if you're really using that home.net. domain here, that's very likely not correct DNS for your network. (I'm here assuming that you don't have home.net registered, though you might have permission of the registrar to use a subdomain of that for some other purpose?)
To verify DNS on OS X Server, launch Terminal.app from Applications > Utilities on the server, and enter the following harmless diagnostic command:
sudo changeip -checkhostname
You'll need an administrative password for the sudo, might get a one-time message for the use of sudo, then some information on the local network, and finally an indication that no changes are required, or that there are network or DNS server issues to be reviewed and addressed.
yes, FromOZ is most definitely correct! Adding our domain to the DHCP subnet settings resolved the issue for us 🙂
Windows will not get a DHCP address from my OS X Server
