Linux-Noob Forums - Samba and NFS

That went nowhere, so new strategy...now CIFS mount is saying, "Host is down"

Wed, 29 May 2019 21:19:03 +0200

I've changed strategies. Since the permissions issue was obviously too complex to tackle with my limited ability to explain the problem, I decided to simply use my router's Samba hosting and plug the hard drive in there. SUCCESS! I can access the samba share using smbclient from the command line, and I can access it from Gnome in "Files."

However, when I try to use CIFS to create a permanent mount to the Samba drive using the EXACT. SAME. INFORMATION. it says, "mount error(112): Host is down."

This is the most frustrating thing I've experienced in the world of computing. I just want to share my damn external drive so that I can use Plex/Kodi/etc. to watch my decades of media on my devices in my house. I'm using Ubuntu 18.04. It shouldn't be this complicated. Any help would be greatly appreciated.

Can see Samba share from external hard drive, but cannot copy files/create folders/etc

Tue, 28 May 2019 22:20:20 +0200

I am running Ubuntu 18.04. I'm new to Linux, but I'm pretty good at reading various guides. Unfortunately, I've tried so many solutions to this problem that I'm not even sure where I am in solving the issue at this point. I have successfully setup a Samba share on my Ubuntu machine, but when I open the folder on my Mac, I cannot do anything other than see the folders and open the files. Trying to do otherwise results in an "Operation not permitted" error on OSX. I know this must be a permissions issue, but I have attempted changing ownership and permissions to wide open in an effort to force the ability to add files to the external hard drive on the Ubuntu machine from my MacBook, and I'm having no luck.

Like I said...I'm new to Linux, so I don't even know where to begin regarding logs, etc. Any guidance--even if it's "completely remove Samba and start over"--would be appreciated. Please bear with me, as I've explained the issue as much as I currently know how to explain it.

Simple guest read, password writable Samba server for a small network

Sat, 05 May 2012 15:09:02 +0200

I use Samba on a CentOS 6 server to share files between Windows, Linux and Mac clients. Guest access is allowed to all folders, but is read only, and there are several Samba accounts for writing files to the shares.

The purpose of this tutorial is to document, roughly, what my configuration was to set up Samba for sharing a couple of folders on the local network in this way.

Install Samba

Code:
# yum install samba

# service smb start

# service nmb start

# chkconfig nmb on

# chkconfig smb on

Create the sharing directories

(In my actual setup, I have used /etc/fstab to mount these directories on separate, large disks, so there's plenty of space. That's beyond the scope of this tutorial, but:

/etc/fstab

UUID=xxxxxxxxx /var/lib/samba/photos ext3 defaults 1 0

UUID=xxxxxxxxx /var/lib/samba/sharedfiles ext3 defaults 1 0

with the real UUIDs substituted in!)

Let's create the two directories where our shared files will be stored:

Code:
# mkdir /var/lib/samba/photos

# mkdir /var/lib/samba/sharedfiles

Add the users and groups

In order to support this model of guests having read only access, and granting write access only to known users, we need to have some users and groups set up at the Unix level. The users and groups at the Unix level map to some of the Samba users we will create later.

They are separate users -- having a Samba login and password doesn't mean you have to give the user in question shell access, because they are two separate accounts and can have two separate passwords. We simply use the users, as I said, to 'map' the Samba credentials to the Unix permissions on disk.

We will also create a group, samba-writers, to allow us to have group write access to the shared folders. I'll add my user account, peter, to this group.

Code:
# groupadd samba-writers

# usermod -a -G samba-writers peter

Let's set the permissions on our two shared folders for this group:

Code:
# chown peter:samba-writers /var/lib/samba/photos

# chown peter:samba-writers /var/lib/samba/sharedfiles

# chmod 775 /var/lib/samba/photos

# chmod 775 /var/lib/samba/sharedfiles

Mode '775' on a directory allows the user (peter), the group (samba-writers) to write files, and others (guests) to just read.

Now, let's add the mappings between Samba users and Unix users. Open /etc/samba/smbusers using your favourite text editor. I'll use vim throughout this guide.

