Comment 8 for bug 456808

#4 Re:"Winbind, because somewhere it was recommended to have installed."
<<winbind is a component of the Samba suite of programs that solves the unified logon problem. Winbind uses a UNIX implementation of Microsoft RPC calls, Pluggable Authentication Modules (PAMs), and the name service switch (NSS) to allow Windows NT domain users to appear and operate as UNIX users on a UNIX machine>>

I fail to see how winbind can help in your scenario (since you don't use a Windows domain) and I can certainly imagine how it can lead you to failure if badly configured.

Please try with just "samba" installed, and not "winbind".

#5 What does "smb://<IP of a remote PC>/sharename" return ?

#6 2. it's /var/log/samba/log.nmbd. And we need those of the remote PC, the one that you're trying to connect to and fail.

I'm still trying to figure out what exact bug you're reporting here, apart from general failure to configure SMB networking on your machines, and how much simpler this should be (which is not a bug). I suppose it's the "can't access remote PC via smb:// in Nautilus, while I can access it just fine locally". If I got it right, could you:

1/ try accessing the share using smbclient rather than Nautilus ? Try smbclient //remote_system/share_name
2/ try to define "guest ok = yes" in your share to rule out account name issues.