Yet another filesharing problem (Mint 12/Cinnamon/Win7)

[kaidukhanne]

Hello,
Well, I'm prooud I haven't lashed out in frustration thus far, but figured it was high-time to reach out for help.

I've got Mint seeing the Win7 shares just fine, but not it's own or (and this is what I'm trying to make work) the Win7 seeing the Mint shares.

Code: Select all

[b]testparm:[/b]
onesock2@onesock2-desktop ~ $ testparm -s
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[printers]"
Processing section "[print$]"
Processing section "[NBDownMint2]"
Loaded services file OK.
Server role: ROLE_STANDALONE
[global]
   workgroup = MDKGROUP
   netbios name = ONESOCK-DESK
   map to guest = Bad User
   pam password change = Yes
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
   username map = /etc/samba/smbusers
   unix password sync = Yes
   syslog = 0
   log file = /var/log/samba/log.%m
   max log size = 1000
   dns proxy = No
   usershare allow guests = Yes
   panic action = /usr/share/samba/panic-action %d
   force user = onesock2

[printers]
   comment = All Printers
   path = /var/spool/samba
   create mask = 0700
   printable = Yes
   browseable = No

[print$]
   comment = Printer Drivers
   path = /var/lib/samba/printers

[NBDownMint2]
   path = /home/onesock2/NBDownloads
   read only = No
   guest ok = Yes
onesock2@onesock2-desktop ~ $


and

Code: Select all

[b]smbtree[/b]
MDKGROUP
   \\VHIBS                VHIBS
cli_start_connection: failed to connect to VHIBS<20> (0.0.0.0). Error NT_STATUS_UNSUCCESSFUL
   \\ONESOCK-DESK         Samba 3.5.11
cli_start_connection: failed to connect to ONESOCK-DESK<20> (0.0.0.0). Error NT_STATUS_UNSUCCESSFUL
   \\KAIDU-PC             
      \\KAIDU-PC\Users             
      \\KAIDU-PC\NBDownloads2      
      \\KAIDU-PC\IPC$              Remote IPC
      \\KAIDU-PC\H$                Default share
      \\KAIDU-PC\G$                Default share
      \\KAIDU-PC\Downloads         
      \\KAIDU-PC\D$                Default share
      \\KAIDU-PC\C$                Default share
      \\KAIDU-PC\ADMIN$            Remote Admin


Any suggestions or help would be appreciated. Nearing wit's end as they say.

FWIW, oddities I've noticed:
nautilus-share is installed, but seems to have no effect at all on the smb.conf.
Tried to make sure permissions were set (the user on the win7 machine is Kaidu, Onesock2 on Mint) but Kaidu couldn't be added to smbshare using gpasswd, however kaidu could and onesock2 could (don't remember if I tried Onesock2).

Thanks,
Kaidu

[altair4]

onesock2@onesock2-desktop ~ $ testparm -s

Your mint machine is invisible to the network because your host name is 1 character too long.

The easiest way to fix this for samba purposes is to use samba itself:

Edit smb.conf as root:

Code: Select all

gksu gedit /etc/samba/smb.conf

Add a line to the [global] section - right under the workgroup line:

Code: Select all

netbios name = onesock2-desk

It doesn't have to be that exact name but it has to be 15 characters or less in length
While you're there add another line:

Code: Select all

name resolve order = bcast host lmhosts wins

Then save smb.conf and back in the terminal restart samba:

Code: Select all

sudo service nmbd restart

Code: Select all

sudo service smbd restart

See how far that gets you. If you have further problems you might go through the following checklist:
Samba Browsing Problems Checklist: http://forums.linuxmint.com/viewtopic.php?f=42&t=88146&start=0

nautilus-share is installed, but seems to have no effect at all on the smb.conf.

It won't. It's shares are defined in /var/lib/samba/usershares. The way to show how all of these Usershares are configured is to issue the following command:

Code: Select all

net usershare info --long

[kaidukhanne]

Hello,
Thanks for the reply Altair, I've actually read quite a few of your posts.

