Smb2Client

Performs operations on an SMB2 server.

Synopsis

Smb2Client <subcommand>

Subcommands

For help on a subcommand, use Smb2Client <subcommand> -h

Smb2Client enumnics

Queries the server for a list of network interfaces.

Synopsis

Smb2Client enumnics [options] <UncPath>

Parameters

Options

Authentication

Authentication (Kerberos)

Authentication (NTLM)

Client Behavior

Connection

Output

Details

Clients generally use this functionality to establish multiple channels.

The <UncPath> parameter specifies the target of the command using the format \<server>[:<port>]\<share>[\<path>] where <port> is an integer specifying the port to connect to. If -HostAddress is specified, Smb2Client enumnics resolves it either as an IP address (IPv4 or IPv6) or a DNS name. If -HostAddress is not specified, <server> is resolved. In either case, the resulting IP addresses may be filtered by address family using -4 or -6. In either case, <server> is used to refer to the server within the SMB2 protocol.

Smb2Client enumnics supports both NTLM and Kerberos authentication. The -UserName and -Password parameters apply to both NTLM and Kerberos. You may also specify -NtlmHash for NTLM. Each authentication mechanism has a variety of parameters to customize the negotiation.

Kerberos is only enabled if you specify -kdc with the name or address of the KDC. If you specify a name, Smb2Client enumnics applies the same filtering rules for -4 and -6.

Smb2Client enumopenfiles

Lists files open on the server.

Synopsis

Smb2Client enumopenfiles [options] <ServerName>

Parameters

Options

Authentication

Authentication (Kerberos)

Authentication (NTLM)

Client Behavior

Connection

Output

Details

Use -OpenBy to filter the results by the name of the user that has the file open. The filtering is performed by the server. The user name should be only the name of the user without the domain. Including the domain will generate a warning and likely cause the all results to be filtered out.

Use -BasePath to specify the path to filter by. The filtering is performed by the server, which checks whether the path of each open file starts with the base path. This must be an absolute path to succeed. For files, the path must start with X: where X is the drive letter. To search for named pipes, the path must begin with a backslash (e.g. \srvsvc). Since -BasePath uses string filtering, the path need not be a valid object. For example, filtering by ‘C:\Win’ would include results under C:\Windows. Wildcards are not supported.

Smb2Client enumsessions

Lists active sessions on the server.

Synopsis

Smb2Client enumsessions [options] <ServerName>

Parameters

Options

Authentication

Authentication (Kerberos)

Authentication (NTLM)

Client Behavior

Connection

Output

Details

Use -ClientComputer and -ClientUserName to filter the results. The filtering is processed on the server. The protocol requires the computer name to begin with \, even for IP addresses. However, if you neglect to do this, Smb2Client enumsessions prepends \ to the name you provide. The user name provided to -ClientUserName should not contain a domain. If it does, you’ll receive a warning, but the value will still be passed to the server.

Smb2Client enumshares

Lists shares on the server

Synopsis

Smb2Client enumshares [options] <ServerName>

Parameters

Options

Authentication

Authentication (Kerberos)

Authentication (NTLM)

Client Behavior

Connection

Output

Details

The Server service returns different levels of share information. Anything about Level1 requires administrator access. By default, Smb2Client enumshares attempts to query for Level502; if this fails, it falls back to Level1, returning a subset of the available fields. You may specify one or more levels to override this default, or specify the desired fields. In the latter case, Smb2Client enumshares determines which levels to query to populate the requested fields.

Examples

Example 1 - List basic share info

Smb2Client enumshares LUMON-FS1 -UserName marks@LUMON -Password She's@live!! -Kdc LUMON-DC1

Example 2 - List Level2

Smb2Client enumshares LUMON-FS1 -UserName milchick@LUMON -Password Br3@kr00m! -Kdc LUMON-DC1 -OutputFields ShareName, Type, Path

Since Path requires Level2, the command attempts to query Level2, falling back to Level1 if necessary

Example 3 - List security descriptors

Smb2Client enumshares LUMON-FS1 -UserName milchick@LUMON -Password Br3@kr00m! -Kdc LUMON-DC1 -OutputFields ShareName, Type, Path, SecurityDescriptor

Smb2Client enumsnapshots

Lists the available snapshots for a file or directory.

Synopsis

Smb2Client enumsnapshots [options] <UncPath>

Parameters

Options

