Smb4K – Samba (SMB) share advanced browser
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

345 lines
13KB

  1. Frequently Asked Questions (FAQ)
  2. ================================
  3. (Version: 2005-12-20)
  4. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
  5. ! This file is deprecated. Please refer to the "Frequently Asked Questions" !
  6. ! section of the handbook for the latest version of the FAQ. !
  7. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
  8. Reporting bugs
  9. --------------
  10. Q: I think, I found a bug. Where can I report it?
  11. A: There are two possible ways, how to do it. You can either click on the
  12. menu item Help->Report Bug... and submit your report there, or you go to
  13. the project's bug tracking site:
  14. http://developer.berlios.de/bugs/?group_id=769.
  15. NOTE:
  16. - Before reporting a bug, try the latest version of Smb4K. Maybe the bug
  17. you found has already been fixed.
  18. - If you are reporting a bug, please include as much information as
  19. possible. To reproduce your problem, it is mandatory that you tell us
  20. what you did exactly. Also, it is necessary that you provide the version
  21. of Smb4K and KDE that you are using and which operating system (Linux,
  22. FreeBSD, etc.) and distribution (if applicable) is running on your
  23. computer.
  24. Compilation and Installation
  25. ----------------------------
  26. Q: I have compiled Smb4K from source. After starting it, I can't see the
  27. toolbar. What went wrong?
  28. A: Most likely, you installed Smb4K to the wrong place. To correct this,
  29. uninstall Smb4K first. Go to the source's root directory and run
  30. $ su -c "make uninstall"
  31. from the shell.
  32. NOTE:
  33. This will not work, if you ran
  34. $ make distclean
  35. in the meantime.
  36. Now, reconfigure the source by passing the '--prefix=PREFIX' option to
  37. the configure script:
  38. $ ./configure --prefix=`kde-config --prefix`
  39. Afterwards, compile and install it:
  40. $ make && su -c "make install"
  41. Smb4K will be installed to the right path and everything should work fine.
  42. Q: I want to compile Smb4K from source and I want to be able to uninstall it
  43. easily. Is that possible?
  44. A: If you want to be able to uninstall Smb4K easily, you might want to use
  45. checkinstall. It keeps track of all files installed by the "make install"
  46. command or equivalent, creates a Slackware, RPM, or Debian package with
  47. those files, and adds it to the installed packages database, allowing for
  48. easy package removal or distribution.
  49. Configuration, compilation and installation using checkinstall will work
  50. like this (see also above):
  51. $ ./configure --prefix=`kde-config --prefix` && make && su -c "checkinstall"
  52. Q: The configure script fails and tells me, it can't find my Qt
  53. installation.
  54. A: There are two things you should check:
  55. 1. It may be that the Qt header files are not installed. If this is true,
  56. install them and run the configure script again.
  57. 2. The QTDIR environment variable might not be set properly or at all.
  58. Check for the following line in your ~/.bashrc file
  59. export QTDIR=PREFIX
  60. and add it, if it is not present. Replace PREFIX with the prefix of your
  61. Qt installation. Run
  62. $ source ~/.bashrc
  63. from the shell. Now, you're set for a second configuration attempt.
  64. If the header files are installed and the QTDIR variable is set, but you
  65. still get the same error, you might want to try to pass the
  66. '--with-qt-includes=/path/to/header/files' option to the configure script.
  67. Q: The configure script fails and tells me, it can't find my KDE
  68. installation.
  69. A: There are two things you should check:
  70. 1. Probably the KDE header files are not installed. If so, install them and
  71. run the configure script again.
  72. 2. The KDEDIR environment variable might not be set properly or at all.
  73. Check for the following line in your ~/.bashrc file
  74. export KDEDIR=PREFIX
  75. and add it, if it is not present. Replace PREFIX with the prefix of your
  76. KDE installation. Run
  77. $ source ~/.bashrc
  78. from the shell. Now, you're set for a new configuration attempt.
  79. Browsing
  80. --------
  81. Q: When I scan the network, there are several workgroups appearing, that
  82. are not accessible. What can I do to avoid this behavior?
  83. A: This behavior might be caused by Samba's enhancements to cross-subnet browse
  84. propagation (see smb.conf(5) manual page). You can switch off this feature in
  85. the smb.conf by adding the following entry to the [global] section:
  86. [global]
  87. ...
  88. enhanced browsing = no
  89. ...
  90. This option seems to have no effect, if you do not use a WINS server.
  91. Q: When I start Smb4K, there is nothing in the network browser!
  92. A: Please follow this list to fix the problem:
  93. - If your network has a WINS server, add it to the [global] section of
  94. your smb.conf file and restart Samba (if necessary) and Smb4K.
  95. - Make sure the SMB ports 137 (TCP+UDP), 138 (UDP), 139 (TCP+UDP), and 445
  96. (TCP+UDP) are not blocked by a firewall. If you are using SUSE's firewall,
  97. see below.
  98. - Try to use a different look-up method. Therefore, change the settings
  99. under Settings->Configure Smb4K...->Network->Browse List.
  100. If there still isn't anything visible in the browser widget, ask for help on
  101. the Smb4K-general mailing list or file a bug report.
  102. Q: I'm using SUSE Linux with its firewall enabled. As normal user, I cannot
  103. browse the network neighborhood. The browser window is always empty.
  104. A: The solution to this issue is covered by several pages on the net. You may
  105. want to take a look at:
  106. - Novell Cool Solutions:
  107. http://www.novell.com/coolsolutions/feature/11952.html
  108. - HOWTO at TweakHound:
  109. http://www.tweakhound.com/linux/samba/page_8.htm
  110. - SUSE Linux Forums:
  111. http://forums.suselinuxsupport.de/
  112. Q: If I open a Windows 98 server, there are no shares shown although I know
  113. that there should be serveral. What's wrong?
  114. A: As of version 0.6.0, Smb4K uses the 'net' command to retrieve the list of
  115. shares from a host. With the default settings, the 'net' command will try
  116. to guess the protocol that is needed to communicate with the server (RAP or
  117. RPC). Unfortunately, this does not seems to work well with Windows 98 and
  118. earlier. To make things work, go to Settings->Configure Smb4K...->Samba->
  119. net->Protocol and check the RAP button.
  120. NOTE:
  121. This does not apply to versions prior to 0.6.0, because they use the RAP
  122. protocol based 'smbclient' command to retrieve the browse list. Smb4K
  123. 0.7.0 and above will automatically rescan the target server with the RAP
  124. protocol if the first attempt failed.
  125. Mounting/Unmounting of shares
  126. -----------------------------
  127. Q: Mounting a share fails and I get the following error message:
  128. smbmnt must be installed suid root for direct user mounts (500,500)
  129. smbmnt failed: 1
  130. What does that mean?
  131. A: It means, that you do not have enough permissions to mount SMB shares.
  132. There are two things you can do:
  133. 1. Set the SUID root bit for smbmnt. Therefore you have to find out,
  134. where the binary is located. Try
  135. $ ls -la `which smbmnt`
  136. in the shell. If this is a symlink, follow it to find the binary.
  137. Change into the directory, where smbmnt resides and run
  138. $ chmod +s smbmnt
  139. Now the mounting should work.
  140. WARNING:
  141. Do not set the SUID root bit for smbmount! If you do, mounting will
  142. too fail with the following error message:
  143. libsmb based programs must *NOT* be setuid root.
  144. 6002: Connection to dustpuppy failed
  145. SMB connection failed
  146. 2. You can execute mount and umount SUID using the program super (since
  147. Smb4K 0.4.0) or sudo (since Smb4K 0.5.0). To enable this feature, you
  148. have to go to Settings->Configure Smb4K...->Super User and adjust the
  149. settings.
  150. Q: If I want to unmount a share, I get the following message:
  151. smbumount must be installed suid root
  152. What do I have to do?
  153. A: You have similar options as above. Either you set the SUID root bit for
  154. smbumount or you enable the feature "Use super user privileges to mount and
  155. unmount shares" under Settings->Configure Smb4K...->Super User->Actions.
  156. For details see above.
  157. Q: I'm using the CIFS file system for mounting and I've set the UID/GID in
  158. the configuration dialog, but Smb4K does not seem to care about that at
  159. all!
  160. A: This is a Samba feature. If the target server supports the CIFS Unix
  161. extentions, the uid and gid option will be ignored. For more information
  162. see the mount.cifs(8) manual page.
  163. Q: When I try to mount a share from a Windows 2003 server, I get the following
  164. error message
  165. cli_negprot: SMB signing is mandatory and we have disabled it.
  166. 4377: protocol negotiation failed
  167. SMB connection failed
  168. and the mounting fails. What's wrong?
  169. A: You are using the SMBFS file system that does not support signing. You
  170. have to switch to the CIFS file system in order to be able to mount the
  171. share. Go to Settings->Configure Smb4K...->Samba->File System and choose
  172. CIFS instead of SMBFS.
  173. NOTE:
  174. Smb4K will use the mount.cifs binary to mount CIFS shares. That's why
  175. you should also enable the "Use super user privileges to mount and unmount
  176. shares" option under Settings->Configure Smb4K...->Super User->Actions.
  177. Q: Smb4K fails unmounting a share. The error message is:
  178. Could not unmount /mount/point: Device or resource busy
  179. How can I make unmounting work?
  180. A: First of all, check that you haven't opened the mount point or one of its
  181. subdirectories in a shell or with a file manager. Also, make sure you
  182. haven't opened any file belonging to the share. If neither is the case,
  183. you might have encountered a problem, that is known but not related to
  184. Smb4K. It seems, that under certain circumstances (that we could not
  185. figure out exactly) kdeinit (KDE < 3.4) background processes access files
  186. and/or directories of the share and keep them open. Unmounting is not
  187. possible unless you send
  188. $ kill -HUP <PID>
  189. to each kdeinit instance that has access to the share or its files.
  190. Alternatively, you can force the unmounting of the share. Highlight the
  191. share and use the Shares->Force Unmounting menu item or press Ctrl+F.
  192. Q: I'm using sudo and the CIFS file system. Everytime I want to mount a share
  193. (from a Windows 2003 server), I get the following error:
  194. mount error 13 = Permission denied
  195. Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)
  196. What can I do to make mounting work?
  197. A: It is very possible, that the 'env_reset' flag has been set in the
  198. /etc/sudoers file (It's the default in Gentoo for example.), which
  199. resets the environment to only contain a limited number of environment
  200. variables. Especially, the PASSWD variable is removed which is needed by
  201. Smb4K.
  202. To make mounting work, there are three things you should try alternatively:
  203. - Insert manually the following line after the line beginning with
  204. "User_Alias SMB4KUSERS":
  205. Defaults:SMB4KUSERS env_keep=PASSWD
  206. This should be the preferred method on a multi-user system.
  207. - Remove the Smb4K user entries from /etc/sudoers manually or using
  208. Smb4K and rewrite them (Smb4K >= 0.6.4).
  209. - Comment out the 'env_reset' variable (not recommended).
  210. If you are still not able to mount a share, please file a bug report.
  211. Miscellaneous
  212. -------------
  213. Q: I'm using Smb4K 0.4.x. After starting it, I cannot see the main window.
  214. Is this a bug?
  215. A: No. This is a special behavior of the 0.4.x series, which was changed in
  216. later releases. Smb4K 0.4.x immediately docks to the system tray. You'll
  217. find an icon there with which you can bring up the main window. Restoring
  218. the visible main window after logging in will not work.
  219. Q: I want to use super to mount and unmount the shares. When I try to enable
  220. either "Use super user privileges to force the unmounting of (broken)
  221. shares" or "Use super user privileges to mount and unmount shares", Smb4K
  222. complains that it cannot find the super.tab file. What do I have to do?
  223. A: Create the super.tab file in the appropriate etc directory. Therefore
  224. change into it (most likely /etc (Linux) or /usr/local/etc (FreeBSD)) and
  225. run
  226. $ touch super.tab && chmod 0644 super.tab
  227. as root. Smb4K will take care of the rest.
  228. Q: After installing Smb4K, I wanted to take advantage of the Konqueror
  229. plugin but I couldn't find it. What do I have to do?
  230. A: Right-click on the frame of Konqueror's navigation widget and choose
  231. Add New->Samba Browser from the menu. The Konqueror plugin will be
  232. added.