Sponsored Content
Full Discussion: mount windows share folder
Operating Systems Solaris mount windows share folder Post 302427916 by blicki on Tuesday 8th of June 2010 09:01:11 AM
Old 06-08-2010
As already said by jlliagre, there is no support for SMBFS in Solaris 10. SUN announced to support SMBFS by Solaris 11 (or already by OpenSolaris since longer period of time).

The package, adelsin told about, supports a CLI client, that can be used to get and put data to SMBFS. This client acts like an ftp client, and you do not have to be root to handle it. Therefore, you may also try to use it in scripts.

To have Windows 200x to support NFS is not a good idea. The package does not support cluster functionality or let itself fully integrate to Active Directory as it comes with an extra usermapping part.

I never took a closer look at Sharity's SMBFS for Unix... If you will buy it, let me know about your results, please Smilie

Greets!
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

using the mount command to connect to a windows share

Until recently I have been using the following command successfully to connect to a windows share: mount -t smbfs -o username=my_username,password=my_password /home/temp //oldserverx1/openexchange But from today, I've been getting the following error: INFO: Debug class all level = 1 (pid... (1 Reply)
Discussion started by: cw1972
1 Replies

2. UNIX for Advanced & Expert Users

How to Mount a Unix share drive on Windows

We are trying to mount a Unix share drive on a Windows 2003 server to avoid transfering files accross the network using sftp. I can see shared drives on the Solaris server using the "share" command. How can I mount the drives on my Windows server so that I can read them directly. Do I need... (2 Replies)
Discussion started by: rbdenham
2 Replies

3. AIX

Mount drive to Win2003 share folder

Dear all, How can mount a drive from AIX 4.3 to Windows 2003 Server share folder ? Thank a lot. (1 Reply)
Discussion started by: sinopec
1 Replies

4. Solaris

How to mount windows Share on solaris using SAMBA

Hi All I am new for Solaris and, I have configured SAMBA on my SUN10 Network machine and it's working fine. can anyone tell me how to mount windows share on my SUN10 machine. Thanks in advance daya (2 Replies)
Discussion started by: daya.pandit
2 Replies

5. Red Hat

Mount Windows share on Redhat, WITHOUT Samba?

Hi, Please let me know whether I can mount a windows share on Redhat, which does not have Samba installed. The constraint is that I cannot install Samba . Looking forward for a possible solution. (1 Reply)
Discussion started by: jksena
1 Replies

6. Solaris

how to mount Windows NFS share on solaris

Hi, How can i mount an NFS share on a solaris machine a filesystem ? I have enabled nfs on a windows server and the shares has given read/write access to it to all the users. I would like to mount it on around 10 different solaris boxes with different versions of solaris. Thanks in advance. (2 Replies)
Discussion started by: uxadmin007
2 Replies

7. IP Networking

Can't see home folder on one NFS mount but can in another mount on another share

Hello, I have a few Ubuntu 9.10 laptops I'm trying to learn NFS sharing with. I am just experimenting on this right now, so no harsh words about the security of what I'm playing with, please ;) Below are the configs /etc/exports on host /home/woodnt/Homeschool... (2 Replies)
Discussion started by: Narnie
2 Replies

8. UNIX and Linux Applications

Virtualbox Need to change share folder name before i can mount it

HI I would like to ask about my virtualbox 4.0.4 in my lucyd lynx box My shared forlder isn't auto mount in my linux guest OS. And everytime i manually mount using command sudo mount -t vboxsf <shared_folder_name> <Guest_location> it throw an error msg "/sbin/mount.vboxsf: mounting failed... (1 Reply)
Discussion started by: jao_madn
1 Replies

9. Red Hat

unable to mount windows share on linux 5.1

Hi, I am using redhat linux 5.1 - 64bit, using command mount -t cifs //192.192.192.192/SW/Ex /192.192.192.192 -o username=test I am getting below error. mount: block device //192.192.192.192/SW/Ex is write-protected, mounting read-only mount: cannot mount block device... (3 Replies)
Discussion started by: manoj.solaris
3 Replies

10. UNIX for Beginners Questions & Answers

Trying to share a folder between windows machine and VM

I was following the guide I found here for doing this and I reached the step where I added myself to the vboxsf group but I am still getting a permissions denied message when I try to get into the folder: ubuntu12@ubuntu12-VirtualBox: /media$ cd sf_Shared_files/ bash: cd: sf_Shared_files/:... (0 Replies)
Discussion started by: Circuits
0 Replies
nsmbrc(4)							   File Formats 							 nsmbrc(4)