Authentication

Authentication (Kerberos)

Authentication (NTLM)

Client Behavior

Connection

Output

Details

The <UncPath> parameter specifies the target of the command using the format \<server>[:<port>]\<share>[\<path>] where <port> is an integer specifying the port to connect to. If -HostAddress is specified, Smb2Client enumsnapshots resolves it either as an IP address (IPv4 or IPv6) or a DNS name. If -HostAddress is not specified, <server> is resolved. In either case, the resulting IP addresses may be filtered by address family using -4 or -6. In either case, <server> is used to refer to the server within the SMB2 protocol.

Smb2Client enumsnapshots supports both NTLM and Kerberos authentication. The -UserName and -Password parameters apply to both NTLM and Kerberos. You may also specify -NtlmHash for NTLM. Each authentication mechanism has a variety of parameters to customize the negotiation.

Kerberos is only enabled if you specify -kdc with the name or address of the KDC. If you specify a name, Smb2Client enumsnapshots applies the same filtering rules for -4 and -6.

Smb2Client enumstreams

Lists the data streams of a file or directory.

Synopsis

Smb2Client enumstreams [options] <UncPath>

Parameters

Options

Authentication

Authentication (Kerberos)

Authentication (NTLM)

Client Behavior

Connection

Output

Details

The <UncPath> parameter specifies the target of the command using the format \<server>[:<port>]\<share>[\<path>] where <port> is an integer specifying the port to connect to. If -HostAddress is specified, Smb2Client enumstreams resolves it either as an IP address (IPv4 or IPv6) or a DNS name. If -HostAddress is not specified, <server> is resolved. In either case, the resulting IP addresses may be filtered by address family using -4 or -6. In either case, <server> is used to refer to the server within the SMB2 protocol.

Smb2Client enumstreams supports both NTLM and Kerberos authentication. The -UserName and -Password parameters apply to both NTLM and Kerberos. You may also specify -NtlmHash for NTLM. Each authentication mechanism has a variety of parameters to customize the negotiation.

Kerberos is only enabled if you specify -kdc with the name or address of the KDC. If you specify a name, Smb2Client enumstreams applies the same filtering rules for -4 and -6.

Smb2Client get

Gets the contents of a file.

Synopsis

Smb2Client get [options] <UncPath> [ <DestinationFileName> ]

Parameters

Options

Authentication

Authentication (Kerberos)

Authentication (NTLM)

Client Behavior

Connection

Output

Details

The <UncPath> parameter specifies the source file or directory to get via SMB. The <UncPath> may also include a wildcard pattern (with * or ?).

When copying a file, <DestinationFileName> is optional. If <DestinationFileName> is specified, Smb2Client get fetches the file and writes it to the destination file. If no destination file is specified, Smb2Client get writes the file to the console.

When copying a directory, <DestinationFileName> is required and must indicate a directory that already exists or is to be created. Smb2Client get traverses the directory tree, optionally filtering the contents by the wildcard specified in <UncPath>. The traversal is limited by -Depth, where a depth of 0 indicates that only objects in the source directory are copied and a depth of -1 indicates no practical limit. This includes files and directories in the sense that the subdirectories are created locally but not populated. Smb2Client get does not exclude empty directories, nor does it skip hidden files.

When copying the file, Smb2Client get fetches the file one chunk at a time. The default chunk size is 32,768 bytes, which loosely resembles using the COPY command on a command prompt. Use -ChunkSize to override the chunk size. The chunk size must not exceed the MaxReadSize of the server. You can view this by including the -Verbose switch.

When writing a file locally, Smb2Client get applies the CreationTimeUtc and LastWriteTimeUtc timestamps as well as applying the same file attributes as the source file.

The <UncPath> parameter specifies the target of the command using the format \<server>[:<port>]\<share>[\<path>] where <port> is an integer specifying the port to connect to. If -HostAddress is specified, Smb2Client get resolves it either as an IP address (IPv4 or IPv6) or a DNS name. If -HostAddress is not specified, <server> is resolved. In either case, the resulting IP addresses may be filtered by address family using -4 or -6. In either case, <server> is used to refer to the server within the SMB2 protocol.

Smb2Client get supports both NTLM and Kerberos authentication. The -UserName and -Password parameters apply to both NTLM and Kerberos. You may also specify -NtlmHash for NTLM. Each authentication mechanism has a variety of parameters to customize the negotiation.

