• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

Solved [SOLVED]Samba shows up, now doesn't. Ideas?

Itproman

Member

Thanks: 1
Messages: 75

#1
The other night I Installed Samba 4. from Ports and the next day noticed there was no /../examples/smb.conf, so I found the standard file online and copied it using ssh. Today I edited it and this morning my FreeBSD machine showed up in win. Now, it's no longer there, yet, I never changed anything, AFAIK.

Testparm shows everything is ok and samba_server is listed in services.

Here is my smb4.conf file:
(After getting an error about smb.conf not being found, I renamed it smb4.conf and it showed up right away)
Note: Only the networking has been changed, plus local, master browser, etc.The network=1 Win7 laptop,1 Ubuntu 12.04 server/desktop /w Samba,1 FreeBSD 10 server

Code:
#======================= Global Settings =====================================
[global]

# workgroup = NT-Domain-Name or Workgroup-Name, eg: REDHAT4
   workgroup = MSHOME

# server string is the equivalent of the NT Description field
   server string = Samba Server

# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
   hosts allow = 192.168.2.

#Name Resolve Order
   name resolve order= bcast host lmhosts wins

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

# you may wish to override the location of the printcap file
;   printcap name = /etc/printcap

# on SystemV system setting printcap name to lpstat should allow
# you to automatically obtain a printer list from the SystemV spool
# system
;   printcap name = lpstat

# It should not be necessary to specify the print system type unless
# it is non-standard. Currently supported print systems include:
# bsd, sysv, plp, lprng, aix, hpux, qnx
;   printing = bsd

# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
;  guest account = pcguest

# this tells Samba to use a separate log file for each machine
# that connects
   log file = /usr/local/samba/var/log.%m

# Put a capping on the size of the log files (in Kb).
   max log size = 50

# Security mode. Most people will want user level security. See
# security_level.txt for details.
   security = user

# Use password server option only with security = server
# The argument list may include:
#   password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
#   password server = *
;   password server = <NT-Server-Name>

# Note: Do NOT use the now deprecated option of "domain controller"
# This option is no longer implemented.

# You may wish to use password encryption. Please read
# ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation.
# Do not enable this option unless you have read those documents
encrypt passwords = yes

# 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 = /usr/local/samba/lib/smb.conf.%m

# Most people will find that this option gives better performance.
# See speed.txt and the manual pages for details
# You may want to add the following on a Linux system:
#         SO_RCVBUF=8192 SO_SNDBUF=8192
   socket options = TCP_NODELAY 

# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
;   interfaces = 192.168.12.2/24 192.168.13.2/24 

# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
   local master = yes

# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
    os level = 33

# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
   domain master = yes 

# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
   preferred master = yes

# Enable this if you want Samba to be a domain logon server for 
# Windows95 workstations. 
;   domain logons = yes

# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
;   logon script = %m.bat
# run a specific logon batch file per username
;   logon script = %U.bat

# Where to store roving profiles (only for Win95 and WinNT)
#        %L substitutes for this servers netbios name, %U is username
#        You must uncomment the [Profiles] share below
;   logon path = \\%L\Profiles\%U

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
    wins support = yes

# 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

# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one	WINS Server on the network. The default is NO.
;   wins proxy = yes

# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The built-in default for versions 1.9.17 is yes,
# this has been changed in version 1.9.18 to no.
   dns proxy = no 

#============================ Share Definitions ==============================
[homes]
   comment = Home Directories
   browseable = yes
   writable = yes

# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
;   comment = Network Logon Service
;   path = /usr/local/samba/lib/netlogon
;   guest ok = yes
;   writable = no
;   share modes = no


# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
;    path = /usr/local/samba/profiles
;    browseable = no
;    guest ok = yes


# NOTE: If you have a BSD-style print system there is no need to 
# specifically define each individual printer
[printers]
   comment = All Printers
   path = /usr/spool/samba
   browseable = no
# Set public = yes to allow user 'guest account' to print
   guest ok = no
   writable = no
   printable = yes

# This one is useful for people to share files
;[tmp]
;   comment = Temporary file space
;   path = /tmp
;   read only = no
;   public = yes

# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
;   comment = Public Stuff
;   path = /home/samba
;   public = yes
;   writable = yes
;   printable = no
;   write list = @staff

