Ubuntu who is connected samba

While smbstatus --shares list active connections in your computer, you may want to know which folders are selected as samba shared , even when no current connection is active. Ubuntu Community Ask! Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? Learn more. List samba shares and current users Ask Question. Asked 9 years, 9 months ago. Active 9 months ago. Viewed k times. Looking for a simple way to do this from the command line. List samba shares and the users who can access each of them. List samba shares and the users currently connected to them.

Improve this question. We can list shares from command line using smbtree. Add a comment. Active Oldest Votes. Improve this answer. Hans Ginzel Hans Ginzel 6 6 silver badges 12 12 bronze badges.

This controls whether the client offers or even demands the use of the netlogon schannel. This option yields precedence to the require strong key option. This controls whether the client is allowed or required to use SMB signing.

It is also possible to remove individual algorithms from the default list, by prefixing them with '-'. This can avoid having to specify a hardcoded list. This parameter controls whether a client should try or is required to use SMB encryption. This parameter can be set globally. Currently this is only supported smbclient of by Samba 3.

Windows does not support this feature. When set to default, SMB encryption is probed, but not enforced. It is only used by Samba if client max protocol is set to SMB3 or newer. These features can be controlled with settings of client smb encrypt as follows:. Setting it to desired globally will enable negotiation and will turn on data encryption on sessions and share connections for those servers that support it. Setting it to required globally will enable negotiation and turn on data encryption on sessions and share connections.

Clients that do not support encryption will be denied access to the server. Setting it to off globally will completely disable the encryption feature for all connections. This parameter determines whether Samba client tools will try to authenticate using Kerberos.

For Kerberos authentication you need to use dns names instead of IP addresses when connnecting to a service. There will be no falllback to NTLM or a different alternative. In case that weak cryptography is not allowed e. FIPS mode the default will be forced to required. This parameter determines whether or not smbclient 8 and other samba components acting as a client will attempt to use the server-supplied principal sometimes given in the SPNEGO exchange.

If enabled, Samba can attempt to use Kerberos to contact servers known only by IP address. Kerberos relies on names, so ordinarily cannot function in this situation. It will be removed in a future version of Samba. If disabled, Samba will use the name used to look up the server when asking the KDC for a ticket.

This avoids situations where a server may impersonate another, soliciting authentication as one principal while being known on the network as another.

Note that Windows XP SP2 and later versions already follow this behaviour, and Windows Vista and later servers no longer supply this 'rfc hint' principal on the server side. This parameter is deprecated in Samba 4. This enables Kerberos authentication in particular. With this parameter you can add additional addresses that nmbd will register with a WINS server.

This parameter specifies whether Samba should contact ctdb for accessing its tdb files and use ctdb as a backend for its messaging backend. Set this parameter to yes only if you have a cluster setup with ctdb running. This is a text field that is seen next to a share when a client does a queries the server, either via the network neighborhood or via net view to list what shares are available. If you want to set the string that is displayed next to the machine name then see the server string parameter.

This controls the backend for storing the configuration. Possible values are file the default and registry. So this triggers a registry only configuration. Share definitions are not read immediately but instead registry shares is set to yes. This allows you to override the config file to use, instead of the default usually smb.

There is a chicken and egg problem here as this option is set in the config file! For this reason, if the name of the config file has changed when the parameters are loaded then it will reload them from the new config file. If the config file doesn't exist then it won't be loaded allowing you to special case the config files of just a few clients.

This parameter allows you to "clone" service entries. The specified service is simply duplicated under the current service's name. Any parameters specified in the current section will override those in the section being copied. This feature lets you set up a 'template' service and create similar services easily. Note that the service being copied must occur earlier in the configuration file than the service doing the copying. Setting this parameter to no prevents winbind from creating custom krb5.

Winbind normally does this because the krb5 libraries are not AD-site-aware and thus would pick any domain controller out of potentially very many. Winbind is site-aware and makes the krb5 libraries use a local DC by creating its own krb5. Preventing winbind from doing this might become necessary if you have to add special options into your system-krb5. Any bit not set here will be removed from the modes set on a file when it is created.

The default value of this parameter removes the group and other write and execute bits from the UNIX modes. Following this Samba will bit-wise 'OR' the UNIX mode created from this parameter with the value of the force create mode parameter which is set to by default. This parameter does not affect directory masks. See the parameter directory mask for details.