Kerberos is only enabled if you specify -kdc with the name or address of the KDC. If you specify a name, Smb2Client get applies the same filtering rules for -4 and -6.

Examples

Example 1 - Print a file to the terminal

Smb2Client get \\SERVER\Share\File.txt -u DOMAIN\User -p Password

Copies File.txt from SERVER and prints to the terminal

Example 2 - Copies a file

Smb2Client get \\SERVER\Share\File.txt LocalFile.txt -u DOMAIN\User -p Password

Copies File.txt from SERVER and saves it to a local file named LocalFile.txt

Example 3 - Copies a directory tree of *.txt files

Smb2Client get \\SERVER\Share\*.txt LocalTextFiles -depth 20 -u DOMAIN\User -p Password

Copies all files matching *.txt from a directory tree, up to a depth of 20, into a local directory named LocalTextFiles

Example 4 - Copies a directory tree structure (no files)

Smb2Client get \\SERVER\Share\Departments Departments -depth -1 -u DOMAIN\User -p Password

Copies the directory structure with an unlimited depth without copying any files

Smb2Client ls

Lists the contents of a directory (including named pipes).

Synopsis

Smb2Client ls [options] <UncPath>

Parameters

Options

Authentication

Authentication (Kerberos)

Authentication (NTLM)

Client Behavior

Connection

Output

Details

Smb2Client ls sends a request to the SMB server for a directory listing. If <UncPath> is a directory, the contents of the directory are printed. If <UncPath> is a file, the directory information for that file is printed. If <UncPath> end with a wildcard pattern, only files matching the pattern are printed.
You may specify which fields to retrieve and print with the -Fields parameter. If any of the selected fields are not contained in the directory listing, an additional QUERY_INFO request is sent for each file. The default field set contains LinkTarget, which is not contained in this default set. When requestinf the additional fields, the access mask is calculated depending on the fields requested. For example, requesting the SACL requires ACCESS_SYSTEM_SECURITY; other security fields require READ_CONTROL. If this access check fails, none of the fields in that request are retrieved. The MaxAccess field sends a MAXIMAL_ACCESS_REQUEST when opening the file to retrieve additional info but does not itself result in an additional QUERY_INFO. A failure to retrieve the additional details does not result in an error, but the fields values are omitted from the output.

The <UncPath> parameter specifies the target of the command using the format \<server>[:<port>]\<share>[\<path>] where <port> is an integer specifying the port to connect to. If -HostAddress is specified, Smb2Client ls resolves it either as an IP address (IPv4 or IPv6) or a DNS name. If -HostAddress is not specified, <server> is resolved. In either case, the resulting IP addresses may be filtered by address family using -4 or -6. In either case, <server> is used to refer to the server within the SMB2 protocol.

Smb2Client ls supports both NTLM and Kerberos authentication. The -UserName and -Password parameters apply to both NTLM and Kerberos. You may also specify -NtlmHash for NTLM. Each authentication mechanism has a variety of parameters to customize the negotiation.

Kerberos is only enabled if you specify -kdc with the name or address of the KDC. If you specify a name, Smb2Client ls applies the same filtering rules for -4 and -6.

Examples

Example 1 - Listing the contents of a share (NTLM)

Smb2Client ls \\LUMON-FS1\MDR -u milchick -p Br3@kr00m!

Example 2 - Listing named pipes as anonymous

Smb2Client ls \\LUMON-FS1\IPC$ -anon

Example 3 - Listing named pipes

Smb2Client ls \\LUMON-FS1\IPC$ -u milchick -p Br3@kr00m!

Example 4 - Using Kerberos with a password

Smb2Client ls \\LUMON-DC1\sysvol -u milchick@LUMON -p Br3@kr00m! -Kdc LUMON-DC1

This command line specifies credentials along with the -Kdc option specifying the KDC to request a ticket from.

Example 5 - Listing the contents of a share with an alternate host name

Smb2Client ls \\SERVER\MDR -ha 10.66.0.13 -u milchick -p Br3@kr00m!

In this example, the command line specifies a host name differing from the server name to resolve for connecting to the server. When connecting to the target, the specified host address (10.66.0.13) is used. Once the TCP connection is established, the name ‘SERVER’ is used in the application protocol. In addition, the name SERVER is used as the SPN, both with NTLM and Kerberos; if strict SPN checking is enabled, this results in STATUS_ACCESS_DENIED.

