<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Smb on Michael’s Domain</title><link>https://jeltsch.org/en/tags/smb/</link><description>Recent content in Smb on Michael’s Domain</description><generator>Hugo</generator><language>en-us</language><copyright>Copyright © 2002 - 2026 Michael Jeltsch.</copyright><lastBuildDate>Fri, 24 Jul 2026 00:18:18 +0300</lastBuildDate><atom:link href="https://jeltsch.org/en/tags/smb/index.xml" rel="self" type="application/rss+xml"/><item><title>Deleting files with "illegal characters"</title><link>https://jeltsch.org/en/deleting_files_with_illegal_characters/</link><pubDate>Fri, 08 Sep 2017 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/deleting_files_with_illegal_characters/</guid><description>&lt;p&gt;In the cross-platform environment of our university, at least three different OS connect to the smb shared group directories. Apparently Macs are able to save files with characters that are not allowed on other platforms and which cannot be easily deleted. Recently we had several files which ended with a &amp;lsquo;.&amp;rsquo; (dot) or a &amp;rsquo; &amp;rsquo; (space), and we were not able to remove them via the GUI. In Windows 7, I managed via the command line with:&lt;code&gt;delete &amp;quot;file.&amp;quot;&lt;/code&gt; or&lt;code&gt;delete &amp;quot;file &amp;quot;&lt;/code&gt;I have, however, not found a way to so from my Ubuntu machine and it is annoying to boot into Windows merely to delete some files. Unfortunately, this became necessary because the 
 &lt;a href="https://www.cloudberrylab.com" target="_blank" rel="noopener noreferrer nofollow"&gt;Cloudberry&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
 backup system (which is running on Ubuntu) chokes on such files. I am looking into a new backup system for our lab&amp;rsquo;s computers since 
 &lt;a href="https://www.crashplan.com" target="_blank" rel="noopener noreferrer nofollow"&gt;CrashPlan&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
 decided to discontinue support for non-business customers…&lt;/p&gt;</description></item><item><title>Mount Samba shares (why doesn't Nautilus work?) and making smb mounts permanent</title><link>https://jeltsch.org/en/mount_samba_shares_why_doesn_t_nautilus_work_and_making_smb_mounts_permanent/</link><pubDate>Sat, 26 May 2007 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/mount_samba_shares_why_doesn_t_nautilus_work_and_making_smb_mounts_permanent/</guid><description>&lt;p&gt;&lt;strong&gt;Mount Samba shares&lt;/strong&gt;Apparently it is very easy to connectfrom within Nautilus to Windows computers (or rather to computers running smb services). The only thing you have to do is to type smb:/// into the URL bar and the network is browsed for available domains, workgroups and services. However when one tries to open some files (e.g. some image) there often appears the error message that those files cannot be accessed via samba.What to do? I figured that when you mount smb shares, that this works correctly. In order to mount my user directory on another computer this is the command:&lt;code&gt;sudo mount -t smbfs -o username=michael,password=here_goes_my_password //paula/michael /mnt/smb&lt;/code&gt;paula is the netbios name of the other computer and michael is the name of the share.You can also set the owner of all the files of the mounted file system with the -o uid=owner option:&lt;code&gt;sudo mount -t smbfs -o username=michael,password=here_goes_my_password -o uid=500 //paula/michael /mnt/smb&lt;/code&gt;If you don&amp;rsquo;t want to type your password, you can save it in a file like this:&lt;code&gt;username=susannepassword=0sdf7b&lt;/code&gt;and then you can refer to this &amp;ldquo;credentials&amp;rdquo; file:&lt;code&gt;sudo mount -t smbfs -o username=susanne,credentials=/home/susanne/.smbpasswd //patolmac217/susanne /mnt/smb&lt;/code&gt;In order to unmount use:&lt;code&gt;sudo umount /mnt/smb&lt;/code&gt;This mostly fails as you are likely to have some open windows/terminals that keep the connection active. Close them and try again. You also might try umount -f.&lt;strong&gt;Making smb mounts permanent&lt;/strong&gt;When you mount an SMB share, it will be gone upon system restart. To make it mount automatically during system bootup, you have to create a new entry in the /etc/fstab file. In my case e.g.:&lt;code&gt;//paula/michael /mnt/smb smbfs credentials=/home/jeltsch/.smbpasswd 0 0&lt;/code&gt;In the .smbpasswd file is my username and my password. Probably not very safe, but who cares? .smbpasswd should be anyway only readable by yourself!&lt;/p&gt;</description></item><item><title>Samba trouble (smb, smbadduser, smbpasswd)</title><link>https://jeltsch.org/en/samba_trouble_smb_smbadduser_smbpasswd/</link><pubDate>Wed, 23 May 2007 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/samba_trouble_smb_smbadduser_smbpasswd/</guid><description>&lt;p&gt;If your samba is unreliable, there can be a number of reasons. I got the impression that YAST overwrites configuration data you have manually edited (e.g. in the password and user files) when you try to change settings via the YAST samba setup procedure. Here follows a checklist in case samba is again not responding or not visible in the network neighborhood. It could be that the unreliability is due to a PDC shutting down. Maybe I should make my Linux the PDC as it is always running. Anyway even if I manage to connect from W2K (using map network drive) I couldn&amp;rsquo;t connect from W98 by clicking the visible icon of my computer in the MCBL workgroup (&amp;ldquo;network path not found&amp;rdquo;). And in MacOSX my computer was not visible at all (but I could connect via the manual command &amp;ldquo;smb://128.214.186.42/homes&amp;rdquo;). Strange…In /etc/samba/smb.conf:&lt;/p&gt;</description></item><item><title>autofs, automount, auto.master and mounting samba shares</title><link>https://jeltsch.org/en/autofs_automount_auto_master_and_mounting_samba_shares/</link><pubDate>Mon, 21 May 2007 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/autofs_automount_auto_master_and_mounting_samba_shares/</guid><description>&lt;p&gt;First I added a symbolic link to /etc/init.d/rc5.d/:&lt;code&gt;cd /etc/init.d/rc5.d sudo ln -s ../autofs S21autofs&lt;/code&gt;Then I added to the /etc/auto.master the following line:&lt;code&gt;/media/automounts /etc/auto.smbmounts&lt;/code&gt;Then I created the file auto.smbmounts with the following content:&lt;code&gt;michael_msbl.helsinki.fi -fstype=smbfs,username=michael,password=## ://paula/michael&lt;/code&gt; Then I created the mountpoint:&lt;code&gt;sudo mkdir /media/automounts/michael_msbl.helsinki.fi&lt;/code&gt;Then I activated the autofs daemon:&lt;code&gt;sudo /etc/init.d/autofs start&lt;/code&gt;Now whenever one tries to access the directory /media/automounts/michael_msbl.helsinki.fi, the autofs daemon will mount the smb share automatically and unmount after a certain period of inactivity.&lt;/p&gt;</description></item><item><title>smb mounts via fstab or automount?</title><link>https://jeltsch.org/en/smb_mounts_via_fstab_or_automount/</link><pubDate>Mon, 21 May 2007 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/smb_mounts_via_fstab_or_automount/</guid><description>&lt;p&gt;I have many computers I need to connect to from my Linux box. Network browsing works, but is terribly slow, so I want to create some shortcuts, that I can mount with a single mouseclick what I need from a list. First I thought to modify the fstab and put there entries that would allow me to easily mount smb shares as a normal user. E.g.:&lt;code&gt;//paula/michael /media/smbmounts smbfs noauto,user,credentials=/home/jeltsch/.smbpasswd1 0 0&lt;/code&gt;This works if I have the entry mounted at system startup (without the &amp;ldquo;noauto&amp;rdquo; entry). If the &amp;ldquo;noauto&amp;rdquo; entry is present, the smb share is not mounted at system startup, but must explicitely be mounted by the following command:&lt;code&gt;mount /media/smbmounts&lt;/code&gt;Because of the &amp;ldquo;user&amp;rdquo; option in the fstab, every regular user should be able to do this. Not so! First I had to enable the &amp;ldquo;suid&amp;rdquo; for the smbmnt command (it appeared to be in /usr/bin/smbmnt, but was linked to a link that linked to /usr/lib/samba/classic/smbmnt:&lt;code&gt;chmod +s /usr/lib/samba/classic/smbmnt&lt;/code&gt;Then I found contradicting information whether the mountpoint (in my case /media/smbmounts) has to owned by the mounting user or not. To be safe it did:&lt;code&gt;chown jeltsch /media/smbmounts&lt;/code&gt;Still I got an error which I couldn&amp;rsquo;t figure out and I decided to use automounts.&lt;/p&gt;</description></item><item><title>What nfs and smb shares are available on a server (showmount, smbclient)?</title><link>https://jeltsch.org/en/what_nfs_and_smb_shares_are_available_on_a_server_showmount_smbclient/</link><pubDate>Thu, 05 Apr 2007 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/what_nfs_and_smb_shares_are_available_on_a_server_showmount_smbclient/</guid><description>&lt;p&gt;The command to figure out what shares are available e.g. on the computer 192.168.0.2 type:For nfs: &lt;code&gt;/usr/sbin/showmount -e 192.168.0.2&lt;/code&gt;For samba: &lt;code&gt;smbclient -L 192.168.0.2&lt;/code&gt;&lt;/p&gt;</description></item><item><title>smbclient (mount, Windows XP, SFS, file sharing)</title><link>https://jeltsch.org/en/smbclient_mount_windows_xp_sfs_file_sharing/</link><pubDate>Wed, 04 Apr 2007 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/smbclient_mount_windows_xp_sfs_file_sharing/</guid><description>&lt;p&gt;Since I always use some GUIs, I don&amp;rsquo;t really remember anymore how to connect to a Windows machine via the command line. &lt;code&gt;smbclient -L windowshost&lt;/code&gt; shows you the shares that are available. Often, you you cannot browse them without a login/password for that windows machine, therefore you need to type &lt;code&gt;smbclient -L windowshost -U username&lt;/code&gt; And occasionally the netbios name doesn&amp;rsquo;t work either and you need to replace it by the IP address.&lt;/p&gt;</description></item><item><title>Restricting Samba access on SuSE 10.1 to one IP</title><link>https://jeltsch.org/en/restricting_samba_access_on_suse_10_1_to_one_ip/</link><pubDate>Mon, 14 Aug 2006 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/restricting_samba_access_on_suse_10_1_to_one_ip/</guid><description>&lt;p&gt;When you allow Samba access to your SuSE 10.1 machine by using the YaST firewall setup tool, three changes are made to /etc/sysconfig/SuSEfirewall2:&lt;/p&gt;</description></item><item><title>Hiding dot files for samba shares</title><link>https://jeltsch.org/en/hiding_dot_files_for_samba_shares/</link><pubDate>Mon, 23 Feb 2004 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/hiding_dot_files_for_samba_shares/</guid><description>&lt;p&gt;To suppress the display of system files (configuration files, those that start with a dot) when connecting from a Windows computer to your samba server, write the following into the /etc/samba/smb.conf:&lt;/p&gt;</description></item></channel></rss>