JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Managing SMB File Sharing and Windows Interoperability in Oracle Solaris 11.1     Oracle Solaris 11.1 Information Library
search filter icon
search icon

Document Information

Preface

1.  Sharing Files Between Windows and Oracle Solaris Systems

2.  Setting Up Identity Mapping Between Windows and Oracle Solaris Systems

3.  Setting Up a Oracle Solaris SMB Server to Manage and Share Files

Disabling the Samba Service

How to Disable the Samba Service

Configuring the SMB Server Operation Mode (Task Map)

How to Configure the SMB Server in Domain Mode

How to Configure the SMB Server in Workgroup Mode

Managing SMB Shares

Managing SMB Shares in This Release

Managing SMB Shares (Task Map)

How to Enable Cross-Protocol Locking

How to Create an SMB Share (zfs)

How to Enable Guest Access to an SMB Share

How to Enable Access-Based Enumeration for a Share

How to Modify SMB Share Properties (zfs)

How to Remove an SMB Share (zfs)

How to Create a Specific Autohome Share Rule

How to Restrict Client Host Access to an SMB Share (zfs)

Managing SMB Groups (Task Map)

How to Create an SMB Group

How to Add a Member to an SMB Group

How to Remove a Member From an SMB Group

How to Modify SMB Group Properties

Configuring the WINS Service

How to Configure WINS

Enabling CATIA V4/V5 Character Translations

How to the Enable CATIA Interoperability Feature

Configuring SMB Printing (Task Map)

How to Enable the SMB Print Service

Troubleshooting the SMB Service

Cannot Join a Windows Domain

Checking the DNS Configuration

Ensuring That Kerberos Is Correctly Configured

Ensuring That You Specify the Correct Password for Your Domain User

Ensuring the Firewall Software Does Not Filter Out Required Ports

Viewing Oracle Solaris SMB Service Property Settings

Excluding IP Addresses From WINS Name Resolution

Changes to Windows Group Membership and to User Mapping Do Not Take Effect

Windows Clients Cannot Connect by NetBIOS Name or Are Missing From Browse List or Network Neighborhood

Cannot Set Share Security, All Shares Inherit the Security of the Directory Object

Older Versions of Windows Cannot Copy Files Larger Than Four Gbytes

Cannot Use SMB to Map Drives

Cannot See the Security Tab From Windows Clients

Microsoft Access or SQL Server Sessions Time Out After a Period of Inactivity

Cannot Add Windows Local Groups to Access Control List

SMB Browsing Fails When share.smb=on Is Set on a ZFS Pool

Samba or SMB Service Cannot Bind Various Ports

SMB Shares on a ZFS File System are Inaccessible After a Reboot

Invalid Password Errors Appear When Mapping a Drive or Browsing Computers in the Workgroup

Access Control List Inheritance Issues

Missing Security Tab on Windows XP Clients

4.  Using SMB File Sharing on Client Systems

A.  SMB DTrace Provider

Glossary

Index

Configuring SMB Printing (Task Map)

SMB printing enables you to gain access to all of the Common UNIX Printing System (CUPS) printers. Each printer can be made accessible as SMB shares. The share names match the printer names, and the shared path is inherited from the print$ share that you create.

By default, support for SMB printing is disabled.

The following table points to the tasks that you can use to configure SMB printing.

Task
Description
For Instructions
Add a printer to the system.
Use the CUPS Print Manager tool to administer remote print queues.
Share a printer.
Use the CUPS Print Manager tool to share a printer.
Enable the SMB print service.
Use the sharectl command to enable the SMB print service.

How to Enable the SMB Print Service

This procedure shows how to enable support for SMB printing on your Oracle Solaris system. Part of this procedure includes the creation of a share called print$. The share path can point to any directory, which is used as the spool path for all SMB shared printers. This share must exist before you can print.

SMB printing is disabled by default, due to the print_enable property being set to false.


Note - You cannot map the print$ share as a disk share. Attempts to do so might result in the Password prompt being issued but access being denied. Such a failure is reported in the system log.


After SMB printing is enabled, you can use the Windows Add Printer wizard to attach your Windows client to shared printers. The SMB shared printers are connected to the network and can be selected by name.

  1. Become an administrator, obtain the solaris.smf.value.shares and solaris.smf.manage.shares RBAC authorizations, or use the SMB Management RBAC profile.

    For more information, see How to Use Your Assigned Administrative Rights in Oracle Solaris 11.1 Administration: Security Services.

  2. Create and publish a share called print$.

    The share path can point to any directory, which is used as the spool path for all SMB shared printers.

    # zfs share -o share.smb=on -o share.path=/pool/dataset pool/dataset%print$
  3. Set permissions on the directory to permit root access.
    # chmod A=user:root:full_set:allow pathname
  4. Enable the SMB print service.
    # sharectl set -p print_enable=true smb
  5. Verify that the SMB print service is enabled.
    # sharectl get -p print_enable smb

    If the SMB print service is enabled, the print_enable property is set to true.

  6. (Optional) Refresh the SMB service if a CUPS printer is added after the SMB print service is first enabled.
    # svcadm refresh smb/server

Example 3-7 Enabling the SMB Print Service

This example assigns the print$ share to an existing directory, /tank/printspool, and enables the SMB print service.

# mkdir /tank/printspool
# zfs share -o share.smb -o share.path=/tank/printspool tank%print$
# chmod A=user:root:full_set:allow /tank/printspool
# sharectl set -p print_enable=true smb