Example 6 - Passing the hash

Smb2Client ls \\LUMON-FS1\MDR -u milchick -NtlmHash B406A01772D0AD225D7B1C67DD81496F

This command line provides the credentials as an NTLM hash.

Example 7 - Listing all columns

Smb2Client ls \\LUMON-FS1\C$\Windows -u milchick -Password Br3@kr00m! -OutputFields *

This command prints all file properties.

Example 8 - Customizing NTLM

Smb2Client ls \\LUMON-FS1\MDR -u milchick -p Br3@kr00m! -ntlmver 10.0.0.0 -w MILCHICK-WKS

This command line specifies a different NTLM version and workstation name to send during authentication.

Smb2Client mkdir

Creates a directory.

Synopsis

Smb2Client mkdir [options] <UncPath>

Parameters

Options

Authentication

Authentication (Kerberos)

Authentication (NTLM)

Client Behavior

Connection

Output

Details

By default, parent directories are not created. If the directory already exists, the server returns STATUS_OBJECT_NAME_COLLISION. Smb2Client mkdir only supports creating a single level directory at a time. That is, if you try to create \SERVER\Share\Dir1\Subdir2\Subdir3, then \SERVER\Share\Dir1\Subdir2 must exist or the server returns STATUS_OBJECT_PATH_NOT_FOUND.

If you specify -Parents, Smb2Client mkdir attempts to create the directory with the full path, as above. If the server returns STATUS_OBJECT_PATH_NOT_FOUND, it then starts at the root of the share and checks for each directory, creating if necessary. If the specified directory already exists, no error is generated. This does result in more traffic, as each directory level generates a CREATE request.

The <UncPath> parameter specifies the target of the command using the format \<server>[:<port>]\<share>[\<path>] where <port> is an integer specifying the port to connect to. If -HostAddress is specified, Smb2Client mkdir resolves it either as an IP address (IPv4 or IPv6) or a DNS name. If -HostAddress is not specified, <server> is resolved. In either case, the resulting IP addresses may be filtered by address family using -4 or -6. In either case, <server> is used to refer to the server within the SMB2 protocol.

Smb2Client mkdir supports both NTLM and Kerberos authentication. The -UserName and -Password parameters apply to both NTLM and Kerberos. You may also specify -NtlmHash for NTLM. Each authentication mechanism has a variety of parameters to customize the negotiation.

Kerberos is only enabled if you specify -kdc with the name or address of the KDC. If you specify a name, Smb2Client mkdir applies the same filtering rules for -4 and -6.

Smb2Client mklink

Creates a symbolic link.

Synopsis

Smb2Client mklink [options] <UncPath> <TargetPath>

Parameters

Options

Authentication

Authentication (Kerberos)

Authentication (NTLM)

Client Behavior

Connection

Output

Details

By default, <TargetPath> is interpreted as a full path, regardless of the form. Use -Relative to specify a relative link. For an absolute path to function properly, the actual link path must begin with \??\. If you don’t specify this, it is added for you without a warning.

If an object already exists <UncPath>, it must be of the correct type. That is, it must be a file for a file link or a directory to a directory link. If it does not exist, it is created.

A symlink contains two components: the substitution path and the print path. The substitution path specifies the target of the link, whereas the print path is displayed to the user in directory listings. They do not have to correlate. By default, Smb2Client mklink sets the print path to <TargetPath>, before prepending \??\ (if applicable). Use -PrintPath to explicitly set the print path.

Smb2Client mklink cannot be used to create junctions. For this, use mount.

The <UncPath> parameter specifies the target of the command using the format \<server>[:<port>]\<share>[\<path>] where <port> is an integer specifying the port to connect to. If -HostAddress is specified, Smb2Client mklink resolves it either as an IP address (IPv4 or IPv6) or a DNS name. If -HostAddress is not specified, <server> is resolved. In either case, the resulting IP addresses may be filtered by address family using -4 or -6. In either case, <server> is used to refer to the server within the SMB2 protocol.

Smb2Client mklink supports both NTLM and Kerberos authentication. The -UserName and -Password parameters apply to both NTLM and Kerberos. You may also specify -NtlmHash for NTLM. Each authentication mechanism has a variety of parameters to customize the negotiation.