This stands for client-side caching policy , and specifies how clients capable of offline caching will cache the files in the share. The valid values are: manual, documents, programs, disable. The default path as of ctdb 1. In a cluster environment using Samba and ctdb it is critical that locks on central ctdb-hosted databases like locking. With the current Samba architecture it happens that Samba takes a lock and while holding that lock makes file system calls into the shared cluster file system.

This option makes Samba warn if it detects that it has held locks for the specified number of milliseconds. If this happens, smbd will emit a debug level 0 message into its logs and potentially into syslog. The most likely reason for such a log message is that an operation of the cluster file system Samba exports is taking longer than expected.

The messages are meant as a debugging aid for potential cluster problems. This parameter specifies a timeout in milliseconds for the connection between Samba and ctdb.

When something in the cluster blocks, it can happen that we wait indefinitely long for ctdb, just adding to the blocking condition. In a well-running cluster this should never happen, but there are too many components in a cluster that might have hickups. Choosing the right balance for this value is very tricky, because on a busy cluster long service times to transfer something across the cluster might be valid. Setting it too short will degrade the service your cluster presents, setting it too long might make the cluster itself not recover from something severely broken for too long.

Be aware that if you set this parameter, this needs to be in the file smb. Setting ctdb timeout to n makes any process waiting longer than n milliseconds for a reply by the cluster panic.

Setting it to 0 the default makes Samba block forever, which is the highly recommended default. This parameter is only applicable if printing is set to cups. If set, this option specifies the number of seconds that smbd will wait whilst trying to contact to the CUPS server.

The connection will fail if it takes longer than this number of seconds. This parameter is only applicable if printing is set to cups and if you use CUPS newer than 1.

Possible values are auto , yes and no. If that fails, we will fall back to unencrypted operation. Its value is a free form string of options passed directly to the cups library. You can also pass any printer specific option as listed in "lpoptions -d printername -l" valid for the target queue. This is necessary if you have virtual samba servers that connect to different CUPS daemons.

Optionally, a port can be specified by separating the server name and port number with a colon. If no port was specified, the default port for IPP will be used. The value of the parameter a decimal integer represents the number of minutes of inactivity before a connection is considered dead, and it is disconnected. The deadtime only takes effect if the number of open files is zero. This is useful to stop a server's resources being exhausted by a large number of inactive connections.

Most clients have an auto-reconnect feature when a connection is broken so in most cases this parameter should be transparent to users. For more information about currently available debug classes, see section about log level.

This option will make the smbd server and client code using libsmb smbclient, smbget, smbspool, This information will be printed in logs at level 0. Warning: access to these values enables the decryption of any encrypted traffic on the dumped sessions. This option should only be enabled for debugging purposes. Sometimes the timestamps in the log messages are needed with a resolution of higher that seconds, this boolean parameter adds microsecond resolution to the timestamp message header when turned on.

Note that the parameter debug timestamp must be on for this to have an effect. When using only one log file for more then one forked smbd 8 -process there may be hard to follow which process outputs which message. This boolean parameter is adds the process-id to the timestamp message headers in the logfile when turned on.

With this option enabled, the timestamp message header is prefixed to the debug message without the filename and function information that is included with the debug timestamp parameter. This gives timestamps to the messages without adding an additional line.

Note that this parameter overrides the debug timestamp parameter. Samba is sometimes run as root and sometime run as the connected user, this boolean parameter inserts the current euid, egid, uid and gid to the timestamp message headers in the log file if turned on.

Specifies the absolute path to the kerberos keytab file when kerberos method is set to "dedicated keytab". See the section on name mangling.

Also note the short preserve case parameter. This parameter is only applicable to printable services. The device mode can only correctly be generated by the printer driver itself which can only be executed on a Win32 platform.

Because smbd is unable to execute the driver code to generate the device mode, the default behavior is to set this field to NULL. Certain drivers will do things such as crashing the client's Explorer. However, other printer drivers can cause the client's spooler service spoolsv.

This parameter should be used with care and tested with the printer driver in question. This parameter specifies the name of a service which will be connected to if the service actually requested cannot be found. Note that the square brackets are NOT given in the parameter value see example below. There is no default value for this parameter. If this parameter is not given, attempting to connect to a nonexistent service results in an error.

