If you install Samba on a Ubuntu Gutsy box and you are using the Networkmanager for your network settings you are very likely to encounter the following error message when you shutdown:
CIFS: VFS server not responding
CIFS: No response for cmd 114 mid 3
It’s a bug in Gutsy and it looks like it’s a bug in Hardy as well but there is a work around.
The reason for getting the error message is the fact that the network (NetworkManager) is being shutdown before dismounting of the Samba shares, and dismounting a network share without a network well that won’t work so well 
You can use the following work around:
cd /etc/rc6.d
ls -la
You should see :
S<nr>wpa-ifupdown the nr is probably 15
and
S<nr>umountnfs.sh that nr is probably 31
Type:
sudo mv S31umountnfs.sh S14umountnfs.sh
The point is to give the umountnfs.sh a lower as your wpa-ifupdown.sh
Follow the above steps also for /etc/rc0.d (Thanks to Deb Early for the suggestion)
Entries (RSS)
This is BRILLIANT! Thank you SO much for this solution to a problem I know many, many people are tearing their hair out over! One thing I would add: folks should also check /etc/rc0.d. The change to rc6 worked beautifully for reboots, but shutdowns were still exhibiting the problem until I thought to look in /etc/rc0.d. Again — bless you!!
I never get any error. I thought I had a hibernate problem until I noticed the shutdown didn’t work last night. My laptop screen simply goes blank and I noticed that if I leave it that way the fan spins-up and the temps climb fast. On reading your post I decided to go back to WICD and see if that solved it. I’ve only had one shutdown since then and it worked well.
So to rant a bit, why on earth does Network Manager still exist? It seems to be one of the glaring thorns in the side of most new users and seems at best to be a half-baked solution for wireless networking.
My comment above not withstanding, WICD did not solve the problem. Several attempts and a reinstall later and I am back to this fix. I guess I didn’t fully understand what I was seeing from ls -la. I’ll try to come back and post the results.
I still agree with NM being a problem child, even though this is not NMs fault.
Nope, not the answer for me.
Thanks! Nice simple solution. Worked for me.
Awesome - had this problem in Hardy Heron 8.04 and fixed everything like a charm.
thank you, hey i also ad a bit of trouble with your explication on the ls -la
figured it out anyways , but for those are new to linux and do not understand try this instead of the plain ls -la write : ls -la | grep S31 and ls -la | grep S15 it will be more clear then
Works as advertised. Thanks for the workaround!
[...] oplossing [...]
Thanks so much for the fix– this has been an annoyance for months. When I finally got around to researching it, it seems like this bug has been around since Dapper. Unbelievable that this workaround is still needed…
Does exactly what it says on the tin - thanks!
[...] had set it up to shutdown network connections before attempting to unmount shares. I followed these instructions, and it fixed the problem, so it no longer takes forever to turn off my [...]
Thanks a bunch. Worked on hardy for me. I had the problem of having the nvidia drivers installed too, and instead of giving me the error, the screen was just random colors. When I found out what the problem was, it was nice to know there’s such an elegant solution.
Yeah! I also had the nvidia driver and was always getting the vertical color line show. I never would have found this solution if I hadnt followed jeffeb3’s thread about vertical color lines. Kudos.
Thanks! Now my reboot boosted ^_^