When used with a Zoom X5 router as the DHCP server, FreeNAS is allocated a suitable IP address (e.g. 10.0.0.14), but does not find the correct IP address for the DNS server (default 10.0.0.2).
Looking at the log file of errors (see attached), FreeNAS is trying to send something to IP address 10.0.0.255 which does not exist.
Because the FreeNAS computer name is not sent to the DNS Server, it does not appear in the 'Computers Near Me' window of WinXP, 2K, or 98SE.
Also, it does not appear in the 'Windows Shares' of Ubuntu Linux 6.06.
Note that it is possible to find the FreeNAS device by typing the DHCP allocated IP address into the Windows Run command, but this relies on knowing the IP address which can change (e.g. after a shut-down). Also, using this method produces unusual results in Windows Explorer, with the FreeNAS drives in the right-hand window, but not in the computers / drives / directories tree in the left-hand window!
If FreeNAS is changed from using the DHCP server to having a fixed IP address (e.g. 10.0.0.100/24) and the gateway is set to 10.0.0.2, FreeNAS works correctly and appears in the network shares of Windows and Ubuntu.
For correct operation, FreeNAS should find the DHCP Server, the Gateway, and the DNS Server at 10.0.0.2/24.
Note that the Zoom X5 router works correctly with other linux computers, including a Samba server with Ubuntu 5.10. Hence, this bug must be in FreeNAS or BSD linux.
Log in to post a comment.