Page 1 of 3

Samba problems [SOLVED]

Posted: Mon Nov 10, 2008 11:03 pm
by jcfuller
Rather than hijack another thread I decided to move the followup here in case someone wants to comment further.
Previous thread: http://foldingforum.org/viewtopic.php?f=52&t=6793

Code: Select all

Check to see if Samba is Running
It should return a [ok] on the right side of your terminal
No Ok's I get:
* nmbd is running
* smdb is running

Code: Select all

Add Samba password for your users that will be accessing the shared folder.
Confusing to this old brain. I only have one user on this box.

I found you cannot add a samba user without it being a Linux user.

Code: Select all

Restart Samba

Code: Select all

Browse to The New Shared Folder
- Open IE or Firefox and put the IP address in the address bar like so:
I changed \\ to // or left them out and Firefox cannot find the server.

I can see it in Windows Explorer but login fails.

James

Re: Samba problems

Posted: Mon Nov 10, 2008 11:35 pm
by KE1HA
jcfuller wrote:Rather than hijack another thread I decided to move the followup here in case someone wants to comment further.
Previous thread: http://foldingforum.org/viewtopic.php?f=52&t=6793

Code: Select all

Check to see if Samba is Running
It should return a [ok] on the right side of your terminal
No Ok's I get:
* nmbd is running
* smdb is running

Code: Select all

Add Samba password for your users that will be accessing the shared folder.
Confusing to this old brain. I only have one user on this box. I found you cannot add a samba user without it being a Linux user.

Code: Select all

Restart Samba

Code: Select all

Browse to The New Shared Folder
- Open IE or Firefox and put the IP address in the address bar like so:
I changed \\ to // or left them out and Firefox cannot find the server. I can see it in Windows Explorer but login fails.
James
No Ok's I get:
* nmbd is running
* smdb is running
That's ok, the samba server is running and thats what you need. I was thinking about the restart which gives the [ok] for both shutting down the deamon and starting it back up.

Example:

Code: Select all

sudo /etc/init.d/samba restart
Results:
* Stopping Samba daemons [ OK ]
* Starting Samba daemons [ OK ]
Confusing to this old brain. I only have one user on this box. I found you cannot add a samba user without it being a Linux user.
Yes, I didn't state it, the username must have an account on that particular system, I use only one user on the boxes I build as well. After you've modified the the smb.conf file and added the username and pw, do a restart of the samba sever like I stated above. You should then be able to simply add your IP address in the address bar and hit enter. When prompted, use the same username and password you added above to access the folder. One thing to note, click the rememebr password on the Windows Ddialog box. I'm not at home or could validate each step.

If you still can't access it, post back here, and I'll sort it out when I get home for sure.
.

Re: Samba problems

Posted: Tue Nov 11, 2008 12:14 am
by tmoble
what I do is map a drive from my Win desktop to the ubuntu box.
I don't have a local DNS server on my home network so I make an entry in the \Windows\system32\drivers\etc\hosts file. there's a sample in there already, pattern after it. Mine looks like:

192.168.1.108 ubunfold

then I can ping it by name and it's easy to map a drive letter to the share on the ubuntu box. From the windows command line it can be done like this:

net use z: \\ubunfold\tom

tom being the name of my home dir on the ubuntu box. Or, use the drive mapping tool on the windows explorer Tools menu. When it prompts me for a username/password, I logon with the same username/password as I use to log on to the unbuntu box from it's keyboard and monitor.

once you have the drive mapped it easy to add it to fahmon, just like a local FAH install. remember you have to drill down to the folder that contains the FAHlog.txt file.

Clear as mud? Good. If you have trouble with getting samba going correctly post a note here, I'll put up a copy of my smb.conf file.

Re: Samba problems

Posted: Tue Nov 11, 2008 12:17 am
by jcfuller
I'm still having no luck.
Firefox will not connect.
I can see the folder in Windows Explorer and I get this login box:
http://www.jcfuller.com/ubu64.PNG

Notice the title bar: "nycap.rr.com" This is my isp.

After I enter the user and password I get this message box:

http://www.jcfuller.com/nogo.PNG

James

Re: Samba problems

Posted: Tue Nov 11, 2008 12:32 am
by tmoble
why are you trying to open it with FF? use windows explorer. You'll need to have a web server running on the ubuntu box to get a connection in FF AFAIK.