The netbios name is set shorter (I got that from one of your earlier posts) already, you may need to scroll down in the "code"section.

I'm pretty sure it also has the resolver order right, but will double-check.

I was bashing my head for a while, when I realized I'd not restarted the nmbd daemon, once I did that, the computer shows up under win7, but I can't access the share. That's where I'm stuck.

Thanks,
Kaidu

[kaidukhanne]

I thought maybe it was something wrong with the permissions section, but I'm totally not sure. There is a onesock2 and Kaidu user.

Here's the whole SMB.conf

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

## Browsing/Identification ###

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

   netbios name = onesock-desk

   force user = onesock2

# 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 = bcast lmhosts host 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 = 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 <<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
   username map = /etc/samba/smbusers

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

[NBDownMint2]
   path = /home/onesock2/NBDownloads
   writeable = yes
   browseable = yes
   forceuser = onesock2
   guest ok = yes

[kaidukhanne]

net usershare info --long (which needed to be sudo, btw)

Code: Select all

[nbdownmint2]
path=/home/onesock2/NBDownloads
comment=
usershare_acl=Everyone:F,
guest_ok=y


Sorry if I'm flooding you with too much info, I figure it's better than not enough.

[altair4]

net usershare info --long (which needed to be sudo, btw)

No it does not. "net usershare info" will show you all the usershares you created under your own username. "net usershare info --long" will show you all shares created by everyone - including root.
EDIT:

net usershare info on its own dumps out info on the user defined shares that were created by the current user, or restricts them to share names that match the given wildcard pattern ('*' matches one or more characters, '?' matches only one character). If the '-l' or '--long' option is also given, it prints out info on user defined shares created by other users.

You have created shares using both Classic and Usershares on the same target which will eventually cause problems so I would get rid of one or the other.

What are the permissions on the target:

Code: Select all

ls -al /home/onesock2

If you don't want to post the entire output I need to see at least the ones ending in "." and ".." and "NBDownloads"

[kaidukhanne]

Truly appreciate the help. I'll get that list output as soon as I'm back at the house (I was home for lunch).

For some reason when I tried the net usershare info --long it hung. I waited maybe 3-5 minutes. Then broke out and re-ran it as sudo. *shrugs*
Thanks again,
Kaidu

[altair4]

The only thing I can think of that would have that affect on "net usershare" is if you aren't a member of a particular group. Run the following command:

Code: Select all

id

And see if you are a member of: 123(sambashare)
If not add yourself:

Code: Select all

sudo gpasswd -a your-user-name sambashare

Then logout and login again.

If you weren't a member of that though you would never have been able to create a share through Nautilus as a regular user - only as root.

[kaidukhanne]

Home now.
Thanks for sticking with me.

id was fine for both onesock2 and kaidu. Both had the 123(sambashare) group.

Here's the list you mentioned earlier:
Interesting that sambashare group seems to own the directory, is that right?

Code: Select all

kaidu@onesock2-desktop ~ $ ls -al /home/onesock2
total 584
drwxr-xr-x 44 onesock2 onesock2     4096 2012-05-07 17:40 .
drwxr-xr-x  4 root     root         4096 2012-04-24 21:36 ..
drwx------  3 onesock2 onesock2     4096 2012-04-22 11:39 .adobe
-rw-------  1 onesock2 onesock2     3660 2012-05-07 17:40 .bash_history
-rw-r--r--  1 onesock2 onesock2      220 2012-04-22 02:41 .bash_logout
drwx------  5 onesock2 onesock2     4096 2012-04-22 02:45 .cache
drwxr-xr-x  2 onesock2 onesock2     4096 2012-04-22 11:55 .caja
drwxr-xr-x 17 onesock2 onesock2     4096 2012-05-06 19:27 .config
drwxrwxr-x  5 onesock2 onesock2     4096 2012-05-06 11:20 .cxoffice
drwx------  3 onesock2 onesock2     4096 2012-04-22 02:45 .dbus
drwxr-xr-x  2 onesock2 onesock2     4096 2012-04-22 19:12 Desktop
-rw-rw-r--  1 onesock2 onesock2       28 2012-05-06 10:13 .dmrc
drwxr-xr-x  6 onesock2 onesock2     4096 2012-04-22 18:27 Documents
drwxr-xr-x 11 onesock2 onesock2     4096 2012-05-07 12:30 Downloads
-rw-------  1 onesock2 onesock2       16 2012-04-22 02:45 .esd_auth
drwxr-xr-x  2 onesock2 onesock2     4096 2012-05-06 11:20 .fontconfig
drwx------  5 onesock2 onesock2     4096 2012-05-06 10:13 .gconf
-rw-r-----  1 onesock2 onesock2        0 2012-05-07 12:16 .gksu.lock
drwx------  5 onesock2 onesock2     4096 2012-05-07 17:40 .gnome2
drwx------  2 onesock2 onesock2     4096 2012-04-22 02:55 .gnome2_private
drwxrwxr-x  2 onesock2 onesock2     4096 2012-05-06 01:40 .gstreamer-0.10
-rw-rw-r--  1 onesock2 onesock2      152 2012-05-06 10:13 .gtk-bookmarks
drwx------  2 onesock2 onesock2     4096 2012-04-22 02:45 .gvfs
-rw-------  1 onesock2 onesock2     5740 2012-05-06 10:13 .ICEauthority
drwxrwxr-x  2 onesock2 onesock2     4096 2012-04-22 12:24 .icons
drwxrwxr-x  3 onesock2 onesock2     4096 2012-04-22 19:12 .kde
drwxrwxr-x  5 onesock2 onesock2     4096 2012-04-22 16:42 .linuxmint
drwxr-xr-x  3 onesock2 onesock2     4096 2012-04-22 02:45 .local
drwx------  3 onesock2 onesock2     4096 2012-04-22 11:59 .macromedia
drwx------  3 onesock2 onesock2     4096 2007-11-05 19:39 MAIL
drwx------  3 onesock2 onesock2     4096 2012-01-29 12:06 Mail2
drwx------  5 onesock2 onesock2     4096 2012-04-22 14:38 .mate2
drwx------  2 onesock2 onesock2     4096 2012-04-22 11:55 .mate2_private
drwx------  5 onesock2 onesock2     4096 2012-05-06 19:25 .mateconf
drwx------  2 onesock2 onesock2     4096 2012-05-06 19:45 .mateconfd
-rw-rw-r--  1 onesock2 onesock2      388 2012-04-22 19:12 .mime.types
drwxr-xr-x  4 onesock2 onesock2     4096 2012-04-22 02:41 .mozilla
drwxr-xr-x  2 onesock2 onesock2     4096 2012-04-22 02:45 Music
drwxrwxrwx 15 onesock2 sambashare   4096 2012-05-07 12:30 NBDownloads
drwx------  3 onesock2 onesock2     4096 2012-05-05 21:39 .nv
-rw-rw-r--  1 onesock2 onesock2     1285 2012-04-22 11:44 .nvidia-settings-rc
drwxr-xr-x  2 onesock2 onesock2     4096 2012-04-22 02:45 Pictures
-rw-r--r--  1 onesock2 onesock2      797 2012-05-06 19:07 .profile
drwxr-xr-x  2 onesock2 onesock2     4096 2012-04-22 02:45 Public
drwx------  2 onesock2 onesock2     4096 2012-05-06 10:13 .pulse
-rw-------  1 onesock2 onesock2      256 2012-04-22 02:45 .pulse-cookie
drwx------  6 onesock2 onesock2     4096 2012-05-07 17:40 .purple
drwxr-xr-x  2 onesock2 onesock2     4096 2012-05-06 10:14 .quicksynergy
-rw-r--r--  1 onesock2 onesock2        0 2012-04-22 02:51 .sudo_as_admin_successful
drwxr-xr-x  2 onesock2 onesock2     4096 2012-04-22 02:45 Templates
drwxrwxr-x  3 onesock2 onesock2     4096 2012-04-22 15:39 .themes
drwx------  4 onesock2 onesock2     4096 2012-04-22 15:01 .thumbnails
drwx------  4 onesock2 onesock2     4096 2012-04-22 23:47 .thunderbird
drwxr-xr-x  2 onesock2 onesock2     4096 2012-04-22 02:45 Videos
drwxrwx---  6 onesock2 onesock2     4096 2012-05-06 03:03 .wesnoth1.8
-rw-------  1 onesock2 onesock2        0 2012-05-07 17:40 .Xauthority
drwx------  4 onesock2 onesock2     4096 2012-05-06 22:44 .xchat2
-rw-------  1 onesock2 onesock2   364784 2012-05-07 17:40 .xsession-errors


