if the device with static IP is off and the DHCP server receives a request for IP it can assign to the client the same IP you set as static, if you power-on the machine it creates an IP conflict.
that's where i'm getting confused, surely as soon as the static ip pc is turned on and requests it's ip the dhcp server recognises it's already issued that ip and kicks the other pc off the network requiring it to ask for a new ip or sends an ip update notice/request to the conflicting pc to issue it with a new ip so the static ip device can use it's static ip and and the other device seamlessly gets a new ip automatically therefore avoiding any problems with conflicts.
like i said even though i've set static ip's for years i've never had a conflict ever as far as i remember, so thought the only way to get one was to issue the same static ip to 2 pc's or if there was a serious problem with the dhcp server where it was not doing it's job correctly, and why i was wondering, because it's the first time i've heard anyone recommend setting a static ip outside the dhcp range, if setting static ip's outside the dhcp range was the new way of setting things up or if that's always been best practise and i've been doing it wrong and should remember to change the way i do things and also recommend to people even though at the moment i really don't see the need to set a static ip outside dhcp range if it's doing it's job correctly, as it should be doing.
Edited by terry1966, 01 August 2017 - 05:59 AM.