Kerberos is only enabled if you specify -kdc with the name or address of the KDC. If you specify a name, Smb2Client mklink applies the same filtering rules for -4 and -6.

Examples

Example 1 - Creates a symlink to a file

Smb2Client mklink \\SERVER\Share\Symlink -Relative ActualFile.txt

Creates a symlink at \SERVER\Share\Symlink that points to ActualFile.txt within the same directory

Example 2 - Creates a symlink to a directory

Smb2Client mklink \\SERVER\Share\SymlinkDir -Directory -Relative ActualDir

Creates a symlink directory at \SERVER\Share\SymlinkDir that points to ActualFir within the same directory

Example 3 - Creates a symlink to a directory with a different label

Smb2Client mklink \\SERVER\Share\SymlinkDir -Directory -Relative ActualDir -PrintName "Not ActualDir"

Creates a symlink directory at \SERVER\Share\SymlinkDir that points to ActualFir within the same directory, but a directory listing prints “Not ActualDir”

Smb2Client mount

Creates a mount point or junction.

Synopsis

Smb2Client mount [options] <UncPath> <TargetPath>

Parameters

Options

Authentication

Authentication (Kerberos)

Authentication (NTLM)

Client Behavior

Connection

Output

Details

The TargetPath may be either a volume or directory. For volumes, the target path should start with \??\ and end with a trailing backslash. To mount a directory (a.k.a. junction), the target path should specify a full path starting with X:\ where X is the drive letter. Smb2Client mount checks the path and issues a warning if the path doesn’t look quite right, but this does not generate an error and will pass the path unaltered to the server.

A mount point contains two components: the substitution path and the print path. The substitution path specifies the target of the, whereas the print path is displayed to the user in directory listings. They do not have to correlate. By default, Smb2Client mount sets the print path to <TargetPath>, before prepending \??\ (if applicable). Use -PrintPath to explicitly set the print path.

Smb2Client mount does not require that the directory specified by <UncPath> already exists, and will create the directory if it doesn’t exist. If <UncPath>specifies a file instead of a directory, the server will likely fail the operation.

The <UncPath> parameter specifies the target of the command using the format \<server>[:<port>]\<share>[\<path>] where <port> is an integer specifying the port to connect to. If -HostAddress is specified, Smb2Client mount resolves it either as an IP address (IPv4 or IPv6) or a DNS name. If -HostAddress is not specified, <server> is resolved. In either case, the resulting IP addresses may be filtered by address family using -4 or -6. In either case, <server> is used to refer to the server within the SMB2 protocol.

Smb2Client mount supports both NTLM and Kerberos authentication. The -UserName and -Password parameters apply to both NTLM and Kerberos. You may also specify -NtlmHash for NTLM. Each authentication mechanism has a variety of parameters to customize the negotiation.

Kerberos is only enabled if you specify -kdc with the name or address of the KDC. If you specify a name, Smb2Client mount applies the same filtering rules for -4 and -6.

Examples

Example 1 - Creates a volume mount point

Smb2Client mount \\SERVER\Share\MountPoint \??\Volume{12345678-1234-1234-1234-123456789ABC}\

Creates a mount point at \SERVER\Share\MountPoint that points to the volume {12345678-1234-1234-1234-123456789ABC}

Example 2 - Creates a junction

Smb2Client mount \\SERVER\Share\Junction \??\C:\WINDOWS

Creates a junction at \SERVER\Share\Junction that points to C:\WINDOWS on the remote system

Example 3 - Creates a junction with a different label

Smb2Client mount \\SERVER\Share\Junction \??\C:\WINDOWS -PrintName "Not Windows"

Creates a junction at \SERVER\Share\Junction that points to C:\WINDOWS on the remote system, but prints the link as Not Windows in a directory listing.

Smb2Client mountfs

Mounts an SMB2 server or share to the local file system.

Synopsis

Smb2Client mountfs [options] <UncPath> [ <Mountpoint> ]

Parameters

Options

Authentication

Authentication (Kerberos)

Authentication (NTLM)

Client Behavior

Connection

Output

Details

The UNC path may either be a server, a share, or a path within a share. If the UNC path is a server, the directory listing enumerates shares on the server.

The filesystem is mounted as read-only unless -ReadWrite is specified.

The directory listings use the UID and GID of the current user (obtained using getuid() and getegid()) and a mode of r-xr-xr-x or rwxr-xr-x, dependening on whether -ReadWrite is specified. To retrieve the actual owner and DACL, print the extended attributes titanis.smb2.file.ownersid and titanis.smb2.file.dacltext. For example:

