This shows you the differences between two versions of the page.
Next revision | Previous revisionLast revisionBoth sides next revision | ||
admin-cifs [2022/01/05 13:10] – created rs232 | admin-cifs [2022/02/17 15:48] – grammar "LAN only" hogwild | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== CIFS Client ====== | ====== CIFS Client ====== | ||
- | The CIFS Client menu enables and configures FreshTomato' | + | The CIFS Client menu enables and configures FreshTomato' |
- | CIFS clients use the UNC (Universal Naming Convention) syntax for connecting to shares. This takes the form < | + | CIFS, the Common Internet File System is an older implementation of Microsoft's SMB networking protocol. Among other things, CIFS originally provided filesharing to Windows computers. However, in time, other systems, including FreshTomato, grew to be able to access |
- | ===== ===== | + | CIFS clients use the UNC (Universal Naming Convention) syntax for connecting to shares. This takes the form %%\\computername\sharename .%% For example, if you wanted to access the " |
- | <font 20px/ | + | \\ |
[[https:// | [[https:// | ||
- | **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, as described above, | + | **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 21: | Line 21: | ||
**Password: | **Password: | ||
- | **Domain:** This field is usually left blank on home (workgroup or homegroup) | + | **Domain:** This field is usually left blank on home peer to peer networks. If the network includes an actual domain, |
- | **Execute When Mounted:** Here, you can specify the name of a script to be executed | + | **Execute When Mounted:** Here, you can specify the name of a script to be executed |
- | **Security: | + | **Security: |
- | <font 20px/ | + | |
[[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, as described above, | + | **UNC:** Here, enter the UNC pathname for the second CIFS share to which you want to connect. For example, |
- | **Netbios Name: **Here, the Netbios Name of the second host to which you wany to connect. (Default: blank). | + | **Netbios Name: **Here, |
**Username: | **Username: | ||
Line 43: | Line 43: | ||
**Domain:** This field is usually left blank on home (workgroup or homegroup) peer to peer networks. If the network includes an actual domain, the domain name should be included. (Default: blank) | **Domain:** This field is usually left blank on home (workgroup or homegroup) peer to peer networks. If the network includes an actual domain, the domain name should be included. (Default: blank) | ||
- | **Execute When Mounted:** Here, you can specify | + | **Execute When Mounted:** Here, you can specify a script to be executed as soon as the second CIFS share is mounted. This is usually |
**Security: | **Security: | ||
+ | |||
+ | \\ | ||