File server setup question

j0eh4x · 06-27-2012, 11:57 AM

I have two one terabyte hardiness drives that I'm considering turning into a file server, I was going to put both of them in one machine and share them to my network with samba, I was also considering putting a torrent client on the server that could be remote controlled via an android device, I have a few questions. What would be the optimal hd configuration? Should I put Linux on a small partition and have it mount ntfs partitions, or would I be better off to just leave it at having a Linux file system? Also does anyone know of a Linux torrent client that can do this, please keep in mind I will be using ubuntu server and will not have access to a gui. Any ideas or suggestions would be great? Encryption on the drives would be nice too but not a must.

pan64 · 06-27-2012, 01:13 PM

you would need at least two partitions, one for the OS and the second for the data, for the share. But probably you can use more.

j0eh4x · 06-27-2012, 02:23 PM

Does it matter what fjust use a Linux partition on the storage drives? And is there an easy way I can link the two as one so that instead of having folder1(hd 1) and folder2(hd 2) so I can just have one shared folder

thehouseofho · 06-28-2012, 07:03 AM

How important is the data to you? If you only have the two hard drives and the data is important, I would recommend RAID 1 for mirroring so that you have a backup. Ideally, you would have a third hard drive to set up RAID 5.

As for being able to see the two drives as one, LVM is your answer. You'll need to set up the disks as a volume group first, then you create logical volumes (partitions) within the volume group. The operating system will treat the volume group as a single disk and the logical volumes you create will be able to span across the physical disks.

j0eh4x · 06-28-2012, 01:10 PM

Thank you I will research that some, also I'm trying to set up samba with ubuntu server 12.04 and I've tried just about every guide on the Internet and when I try to access from windows 7 it still says invalid user or pass

thehouseofho · 06-28-2012, 01:27 PM

Quote:

Originally Posted by j0eh4x

Thank you I will research that some, also I'm trying to set up samba with ubuntu server 12.04 and I've tried just about every guide on the Internet and when I try to access from windows 7 it still says invalid user or pass

This requires a little bit more info. Are you using centralized user management or local user accounts?

j0eh4x · 06-28-2012, 01:40 PM

Quote:

Originally Posted by thehouseofho

This requires a little bit more info. Are you using centralized user management or local user accounts?

Um I'm not sure. Kind of a newbie, what I did was followed a guide to configure smb.conf to be open no password, but it kept asking for login and password so I configured it to be users secured and did smbpasswd for the user is created on install of the server then when it asked for credentials on windows in clicked use other account and entered the login and password, still didn't work

thehouseofho · 06-28-2012, 01:47 PM

Quote:

Originally Posted by j0eh4x

Um I'm not sure. Kind of a newbie, what I did was followed a guide to configure smb.conf to be open no password, but it kept asking for login and password so I configured it to be users secured and did smbpasswd for the user is created on install of the server then when it asked for credentials on windows in clicked use other account and entered the login and password, still didn't work

OK, it sounds like you're using a local account. Are you entering the username in the username@LinuxServerName format? If you don't, Windows automatically prepends the computer name and a \ to the username.

j0eh4x · 06-28-2012, 01:58 PM

Quote:

Originally Posted by thehouseofho

OK, it sounds like you're using a local account. Are you entering the username in the username@LinuxServerName format? If you don't, Windows automatically prepends the computer name and a \ to the username.

Just tried still a no go

j0eh4x · 06-28-2012, 02:04 PM

this is my smb.conf file

Quote:

#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
# - When such options are commented with ";", the proposed setting
# differs from the default Samba behaviour
# - When commented with "#", the proposed setting is the default
# behaviour of Samba but the option is considered important
# enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.
# A well-established practice is to name the original file
# "smb.conf.master" and create the "real" config file with
# testparm -s smb.conf.master >smb.conf
# This minimizes the size of the really used smb.conf file
# which, according to the Samba Team, impacts performance
# However, use this with caution if your smb.conf file contains nested
# "include" statements. See Debian bug #483187 for a case
# where using a master file is not a good idea.
#

#======================= Global Settings =======================

[global]
log file = /var/log/samba/log.%m
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
obey pam restrictions = yes
null passwords = yes
map to guest = bad user
winbind use default domain = no
passwd program = /usr/bin/passwd %u
passdb backend = tdbsam
dns proxy = no
server string = %h server (Samba, Ubuntu)
unix password sync = yes
workgroup = WORKGROUP
syslog = 0
panic action = /usr/share/samba/panic-action %d
usershare allow guests = yes
max log size = 1000
pam password change = yes

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of

# server string is the equivalent of the NT Description field

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
# wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z

# This will prevent nmbd to search for NetBIOS names through DNS.

# What naming service and in what order should we use to resolve host names
# to IP addresses
; name resolve order = lmhosts host wins bcast

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
; interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = yes

#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects

# Cap the size of the individual log files (in KiB).

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
# syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.

# Do something sensible when Samba crashes: mail the admin a backtrace

####### Authentication #######

# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
# security = user

