Quote Originally Posted by maxIT
I've solved this issue on the router-side instead of client-side.
I've an 11pc LAN network with static addresses: 192.168.0.10 to 192.168.0.20.
I've setted my d-link dsl500 router to assign dhcp range ip between 192.168.0.2 to 192.168.0.9, so if some laptop come in my lan it doesn't conflict with statics_ip_desktops.
Yes, this should work and is in fact the "last ditch fix" that I listed above. But the problem is that Knoppix or other live CDs also get the DHCP address this way. I find it is better for me if I know what IP address Knoppix is assigned. That way if I boot it on my Desktop I know it will be 192.168.0.100, if I boot it on my notebook I know it will be 192.168.0.103 and so on. This is particularly handy as I move between systems trying to resolve some networking issues, accessing one system from another by FTP or some other technology and what to be able to plug in IP addresses that are just natural to me, without having to move back to the Live CD systems and look up what IP address they got after their last reboot. Chip should be able to at the very least determine why the router is handing out duplicate IP addresses (if it even is his own router), and depending on the router may be able to use some router features to hand out IP addresses in a less than random way.