[altair4]

The users on your network are confusing me. Actually there are a lot of things in your description that is confusing me.

For some reason when I tried the net usershare info --long it hung. I waited maybe 3-5 minutes. Then broke out and re-ran it as sudo.

I have no explanation for that phenomenon. I can't even figure out how to reproduce it.

drwxrwxrwx 15 onesock2 sambashare 4096 2012-05-07 12:30 NBDownloads
... Interesting that sambashare group seems to own the directory, is that right?

Since the permissions on the folder are set to rwx for everyone it doesn't matter what the group is but that group of sambashare didn't happen by itself. If you didn't explicitly set it to that manually I have no explanation for why that's happening either.

Tried to make sure permissions were set (the user on the win7 machine is Kaidu, Onesock2 on Mint) but Kaidu couldn't be added to smbshare using gpasswd, however kaidu could and onesock2 could (don't remember if I tried Onesock2)

You're going to have to help me with this. Kaidu and kaidu in Linux are 2 different users. Are you setting this up assuming that one is the same as the other?

failed to connect to ONESOCK-DESK<20> (0.0.0.0). Error NT_STATUS_UNSUCCESSFUL

That's usually caused by the either the netbios name length problem or the name resolve order but you've fixed all that. Of course there are other impediments like a firewall or an encrypted home directory or if the machines are in different subnets. Worst case I'd access the share by ip address to bypass this netbios issue just to see if you can get access. From the Mint machine have the samba client access it's own samba server using your own ip address:

Code: Select all

nautilus smb://192.168.0.100

As far as your share is concerned, I see nothing wrong with the way it's set up although I wouldn't have shared the same folder twice. It allows guest access and the Linux permissions are set to 777 so there's nothing stopping a remote anonymous login. But remember that Windows passes the users login user name and password automatically without being asked. If you didn't set up a Linux user for that windows user and did not give him a samba password then Samba would have converted that Windows user to the guest account ( "nobody" ) automatically and he would have access.

But if you did create a user on the Mint machine that matches the user on the Windows machine and gave him a samba password different from the Windows user's login password then you will be prompted for a password in Windows. Since you only have a guest share it wouldn't have been necessary to create any users or give anyone a samba password but ....

[kaidukhanne]

So, did a few things:
1. Took ownership of the folder back, no joy.
2. Created a kaidu user (had to remove the Kaidu user, it wouldn't let me have both using whatever user mgr is included in cinnamon)
3. Added kaidu to smbshare, restarted smbd and nmbd, no joy.
4. Removed the nautilus share, no joy
5. Removed share from the smb.conf
6. Turned off the firewall
7. Created the share (new name, same folder) with nautilus, no joy (also, no anon users)
8 Restarted the system (actually had to get something from the windows dual booted side)

Viola! Working. Doesn't explain why, but..
*edit-update*
I turned the ufw back on, and it stopped working.
Turned it off and it didn't help.. until I rebooted. So, something in ufw isn't opening up after it's turned off is my guess.
I guess to be a good citizen, I should review the ufw instructions and see if I can figure out why it's not working while that's on.

Kaidu

[altair4]

Not an expert on firewalls but are you allowing samba through the firewall?

Code: Select all

sudo ufw allow Samba

[kaidukhanne]

Sweet, that worked. You da' man.
If you guys ever make it to Penguicon, look me up, I'll buy you a beer (or whatever your drink of choice is)