NAME
nsmbrc - configuration file for Solaris CIFS client requests SYNOPSIS
$HOME/.nsmbrc DESCRIPTION
Global behavior of the Solaris CIFS client is defined by property values that are stored in the Service Management Facility (SMF). The .nsmbrc file can be used to customize the behavior of the Solaris CIFS client on a per-user basis. Settings in the $HOME/.nsmbrc file are used unless they have security implications. An authorized user can use the sharectl command to set global values for these properties in SMF. See sharectl(1M). A regular user can change the global values when granted the "SMBFS Management" rights profile in the /user_attr file. See user_attr(4) and rbac(5). The SMBFS library first reads from SMF and then the $HOME/.nsmbrc file when determining which policy to apply to a particular server, user, or share. $HOME/.nsmbrc entries take precedence with the exception of the minauth property value. For minauth, the strongest authentication level specified is used. Sections are applied so that more specific sections override less specific sections. Not all keywords are valid in all sections. The configuration file is comprised of these four section types. Each section can include zero or more properties and associated values. The sections also have a hierarchical relationship with each other, as shown by the order of the following list: o Default section. Specifies the default property values to be used by all other sections unless specifically overridden. The section name appears in the .nsmbrc file as [default]. o Server section. Specifies the property values to be used by sections that are related to the named server. These property values can be specifically overridden by a related user section or share section. The section name appears in the .nsmbrc file as [server-name]. server-name must use uppercase characters to match. o User section. Specifies the property values to be used by sections that are related to the named server and user. These property values can be specifically overridden by a related share section. The section name appears in the .nsmbrc as [server-name:username]. Both server-name and username must use uppercase characters to match. o Share section. Specifies the property values to be used by sections that are related to the named server, user, and share. The section name appears in the .nsmbrc as [server-name:username:share-name]. Both server-name and username must use uppercase characters to match. The end of each section is marked either by the start of a new section or by an end of file (EOF). The following list describes the properties and states in which sections they can be set: addr Specifies the DNS name or IP address of the CIFS server. This property can only be set in a server section. If this property is speci- fied, it must specify a value as there is no default. domain Specifies the Windows domain name to use when authenticating with a server. The default value is WORKGROUP. This property can only be set in the default and server sections. minauth Is the minimum authentication level required, which can be one of kerberos, ntlmv2, ntlm, lm, or none. If minauth is set globally and in a user's .nsmbrc file, the stronger authentication setting are used whether set by the user or globally. This property can only be set in the default and server sections. The default value is ntlm. nbns Specifies the DNS name or IP address of the NetBIOS/WINS name server. This property can only be set by an administrator by using the sharectl command. This property can only be set in the default section. The default value is empty, nbns="". nbns_broadcast Specifies whether to perform NetBIOS/WINS broadcast lookups. Broadcast lookups are less secure than unicast lookups. To prevent broad- cast lookups, set the value to no. This property has no effect if the nbns_enable property is set to no or false. This property can only be set by an administrator by using the sharectl command. This property can only be set in the default section. Valid values are yes, true, no, and false. The default value is yes. nbns_enable Specifies whether to perform NetBIOS/WINS name lookups. To force all lookups to be done through the name service switch (see nss- witch.conf(4)), set the value to no. This property can only be set by an administrator by using the sharectl command. This property can only be set in the default section. Valid values are yes, true, no, and false. The default value is yes. password Specifies the password to use when authenticating a server. The password property value is used as long as the .nsmbrc file can only be read and written by the owner. This property can be set in the default, server, user, and share sections. If you assign the hashed password from the smbutil crypt command to the password property, be sure to escape the special characters in the password. signing Specifies whether communications are digitally signed by SMB security signatures for the Solaris CIFS client. This property can only be set in the default and server sections. Valid values are disabled, enabled, and required. The default value is disabled. When set to disabled, the client permits the use of SMB security signatures only if the server requires signing. In such an instance, the Solaris CIFS client ignores local property values. When set to enabled, the client permits, but does not require, the use of SMB security signatures. When set to required, the client requires the use of SMB security signatures. So, if SMB security signatures are disabled on a CIFS server and a client has signing required, the client cannot connect to that server. timeout Specifies the CIFS request timeout. By default, the timeout is 15 seconds. This property can only be set in the default, server, and share sections. user Specifies the user name to use when authenticating a server. The default value is the Solaris account name of the user performing the authentication. This property can only be set in the default and server sections. workgroup Is supported for compatibility purposes and is a synonym for the domain property. Use the domain property instead. EXAMPLES
The examples in this section show how to use the .nsmbrc file and the smbutil command to configure the ex.com environment. The ex.com environment is described by means of these sections and settings: o The default section describes the default domain, which is called MYDOMAIN, and sets a default user of MYUSER. These default settings are inherited by other sections unless property values are overridden. o FSERVER is a server section that defines a server called fserv.ex.com. It is part of the SALES domain. o RSERVER is a server section that defines a server called rserv.ex.com that belongs to a new domain called REMGROUP. Example 1 Using the $HOME/.nsmbrc Configuration File The following example shows how a user can configure the ex.com environment by creating the .nsmbrc file. All lines that begin with the # character are comments and are not parsed. # Configuration file for ex.com # Specify the Windows account name to use everywhere. [default] domain=MYDOMAIN user=MYUSER # The 'FSERVER' is server in our domain. [FSERVER] addr=fserv.ex.com # The 'RSERVER' is a server in another domain. [RSERVER] domain=REMGROUP addr=rserv.ex.com Example 2 Using the sharectl Command The following example shows how an authorized user can use sharectl commands to configure global settings for the ex.com environment in SMF. # sharectl set -p section=default -p domain=MYDOMAIN -p user=MYUSER smbfs # sharectl set -p section=FSERVER -p addr=fserv.ex.com smbfs # sharectl set -p section=RSERVER -p domain=REMGROUP -p addr=rserv.ex.com smbfs Example 3 Using the sharectl Command to Show Current Settings The following example shows how an authorized user can use the sharectl get command to view the global settings for smbfs in SMF. The val- ues shown are those set by the previous example. # sharectl get smbfs [default] domain=MYDOMAIN user=MYUSER [FSERVER] addr=fserv.ex.com [RSERVER] domain=REMGROUP addr=rserv.ex.com FILES
$HOME/.nsmbrc User-settable mount point configuration file to store the description for each connection. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWsmbfscu | +-----------------------------+-----------------------------+ |Interface Stability |Committed | +-----------------------------+-----------------------------+ SEE ALSO
smbutil(1), mount_smbfs(1M), sharectl(1M), nsswitch.conf(4), user_attr(4), attributes(5), rbac(5), smbfs(7FS) NOTES
By default, passwords stored in the .nsmbrc file are ignored unless only the file owner has read and write permission. SunOS 5.11 Dec 8 2008 nsmbrc(4)
All times are GMT -4. The time now is 02:06 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy