Bug 374128 - Accessing an smb:// fails by showing the authentication dialog again
Summary: Accessing an smb:// fails by showing the authentication dialog again
Status: RESOLVED NOT A BUG
Alias: None
Product: kio-extras
Classification: Frameworks and Libraries
Component: default (show other bugs)
Version: 5.8.7
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-24 21:58 UTC by Gregor Mi
Modified: 2018-04-09 19:08 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gregor Mi 2016-12-24 21:58:02 UTC
Background
----------
I would like to setup a shared folder for the local home network. I use openSUSE 42.1 and Plasma 5.28.0. To test the setup I try to access the configured share from the same machine.

Using dolphin
-------------
I enter smb://user1@localhost/myfolder/ into the address bar and the authentication dialog appears. I enter username and password and the dialog appears again. On the console where I started dolphin there is no further explanation for this error. Then I get the message "Access denied to...".

How to track down the error?
----------------------------
To find the root cause of this error I tried to mount the samba share via command line:

```
$ sudo mount -t cifs -o user=user1 //127.0.0.1/myfolder /home/user1/tmp/mntsmbtest/
Password for user1@//127.0.0.1/myfolder:  *****
mount error(5): Input/output error
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
```

As recommended here (https://www.thomas-krenn.com/de/wiki/Windows_Freigabe_unter_Linux_mounten) I used the cifs filesystem instead of smbfs.

The "Input/output error" I got is described here: http://www.linuxquestions.org/questions/linux-networking-3/cifs-mount-error-5-%3D-input-output-error-but-smbfs-works-456897/ One solution there is to use sec=ntml but this does not work (because I do not connect to a windows host but to my own openSuSE host where I didn't configure anything special)

How would you start to track down the root cause of the problem?

Is using a Samba share even the recommended way of sharing a folder in the local network nowadays?
Comment 1 Nate Graham 2018-01-26 00:29:43 UTC
Yes, Samba is still the recommended approach. But you don't need to use an smb:// URL to access a locally-available folder; just navigate there normally. The Samba share should work find if you try to access it from another machine.