Code:
# vim /etc/samba/smbusers

peter = peter

user1 = user1

user2 = user2

The example accounts user1 and user2 will be for our other Samba-enabled accounts.

Again, we will create Unix shell accounts for user1 and user2, but use different passwords for SMB and their Unix account, and not share the shell password with the users. They only need and want Samba access, so we won't let them log in to the shell.

First, we'll set my password for Samba. A different password from my shell login password.

Code:
# smbpasswd -a peter

('-a' to add the user for the first time. To change it later, just 'smbpasswd peter')

And let's add the other users.

Code:
# useradd -G samba-writers -s /sbin/nologin user1

# passwd user1

# smbpasswd -a user1

Notice we set the shell to /sbin/nologin. These users, as I've said several times already, we are not allowing shell access.

Code:
# useradd -G samba-writers -s /sbin/nologin user2

# passwd user2

# smbpasswd -a user2

Set up the configuration files

Now that our users are ready for Samba, we need to set up the Samba configuration to share the two folders we've created, and allow the right level of access to users, as well as to guests.

Code:
# vim /etc/samba/smb.conf

The default CentOS configuration file has quite a lot already in it. Look for the headings, and make these changes:

Under Network Related Options:

Code:
    workgroup = WORKGROUP

    server string = Server Shared Files

    netbios name = MACHINENAME

    hosts allow = 127. 192.168.0.

    hosts deny = ALL

Set WORKGROUP to the workgroup name, if it's configured differently on your Windows clients. (On some older Windows versions, it may need to be MSHOME.)

Set MACHINENAME to the name you want the Samba server to have.

Finally, we use the 'hosts allow' and 'hosts deny' directives to force Samba only to serve to clients on the local network. In this case, 192.168.0.1 -- 192.168.0.254. You may want to change this to your IP addressing scheme in your network, or remove it to not restrict access to the local network.

Under Standalone Server Options:

Code:
security = user

passdb backend = tdbsam

map to guest = Bad Password

domain master = yes

Under Browser Control Options:

Code:
local master = yes

os level = 99

preferred master = yes

These directives aren't strictly necessary -- in fact, they may cause conflict if you're doing other Windows networking things on the same workgroup. 'os level = 99', combined with the other options, will force this machine to be the 'local master browser' (LMB) and the 'domain master browser' (DMB).

Whichever machine on the network has these roles is responsible for keeping a list of the other machines on the network. Clients use this list to look for other machines that have shared folders available. I've found that forcing my Samba server to be the LMB and DMB, as well as using it as a WINS server, speeds up the time it takes Windows to 'search' for other machines on the network by many many times. (Remember opening 'My Network Places' and clicking 'Show workgroup computers' only to have to wait 15 seconds while Explorer locks up? This avoids that.)

In more complex scenarios, you might not want to enable this to avoid conflict. For our small network scenario, it's a useful speed bonus and causes no problems.

Under Name Resolution:

Code:
wins support = yes

Samba becomes a WINS server, which again can help speed things up -- it means you can address other sharing computers by name without waiting for long periods for NetBIOS to resolve the name. (Some more tech info about this, if you're interested.)

You may want to configure your Windows machines' 'WINS server' IP address to point to your Samba server to get this benefit. (You might need to configure this in your router's DHCP settings for it to stick to all of them.)

Finally, at the bottom of the file, we add our shares:

Code:
[sharedfiles]

comment = Shared files for the network

path = /var/lib/samba/sharedstuff

guest ok = yes

writable = no

create mask = 0664

directory mask = 0775

force group = samba-writers

write list = @samba-writers

[Photos]

comment = Shared photos

path = /var/lib/samba/photos

guest ok = yes

writable = no

create mask = 0664

directory mask = 0775

force group = samba-writers

write list = @samba-writers

Each folder has its own name in brackets, followed by the options for that folder.

We use 'guest ok = yes' to allow guests, but 'writable = no' to make them read only. Anyone in the 'write list' (anyone in the group samba-writers) can write.