# Other examples. 
#
# A private printer, usable only by fred. Spool data will be placed in fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
;   comment = Fred's Printer
;   valid users = fred
;   path = /homes/fred
;   printer = freds_printer
;   public = no
;   writable = no
;   printable = yes

# A private directory, usable only by fred. Note that fred requires write
# access to the directory.
;[fredsdir]
;   comment = Fred's Service
;   path = /usr/somewhere/private
;   valid users = fred
;   public = no
;   writable = yes
;   printable = no

# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %U option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
;  comment = PC Directories
;  path = /usr/pc/%m
;  public = no
;  writable = yes

# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
;[public]
;   path = /usr/somewhere/else/public
;   public = yes
;   only guest = yes
;   writable = yes
;   printable = no

# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
;[myshare]
;   comment = Mary's and Fred's stuff
;   path = /usr/somewhere/shared
;   valid users = mary fred
;   public = no
;   writable = yes
;   printable = no
;   create mask = 0765
 

Chris_H

Aspiring Daemon

Thanks: 111
Messages: 829

#2
Re: Samba shows up,now doesn't.Ideas?

Greetings, @Itproman.
I won't profess to be a samba() expert. It's been some time, since I've had a need for it. But, it would really help to deduce who's not functioning correctly, by at least getting some of the output from Samba's log. In other words; does Samba's log(s) indicate Samba is happy?

Just thought I'd mention it. Because that's probably the first place I'd look, if it were me. That helps to determine whether Samba's upset, or one of your other clients -- Windows, Linux, ...

--Chris
 
Last edited by a moderator:

bigb89

New Member


Messages: 19

#3
Re: Samba shows up, now doesn't. Ideas?

I have one server running Samba 3 and another one running Samba 4. I've found that if you just want a 'standalone' samba server to create shares, then you might want to stick with samba 3. Since samba4 appears to be heavily used as an AD DS replacement, rather than a standalone server. In all cases, you can also use samba4 as standalone (that's what I have):

Here's what I get when run a samba_server status:
Code:
# /usr/local/etc/rc.d/samba_server status
nmbd is running as pid 75203.
smbd is running as pid 75207.
winbindd is running as pid 75211.
What services do you get when you run that?

Also, I could be wrong, but I don't think that just renaming smb.conf to smb4.conf will correct the issue, since I believe both files have different settings. Samba4 has been completely re-written and it's not the same as samba 3, per say.

For example, looking over your smb.conf (smb4.conf) file, there are settings that you do not have present , such as:
Code:
server role = standalone server
The above let's the service know whether to run in standalone mode, or be an AD DS server, etc. Not sure how much that could affect your configuration, but you never know.

With that said, instead of re-naming smb.conf to smb4.conf, you should backup smb.conf and run the following command:

samba-tool domain provision --use-rfc2307 --interactive


That will prompt you how to configure the samba4 server after it's installed, and will create a new smb4.conf file with the correct settings.
 

Itproman

Member

Thanks: 1
Messages: 75

#4
Re: Samba shows up, now doesn't. Ideas?

The result of the query suggested above:

