The most problems with Komba2 depends on a wrong samba configuration. That's why you should take some time and verify your settings.
It seems to be trivial but is the most source of trouble. Use
% smbclient -L localhost |
And
% nmblookup "*" -U localhost |
In smb.conf (type smbstatus -d to know where to find it) should you find an entry
workgroup =
The use as non root user should be the normal case. It's recommended not to use Komba2 with su. It creates security holes. In this case Komba2 starts other programs with root permissions (for example Konqueror).
If you start Komba2 as a normal user you have not enough permissions to mount and unmount shares at first.
You have to change the permissions on smbmount and smbumount. Please note, it can open a security lack on your machine. So be carefull!
It would be enough to change the bit SETUID on smbmnt and smbumount. If this bit is set the programs start with the permissions of the owner (in this case root). Now all users can mount and unmount smb shares.
We tell you now how to set the permissions only to group of users. For following commands you must be root. At first you add a group to your system.
% groupadd sambamount |
Now you add the users to the new group.
% usermod -G sambamount username |
Change the group on smbmount und smbumount to sambamount.
% chgrp sambamount smbumount % chgrp sambamount smbmount |
At least you set the permissions that only users of the group (and root) can run smbmount and smbunmount and set the SUID bit
% chmod 4750 smbumount % chmod 4750 smbmount |
Now you can use Komba2.