Typically the default service would be a guest ok , read-only service. This allows for interesting things. Windows allows specifying how a file will be shared with other processes when it is opened.

Sharing violations occur when a file is opened by a different process using options that violate the share settings specified by other processes. This parameter causes smbd to act as a Windows server does, and defer returning a "sharing violation" error message for up to one second, allowing the client to close the file causing the violation in the meantime.

There should be no reason to turn off this parameter, as it is designed to enable Samba to more correctly emulate Windows. For a Samba host this means that the printer must be physically deleted from the underlying printing system.

The deleteprinter command defines a script to be run which will perform the necessary operations for removing the printer from the print system and from smb. The deleteprinter command is automatically called with only one parameter: printer name. Once the deleteprinter command has been executed, smbd will reparse the smb. This parameter allows readonly files to be deleted. This option may be useful for running applications such as rcs, where UNIX file ownership prevents changing file permissions, and DOS semantics prevent deletion of a read only file.

The delete share command is used to define an external program or script which will remove an existing service definition from smb. In order to successfully execute the delete share command , smbd requires that the administrator connects using a root account i. Scripts defined in the delete share command parameter are executed as root. When executed, smbd will automatically invoke the delete share command with two parameters.

This parameter is only used to remove file shares. To delete printer shares, see the deleteprinter command. Full path to the script that will be called when a user is removed from a group using the Windows NT domain administration tools.

This is the full pathname to a script that will be run by smbd 8 when managing users with remote RPC NT tools. This script is called when a remote client removes a user from the server, normally using 'User Manager for Domains' or rpcclient. This option is used when Samba is attempting to delete a directory that contains one or more vetoed directories see the veto files option.

If this option is set to no the default then if a vetoed directory contains any non-vetoed files or directories then the directory delete will fail. This is usually what you want. If this option is set to yes , then Samba will attempt to recursively delete any files and directories within the vetoed directory. The dfree cache time should only be used on systems where a problem occurs with the internal disk space calculations.

This has been known to happen with Ultrix, but may occur with other operating systems. The symptom that was seen was an error of "Abort Retry Ignore" at the end of each directory listing.

This is a new parameter introduced in Samba version 3. It specifies in seconds the time that smbd will cache the output of a disk free query. If set to zero the default no caching is done.

This allows a heavily loaded server to prevent rapid spawning of dfree command scripts increasing the load. The dfree command setting should only be used on systems where a problem occurs with the internal disk space calculations. This setting allows the replacement of the internal routines to calculate the total disk space and amount available with an external routine.

The example below gives a possible script that might fulfill this function. In Samba version 3. The external program will be passed a single parameter indicating a directory in the filesystem being queried. This will typically consist of the string. The first should be the total disk space in blocks, and the second should be the number of available blocks.

An optional third return value can give the block size in bytes. The default blocksize is bytes. Note: Your script should NOT be setuid or setgid and should be owned by and writeable only by root!

Note that you may have to replace the command names with full path names on some systems. Also note the arguments passed into the script should be quoted inside the script in case they contain special characters such as spaces or newlines. By default internal routines for determining the disk capacity and remaining space will be used. Any bit not set here will be removed from the modes set on a directory when it is created. The default value of this parameter removes the 'group' and 'other' write bits from the UNIX mode, allowing only the user who owns the directory to modify it.

Following this Samba will bit-wise 'OR' the UNIX mode created from this parameter with the value of the force directory mode parameter. This parameter is set to by default i. This parameter specifies the size of the directory name cache for SMB1 connections. It is not used for SMB2. Enabling this parameter will disable netbios support in Samba.

Netbios is the only available form of browsing in all windows versions except for and XP. Clients that only support netbios won't be able to see your samba server when netbios support is disabled. However, this will also disable the ability to upload printer drivers to a Samba server via the Windows NT Add Printer Wizard or by using the NT printer properties dialog window.

Be very careful about enabling this parameter. This would typically be used in conjunction with a hierarchical storage system that automatically migrates files to tape.

Note that Samba infers the status of a file by examining the events that a DMAPI application has registered interest in. This heuristic is satisfactory for a number of hierarchical storage systems, but there may be system for which it will fail.

