Accessing Shares on Network

Questions about Wi-Fi and other network devices, file sharing, firewalls, connection sharing etc
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
Txnca

Accessing Shares on Network

Post by Txnca »

I am getting totally p*****! :evil: It was working now it isn't!

I am running Isadora KDE from my laptop. I have a Windows XP Pro Box downstairs. It has the printer hooked up to it. It also has 3.82TB of hard drive space which has all my stuff. All the other computers in the house run Windows XP Home edition so networking has to be simple file sharing which is how every thing is set up.
Problem is, when I try to access my Windows shares from my laptop, Samba INSISTS that there HAS to be a password. :evil: THERE IS NO PASSWORD! :evil: I have looked everywhere for an answer. I've looked through all of the stuff here on Samba and googled till my fingers are blue to no avail! I've read the Samba man pages forwards and backwards, I have went to the Samba website and read there setups. Everything seems to say you have to have a password. You have to set your linux box up as a server etc. I am NOT going to do that. I have kids who pull movies off of my XP box who are not computer literate enough to do so if I have to setup a Domain. There is NO reason to do so in MY HOME!
Do I sound P****D YET??!! Especially when it was working! I had everything going. No problems at all. I could get to my shares no problem. I could jam to my Floyd or whatever on my laptop without having any problems (except from the kids and the wife who don't know what good music is!). Then all of a sudden it starts asking for a password to try to get onto my shares.

Here is a rundown of my smb.conf file. Maybe yall can see something I am missing.

Code: Select all

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

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = HOME
   netbios name = SDBKDELT1
# 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 bcast wins

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

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

# 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 <<kahan@informatik.tu-muenchen.de> 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

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

# 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.
# 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
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
altair4
Level 20
Level 20
Posts: 11460
Joined: Tue Feb 03, 2009 10:27 am

Re: Accessing Shares on Network

Post by altair4 »

Txnca wrote:Problem is, when I try to access my Windows shares from my laptop, Samba INSISTS that there HAS to be a password. :evil: THERE IS NO PASSWORD! :evil: I have looked everywhere for an answer. I REFUSE to use a password on a simple file sharing arraignment. :evil: I've looked through all of the stuff here on Samba and googled till my fingers are blue to no avail! I've read the Samba man pages forwards and backwards, I have went to the Samba website and read there setups. Everything seems to say you have to have a password. You have to set your linux box up as a server etc. I am NOT going to do that. I have kids who pull movies off of my XP box who are not computer literate enough to do so if I have to setup a Domain. There is NO reason to do so in MY HOME!
First off, Samba itself is a server utility and it's purpose is to provide shares to your Windows clients ( in this case ). It has nothing to do with accessing a Windows share. All those HowTo's you looked at are describing setting up a Samba server.

Second, Smbclient ( the samba client utility ). which is what you use to access the Windows share, is not asking for a password - it's just relaying the message. Windows is the one asking for a password.

In a terminal run the following command to see if it generates any error messages:

Code: Select all

smbtree
Last edited by altair4 on Fri Nov 12, 2010 12:28 pm, edited 1 time in total.
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
JasonLG

Re: Accessing Shares on Network

Post by JasonLG »

I had similar problems trying to get a samba share from a NAS to auto-mount at start up using smbfs. It wouldn't mount unless I set a password. After I did no problems. From what I remember if you set a password you can set XP to remember it so your kids won't have to enter it every time. I followed the instruction on this page https://help.ubuntu.com/community/Samba ... lientGuide under Connecting using CIFS now my samba share mounts in my home folder and acts like part of the native file system.

altair4, I'm glad you came along. You seem to be the resident samba guru around here. I think I'll bow out and pass the ball to you buddy. :)
Last edited by JasonLG on Fri Nov 12, 2010 12:33 pm, edited 1 time in total.
Txnca

Re: Accessing Shares on Network

Post by Txnca »

From running smbtree as requested;

Code: Select all

smbtree
Unknown parameter encountered: "SO_RCVBUF"
Ignoring unknown parameter "SO_RCVBUF"
Enter txnca's password: 
HOME
        \\SDBKDELT1                     SFTLT1 server (Samba, Ubuntu)
Server requested LANMAN password (share-level security) but 'client lanman auth' is disabled
failed tcon_X with NT_STATUS_ACCESS_DENIED
        \\SDB1           
                \\SDB1\Samsung          Samsung ML-2510 Series
                \\SDB1\J$               Default share
                \\SDB1\Tups           
                \\SDB1\Printer          Send To OneNote 2007
                \\SDB1\C$               Default share
                \\SDB1\H$               Default share
                \\SDB1\ADMIN$           Remote Admin
                \\SDB1\Music          
                \\SDB1\F$               Default share
                \\SDB1\Vuze           
                \\SDB1\Pink Floyd     
                \\SDB1\H-Downloads    
                \\SDB1\Printer4         hp psc 1300 series
                \\SDB1\ACE_Online     
                \\SDB1\My ISO Files   
                \\SDB1\Downloads      
                \\SDB1\G$               Default share
                \\SDB1\D-Downloads    
                \\SDB1\I$               Default share
                \\SDB1\SharedDocs     
                \\SDB1\print$           Printer Drivers
                \\SDB1\D$               Default share
                \\SDB1\IPC$             Remote IPC
                \\SDB1\TorrentDLs     
                \\SDB1\uTorrent       
                \\SDB1\E$               Default share
        \\EDB1           
                \\EDB1\EDB1 Share     
                \\EDB1\IPC$             Remote IPC
