DHCP 'Removed due to conflict'

[pkley]

Because Fortinet won't post bug lists...

Known bug in 5.2, seems that it handed out a DHCP address to a new device when the old device hadn't timed out and had only been powered off for a day. When it came back on the network the device said 'ip conflict', asked for a new IP, the FGT said - 'ok here you go' but then went thru every IP left in the range. Had to dhcp lease-clear to resolve.

It's the second device I had this happen on.

[Carlos_A_Almeida]

pkley wrote:

Because Fortinet won't post bug lists...

Known bug in 5.2, seems that it handed out a DHCP address to a new device when the old device hadn't timed out and had only been powered off for a day. When it came back on the network the device said 'ip conflict', asked for a new IP, the FGT said - 'ok here you go' but then went thru every IP left in the range. Had to dhcp lease-clear to resolve.

It's the second device I had this happen on.

Try to see the parameter: conflicted-ip-timeout 

http://docs-legacy.fortinet.com/fgt/handbook/cli_html/index.html#page/FortiOS%205.0%20CLI/config_sys...

Maybe isn't properly configured.