There are also other settings to set the default permisisons on files ('create mask = 0664', owner read+write, group read+write, others read only) and folders ('directory mask = 0775', owner read+write+enter, group read+write+enter, others read+enter).

Once we're done, save that file and quit the editor, and reload Samba:

Code:
# service smb restart

# service nmb restart

Just make sure your firewall is letting Samba through:

Code:
# system-config-firewall-tui

And we're ready to test!

Accessing the shares

Linux

Without logging in, we can access the shares by going to smb://machinename (or smb://192.168.0.whatever) in the address bar of the file manager. This works in most file managers.

To log in and have write access, you may have luck with a 'Connect to Server' window that lets you type in the username and password, like this one in the Ubuntu 12.04 desktop's File menu.

[img]/monthly_05_2012/post-1019-0-13574400-1336222085_thumb.png[/img]

I've had problems with write access this way, though, so you may need to use something like smbfs to mount the share permanently.

Mac

Under recent versions of Mac OS X, the server should appear right away in the Finder's sidebar. Simply click the server name to see the shares and browse them.

For write access, simply click the 'Connect As' button in the window and enter your username and password for SMB that you set up earlier.

[img]/monthly_05_2012/post-1019-0-30053800-1336222587_thumb.png[/img]

[img]/monthly_05_2012/post-1019-0-26884900-1336222692_thumb.png[/img]

If you don't see the server in the sidebar, (Lion is more temperamental than Snow Leopard was about this), press ⌘K to bring up the 'Connect to Server' dialogue. Type cifs://machinename or cifs://192.168.0.whatever and click OK to connect.

Windows

The server should show up in 'Network' for guest access.

The best way to log in and have write access, I have found, is to map the shared folder as a network drive. In an Explorer window, click 'Map Network Drive' in the toolbar (it's under the Tools menu on Windows XP and earlier).

Choose a drive letter, enter \\machinename\foldername as the path, and make sure you tick to 'Connect using different credentials'.

[img]/monthly_05_2012/post-1019-0-89993900-1336223125_thumb.png[/img]

You'll then be asked for the username and password, which is the SMB password you set for the account earlier.

[img]/monthly_05_2012/post-1019-0-73397800-1336223138_thumb.png[/img]

  SMB connect.png (Size: 35.98 KB / Downloads: 495)

  connect as button.png (Size: 46.24 KB / Downloads: 483)

  password entry.png (Size: 34.96 KB / Downloads: 495)

  win_map.png (Size: 52.59 KB / Downloads: 478)

  win_pw.png (Size: 29.52 KB / Downloads: 491)

how to optimize samba performance?

Tue, 04 Jan 2011 05:21:32 +0100

Hello,

I have installed a linux server, centos gui server with Raid1, his role will be only a file server. I installed samba and configured it. The file system is EXT3. the server got 4 gigs of memory.

There is a program in windows that writes files to the share.

I searched and i found that there is some commands that you add and they boost the performance. This is what i added to smb.conf

refresh = 1

socket options = TCP_NODELAY IPTOS_LOWDELAY

read raw = No

write raw = Yes

max xmit = 131072

use sendfile = Yes

dead time = 15

getwd cache = Yes

otlocks = No

strict allocate = yes

I got complains that the writes are not fast enough. Before me another IT guy configured the file server and it was faster, what he told my customer that he changed some command of cache but i dont know exactly what he did. I have been asked to find how to boost the performance.

Please give me more commands to try to boost the performance of Samba or tell me if i need to change anything..

Thanks A Lot.

USB drive sharing

Mon, 10 Aug 2009 22:06:53 +0200

Hey,

I use aserver computer to share a usb drive and printer so that me and my mother can both use them.

It was running xp, but in the interest of stablity, I decided to switch it to linux.

The problem is this:

When I share the drive with samba, it works fine and all, but when I reboot, the share is lost.

I had this problem in xp, but I solved it by mounting the drive to a folder on my system drive.

However, I am noob @ linux, so I don't know how to overcome this issue in a foreign os.

Tyvm, wheybags

P.S: Running ubuntu.

Samba Problem.

Fri, 22 Sep 2006 07:41:13 +0200

I install samba 3.0.23 in fedora core 4,

I've finish configuring samba, I can access the samba server from any computer(windows xp pro) in my network,

The problem is, i cannot access my shared folder.

This is my smb.conf file

[shared]

comment = shared document

path = /shared

valid users = lerry

browsable = yes

I already create lerry account in my linux mechine using these command

[root@Testing ~]# useradd lerry

[root@Testing ~]# passwd lerry

New UNIX passwordlerry)

