I have just installed samba. I’m using it as an alternative to using dolphin to connect to a nas.
Accessing the dolphin way is just like using the local disc. Samba is very very slow up to a point where it reads an actual directory structure then it speeds up. It also works much more quickly when it’s accessed again with dolphin but if an app accesses it’s slow again.
One thing I noticed while installing with YAST is that there doesn’t seem to be any opportunity to introduce a fixed ip address only workgroup and server names. I wonder if this is the cause of the problem. I would make more sense for me to used a fixed ip address really.
Also wonder if there is any need to check the open firewall check box as dolphin worked before doing that.
I would also like to be able to start and stop samba manually but lack the correct command.
Put an address like this in the address bar of dolphin: smb://192.168.1.33/
and you will see all the shares on that box
Or put an address like this if you want to see only into the share called “billygoat”: smb://192.168.1.33/billygoat
Any of these addresses, once they connect, can be stored in the left panel of Dolphin as a shortcut that you can use over and over.
Or, make a link on the desktop with that address in it and just click the link and the destination will open in Dolphin for you to browse.
I would also like to be able to start and stop samba manually but lack the correct command.
This command will stop samba if issued as root user (su to root first):
rcnmb stop;rcsmb stop
This command will start samba if issued as root user (su to root first):
rcnmb start;rcsmb start
Also wonder if there is any need to check the open firewall check box as dolphin worked before doing that.
Just to be thorough:
You should open this service to view a server on the network: samba client
You should open these services to let clients on the network view you: samba server + netbios server
Thanks for help
It’s an interesting area. The dolphin connect does use a direct ip link to the nas and a directory if needed all without installing samba. I haven’t tried writing to the root directory as linux may object to that.
Enabling samba hasn’t made any difference to VLC or Kaffeines behaviour either. Kaffeine still wants this mysterious input plugin. Not at all sure what’s happening with VLC as it should support it.
I’ve been doing some playing about and I suspect some of these problems are down to the kde base system. For instance
Click on an mp3 on the nas and it plays in amarok. Try to use the load as part of a play list and amarok can’t do anything with the play list.
Copy and rpm to the nas and click install with yast and up pops yast and complains because it’s not running as root. The launch bypasses the root login.
Edit a text file on the nas and it can be changed but no backup file is generated.
If I try and save a file from LibreOffice onto the nas I get a message that apart from icons is the same as VLC “You can only select local files”
If I copy the office file onto the nas and click it on Libre loads it. If I editing the file and saving it appears to work but doesn’t. The file remains the same.
As samba works with the nas I don’t see how the problem can be the nas.