Files within IPC$ are presented as sockets.

Smb2Client put

Sends a file to the server.

Synopsis

Smb2Client put [options] [ <SourceFileName> ] <UncPath>

Parameters

Options

Authentication

Authentication (Kerberos)

Authentication (NTLM)

Client Behavior

Connection

Output

Details

The <UncPath> parameter specifies the target file to write to via SMB. If <SourceFileName> is specified, Smb2Client put opens the file and writes it to the destination file on the server. If no source file is specified, Smb2Client put accepts input from the console.

When copying the file, Smb2Client put fetches the file one chunk at a time. The default chunk size is 32,768 bytes, which loosely resembles using the COPY command on a command prompt. Use -ChunkSize to override the chunk size.

When specifying -UseBackupSemantics the server will check if the user has SeBackupPrivilege and SeRestorePrivilege. If they do they are allowed to bypass security checks when accessing files. Notably bypassing security checks does not bypass file locks or a file marked with the read-only attribute.

The <UncPath> parameter specifies the target of the command using the format \<server>[:<port>]\<share>[\<path>] where <port> is an integer specifying the port to connect to. If -HostAddress is specified, Smb2Client put resolves it either as an IP address (IPv4 or IPv6) or a DNS name. If -HostAddress is not specified, <server> is resolved. In either case, the resulting IP addresses may be filtered by address family using -4 or -6. In either case, <server> is used to refer to the server within the SMB2 protocol.

Smb2Client put supports both NTLM and Kerberos authentication. The -UserName and -Password parameters apply to both NTLM and Kerberos. You may also specify -NtlmHash for NTLM. Each authentication mechanism has a variety of parameters to customize the negotiation.

Kerberos is only enabled if you specify -kdc with the name or address of the KDC. If you specify a name, Smb2Client put applies the same filtering rules for -4 and -6.

Smb2Client rm

Deletes a file.

Synopsis

Smb2Client rm [options] <UncPath>

Parameters

Options

Authentication

Authentication (Kerberos)

Authentication (NTLM)

Client Behavior

Connection

Output

Details

The <UncPath> parameter specifies the target of the command using the format \<server>[:<port>]\<share>[\<path>] where <port> is an integer specifying the port to connect to. If -HostAddress is specified, Smb2Client rm resolves it either as an IP address (IPv4 or IPv6) or a DNS name. If -HostAddress is not specified, <server> is resolved. In either case, the resulting IP addresses may be filtered by address family using -4 or -6. In either case, <server> is used to refer to the server within the SMB2 protocol.

Smb2Client rm supports both NTLM and Kerberos authentication. The -UserName and -Password parameters apply to both NTLM and Kerberos. You may also specify -NtlmHash for NTLM. Each authentication mechanism has a variety of parameters to customize the negotiation.

Kerberos is only enabled if you specify -kdc with the name or address of the KDC. If you specify a name, Smb2Client rm applies the same filtering rules for -4 and -6.

Smb2Client rmdir

Deletes a directory.

Synopsis

Smb2Client rmdir [options] <UncPath>

Parameters

Options

Authentication

Authentication (Kerberos)

Authentication (NTLM)

Client Behavior

Connection

Output

Details

The <UncPath> parameter specifies the target of the command using the format \<server>[:<port>]\<share>[\<path>] where <port> is an integer specifying the port to connect to. If -HostAddress is specified, Smb2Client rmdir resolves it either as an IP address (IPv4 or IPv6) or a DNS name. If -HostAddress is not specified, <server> is resolved. In either case, the resulting IP addresses may be filtered by address family using -4 or -6. In either case, <server> is used to refer to the server within the SMB2 protocol.

Smb2Client rmdir supports both NTLM and Kerberos authentication. The -UserName and -Password parameters apply to both NTLM and Kerberos. You may also specify -NtlmHash for NTLM. Each authentication mechanism has a variety of parameters to customize the negotiation.

Kerberos is only enabled if you specify -kdc with the name or address of the KDC. If you specify a name, Smb2Client rmdir applies the same filtering rules for -4 and -6.

Smb2Client touch

Updates the timestamps or attributes of a file or directory on an SMB share.

Synopsis

Smb2Client touch [options] <UncPath>

Parameters

Options