Re: Samba problems

Posted: Tue Nov 11, 2008 12:39 am
by tmoble
this is my smb.conf file, if it posts correctly. Notice that almost all the lines are commented out, only a few are updated. notice the workgroup line, security = user, most of the rest can be commented out. All the lines beginning with # or ; are comments and ignored.

Code: Select all

#
# 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
#

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

[global]

## Browsing/Identification ###

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

# server string is the equivalent of the NT Description field
   server string = %h server (Samba, Ubuntu)

# 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.
#   dns proxy = no

# 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
   log file = /var/log/samba/log.%m

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

# 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.
   syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
   panic action = /usr/share/samba/panic-action %d


####### 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.
#   encrypt passwords = true

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

#   obey pam restrictions = yes

# 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.
#   unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<[email protected]> for
# sending the correct chat script for the passwd program in Debian Sarge).
#   passwd program = /usr/bin/passwd %u
#   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# 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'.
#   pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped 
# to anonymous connections
map to guest = bad user

########## 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

########## 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
   usershare allow guests = yes

#======================= 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 directory 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 = no

# 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 = 0775

# 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 = 0775

# 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
# 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
;   share modes = no

# 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.
# Replace 'ntadmin' with the name of the group your admin users are
# members of.
;   write list = root, @ntadmin

# 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


Re: Samba problems

Posted: Tue Nov 11, 2008 12:40 am
by jcfuller
tmoble wrote:why are you trying to open it with FF? use windows explorer. You'll need to have a web server running on the ubuntu box to get a connection in FF AFAIK.
Following KE1HA suggestions from the other thread.

James

Re: Samba problems

Posted: Tue Nov 11, 2008 12:43 am
by tmoble
Not sure what he's trying to do there. Main reason to get samba up is to map a drive to use fahmon. browser and http stuff won't help there.

Re: Samba problems

Posted: Tue Nov 11, 2008 12:49 am
by tmoble
on the workgroup line in the smb.conf file above, 20310 is the name of my local workgroup on my home LAN. If you're not sure what yours is rt-clk on your "My Computer" icon, choose properties, go to the Computer Name tab.

Re: Samba problems

Posted: Tue Nov 11, 2008 1:09 am
by KE1HA
Belay my last, I read the wrong post.

@ jcfuller -

If understad things correctly, you have a home network and you followed the How-To get a GPU2 client running on a linux box yes? The you added Samba to allow for monitoring via FahMon? Im assuming both your Windows machine and the linux box are on the same LAN yes ?
.

Re: Samba problems

Posted: Tue Nov 11, 2008 1:22 am
by tmoble
I didn't add that at all. I'm sharing my home dir as is default. The FAH directories are sub-directories of my home dir so they're accessible. Ever use a text editor called nano? or vi? with no GUI on the machine you'll be needing to use one of those to edit the smb.conf file.

Re: Samba problems

Posted: Tue Nov 11, 2008 1:28 am
by KE1HA
Sorry tmoble .. I was reading your posts thinking it was jc's posts. It's been a long day :oops:

The way youv'e described works as well. I use a standard template for installs on UB right out ot the box, so I've attempted to minimize the amount of post install work for each node.

Re: Samba problems

Posted: Tue Nov 11, 2008 1:31 am
by tmoble
KE1HA, good thing you're here. Thanks for taking time to write up that guide, it's excellent.

I don't see the post from jcfuller that I responded to above. He asked if I appended your text creating the FAH-Share, I didn't.

Re: Samba problems

Posted: Tue Nov 11, 2008 1:37 am
by jcfuller
KE1HA wrote:Belay my last, I read the wrong post.

@ jcfuller -

If understad things correctly, you have a home network and you followed the How-To get a GPU2 client running on a linux box yes? The you added Samba to allow for monitoring via FahMon? Im assuming both your Windows machine and the linux box are on the same LAN yes ?
.
Yes.
I changed my smb.conf to almost match tmoble except I added a [FHA-SHARE] section.
Still no connect from Windows Explorer.

James

Re: Samba problems

Posted: Tue Nov 11, 2008 1:44 am
by jcfuller
The denial message box from above says there may be a problem if logging on as the same user
who is logged in on the linux box???

James