# You may wish to use password encryption. See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections

########## Domains ###########

# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
#
; domain logons = yes
#
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
; logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
# logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
; logon drive = H:
# logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
; logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe. The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe.
# The following assumes a "machines" group exists on the system
; add machine script = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.
; add group script = /usr/sbin/addgroup --force-badname %g

########## Printing ##########

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
# load printers = yes

# lpr(ng) printing. You may wish to override the location of the
# printcap file
; printing = bsd
; printcap name = /etc/printcap

# CUPS printing. See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
; printing = cups
; printcap name = cups

############ Misc ############

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /home/samba/etc/smb.conf.%m

# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
# SO_RCVBUF=8192 SO_SNDBUF=8192
# socket options = TCP_NODELAY

# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
; message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &

# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
# domain master = auto

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
; idmap uid = 10000-20000
; idmap gid = 10000-20000
; template shell = /bin/bash

# The following was the default behaviour in sarge,
# but samba upstream reverted the default because it might induce
# performance issues in large organizations.
# See Debian bug #368251 for some of the consequences of *not*
# having this setting and smb.conf(5) for details.
; winbind enum groups = yes
; winbind enum users = yes

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 (default) means that usershare is disabled.
; usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones

#======================= Share Definitions =======================

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home director as \\server\username
;[homes]
; comment = Home Directories
; browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
; read only = yes

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
; create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
; directory mask = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server. Un-comment the following parameter
# to make sure that only "username" can connect to \\server\username
# The following parameter makes sure that only "username" can connect
#
# This might need tweaking when using external authentication schemes
; valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
; comment = Network Logon Service
; path = /home/samba/netlogon
; guest ok = yes
; read only = yes

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = no
; create mask = 0600
; directory mask = 0700

[printers]
comment = All Printers
browseable = no
path = /var/spool/samba
printable = yes
guest ok = no
read only = yes
create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
browseable = yes
read only = yes
guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
; write list = root, @lpadmin

# A sample share for sharing your CD-ROM with others.
;[cdrom]
; comment = Samba server's CD-ROM
; read only = yes
; locking = no
; path = /cdrom
; guest ok = yes

# The next two parameters show how to auto-mount a CD-ROM when the
# cdrom share is accesed. For this to work /etc/fstab must contain
# an entry like this:
#
# /dev/scd0 /cdrom iso9660 defaults,noauto,ro,user 0 0
#
# The CD-ROM gets unmounted automatically after the connection to the
#
# If you don't want to use auto-mounting/unmounting make sure the CD
# is mounted on /cdrom
#
; preexec = /bin/mount /cdrom
; postexec = /bin/umount /cdrom

[joe]
path = /home/joe/fs

available = yes

valid users = joe

read only = no

browsable = yes

public = yes

writable = yes

thehouseofho · 06-28-2012, 02:53 PM

One of your issues is that you're attempting to share the user home directory. You'll need to tweak the entries under ##Share Definitions## to get that working.

Check out this link. It will help you with your original intended request of sharing a folder via Samba without a password.
http://amazingrando.wordpress.com/20...password-easy/

j0eh4x · 06-28-2012, 11:50 PM

Quote:

Originally Posted by thehouseofho

One of your issues is that you're attempting to share the user home directory. You'll need to tweak the entries under ##Share Definitions## to get that working.

Check out this link. It will help you with your original intended request of sharing a folder via Samba without a password.
http://amazingrando.wordpress.com/20...password-easy/

this may be a stupid question but what would be a good place to put my share? the purpose of this server is to be a file server so it doesn't really matter to me where it is located.

j0eh4x · 06-29-2012, 12:19 AM

Quote:

Originally Posted by thehouseofho

One of your issues is that you're attempting to share the user home directory. You'll need to tweak the entries under ##Share Definitions## to get that working.

Check out this link. It will help you with your original intended request of sharing a folder via Samba without a password.
http://amazingrando.wordpress.com/20...password-easy/

also i followed that guide step by step and it still prompts me for authentication

centos123 · 06-29-2012, 12:37 AM

for configuring file server ....you must have clear scenario of what kind of file server you are going to configure for client...

i have file sever on centos destro..you can take guide from my thread.just search by username you will get the thread..

Well current issue is authentication of windows user in ubuntu server.correct.
for that always remember to have user and passwd of user same in both server and client.then only authentication will granted.

so add user with same name and pass in server..and provide dir permission
also type commnad smbpasswd for user and give same pass..

try this...

j0eh4x · 06-29-2012, 11:07 AM

Quote:

Originally Posted by centos123

for configuring file server ....you must have clear scenario of what kind of file server you are going to configure for client...

i have file sever on centos destro..you can take guide from my thread.just search by username you will get the thread..

Well current issue is authentication of windows user in ubuntu server.correct.
for that always remember to have user and passwd of user same in both server and client.then only authentication will granted.

so add user with same name and pass in server..and provide dir permission
also type commnad smbpasswd for user and give same pass..

try this...

All I need is one excuse to try a new Linux distro and you just gave it to me lol