More information ... By installing WICD, I found that the slow shutdown ('CIFS VFS: No reponse ...') is a problem regardless of whether you use WICD or Network Manager. This get-around works for me ... Make a link in the 2 relevant rc folders to umountnfs.sh that are earlier in the alphabet than the existing link to umountnfs.sh (so that umountnfs.sh runs earlier). # For shutdowns .. cd /etc/rc0.d sudo ln -s ../init.d/umountnfs.sh K02umountnfs # For reboots .. cd /etc/rc6.d sudo ln -s ../init.d/umountnfs.sh K02umountnfs (This doesn't work if you use '-n' with the smbmount command because umountnfs.sh reads the /etc/mtab file to find mounts.) By the way, after trying out WICD, I prefer Network Manager - simpler for the 'average' user and the icon graphically displays an indication of the wireless connection strength. On Sat, Jan 16, 2010 at 10:52 AM, David Collins <<a href="mailto:david.8.collins@gmail.com">david.8.collins@gmail.com</a>> wrote: <div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I have to retract my statement about not having any problems with Network Manager. :) I have just found out that my slow shutdown when I am connected to a Samba share is caused by Network Manager closing down before CIFS mounts are unmounted. Can anyone confirm if you get the same problem when using WICD to connect to a Samba share ? (You get a message 'CIFS VFS: No response ..' and it takes about 2 minutes for the laptop to shut down.) </blockquote></div>