I am running openSuSE 12.2 wth kde4.9.2 at home. There is a samba server that is normally accessed with the very convenient smb:// protocol in dolphin and konqueor. That protocol is preferable to mount.cifs or fstab. The samba server is functioning normally and maps with a windows client or by mount.cifs on a couple linux machines. However, dolphin is unable to make a connection. Does anyone know what is happening? It worked perfectly with dolphin distributed with openSuSE 12.1.

Thanks,

cmrntnnr

Is smbclient (console application) or mount.cifs on the same machine able to connect without issues? (Just to rule out firewall issues).

Also, what versions of Samba are in use on the client machine with the problems and the Samba server?

The samba software versioins on the clients are all the same. The clients are able to access the server via mount.cifs without any problems whatsoever. In fact, I have disconnected the server from the network, shutdown the firewall, and and successfully performed mount.cifs on itself, yet the same shares are not browsable in dolphin via smb://. A window does pop up after a long period of time requesting login credentials but supplying them does nothing.

These are the rpm packages with version information that are installed:

libsmbclient0-3.6.7-48.12.1.x86_64
qtsmbstatus-lang-2.2.0-1.2.x86_64
python-smbc-1.0.13-2.1.2.x86_64
yast2-samba-client-2.22.2-2.1.2.noarch
samba-client-3.6.7-48.12.1.x86_64
samba-client-32bit-3.6.7-48.12.1.x86_64
samba-3.6.7-48.12.1.x86_64
yast2-samba-server-2.22.3-2.1.1.noarch

I will give smb4k a go as a workaround.

Thanks for any insights on how to fix this,

cmrntnnr

My only guess here is that a bug has been triggered in the smb:// kioslave, which is somehow preventing it from operating. I am guessing that it does not matter if you specify a hostname or IP address in the smb:// url?

The same behavior results whether access is made by hostname or ip address. What can I do to provide more detail for meaningful bug report?

Please provide your samba version and the security level of your Samba server (domain, workgroup, guest, etc) to start with I guess.
The Samba kioslave is quite old, and I'm not sure how well maintained it is unfortunately.