When it browses for shares - this is done without the user's In Windows the client's username and password is automatically sent It explains the steps that happen behind the scenes: Happened to stumble across this thread on the Ubuntu forums, and thought it might help. This way, I can set the directory to 775 and I will be able to write because I am joined to the workgroup but other users can only read and execute. I know, it's deprecated, but it works and security = user and map to user = bad user wasn't working for me.Īnyway, now it seems that anyone who connects to the share get's unix global permissions for the directory, which is manageable, but I want users that are joined to the workgroup specified in smb.conf to get unix group permissions. The key was setting security to security = share. Any Windows user who connects to my network can see the NAS under Netowork and access it. UPDATE: So, the share is now available across my network regardless of the work group. Panic action = /usr/share/samba/panic-action %d Socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 Passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully*. Server string = %h server (Samba, Ubuntu) Press enter to see a dump of your service definitions Rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384) Load smb config files from /etc/samba/smb.conf Now I've probably spent at least 4 hours and it's still not working. The worst part is the first time I did this about a week ago, I spent about 30 minutes on it and it worked perfectly. I cant access it manually from XBMC either. I'm trying to share it with XBMC and it's not even showing up under smb in the file manager. It should be totally public to anyone on the network. The problem is, It shouldn't be asking for a password at all. If I'm on a computer with the the default WORKGROUP I can read and execute a computer on my Home workgroup can read write and execute. Once I'm in, The workgroup configuration is working properly. Great now I can access the files in the share. I cant just leave it blank though because it will use my workgroup as the domain so I enter \ for the username to clear it out and log in with a blank username and password. I can get to the share from Windows 7 by going to start and typing \Hostname\Sharename but I'm prompted for a username and password. If I enter the un pw I get full access but I shouldn't have to my current settings are. Now, if I try to connect to \Hostname I'm prompted for a username and password. Users who were not on the share's workgroup had read access but users who were on the workgroup had read/write access. Anyone on my network could access the share and it's contents simply by typing \Hostname. I had a public samba share on Ubuntu server. Here's what I had before and what I am trying to accomplish again. So I should start by saying that I did this successfully less than a week ago and I had no trouble but I have since reformatted and reconfigured my server and now I'm having the hardest time remembering how I did it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |