This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
admin-cifs [2022/01/12 19:39] – hogwild | admin-cifs [2022/01/16 01:22] – -bolded UNC hogwild | ||
---|---|---|---|
Line 33: | Line 33: | ||
\\ **Enable:** This checkbox enables or disables the CIFS client function for the second share you wish to access. (Default: Disabled). | \\ **Enable:** This checkbox enables or disables the CIFS client function for the second share you wish to access. (Default: Disabled). | ||
- | UNC: Here, enter the UNC pathname for the second CIFS share to which you want to connect. For example, \\192.168.1.34\Logs . (Default: blank). If you use an IP address as part of the UNC pathname, make certain it is a static or DHCP Reservation address, and not a dynamic one. Otherwise, if the address changes, FreshTomato may not connect to the CIFS share. The CIFS protocol can be routed, however, that's a complex topic. It is not recommended you use shares across routers here. We suggest using only CIFS shares on the LAN. | + | **UNC:** Here, enter the UNC pathname for the second CIFS share to which you want to connect. For example, \\192.168.1.34\Logs . (Default: blank). If you use an IP address as part of the UNC pathname, make certain it is a static or DHCP Reservation address, and not a dynamic one. Otherwise, if the address changes, FreshTomato may not connect to the CIFS share. The CIFS protocol can be routed, however, that's a complex topic. It is not recommended you use shares across routers here. We suggest using only CIFS shares on the LAN. |
**Netbios Name: **Here, enter the Netbios Name of the second host to which you want to connect. (Default: blank). | **Netbios Name: **Here, enter the Netbios Name of the second host to which you want to connect. (Default: blank). |