Guest access to Samba shares
Guest access to Samba shares
Hi,
I've got Slacko 5.4 up and running from a hard drive, and am trying to get network sharing working now.
I installed Samba and created a share which is seen by Win7. In samba.conf I add guest ok = yes to the share, and Win7 still is queried for a password to enter in. My Windows credentials fail.
I then moved guest ok = yes to global, and the homes share continues to behave the same way it did before, the way the other share did.
Do I need to do some kind of Samba user routine somewhere? Thanks.
I've got Slacko 5.4 up and running from a hard drive, and am trying to get network sharing working now.
I installed Samba and created a share which is seen by Win7. In samba.conf I add guest ok = yes to the share, and Win7 still is queried for a password to enter in. My Windows credentials fail.
I then moved guest ok = yes to global, and the homes share continues to behave the same way it did before, the way the other share did.
Do I need to do some kind of Samba user routine somewhere? Thanks.
No, you have everything you need.... Do I need to do some kind of Samba user routine somewhere?...
Although I haven't setup SAMBA PET as of yet on 5.4 try this to see if it affects Windows access: Turn your firewall off and try again. If it still doesn't work with the f/w off momentarily, post your smb.conf?
And, did you install SAMBA from Slacko Repo via the PPM?
Here to help
Last edited by gcmartin on Mon 24 Dec 2012, 03:56, edited 1 time in total.
Ok, I found that out. Here's the testparm output:
[global]
server string = %h is a NAS
max log size = 50
domain master = No
dns proxy = No
idmap config * : backend = tdb
[homes]
comment = "Home directory for %U"
read only = No
[shared-items]
comment = Place to put public stuff
path = root/shared-items
read only = No
guest ok = Yes
[printers]
comment = All Printers
printable = Yes
print ok = Yes
browseable = No
available = No
[global]
server string = %h is a NAS
max log size = 50
domain master = No
dns proxy = No
idmap config * : backend = tdb
[homes]
comment = "Home directory for %U"
read only = No
[shared-items]
comment = Place to put public stuff
path = root/shared-items
read only = No
guest ok = Yes
[printers]
comment = All Printers
printable = Yes
print ok = Yes
browseable = No
available = No
have you tried
name: root
password: woofwoof
name: root
password: woofwoof
Bionicpup64 built with bionic beaver packages http://murga-linux.com/puppy/viewtopic.php?t=114311
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Xenialpup64, built with xenial xerus packages http://murga-linux.com/puppy/viewtopic.php?t=107331
Ok, some more information and questions.
Samba was installed via the package manager.
Yes, I did try that root/woofwoof.
I dropped the firewall last night, and saw no difference.
When I originally set up the firewall, I allowed 192.168.1.1/24 through. Last night I changed that to 192.168.1.1/255.255.255.0, and then Windows would only see the hostnmame, but would not show the shares without a login. This was a change in the wrong direction.
Today on rebooting Puppy is not seen on the network at all. I'm assuming Samba, now installed, is an autorun?
Samba was installed via the package manager.
Yes, I did try that root/woofwoof.
I dropped the firewall last night, and saw no difference.
When I originally set up the firewall, I allowed 192.168.1.1/24 through. Last night I changed that to 192.168.1.1/255.255.255.0, and then Windows would only see the hostnmame, but would not show the shares without a login. This was a change in the wrong direction.
Today on rebooting Puppy is not seen on the network at all. I'm assuming Samba, now installed, is an autorun?
A scenario for a simple and successful SAMBA start
Before beginning much of what I will share here is also posted in the forum here. Also I must say that I have NOT tested what I share on Slacko5.4, as yet.
Assumption
The following ASSUMES you have NOT changed Microsoft's workgroup name from "Workgroup" which is what it ships with.
Scenario for Slacko 5.4
OK here are steps I offer you to follow:
Note: Leave your Puppy firewall off for this test
Edited: Clarifying steps to avoid misunderstandings
Assumption
The following ASSUMES you have NOT changed Microsoft's workgroup name from "Workgroup" which is what it ships with.
Scenario for Slacko 5.4
OK here are steps I offer you to follow:
Note: Leave your Puppy firewall off for this test
- Exit "X"
Code: Select all
Menu>Shutdown>Exit to Prompt
- Set the Linux password for the root ID (remember this password and use this password ALSO in the next step)
Code: Select all
type "passwd"
- Set the SAMBA password for the root ID (make this password the same as was set for the Linux root ID)
Code: Select all
type "smbpasswd -a root"
- Logout of the terminal
Code: Select all
type "logout"
- create the following 2 folders
Code: Select all
type "mkdir -p /mnt/Downloads /root/Downloads" (one of these may already exist)
- start "X" to get back to the desktop
Code: Select all
type "xwin"
- Rename your current SAMBA config; to say, smb.conf.1 for backup
- Replace your SAMBA config with this one
Code: Select all
[global] server string = Samba Server log file = /var/log/samba/log.%m max log size = 50 max protocol = smb2 dns proxy = No workgroup = Workgroup max protocol = smb2 message command = /usr/local/bin/LinPopUp "%f" "%m" %s; rm %s # Delete the two following lines if you don't want clients to follow symlinks. follow symlinks = yes unix extensions = no # ============== File/Folder Definitions ================ # Sharing Parameters tell what items this PC shares out to the LAN [homes] comment = Home Directories valid users = %S read only = No browseable = No [Downloads] path = /mnt/Downloads comment = A Central Download folder for all to use writeable = true guest ok = Yes [Downloads2] comment = A Central Download folder for all to use path = /root/Downloads read only = No guest ok = Yes # ==================== Printer Definitions ===================== [printers] comment = All Printers path = /var/spool/cups guest only = Yes printable = Yes use client driver = Yes browseable = No [LexmarkLaser] path = /var/spool/cups read only = No guest ok = Yes printable = Yes printer name = Laser browseable = No
- Restart SAMBA via the
Code: Select all
Menu>Network>...SAMBA (there is an on-screen button to do so
- Test that SAMBA is sharing from a terminal
Code: Select all
type "smbclient -L localhost" (You will or should see all that Slacko is sharing)
- Go to any Windows PC on your LAN and let us know..
Edited: Clarifying steps to avoid misunderstandings
Last edited by gcmartin on Wed 26 Dec 2012, 03:15, edited 5 times in total.
Thanks so much for all that effort, gcmartin. Sorry for the delay - I had a few Windows machines come in that needed to be dealt with.
I went through the procedure until getting back into X. I stopped there because in trying to set the SMB password, the error came back, failed to find entry for user root. I assume that needs to be dealt with before any progress can be made.
I went through the procedure until getting back into X. I stopped there because in trying to set the SMB password, the error came back, failed to find entry for user root. I assume that needs to be dealt with before any progress can be made.
Ok, thanks. That went pretty smoothly. There was no menu item that I saw, but i restarted the two services via the command line. Then the test failed: NT login error.
But Win7 did see Puppy, and can write to it.
I'm wondering where the network access is on Puppy. And why when I look at root on Win7 it's a different folder structure than shows under root in the Puppy file manager.
Much thanks again for your help.
But Win7 did see Puppy, and can write to it.
I'm wondering where the network access is on Puppy. And why when I look at root on Win7 it's a different folder structure than shows under root in the Puppy file manager.
Much thanks again for your help.
It was atgcmartin wrote:Can you share when you got this error. On which step number did you get the error?
Code: Select all
type "smbclient -L localhost"
Yes I did. I thought it best for safety. You've got to realize I'm a babe in the woods on this stuff.
I don't recall a password query on the linux side at all. The Win7 side, yes. And I entered the samba login in Windows. That's a little weird because Windows states that root is an account on the Win7 machine in the login box. But I knew linux was not going to recognize my windows login - or at least I suspected so.
I don't recall a password query on the linux side at all. The Win7 side, yes. And I entered the samba login in Windows. That's a little weird because Windows states that root is an account on the Win7 machine in the login box. But I knew linux was not going to recognize my windows login - or at least I suspected so.
OK, I understand. But some of the issues you are seeing is because you may be trying to start your trek from a position without following guidelines to get you started easily.paul1149 wrote:Yes I did. I thought it best for safety. You've got to realize I'm a babe in the woods on this stuff. ...
Once you're started, you can then begin to impose necessary changes to match any environmental needs you feel appropriate.
But, in actuality, I claim responsibility for not sharing that in getting you started, you really should have set BOTH the Linux and the SAMBA passwords to be the same so that all would go smoothly thru-out the initial setup and tests.
So, now, that you have an understanding of what it takes to get your sharing efforts going, you might want to turn your f/w back on.
Here to help