Am 08.11.2010 17:07, schrieb Tomas Bzatek: > GVfs uses libsmbclient for accessing SMB resources and it's only up to > Samba to decide what approach will be used. And since libsmbclient > maintains API transparency, there's very little that can be changed from > client side (GVfs, Nautilus). > > By default, Samba uses broadcasts to discover neighbour computers. > Unfortunately these broadcasts are usually blocked by firewalls in many > linux distributions in their default installations. > > There are however some ways to configure samba clients - either by > changing system smb.conf settings or by placing custom ones in user home > directory. Better to consult with Samba folks first. > > As a debug tool you can try 'smbtree' command, should give you equal > results as Nautilus Thanks for your answer. I did not know GVfs was using smbclient, I thought it was some sort of own implementation. I have checked smb.conf on the clients, and they are correct. I followed smbtree activity with wireshark and could verify it is using WINS to query the server and gets a complete list in return.
As this problem occurs only from time to time, I will check again with smbtree when it happens. But I guess this is more a samba problem then, and will discuss it there. Thanks again, Andreas -- nautilus-list mailing list nautilus-list@gnome.org http://mail.gnome.org/mailman/listinfo/nautilus-list