I’m trying to get my wife’s Windows 7 Pro box to connect to a share I set up on my 13.2 KDE computer. Her computer can connect to mine, but when I click on the folder, Windows generated a “Does not have permission” error. When I go back and remove the “guest access” option, then Windows asks for a username and password, but I haven’t set up one.
This is how I set it up, in case anybody can discover a problem!
I used Yast/Samba Server to create the share.
The share looks like this -
path /home/scott/Dropbox/Photos/Jennifer-Backup
Read only no
guest ok Yes
inherit acls Yes
Bottom options of “Allow users to Share Their Directories” and “Allow Guest Access” are both checked.
The firewall has been disabled.
The “Windows Shares - KDE Control Module” is blank for Default user name and default Password
It seems like you are clearly saying that your machine is an openSUSE 13.2/KDE with a mounted share, but when you (logged in locally) click on the share you are getting a MSWindows (because you capitalized the “W”) error or do you really mean that you are getting a popup error generated by KDE (which means your word “window” should not be capitalized)?
In any case,
You should understand that for all OS there are two layers of permissions when configuring network shares…
There is the lower file system permissions.
There is the higher level network share permissions.
The combination of the two types of file permissions determines the effective requirement to access the share remotely.
Only the file system permission determines the requirement for local access, for instance using a file manager application (but not a “network place” mapped with something like cifs://)
Dangerously making a serious of wild guesses and assumptions about what your’e describing,
I’m assuming that the file system permissions maybe changed from your User account to an actual Guest or Anonymous account instead of configuring a suitable Group that enables both that account and your own User account. Simple solution probably is to simply map a “Network Places” location in your File Manager (Dolphin? PCMan?) so that you access the location exactly the same way the remote machine does.
Alternative probably would be to create and configure the proper User and Group permissions so that both your User account and the Guest account YAST is configuring can access that file tree directly.
The share is set up on my KDE machine. When I go over to the Windows 7 computer and try to get to the share via Windows, it generates the “permission denied” on the windows machine.
The folder on the KDE machine I’m trying to share, the user is “scott” and the group is “users”.
So, are you saying then that you’re connecting remotely from 2 different Win7 machines,
You can connect successfully using your wife’s Win7 machine
but
You cannot connect successfully using your own Win7 machine?
No only trying to connect to the linux machine from my wife’s windows computer. She can connect, but can’t access anything because of a “permission denied” error.
Update - on the wife’s windows computer, my linux computer no longer appears in the computers on the network. It was there before lunch! Just logged out and in trying to see if that would restore it.
On 7/3/2015 10:26 AM, ScottyK wrote:
>
> Greetings!
>
> I’m trying to get my wife’s Windows 7 Pro box to connect to a share I
> set up on my 13.2 KDE computer. Her computer can connect to mine, but
> when I click on the folder, Windows generated a “Does not have
> permission” error. When I go back and remove the “guest access” option,
> then Windows asks for a username and password, but I haven’t set up
> one.
>
> This is how I set it up, in case anybody can discover a problem!
>
> I used Yast/Samba Server to create the share.
>
> The share looks like this -
>
> path /home/scott/Dropbox/Photos/Jennifer-Backup
> Read only no
> guest ok Yes
> inherit acls Yes
>
> Bottom options of “Allow users to Share Their Directories” and “Allow
> Guest Access” are both checked.
>
> The firewall has been disabled.
>
> The “Windows Shares - KDE Control Module” is blank for Default user name
> and default Password
>
> Ideas?? Thanks!
>
>
ScottyK;
This appears to be a permission problem on the share. First make sure that the [global] section of /etc/samba/smb.conf
contains the parameter
map to guest = Bad User
This makes sure that a user without a Samba account will be
mapped to the guest user by Samba. For openSUSE the Samba guest account is identified with the Linux account nobody in
the group nobody.
There are now two basic methods to provide the required permissions. You can adjust the Linux permissions on the
file/directories to be shared so that user nobody has appropriate permissions. e.g. rwxrwxrwx (777) or rwxrw-rw- (766).
You can set permissions in your file manager or with the chmod command. If supported by your file system you can also
use acls using your file manager or the command setfacl (see the manual entries for getfacl and setfacl).
The second method is to use the share level parameters in /etc/samba/smb.conf
force user = <yourusername>
or
force group = <yourgroupname>
With the second method the guest will be mapped to <yourusername> or <yourgroupname> and the nix permissions will apply.
This Tutorial by Swerdna is still valid and will give you more details. However, it is not always online. If you fail
to connect try on a later day. http://swerdna.dyndns.org/susesambaserver.html
If you still have problems please post the contents of your /etc/samba/smb.conf. Cut and paste between code tags.
–
P.V.
“We’re all in this together, I’m pulling for you” Red Green
On 7/4/2015 9:16 AM, ScottyK wrote:
>
> THAT DID IT!! It’s connecting now and she can access the files. I’m
> saving this post for future reference. Thanks again!
>
>
The firewall has been disabled.
It is good to hear that you have your Samba shares working. You should be able to enable the firewall. Just be sure
that these three services are allowed through SuSEfirewall2; Samba Server, Netbios Server and Samba Client.
–
P.V.
“We’re all in this together, I’m pulling for you” Red Green