Code:
/usr/local/etc/rc.d/samba_server status
nmbd is running as pid 889.
smbd is running as pid 893.
winbindd is running as pid 897.
This after trying: smbclient -L richard@freebsdbox and it complaining and telling me that samba_server_enable="YES" needed to be in /etc/rc.conf (not "samba_enable="YES" which is what I had and what the handbook suggested(which is fine for Samba 3.6, which is what I was using with FreeBSD 9.2 -which worked fine.). After I corrected that and restarted the Samba Server, I got the successful reply above.

One error down!

When I restarted, I noticed a number of errors,namely it complaining: unable to open new log file /usr/local/samba/var/log.wb-FREEBSDBOX:No such file or directory.

Also ..../var/log.smbd -same error message.

Also....errors to do with CUPS and failing to retrieve the printer list -probably because there is no printer attached to that machine!

Another test:

Code:
$ smbclient -L richard@freebsdbox
Enter richard's password: 
Connection to richard@freebsdbox failed (Error NT_STATUS_UNSUCCESSFUL)
 

Itproman

Member

Thanks: 1
Messages: 75

#5
Re: Samba shows up, now doesn't. Ideas?

samba-tool domain provision --use-rfc2307 --interactive

I believe I ran the command right:

Code:
root@freebsdbox:/usr/home/richard # service samba_server onerestart
Performing sanity check on Samba configuration: OK
Stopping winbindd.
Waiting for PIDS: 897.
Stopping smbd.
Waiting for PIDS: 893.
Stopping nmbd.
Waiting for PIDS: 889.
Performing sanity check on Samba configuration: OK
Starting nmbd.
Starting smbd.
Starting winbindd.
Still have problem though:

Code:
smbclient -L richard@freebsdbox
Enter richard's password: 
Connection to richard@freebsdbox failed (Error NT_STATUS_UNSUCCESSFUL)
I'll have to work on it more later.
 

Chris_H

Aspiring Daemon

Thanks: 111
Messages: 829

#6
Re: Samba shows up, now doesn't. Ideas?

I can't speak to the Error NT_STATUS_UNSUCCESSFUL, because I don't have any Windows boxes handy. But, regarding the printer related issue(s); do you currently have a printer setup? If so, does it use print/cups?
If so. You'll need to feed samba(7) the details, regarding it.

--Chris
 

bigb89

New Member


Messages: 19

#7
Re: Samba shows up, now doesn't. Ideas?

Are you running the smbclient command from the localhost or from a different machine?

If you're running on a different machine, what happens when run it from the localhost, such as this:

--------
smbclient -U richard -L localhost
--------

As far as the print CUPS error goes, I believe you're correct on that. If you're not using printer on that server, those errors can be ignored and shouldn't affect you browsing your shares.

For the log messages, you can also poke around /var/log/messages after run the 'smbclient' command, you should see something around there.
 

Itproman

Member

Thanks: 1
Messages: 75

#8
Re: Samba shows up, now doesn't. Ideas?

bigb89 said:
Are you running the smbclient command from the localhost or from a different machine?

If you're running on a different machine, what happens when run it from the localhost, such as this:

--------
smbclient -U richard -L localhost
--------

As far as the print CUPS error goes, I believe you're correct on that. If you're not using printer on that server, those errors can be ignored and shouldn't affect you browsing your shares.

For the log messages, you can also poke around /var/log/messages after run the 'smbclient' command, you should see something around there.

I was running the smbclient command from both: another machine and the freebsd box.

After running the samba-tool command suggested above,freebsdbox shows up in Ubuntu and on the Windows 7 laptop.On the former,when i click on the homes icon,it refuses to allow me,in,but,on the windows 7 laptop,after supplying my uid and password,I got in fine and transferred a pdf between the Ubuntu and freebsd boxes and read it,so,we're getting there,except for the log errors,it's all looking a lot better.

Thanks to all.
 

Itproman

Member

Thanks: 1
Messages: 75

#9
Re: Samba shows up, now doesn't. Ideas?

bigb89 said:
Are you running the smbclient command from the localhost or from a different machine?

If you're running on a different machine, what happens when run it from the localhost, such as this:

--------
smbclient -U richard -L localhost
--------

As far as the print CUPS error goes, I believe you're correct on that. If you're not using printer on that server, those errors can be ignored and shouldn't affect you browsing your shares.

For the log messages, you can also poke around /var/log/messages after run the 'smbclient' command, you should see something around there.

Here's the results of the above command:

Code:
$ smbclient -U richard -L localhost
Enter richard's password:
Domain=[MSHOME] OS=[Unix] Server=[Samba 4.1.6]

        Sharename       Type      Comment
        ---------       ----      -------
        homes           Disk      Home Directories
        IPC$            IPC       IPC Service (Samba Server)
        richard         Disk      Home Directories
Domain=[MSHOME] OS=[Unix] Server=[Samba 4.1.6]

        Server               Comment
        ---------            -------
        BLACKBOX             blackbox server (Samba, Ubuntu)
        FREEBSDBOX           Samba Server
        RICHARD-PC           Laptop

        Workgroup            Master
        ---------            -------
        MSHOME               FREEBSDBOX
This from a SSH session from the Windows 7 laptop using Putty.

Now,if I can just solve these error messages mentioned above about log files missing which keep constantly scrolling down my ttys0 screen making work on that terminal very difficult,I'll be finally out of trouble!

I fixed it!

1)I created the missing directories -which didn't fix the problem.
2)I did this cmd found in a forum during a search:"I just created dir '/var/log/samba/' and touch log.smbd. everything great" End of error message! :h