problem with DHCP and sysadmin
Hi All,
OK, a quick question....I am at a major University, and the sysadmin has a strong dislike of Macs (I had to fight just to get t allowed on the network).
The problem is this - he claims that the Mac, in both OS 9 and OS X versions, "steals" IP addresses from other machines using DHCP. He also claims that this can and does happen even when the mac is not rebooting, but I would like to ignore that part of his claim for the moment, because that seems patently absurd.
So my question is this - DOES OS X behave badly on Windows-run DHCP servers? Please, I am NOT looking for "that guy is a jerk" etc, but am not saavy enough to know the particulars of DHCP networking in its various flavors (someone told me that this would not be a problem if the sysadmin either used a *nix box as the DHCP server or properly configured his Windows DHCP server, but my root question is simply IS this possible?)
Thanks,
Fish
OK, a quick question....I am at a major University, and the sysadmin has a strong dislike of Macs (I had to fight just to get t allowed on the network).
The problem is this - he claims that the Mac, in both OS 9 and OS X versions, "steals" IP addresses from other machines using DHCP. He also claims that this can and does happen even when the mac is not rebooting, but I would like to ignore that part of his claim for the moment, because that seems patently absurd.
So my question is this - DOES OS X behave badly on Windows-run DHCP servers? Please, I am NOT looking for "that guy is a jerk" etc, but am not saavy enough to know the particulars of DHCP networking in its various flavors (someone told me that this would not be a problem if the sysadmin either used a *nix box as the DHCP server or properly configured his Windows DHCP server, but my root question is simply IS this possible?)
Thanks,
Fish
Comments
By default, a dhcp client (your mac and the PC's) will shout for a dhcp server. The server will answer and say here I am, you can have this address. (Note, more than one DHCP server can answer at this time) The client then picks one, and tells that dhcp server I'd like this one. If no one else stole that address in the mean time (a few milliseconds) then the server sends you an acknowledgement. Your client sets up your TCP/IP with the info, and the server tags the address as being used.
It is upto the server to keep track of used addresses.
Renewals. Normally the default lease time for addresses given by a DHCP server is 8 days. After 4 days your client will ask for a renew. If successful, you go back upto the full 8 days. This is why if you use the network regularly, you will normally keep the same address.
If you have not been able to contact the original DHCP server for a renew at 7 days, then your client tries a new broadcast to any server.
At exactly 8 days, if you have not been able to contact any DHCP servers, your client should stop using the address immediately.
Although this info I got specifically from a MS course, I think it applies to any DHCP client / server setup as its all based on the same standards.
Hope this helps.