Retype new UNIX passwordlerry)

passwd: all authentication tokens updated successfully.

[root@Testing ~]# smbpasswd lerry

New SMB passwordlerry)

Retype new SMB passwordlerry)

[root@Testing ~]#

Then I try to access shared folder and it ask for username and password,

I entered

username:lerry

password:lerry

but still cannot access the file,

nfs sharing a usb drive?

Sun, 08 Jan 2006 01:52:09 +0100

ComputerA has a usb drive /dev/sdc1 - either fat32 or ntfs.

I mount it as

/dev/sdc1 on /ext/c1 type ntfs (rw,nosuid,nodev,umask=000)

all user on ComputerA can access it.

My /etc/exports has:

/ext 192.168.0.0/24(async,no_subtree_check,rw)

ComputerB has mounted:

ComputerA:/ext on /ext type nfs (rw,nosuid,nodev,addr=192.168.0.7)

no one on B can see files in /ext/c1 - it is like nfs isn't aware that a drive is mounted on 'c1'.

How do I provide nfs access to these usb/firewire drives?

The man page for exports mentions the nohide option, which makes it work for one client - but this did not work for me.

I guess I'll try a share for each drive

I figured nfs would abstract the file system types out of it. Maybe samba is a better choice?

Windows 2003 Domain

Fri, 23 Dec 2005 14:38:54 +0100

This is how I was able to configure Suse 10.0 to authenticate on a Windows 2003 Active Directory Server. I do not know if it will work on previous versions of Windows or with previous versions of Suse Linux.

Notes:

1.Any text that reads domain.internal (lower case) you will replace with your domain.

2.Any text that reads DOMAIN.INTERNAL (upper case) you will replace with your domain in upper case.

3.Any text that reads DOMAIN (upper case) you will replace with your domain (no .internal)

4.The NetBios name is the name of your client (workstation/computer)

This process will require the krb5-client (I installed all of it), Samba, and Samba-Winbind.

Steps

Step 1: Install the Required Packages – This can be done through Yast

Step 2: Edit the /etc/krb5.conf File

[logging]

default = FILE10000:/var/log/krb5lib.log

[libdefaults]

ticket_lifetime = 24000

default_realm = DOMAIN.INTERNAL

default_tkt_enctypes = des3-hmac-sha1 des-cbc-crc des-cbc-md5 aes256-cts arcfour-hmac-md5

default_tgs_enctypes = des3-hmac-sha1 des-cbc-crc des-cbc-md5 aes256-cts arcfour-hmac-md5

[realms]

DOMAIN.INTERNAL = {

kdc = domainserver.domain.internal

admin_server = domainserver.domain.internal

default_domain = DOMAIN.INTERNAL

}

[domain_realm]

.domain.internal = DOMAIN.INTERNAL

domain.internal = DOMAIN.INTERNAL

Step 3: Edit /etc/samba/smb.conf

[global]

security = ads

netbios name = NetBios Name

realm = DOMAIN.INTERNAL

password server = domainserver.domain.internal

workgroup = DOMAIN

idmap uid = 1000-29999

idmap gid = 1000-29999

winbind separator = +

winbind enum users = yes

winbind enum groups = yes

winbind use default domain = yes

template homedir = /home/%D/%U

template shell = /bin/bash

client use spnego = yes

domain master = no

server string =

Step 4: Test the configuration with the testparm command – You should be able to see what you entered in the samba.conf file.

Step 5: Edit /etc/nsswitch.conf to look like the example below

passwd: compat winbind

group: compat winbind

shadow: compat

hosts: files dns wins

networks: files

protocols: db files

services: db files

ethers: db files

rpc: db files

