Am 13.08.2011 19:12, schrieb Bruno Prémont: >> old: 2.6.26-2-vserver-amd64 (Debian stable standard 0.30.216-pre2772 >> kernel) >> new: 2.6.22.19-vs2.3.0.34.1 (dhozac repo supplied; installed from a >> mirror) > ^^^^^^^^^ is that really 2.6.22?? So downgrade of kernel? Yes, it was. Meantime I upgraded to 2.6.32-131.2.1.el5.vs2.3.0.36.29.6.18.x86_64 from another mirror. The necessity to reinstall the sys was not really existing, although it occasionally lost it's network connectivity (totally) and I wanted to track that down on CentOS, which I'm much more familiar with. > Could it be related to netbios/broadcast? Possiby, can't confirm nor deny. But the guest sys was up and running on the distro, nothing has been changed on the guest, so I don't really think it's a problem up to guest or Samba configs. > Can you reach the server via its IP address \\a.b.c.d\ instead of by name? Same thing - long time no replay at all, then come up with "Der Netzwerkpfad wurde nicht gefunden". As mentioned - I don't think it's really a guest config problem - but also I don't really see a reason for this behavings in now two kernel versions of Daniel's CentOS supplied kernels. > Might help to add your subnet's broadcast address to those addresses > available to your samba guest. Will try that soon. > Note: what Windows version is it you are using? Vista/Win7 might also try > some IPv6 access. Both WinXP SP3 and Win7 64bit SP1; both on IPv4 only > You might get some hints by sniffing the Windows box's network activity. The only thing I ever sniffed was once tobacco - and that did not really satisfy. So if you could give me some noob "howto" I'd be happy to try that. -- greez, Guenther Fuchs