The only errors I see have to do with the receive buffer size which it doesn't seem to understand even though it suggests that you use them, and the fact that it is asking for a password for the laptop shares, which is my home directory.
I've never heard of Windows asking for a password for files shared through simple file sharing.
altair4
Level 20
Level 20
Posts: 11460
Joined: Tue Feb 03, 2009 10:27 am

Re: Accessing Shares on Network

Post by altair4 »

I should tell you I know nothing of KDE so .........

On the Mint end, you're getting the lanman error because you're using share level security instead of user level security. And you're sharing you home folder using the [homes] meta share not by actually having a share pointing to your home folder and that share will ask for a password because that's what you told it to do.

To fix the lanman error just go into smb.conf and just comment out the following line:

Code: Select all

# security = share
This will return it to the default "security = user"
Then restart samba:

Code: Select all

sudo service smbd restart
On the Windows side just to make sure I understand the nature of the problem:

All of the shares ending in "$" are administrative shares and Windows will require that you provide it with username = administrator and administrators password. All the the other shares like \\SDB1\Downloads should not be asking for a password. In fact with Windows Simple Sharing there is no way to create a password since all shares are guest accessible by default. Are you being asked for a password for shares not ending with a "$" ?
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
Txnca

Re: Accessing Shares on Network

Post by Txnca »

On the Windows side just to make sure I understand the nature of the problem:

All of the shares ending in "$" are administrative shares and Windows will require that you provide it with username = administrator and administrators password. All the the other shares like \\SDB1\Downloads should not be asking for a password. In fact with Windows Simple Sharing there is no way to create a password since all shares are guest accessible by default. Are you being asked for a password for shares not ending with a "$" ?
That is correct. What is really weird is that sometimes I can see the shares and sometimes just to see the shares it asks for a password. I've never come across this before. When I had Helena running it worked just fine. When I used Gnome it worked just fine, and it was working just fine then all of a sudden it starts asking for the passwords for the simple file shares which can't have a password! It doesn't make any sense. The only thing that it could be is this system since I can get on any other system and get to them without an issue. One reason I know this is the kids would be screaming if the couldn't get to their Barbie or Scoobie Doo movies! I'm at a loss!

I redid the smbtree command, and this is what I am getting now;

Code: Select all

smbtree
Unknown parameter encountered: "SO_RCVBUF"
Ignoring unknown parameter "SO_RCVBUF"
Enter txnca's password: 
HOME
        \\SDBKDELT1                     Samba 3.4.7
                \\SDBKDELT1\ML-2510             ML-2510
                \\SDBKDELT1\Print_to_PDF        Print to a PDF File
                \\SDBKDELT1\IPC$                IPC Service (Samba 3.4.7)
                \\SDBKDELT1\print$              Printer Drivers
                \\SDBKDELT1\homes               Home Directories
        \\SDB1           
        \\EDB1           
                \\EDB1\EDB1 Share     
                \\EDB1\IPC$             Remote IPC
Now it isn't showing the shares on the SDB1 box although it is showing the shares on one of my daughters computers which shouldn't be on, but I am glad it is so you can see that it is showing. I am able to access it btw! OOPS! Nope, it is now asking for a password???!!! confused???!!
altair4
Level 20
Level 20
Posts: 11460
Joined: Tue Feb 03, 2009 10:27 am

Re: Accessing Shares on Network

Post by altair4 »

Wow, SDB1 clearly has shares since smbtree just showed them a few minutes ago - and now they are gone. And there is no error message about why SDB1 has no shares. If it was an authentication or password encryption ( even an anonymous guest passes a password it's just null ) issue it should have given you an error message.

I'll be honest, I've never come across something like this. Let me dig around a bit, I apologize for not having a ready answer.
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.
Txnca

Re: Accessing Shares on Network

Post by Txnca »

That's OK. I don't have one either.

Now I'm really going to throw a wrench at you. If I open Dolphin, which is the file manager for KDE, and I try to get to the shares, I get asked for a password, that is if I click on network, and then click the Samba Shares Icon, then click on the SDB1 Icon. NOW comes the wrench.

IF i just type the path to the share, i.e.

Code: Select all

smb://sdb1
and hit enter, I get to it with no problem, I get no password prompt, I get the list of shares showing. I can then click on ANY of the directories, at least the ones that are not "hidden" (C$) and I can get into them and open any of the files or copy them, all without a password prompt! And that is IN Dolphin! I know I might get some people saying that Konqueror is the default file manager in KDE, and if I used it that I wouldn't be having this problem. Guess what?! I tried it as well, same issue. And the same thing with the typing in the path to the share worked. Maybe it's a bug in Dolphin or the new KDE?

Well, that last isn't correct either. Now I am getting the password prompt again. This is driving me nuts! BTW, Thanks for the help so far! I certainly do appreciate it!
Locked

Return to “Networking”