In this case, Samba may erroneously report files to be offline. This option sets the command that is called when there are DNS updates. This option should not be enabled for installations created with versions of samba before 4. Doing this will result in the loss of static DNS entries. This is due to a bug in previous versions of samba BUG which marked dynamic DNS records as static and static records as dynamic. The IP list is comma and space separated and specified in the same syntax as used in hosts allow , specifically including IP address, IP prefixes and IP address masks.

The default behaviour is to deny any request. A request will be authorized only if the emitting client is identified in this list, and not in dns zone transfer clients deny. If a client identified in this list sends a zone transfer request, it will always be denied, even if they are in dns zone transfer clients allow. This allows the definition of specific denied clients within an authorized subnet. If set to yes , the Samba server will provide the netlogon service for Windows 9X network logons for the workgroup it is in.

This will also cause the Samba server to act as a domain controller for NT4 style domain services. Tell smbd 8 to enable WAN-wide browse list collation. Setting this option causes nmbd to claim a special domain specific NetBIOS name that identifies it as a domain master browser for its given workgroup.

Local master browsers in the same workgroup on broadcast-isolated subnets will give this nmbd their local browse lists, and then ask smbd 8 for a complete copy of the browse list for the whole wide area network.

Browser clients will then contact their local master browser, and will receive the domain-wide browse list, instead of just the list for their broadcast-isolated subnet.

This means that if this parameter is set and nmbd claims the special name for a workgroup before a Windows NT PDC is able to do so then cross subnet browsing will behave strangely and may fail. If domain logons is not enabled the default setting , then neither will domain master be enabled by default.

In general, this parameter should be set to 'No' only on a BDC. There are certain directories on some systems e. This parameter allows you to specify a comma-delimited list of directories that the server should always show as empty. Note that Samba can be very fussy about the exact format of the "dont descend" entries. For example you may need. Experimentation is the best policy This option specifies which charset Samba should talk to DOS clients.

The default depends on which charsets you have installed. Run testparm 1 to check the default on your system. Enabling this parameter allows a user who has write access to the file by whatever means, including an ACL permission to modify the permissions including ACL on it. Note that a user belonging to the group owning the file will not be allowed to change permissions if the group is only granted read access.

Setting this parameter for a share causes Samba to round the reported time down to the nearest two second boundary when a query call that requires one second resolution is made to smbd 8. One of these calls uses a one-second granularity, the other uses a two second granularity. Under DOS and Windows, if a user can write to a file they can change the timestamp on it.

By default, Samba emulates the DOS semantics and allows one to change the timestamp on a file if the user smbd is acting on behalf has write permissions. Due to changes in Microsoft Office and beyond, the default for this parameter has been changed from "no" to "yes" in Samba 3. Microsoft Excel will display dialog box warnings about the file being changed by another user if this parameter is not set to "yes" and files are being shared between users.

When enabled, this option causes Samba acting as an Active Directory Domain Controller to stream Samba database events across the internal message bus.

When enabled, this option causes Samba acting as an Active Directory Domain Controller to stream group membership change events across the internal message bus.

When enabled, this option causes Samba acting as an Active Directory Domain Controller to stream password change and reset events across the internal message bus. This boolean parameter controls whether Samba can grant SMB2 durable file handles on a share. Also note that, for the time being, durability is not granted for a handle that has the delete on close flag set.

This boolean parameter controls whether smbd 8 will allow clients to attempt to access extended attributes on a share. In order to enable this parameter on a setup with default VFS modules:. The underlying filesystem exposed by the share must support extended attributes e. Note that the SMB protocol allows setting attributes whose value is 64K bytes long, and that on NTFS, the maximum storage space for extended attributes per file is 64K.

Giving clients access to this tight space via extended attribute support could consume all of it by unsuspecting client applications, which would prevent changing system metadata due to lack of space.

The default has changed to yes in Samba release 4. Specifies the name of the Elasticsearch server to use for Spotlight queries when using the Elasticsearch backend. Specifies the name of the Elasticsearch index to use for Spotlight queries when using the Elasticsearch backend. Path to a file specifying metadata attribute mappings in JSON format. A value of 0 means no limit. The has been the default behavior in smbd for many years.

This parameter specifies whether core dumps should be written on internal exits. This deprecated parameter controls whether or not smbd will honor privileges assigned to specific SIDs via either net rpc rights or one of the Windows user and group manager tools. This parameter is enabled by default. It can be disabled to prevent members of the Domain Admins group from being able to assign privileges to users or groups which can then result in certain smbd operations running as root that would normally run under the context of the connected user.