netgroup: nis

Step 6: Modify the PAM settings

These files are all located in the /etc/pam.d folder

File: common-account (It should contain only the following lines)

account sufficient pam_winbind.so

account required pam_unix.so

File: common-auth (It should contain only the following lines)

auth sufficient pam_winbind.so

auth required pam_unix.so nullok_secure use_first_pass

File: common-password file

password required pam_unix.so nullok obscure min=4 max=50 md5

File: common-session

session required pam_mkhomedir.so umask=0022 skel=/etc/skel

Step 7: Make a directory to hold domain user home directories

Note: Use Konsole for this

Note: Use the value you put in the WORKGROUP tag smb.conf file

mkdir /home/DOMAIN

Step 8: Initialize Kerberos

Note: Use Konsole for this

kinit domain_admin_account@DOMAIN.INTERNAL

Step 9: Check to be sure you got a ticket from the domain controller

Note: Use Konsole for this

klist

Step 10: Join the Domain

Note: Use Konsole for this

net ads join -U domainadminuser@DOMAIN.INTERNAL

Step 11: Restart Samba-related Services

Note: The order is important

Note: Use Konsole for this

/etc/init.d/smb stop

/etc/init.d/winbind stop

/etc/init.d/smb start

/etc/init.d/winbind start

Step 12: Attempt to switch user and logon as a domain member. If you can logon than you are successful.

Step 13: Configure SUDO

Add the “Domain Admins” group from windows to the /etc/sudoers file

%Domain Admins ALL=(ALL) ALL

Example:

# sudoers file

# Host alias specification

# User alias specification

# Cmnd alias specification

# Defaults specification

Defaults targetpw # ask for the password of the target user i.e. root

%users ALL=(ALL) ALL # WARNING! Only use this together with 'Defaults targetpw'!

# Runas alias specification

# User privilege specification

root ALL=(ALL) ALL

# Uncomment to allow people in group wheel to run all commands

%Domain Admins ALL=(ALL) ALL

# Same thing without a password

# %wheel ALL=(ALL) NOPASSWD: ALL

# Samples

# %users ALL=/sbin/mount /cdrom,/sbin/umount /cdrom

# %users localhost=/sbin/shutdown -h now

Step 14: See if Konsole will list user names and group names from Windows:

wbinfo -u

wbinfo -g

Step 15: Make sure the permission on the DOMAIN folder under Homes is set to the correct permissions so that the new users can create their folder on login.

Setting up a simple NFS server

Tue, 06 Sep 2005 19:25:43 +0200

In this guide I will show you how to setup a simple NFS server using Fedora, but I will show how to set it up via command line so you should be able to configure it on more than one distribution.

The first step is to make sure you have the NFS server software installed you can check this

by issuing the following command:

Code:
rpm -q nfs-utils

if you don't have this package installed, you can use the YUM packages management tool to install the package, to do this issue the following command:

Code:
yum install nfs-utils

Once you have installed the package you can begin to configure the NFS server, you should have

a file in the /etc directory called: "exports". This file determines what directory's will be exported, who

is allowed to access them and what permissions they have.

In this tutorial I will be exporting my /home directory and allowing only the IP of 192.168.0.13 to

access this exported directory. So the first step is to edit the exports file and added the following:

Code:
/home 192.168.0.13(rw,nohide)

The above exports the /home directory with the read and write permissions the attributes

inside the brackets can be read using the man command along with other attributes that can go in the brackets:

Code:
man exports

Once you have setup your export you should start the portmap daemon. The portmap daemon MUST always be running when running a NFS server.

Code:
service portmap start

Once your portmap has been started you can start your NFS server:

Code:
service nfs start

Once the service has started you can check everything is running by issue the following

command:

Code:
rpcinfo -p

You will get output similar to:

