Hi swerdna
the delayed smb boot I know, but this is something I can live with.
The mount to 127.0.0.1 is the last of several mount configurations (e.g. 2 bridged VM's, bridged VM to host, also host-only configurations) I tried (at least THIS should work!!).
The bridged and real IP tests I've done in every combination already...
funny thing is, in some other configuration it had worked on the real network (10.3? 11.0? don't remember, as I thought such simple things always work :-)
just rechecked:
2vm's 11.1, kde4 bridged, same subnet, server set up SUSE basic with samba (the history of the client is mixed, but should be irrelevant as it is a basic kernel function and also other clients behave exactly the same):
same result: bash: //192.168.128.131/documents: Datei oder Verzeichnis nicht gefunden (file or directory not found)
What next? Wait for SUSE 12.5 :-( thats way too long, I'd like to make use of my pc a little earlier ;-)
I DON'T WANT to have to return to a windows server!!!
What I don't know: Is it a mount.cifs or a samba problem? What is the difference between accessing a share via smb:// (dolphin / konqueror), a win client or mount.cifs? Maybe somebody can help me with some background knowledge...