An example of how privileges can be used is to assign the right to join clients to a Samba controlled domain without providing root access to the server via smbd. Inverted synonym for disable spoolss. This boolean controls whether encrypted passwords will be negotiated with the client.

Note that Windows NT 4. MS Windows clients that expect Microsoft encrypted passwords and that do not have plain text password support enabled will be able to connect only to a Samba server that has encrypted password support enabled and for which the user accounts have a valid encrypted password.

Refer to the smbpasswd command man page for information regarding the creation of encrypted passwords for user accounts. The use of plain text passwords is NOT advised as support for this feature is no longer maintained in Microsoft Windows products. If you want to use plain text passwords you must set this parameter to no. This option enables a couple of enhancements to cross-subnet browse propagation that have been added in Samba but which are not standard in Microsoft implementations.

The first enhancement to browse propagation consists of a regular wildcard query to a Samba WINS server for all Domain Master Browsers, followed by a browse synchronization with each of the returned DMBs. The second enhancement consists of a regular randomised browse synchronization with all currently known DMBs. You may wish to disable this option if you have a problem with empty workgroups not disappearing from browse lists.

Due to the restrictions of the browse protocols, these enhancements can cause a empty workgroup to stay around forever which can be annoying. In general you should leave this option enabled as it makes cross-subnet browse propagation much more reliable. The concept of a "port" is fairly foreign to UNIX hosts. LPD Port Monitor, etc By default, Samba has only one port defined-- "Samba Printer Port".

If you wish to have a list of ports displayed smbd does not use a port name for anything other than the default "Samba Printer Port" , you can define enumports command to point to a program which should generate a list of ports, one per line, to standard output.

This option defines a list of log names that Samba will report to the Microsoft EventViewer utility. Refer to the eventlogadm 8 utility for how to write eventlog entries. This is not the same as the ctime - status change time - that Unix keeps, so Samba by default reports the earliest of the various times Unix does keep.

Setting this parameter for a share causes Samba to always report midnight as the create time for directories. Thus the object directory will be created if it does not exist, but once it does exist it will always have an earlier timestamp than the object files it contains.

However, Unix time semantics mean that the create time reported by Samba will be updated whenever a file is created or deleted in the directory. NMAKE finds all object files in the object directory. The timestamp of the last one built is then compared to the timestamp of the object directory. If the directory's timestamp if newer, then all object files will be rebuilt. Enabling this option ensures directories always predate their contents and an NMAKE build will proceed as expected.

Oplocks are the way that SMB clients get permission from a server to locally cache file operations. If a server grants an oplock opportunistic lock then the client is free to assume that it is the only one accessing the file and it will aggressively cache file data.

This can give enormous performance benefits. It is generally much better to use the real oplocks support rather than this parameter. If you enable this option on all read-only shares or shares that you know will only be accessed from one client at a time such as physically read-only media like CDROMs, you will see a big performance improvement on many operations.

If you enable this option on shares where multiple clients may be accessing the files read-write at the same time you can get data corruption. Use this option carefully! This parameter allows the Samba administrator to stop smbd 8 from following symbolic links in a particular share.

Setting this parameter to no prevents any file or directory that is a symbolic link from being followed the user will get an error. However it will slow filename lookups down slightly. This option is enabled i. This parameter specifies a set of UNIX mode bit permissions that will always be set on a file created by Samba. This is done by bitwise 'OR'ing these bits onto the mode bits of a file that is being created. The default for this parameter is in octal The modes in this parameter are bitwise 'OR'ed onto the file mode after the mask set in the create mask parameter is applied.

This parameter specifies a set of UNIX mode bit permissions that will always be set on a directory created by Samba. This is done by bitwise 'OR'ing these bits onto the mode bits of a directory that is being created. The default for this parameter is in octal which will not add any extra permission bits to a created directory. This operation is done after the mode mask in the parameter directory mask is applied. This specifies a UNIX group name that will be assigned as the default primary group for all users connecting to this service.

This is useful for sharing files by ensuring that all access to files on service will use the named group for their permissions checking. Thus, by assigning permissions for this group to the files and directories within this service the Samba administrator can restrict or allow sharing of these files. In Samba 2. This allows an administrator to decide that only users who are already in a particular group will create files with group ownership set to that group. This gives a finer granularity of ownership assignment.

