1. The bug. When an an Ubuntu machine is connected to a Windows peer-to-peer
network, the File Browser will browse network (network:///) showing the
workgroups (smb:///) but it will not reliably browse within the workgroups
(smb://workgroup/).
2. How to trigger in Jaunty. Connect a Jaunty machine to a window peer-to-peer
network.
3. Associated information:
Can connect to hosts by smb://<IP address>, but not by
smb://workgroup/hostname.
But can connect to printers by BOTH smb://<IP address>, and by
smb://workgroup/hostname.
Also present with earlier versions of Ubuntu.
May be a gvfs problem, but afflicts Ubuntu and should be within Ubuntu
bugs.
May be the way that File Browser interrogates Windows master browser
(known to be flaky even for Windows machines).
Very rapid return of 'Unable to browse location. Failed to return share
list from server' by File browser, whereas when browsing workgroups effectively
it takes time to retrieve the information. Possibly something is telling File
browser that there is nothing with the hostname/IP translations.
But SMB4K browses within workgroups reliably.
4. I'm for leaving it here since the core issue (1. above) is clear and
adequately described.
--
Nautilus fails to browse windows shares
https://bugs.launchpad.net/bugs/316862
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