Code:
  program vers proto   port

   100000    2   tcp    111  portmapper

   100000    2   udp    111  portmapper

   100003    2   udp   2049  nfs

   100003    3   udp   2049  nfs

   100003    4   udp   2049  nfs

   100003    2   tcp   2049  nfs

   100003    3   tcp   2049  nfs

   100003    4   tcp   2049  nfs

   100021    1   udp  32833  nlockmgr

   100021    3   udp  32833  nlockmgr

   100021    4   udp  32833  nlockmgr

   100021    1   tcp  32774  nlockmgr

   100021    3   tcp  32774  nlockmgr

   100021    4   tcp  32774  nlockmgr

   100011    1   udp    704  rquotad

   100011    2   udp    704  rquotad

   100011    1   tcp    707  rquotad

   100011    2   tcp    707  rquotad

   100005    1   udp    706  mountd

   100005    1   tcp    709  mountd

   100005    2   udp    706  mountd

   100005    2   tcp    709  mountd

   100005    3   udp    706  mountd

   100005    3   tcp    709  mountd

Once everything is checked out and the services are running you can connect form 192.168.0.13 and mount the /home directory.

Code:
mount 192.168.0.2:/home /mnt/home

Replace 192.168.0.2 with your NFS servers IP and the /mnt/home mount point to one that

suites you.

if you make any changes to the export file you will need to reexport it instead of restarting the

services issue the following:

Code:
exportfs -r

well you can now setup a simple NFS server and store your files on the server

Installing Samba 3.0.14a-2 under Fedora Core 4

Fri, 08 Jul 2005 21:31:14 +0200

This Tutorial is free and may be distributed with reference to this website

It is for people running Fedora Core 4 wanting to setup a working Samba

Server to access the Shares on a Linux machine from a Windows machine

Commands are written in green

Everything else are things you might edit / write / add

Get my Tutorials from [/url][url=http://www.bildunxxluecke.de/usr/fedora]http://www.bildunxxluecke.de/usr/fedora

1.

--------------------------------------------------------------------------------

Prepare your Enviroment:

- samba-common-3.0.14a-2.i386.rpm

- samba-3.0.14a-2.i386.rpm

- samba-client-3.0.14a-2.i386.rpm

- samba-swat-3.0.14a-2.i386.rpm (install only if you want have samba-webinterface)

2.

--------------------------------------------------------------------------------

Now its time to configure SAMBA:

rpm -i samba-common-3.0.14a-2.i386.rpm

rpm -i samba-3.0.14a-2.i386.rpm

rpm -i samba-client-3.0.14a-2.i386.rpm

rpm -i samba-swat-3.0.14a-2.i386.rpm

3.

--------------------------------------------------------------------------------

Everything should be installed now, its time to configure Samba:

- cd /etc/samba/

- vi smb.conf

You can safely edit this file (in fact you must) necessary is :

workgroup = < your windows network workgroup > e.g.: WORKGROUP

server string = < Information about your Samba Server >

netbios name = < Hostname of Sambaserver > e.g.: SMBSERV01

You dont need to touch the shares so far, if you want to share

other directorys keep and eye on the examples in the smb.conf

4.

--------------------------------------------------------------------------------

Now everything is done and you can start:

[root@test] smbd -D

[root@test] nmbd -D

Now you should be able to access your Sambaserver from your

Windowsmachine via \\< smb machine ip >

(5.)

--------------------------------------------------------------------------------

For those who want to use swat with samba :

- cd /etc/xinetd.d/

- vi swat

change disable = yes to => disable = no

- cd /etc/

- vi services

make sure the following line is in it : swat 901/tcp # Samba Web Administration Tool

to test do 'grep 901 /etc/services' , if not in insert it

now do : service xinetd restart

Swat should be running now !

(6.)

--------------------------------------------------------------------------------

To access Swat Webinterface from Lan :

- cd /etc/xinetd.d/

- vi swat

change 'only_from = 127.0.0.1' to 'only_from = 'your.netmask.0.0' e.g.: '192.168.0.0'

the 0 stands for wildcards (e.g. 192.168.0.0 to 192.168.255.255)

--------------------------------------------------------------------------------

Everything is fine .. enjoy now just do http:// SAMBAIP : 901 and login as root

NFS mounts

Thu, 21 Apr 2005 09:17:07 +0200

I'm trying to incorporate a status check on any/all NFS mounts on my system into a script. Is there a simple command that does this? I tried Google-ing up an answer but found nothing helpful. I suck. Anyone have any ideas?

How to mount a Windows share with smbmount

Mon, 21 Mar 2005 23:52:21 +0100

After seeing the how to mount a fat32 partition I thought I'd show you how to mount a share.

First off you need to make sure the share it setup correctly on your Windows system, I'll only focus on sharing with WinXP.

Its not hard on WinXP. First off right-click on the folder you wish to share and select "Sharing and Security".

Select "Share this folder".

You can now set the Share name, you can also fiddle with the maximum number of users allowed at one time (the default is normally good enough).

If you want to heighten the security in this share you can click on "Permissions" and remove the default "Everyone" group (select and click Remove). After this you can click Add. Type the username that will be used to allow access (this has to be a valid user on your WinXP machine). Click Ok, and Ok again. The folder icon should alter and a hand will be holding the folder. This indicates a network share.

Ok so you need to know these things:

The hostname of the WinXP PC (eg winpc). Right click on "My Computer" click on "Computer Name". Look at the "Full Computer Name".

The sharename of the folder (eg shared) Do you remember what you called it .

A user/pass for the winxp system. This is only required if you altered the permissions (i.e. if its not sharing to Everyone).

Phew 50% of the way there.

Ok so onto the Linux system, its relatively simple:

Make the directory you want to mount the share to.

Code:
mkdir /mnt/share

Next either...

Mount the share with user/pass:

Code:
smbmount //winpc/shared /mnt/share -o username=user,password=pass,rw

Or mount the share without a user/pass (this is true if Everyone is still set)

Code:
smbmount //winpc/shared /mnt/share -o rw

Hopefully thats it. Now you can use the share. You cannot create symbolic links or chmod the system (this is restriction on the WinXP side).

If you wish to allow users on the linux side access to the share then you will need to alter the options. Adding in uid= or gid= to allow access to users or groups respectively by mounting the drive with there permissions. Here's an example:

Code:
smbmount //winpc/shared /mnt/share -o rw,uid=znx

This will mount the drive as if user znx had done it. Thus he will have rw access to the shared.

Hands up who I managed to confuse

Winbind = using Windows ADS Accounts to login

Fri, 13 Aug 2004 15:25:56 +0200

This post is to show you how to use Windows ADS accounts to login to your Linux server instead of manually making seperate Linux local accounts. The reason I did this is because some of our clients wanted to use sftp and the easiest way to manage all the different accounts for each client is creating OU's in Active Directory Services in Windows. This document will work with Windows 2000 or 2003 ADS.

Winbind is integrated with Samba and will require you to configure Samba and PAM for this operation to work succesfully. Lets get started

Step 1:

Lets backup your smb.conf file incase you make a mistake you can start over

Code:
cp /etc/samba/smb.conf /etc/samba/smb.bak

Step 2:

Now its time to edit your smb.conf file

Code:
vi /etc/samba/smb.conf

Step 3:

Now enter in the following below. You can delete the contents of your orginal smb.conf file as this will replace everything in there.

You will have to change the following lines to your configuration:

workgroup =

Mount a shared drive

Mon, 26 Jan 2004 23:59:04 +0100

Hello, I hope someone may beable to help me.

I have two computers with drives I need access to, what I do right now is this:

from a terminal I su - so I am on as root then type in:

Mount -t smb //xbox/f /mnt/xbox

once I hit enter it asks for a password I type it in and viola that drive is now mounted.

the other one is:

Mount -t smb //192.168.0.100/storage /mnt/pc2

once I hit enter it asks for a password I type it in and viola that drive is now mounted.

I can also type it in this way:

Mount -a //xbox/f /mnt/xbox and it works fine after I enter my password.

What I would really like to know is how do I enter this into FSTAB so this is all done automatic at boot?

I would sure love a small guide from someone on how to enter this properly

Thank you for any help

Sheriff

Samba Questions

Mon, 15 Dec 2003 17:03:34 +0100

Does Samba work with Active Directory and Server 2003 Yet? Anyone know?