Differences

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

--- admin-cifs [2024/10/21 01:19] – -Condense, formatting hogwild
+++ admin-cifs [2024/10/21 01:38] (current) – -Replaced screenshots with ones done in Tomato theme hogwild
@@ Line 11: / Line 11: @@
  \\
-[[https://wiki.freshtomato.org/lib/exe/detail.php?id=cifs_client&media=a4991ee88fd37428162cdb3b5f60caf4.png|{{:a4991ee88fd37428162cdb3b5f60caf4.png?772}}]]
+ \\ {{::administration-cifs_client-cifs1-2024.1.png?656}}
- \\ **Enable:** This checkbox enables or disables the CIFS client function for the first share you wish to access. (Default: Disabled).
+ \\ **Enable:** enables or disables the CIFS client 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 CIFS shares on the LAN only.
+**UNC:** 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 it.
+The CIFS protocol can be routed, however, that's a complex topic. It is not advisable to use shares across routes. It is best to use CIFS shares on the LAN only.
  \\
-**Netbios Name: **Here, the Netbios Name of the first host to which you want to connect. (Default: blank).
+**Netbios Name: **the Netbios Name of the first host to which you want to connect.
+(Default: blank).
  \\
@@ Line 29: / Line 37: @@
  \\
-**Password:** Here, enter the password of an account allowed to access the first CIFS share. (Default: blank).
+**Password:** the password of an account allowed to access the first CIFS share.
-**Domain:** This field is usually left blank on home peer to peer networks. If the network includes an actual domain, this domain name should be included. (Default: blank)
+(Default: blank).
  \\
-**Execute When Mounted:** Here, you can specify the name of a script to be executed when the first CIFS share is mounted. This is usually left blank and is used by advanced users. (Default: blank).
+**Domain:** This is usually left blank on home/peer-to-peer networks. If the network does include a domain, it should be included.
+(Default: blank)
  \\
-**Security:** Here, select the CIFS client authentication protocol which will be required to connect to the first CIFS share.
+**Execute When Mounted:**  specify the name of a script to be executed when the first CIFS share is mounted.
- \\  \\  \\
+This is usually left blank and is used by advanced users. (Default: blank).
-[[https://wiki.freshtomato.org/lib/exe/detail.php?id=cifs_client&media=b4e43714ca4bc42ccaf700e7d6f7a042.png|{{:b4e43714ca4bc42ccaf700e7d6f7a042.png?869}}]]
+ \\
- \\ **Enable:** enables or disables the CIFS client function for the second share to access. (Default: Disabled).
+**Security:** Here, select the CIFS client authentication protocol required to connect to the first CIFS share.
- \\
+ \\   \\ {{::administration-cifs_client-cifs2-2024.1.png?657}}
+ \\  \\
-**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 CIFS shares on the LAN only.
+**Enable:** enables or disables the CIFS client function for the second share to access. (Default: Disabled).
  \\
-**Netbios Name: **Here, enter the Netbios Name of the second host to which you want to connect. (Default: blank).
+**UNC:** 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's a static or DHCP Reservation address, 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 CIFS shares on the LAN only.
  \\
-**Username:** Here, enter the username of an account allowed to access the the second CIFS share. (Default: blank).
+**Netbios Name: **the Netbios Name of the second host to which to connect.
+(Default: blank).
  \\
-**Password:** Here, enter the password of an account allowed to access the second CIFS share. (Default: blank).
+**Username:** the username of an account allowed to access the the second CIFS share.
+(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)
+**Password:** the password of an account allowed to access the second CIFS share.
+(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).
+**Domain:** This is usually left blank on home (workgroup/homegroup) peer-to-peer networks.
+If the network includes an actual domain, the domain name should be included. (Default: blank)
  \\
-**Security:** From this menu, you select the CIFS client authentication protocol which will be required to connect to the second CIFS share.
+**Execute When Mounted:** Here, specify a script to executed as soon as the second CIFS share is mounted.
+This is usually left blank and only used by advanced users. (Default: blank).
  \\
+**Security:** lets you select the CIFS client authentication protocol required to connect to the second CIFS share.
+\\  \\  \\

FreshTomato Wiki

User Tools

Site Tools

Differences

Page Tools