Mounting remote filesystems...failed (cifs,smbfs,nfs)

[Bazon]

My /etc/fstab contains some windows shares mounted with cifs.
Since the Dapper update of April 24th, these shares aren't mounted on boot.
Instead of that, the message is displayed:

Mounting remote filesystems...failed

But when I type
sudo mount -a
in a terminal, all shares are mounted immidiately without a problem!
This behaviour was reported by severall other users, too:
http://www.ubuntuforums.org/showthread.php?t=163171

When I changed the mount type to smbfs for one share, this share wasn't mounted, too, as well as a NFS share I added.
As before: sudo mount -a in a terminal mounts them all without problem!

As a further information I can give:
A part of /var/log/dmesg:

[4294697.572000] CIFS VFS: Error connecting to IPv4 socket. Aborting operation
[4294697.572000] CIFS VFS: cifs_mount failed w/return code = -101

a line in my /etc/fstab looks like this:
//192.168.1.30/sharename /home/myusername/remotecomputername/sharename cifs user,auto,credentials=/home/myusername/.smbcredentials,uid=myusername,gid=users,iocharset=utf8 0 0

~/.smbcredentials looks like:
username="xxx"
password="xxx"
and is valid (as sudo mount -a working proofs...)

(such a message occurs four times as I try to mount 4 shares. Similar messages are also in /var/log/syslog, /var/log/kern.log)

There are similar bugs reported here before, but they are a year old or older and "fixed", so I started this new one:

https://launchpad.net/distros/ubuntu/+source/udev/+bug/16381
https://launchpad.net/distros/ubuntu/+source/samba/+bug/10474

[Bazon (bazonbloch)]

sam tyger did:

** Changed in: Ubuntu
Sourcepackagename: None => samba

really samba?
I don't even need to have the samba package installed to access remote filesystems, only smbfs, samba-client and samba-common.

Also, I'm wondering:
Isn't it more a question of the boot-up process? I mean, later, when booted, sudo mount -a works and the cifs get mounted after that, so the samba-client seems to work, doesn't it?

[bag (gruening)]

Here I have the same problem. Indeed it is a problem of the boot-order, in particular in combination with network-manager, i think. IMHO the problem is that at time fstab will checked no network is up and so no filesystem could mount over the network (here smb, nfs, sshfs). The most annoying thing is, that it block the whole boot process. Only when i press Control+C continues to boot.

regards

[Laurent Bigonville (bigon)]

I think this is duplicate of bug #30241