Hi,
few days back I upgraded FreeNAS 9.2.1.4 to 9.2.1.5 and then one PC on my network started reporting IP address conflict with another system. After quick investigation I found that the conflicting system was FreeNAS with only port 22 open (I simply shut the server down and the conflict was gone).
What's strange to me: This exact FreeNAS before upgrade to the latest version was running for months without any problems always sitting on IP 192.168.1.178. After upgrade it's IP was still the same, but also it had taken/stolen IP .180 from another computer (DHCP lease).
Even after setting IP .180 on the PC to manual setup, the problem still occured. I even set NIC MAC and IP of that PC on DHCP server, but the problem still exists.
Why is FreeNAS using two IPs (the server has two NICs, but only one has been set and has a cable plugged in). MAC of that ghost IP is 02:90:05:00:09:0b, which doesn't exist by the way :D
Why is it using .180 which was possibly not given by the DHCP server, because it's been leased to another computer?
Or what am I missing here? ;)
Thank you.
few days back I upgraded FreeNAS 9.2.1.4 to 9.2.1.5 and then one PC on my network started reporting IP address conflict with another system. After quick investigation I found that the conflicting system was FreeNAS with only port 22 open (I simply shut the server down and the conflict was gone).
What's strange to me: This exact FreeNAS before upgrade to the latest version was running for months without any problems always sitting on IP 192.168.1.178. After upgrade it's IP was still the same, but also it had taken/stolen IP .180 from another computer (DHCP lease).
Even after setting IP .180 on the PC to manual setup, the problem still occured. I even set NIC MAC and IP of that PC on DHCP server, but the problem still exists.
Why is FreeNAS using two IPs (the server has two NICs, but only one has been set and has a cable plugged in). MAC of that ghost IP is 02:90:05:00:09:0b, which doesn't exist by the way :D
Why is it using .180 which was possibly not given by the DHCP server, because it's been leased to another computer?
Or what am I missing here? ;)
Thank you.