User Tools
admin-cifs
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| admin-cifs [2022/01/12 19:35] – grammar hogwild | admin-cifs [2023/08/01 23:25] (current) – pedro | ||
|---|---|---|---|
| Line 13: | Line 13: | ||
| \\ **Enable:** This checkbox enables or disables the CIFS client function for the first share you wish to access. (Default: Disabled). | \\ **Enable:** This checkbox enables or disables the CIFS client function for the first share you wish to access. (Default: Disabled). | ||
| - | **UNC:** Here, enter the UNC pathname for the first 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, the address may change, and the FreshTomato may fail to 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 routes here. We suggest using only CIFS shares on the LAN. | + | **UNC:** Here, enter the UNC pathname for the first 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, the address may change, and the FreshTomato may fail to 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 routes here. We suggest using CIFS shares on the LAN only. |
| - | **Netbios Name: **Here, the Netbios Name of the first host to which you wany to connect. (Default: blank). | + | **Netbios Name: **Here, the Netbios Name of the first host to which you want to connect. (Default: blank). |
| **Username: | **Username: | ||
| Line 27: | Line 27: | ||
| **Security: | **Security: | ||
| - | \\ | + | |
| [[https:// | [[https:// | ||
| - | \\ | + | |
| - | **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, |
| - | + | ||
| - | 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). | ||
| Line 47: | Line 45: | ||
| **Execute When Mounted:** Here, you can specify a script to be executed as soon as the second CIFS share is mounted. This is usually left blank and is used by advanced users. (Default: blank). | **Execute When Mounted:** Here, you can specify a script to be executed as soon as the second CIFS share is mounted. This is usually left blank and is used by advanced users. (Default: blank). | ||
| - | **Security: | + | **Security: |
| \\ | \\ | ||
admin-cifs.1642016106.txt.gz · Last modified: 2022/01/12 19:35 by hogwild
Page Tools
