Question is this a bug that needs to be filed?
Feb 11 22:12:19 freenas smbd[24674]: [2014/02/11 22:12:19.534761, 0] ../source3/lib/util_sock.c:941(matchname)
Feb 11 22:12:19 freenas smbd[24674]: matchname: host name/name mismatch: 192.168.1.8 != (NULL)
Feb 11 22:12:19 freenas smbd[24674]: [2014/02/11 22:12:19.534802, 0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
Feb 11 22:12:19 freenas smbd[24674]: matchname failed on 192.168.1.8
Im seeing this quite a bit, its from my Sonos since the upgrade to 9.2.1.
But some other machines are also doing it.
Also I get this report every day:
Feb 11 17:07:01 freenas kernel: ugen0.3: <vendor 0x0451> at usbus0
Feb 11 17:07:01 freenas kernel: uhub4: <vendor 0x0451 product 0x8043, class 9/0, rev 2.10/1.00, addr 3> on usbus0
Feb 11 17:07:01 freenas kernel: uhub4: MTT enabled
Feb 11 17:07:02 freenas kernel: uhub4: 4 ports with 4 removable, self powered
Feb 11 22:06:14 freenas kernel: ugen0.3: <vendor 0x0451> at usbus0 (disconnected)
Feb 11 22:06:14 freenas kernel: uhub4: at uhub2, port 2, addr 3 (disconnected)
Feb 11 22:06:24 freenas kernel: ugen0.3: <vendor 0x0451> at usbus0
Feb 11 22:06:24 freenas kernel: uhub4: <vendor 0x0451 product 0x8043, class 9/0, rev 2.10/1.00, addr 3> on usbus0
Feb 11 22:06:24 freenas kernel: uhub4: MTT enabled
Feb 11 22:06:29 freenas kernel: uhub_attach: getting USB 2.0 HUB descriptor failed,error=USB_ERR_TIMEOUT
Feb 11 22:06:29 freenas kernel: device_attach: uhub4 attach returned 6