Differences

This shows you the differences between two versions of the page.

--- cifs_client [2021/01/28 23:27]
hogwild
+++ cifs_client [2021/09/22 22:10]
hogwild
@@ Line 1: / Line 1: @@
 ====== CIFS Client ======
-The CIFS Client menu enables and configures Tomato's CIFS Client function. This allows your Tomato router to read / write to CIFS network shares. CIFS, the Common Internet File System is one version of Microsoft's SMB networking protocol. Among other things, CIFS originally provided filesharing to Windows computers. However, in time, other systems, including Tomato, grew to be able to access CIFS network / SMB shares.
+The CIFS Client menu enables and configures FreshTomato's CIFS Client function. The CIFS client is a redirector, which allows your FreshTomato router to read / write to CIFS network shares. 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 network / SMB shares.
-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 "condos" share on the "Engineering" host, you'd use the syntax [[\\Engineering\condos|]] . How well DNS names in UNC paths should work will depend on what kind of name resolution services are configured on your network. Having a DNS server, or using Tomato as a DNS server can increase the changes UNC paths will work with DNS names. When in doubt, use an IP address in the UNC pathname, but make sure it's a static or DHCP Reserved address. Otherwise, it might change, and the CIFS client connection might fail.
+CIFS clients use the UNC (Universal Naming Convention) syntax for connecting to shares. This takes the form <nowiki>\\computername\sharename .</nowiki> For example, if you wanted to access the "condos" share on the "Engineering" host, you'd use the syntax <nowiki>\\Engineering\condos</nowiki> . How well DNS names in UNC paths should work will depend on what kind of name resolution services are configured on your network. Having a DNS server, or using FreshTomato as a DNS server can increase the changes UNC paths will work with DNS names. When in doubt, use an IP address in the UNC pathname, but make sure it's a static or DHCP Reserved address. Otherwise, it might change, and that might make the CIFS client connection fail.
 =====   =====
 <font 20px/inherit;;inherit;;inherit>/cifs1</font>
+[[https://wiki.freshtomato.org/lib/exe/detail.php?id=cifs_client&media=a4991ee88fd37428162cdb3b5f60caf4.png|{{:a4991ee88fd37428162cdb3b5f60caf4.png}}]]
 **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, 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 (Static) DHCP Reservation address, and not a dynamic one. Otherwise, the address may change, and the Tomato may fail to connect to the CIFS share. The CIFS protocol can be routed, however, it's a complex topic, but it is not recommended to you use that here. We suggest using only CIFS shares on the LAN.
+**UNC:** Here, enter the UNC pathname, as described above, 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 (Static) 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.
 **Netbios Name: **Here, the Netbios Name of the first host to which you wany to connect. (Default: blank).
@@ Line 26: / Line 28: @@
 <font 20px/inherit;;inherit;;inherit>/cifs2</font>
+[[https://wiki.freshtomato.org/lib/exe/detail.php?id=cifs_client&media=b4e43714ca4bc42ccaf700e7d6f7a042.png|{{:b4e43714ca4bc42ccaf700e7d6f7a042.png}}]]
 **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, 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 (Static) DHCP Reservation address, and not a dynamic one. Otherwise, the address may change, and the Tomato may fail to connect to the CIFS share. The CIFS protocol can be routed, however, it's a complex topic, but it is not recommended to you use that here. We suggest using only CIFS shares on the LAN.
+UNC: Here, enter the UNC pathname, as described above, 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 (Static) 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.
 **Netbios Name: **Here, the Netbios Name of the second host to which you wany to connect. (Default: blank).

FreshTomato Wiki

User Tools

Site Tools

Differences

Page Tools