All other users will retain their ordinary primary group. If the force user parameter is also set the group specified in force group will override the primary group set in force user. When printing from Windows NT or later , each printer in smb. The first is the sharename or shortname defined in smb. This is the only printername available for use by Windows 9x clients. The second name associated with a printer can be seen when browsing to the "Printers" or "Printers and Faxes" folder on the Samba server.

This is referred to simply as the printername not to be confused with the printer name option. When assigning a new driver to a printer on a remote Windows compatible print server such as Samba, the Windows client will rename the printer to match the driver name just uploaded. This can result in confusion for users when multiple printers are bound to the same driver. To prevent Samba from allowing the printer's printername to differ from the sharename defined in smb.

Be aware that enabling this parameter may affect migrating printers from a Windows server to Samba since Windows has no way to force the sharename and printername to match. It is recommended that this parameter's value not be changed once the printer is in use by clients as this could cause a user not be able to delete printer connections from their local Printers folder.

This boolean option tells smbd whether to forcefully disable the use of Open File Description locks on Linux. If this parameter is set, a Windows NT ACL that contains an unknown SID security descriptor, or representation of a user or group id as the owner or group owner of the file will be silently mapped into the current UNIX uid or gid of the currently connected user.

This specifies a UNIX user name that will be assigned as the default user for all users connecting to this service. This is useful for sharing files. You should also use it carefully as using it incorrectly can cause security problems.

This user name only gets used once a connection is established. Thus clients still need to connect as a valid user and supply a valid password.

Once connected, all file operations will be performed as the "forced user", no matter what username the client connected as. This can be very useful.

Prior to 2. FSRVP timeouts can be completely disabled via a value of 0. This parameter allows the administrator to configure the string that specifies the type of filesystem a share is using that is reported by smbd 8 when a client queries the filesystem type for a share. The get quota command should only be used whenever there is no operating system API available from the OS that samba can use. The directory is actually mostly just ".

This script should print one line as output with spaces between the columns. The printed columns should be:. This is a tuning option. When this is enabled a caching algorithm will be used to reduce the time taken for getwd calls. This can have a significant impact on performance, especially when the wide links parameter is set to no. This option sets the command that is called to apply GPO policies. Kerberos Policies set kdc:service ticket lifetime, kdc:user ticket lifetime, and kdc:renewal lifetime in smb.

This is a username which will be used for access to services which are specified as guest ok see below. Whatever privileges this user has will be available to any client connecting to the guest service.

This user must exist in the password file, but does not require a valid login. The user account "ftp" is often a good choice for this parameter. On some systems the default guest account "nobody" may not be able to print. Use another account in this case. You should test this by trying to log in as your guest user perhaps by using the su - command and trying to print using the system print command such as lpr 1 or lp 1. If this parameter is yes for a service, then no password is required to connect to the service.

Privileges will be those of the guest account. If this parameter is yes for a service, then only guest connections to the service are permitted.

This parameter will have no effect if guest ok is not set for the service. This is a boolean parameter that controls whether files starting with a dot appear as hidden files. This is a list of files or directories that are not visible but are accessible. The DOS 'hidden' attribute is applied to any files or directories that match. Setting this parameter will affect the performance of Samba, as it will be forced to check all files and directories for a match as they are scanned.

The example shown above is based on files that the Macintosh SMB client DAVE available from Thursby creates for internal use, and also still hides all files beginning with a dot.

Setting this parameter to something but 0 hides files that have been modified less than N seconds ago. A processing application should only see files that are definitely finished. The "noexec" option prevents executable scripts running from the SMB share. Save the file and exit gedit. Now the share will NOT automatically mount when you boot and you will be asked for your samba password.

There is a fix in the troubleshooting section of this forum post. Mounting a share on the local filesystem allows you to work around programs that do not yet use GnomeVFS to browse remote shares transparently. I advise you configure sudo, as above. To mount the share now, just use the following command as root. It will mount automatically on subsequent reboots.

You will see an icon "Windows network" and should be able to browse to your shared folder. You will be asked for a password, leave it blank. Click the "Connect button. Navigate to your Ubuntu server and your share will be available without a password. Select an available letter for your SMB share Default is z:.

Tic Select with the mouse the option "Reconnect at login" if you want the share to be automatically mounted when you boot Windows.