Is there a need to test it on 8.10 then?
2009/5/11 Renzo Bagnati ren...@gmail.com
No, the issues of comment 220 are not present in jaunty and in intrepid.
They are specific of hardy and of the
95_svn_change_fix_smb_browsing.patch, since reverting to the version of
gvfs in hardy-updates restores the ability to browse the smb:/// Windows
Network (but not, of course, the domain shares).
--
nautilus does not display samba shares for machines inside an ADS network.
https://bugs.launchpad.net/bugs/207072
You received this bug notification because you are a direct subscriber
of the bug.
Status in gvfs: Fix Released
Status in “gvfs” source package in Ubuntu: Fix Released
Status in “nautilus” source package in Ubuntu: Invalid
Status in gvfs in Ubuntu Hardy: Fix Committed
Status in nautilus in Ubuntu Hardy: Fix Committed
Status in gvfs in Ubuntu Intrepid: Fix Released
Status in nautilus in Ubuntu Intrepid: Fix Released
Status in gvfs in Ubuntu Jaunty: Fix Released
Status in nautilus in Ubuntu Jaunty: Invalid
Bug description:
Binary package hint: nautilus
Using hardy beta, when I browse with nautilus other machines in an Active
Directory (ADS) network, some of them do not show their shared folders.
The ADS integration of the hardy box was done using winbind, kerberos and
PAM libraries, essentially as described here:
https://help.ubuntu.com/community/ActiveDirectoryWinbindHowto
The network contains mostly windows clients, but also several linux boxes,
which were joined to the ADS domain with the command: 'net ads join'.
Machines running windows XP, windows 2003 and samba show '0 objects' in
nautilus, but after inserting the complete path (eg.: smb://server/share)
the folders can be accessed after the password prompt.
Machines running windows 2000 show their folders regularly.
Here is a detailed description of what happens:
Case 1
-
Browsing from hardy-beta a machine running ubuntu-gutsy server.
In a terminal window:
ren...@vm-hardy:~$ smbclient -L gutsy-server
Password: (password inserted here)
Domain=[LAB] OS=[Unix] Server=[Samba 3.0.26a]
Sharename Type Comment
- ---
IPC$ IPC IPC Service (gutsy-server (Samba 3.0.26a, Ubuntu))
share Disk gutsy-server_share
Domain=[LAB] OS=[Unix] Server=[Samba 3.0.26a]
In Nautilus:
Open Network -- Double-click on the 'LAB' icon (Domain) -- All machines
are displayed;
Double-click on the 'gutsy-server' icon -- after a while, Nautilus returns
'0 objects', without asking for a password;
Insert the full address (smb://gutsy-server/share) -- a password is
requested and the share content is displayed.
Case 2
-
Browsing from hardy-beta a machine running Windows XP
In a terminal window:
ren...@vm-hardy:~$ smbclient -L XP-ACQ
Password: (password inserted here)
Domain=[LAB] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
Sharename Type Comment
- ---
IPC$ IPC Remote IPC
Data Disk
Domain=[LAB] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
In Nautilus:
Same behaviour as in case 1.
smb://XP-ACQ -- '0 objects';
smb://XP-ACQ/Data -- content displayed after password.
Case 3
-
Browsing from hardy-beta a machine running Windows 2000
In a terminal window:
ren...@vm-hardy:~$ smbclient -L TF-2000
Password: (password inserted here)
Domain=[LAB] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager]
Sharename Type Comment
- ---
IPC$ IPC Remote IPC
Data Disk
Domain=[LAB] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager]
In Nautilus:
Open Network -- Double-click on the 'LAB' icon (Domain) -- All machines
are displayed;
Double-click on the 'TF-2000' icon -- All the shared folders are
displayed, without asking for a password;
Double-click on the 'Data' folder icon -- a password is requested and the
content is displayed.
(This is the correct and the expected behaviour).
Using ubuntu-gutsy boxes, with exactly the same samba configuration
(smb.conf), to browse the same machines I never observed Nautilus return '0
objects' as in case 1 and 2.
Such a behaviour in hardy will make a normal user think that browsing an
ADS network does not work at all.
--
nautilus does not display samba shares for machines inside an ADS network.
https://bugs.launchpad.net/bugs/207072
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs