After upgrading one of my two FreeNAS boxes to FreeNAS-9.3-STABLE-201506162331 I'm getting the following error repeated in my logs on my server running FreeNAS-9.3-STABLE-201506042008.
Jun 21 11:35:23 zar nmbd[97875]: process_lanman_packet: Discarding datagram from IP 192.168.2.114. Source name ZARABETH<00> is one of our names !
Setup:
Production host: ZAR 192.168.2.117 running FreeNAS-9.3-STABLE-201506042008, physical server.
Development host: ZARABETH 192.168.2.114 running FreeNAS-9.3-STABLE-201506162331, virtual server on ESX 6.0.
Scenario:
Both production and development were running FreeNAS-9.3-STABLE-201506042008 and I had no issues. I upgraded development to FreeNAS-9.3-STABLE-201506042008 and almost immediately I got the above referenced error in my logs on production, repeating every minute. I searched the GUI for name collisions and also looked at the smb4.conf file to confirm no duplicate name references existed. I see no issues. On a whim, I reverted development to FreeNAS-9.3-STABLE-201506042008 and the errors stopped.
Any advice on what could be wrong?
Jun 21 11:35:23 zar nmbd[97875]: process_lanman_packet: Discarding datagram from IP 192.168.2.114. Source name ZARABETH<00> is one of our names !
Setup:
Production host: ZAR 192.168.2.117 running FreeNAS-9.3-STABLE-201506042008, physical server.
Development host: ZARABETH 192.168.2.114 running FreeNAS-9.3-STABLE-201506162331, virtual server on ESX 6.0.
Scenario:
Both production and development were running FreeNAS-9.3-STABLE-201506042008 and I had no issues. I upgraded development to FreeNAS-9.3-STABLE-201506042008 and almost immediately I got the above referenced error in my logs on production, repeating every minute. I searched the GUI for name collisions and also looked at the smb4.conf file to confirm no duplicate name references existed. I see no issues. On a whim, I reverted development to FreeNAS-9.3-STABLE-201506042008 and the errors stopped.
Any advice on what could be wrong?