Red Hat Bugzilla – Bug 467084
Unable to browse domain computers
Last modified: 2015-03-03 17:33:13 EST
Description of problem:
When browsing windows network in nautilus, it displayes the list of domains and workgroups, but not list of computers in the domain. Instead of asking for credentials, it simply shows empty nautilus window.
Version-Release number of selected component (if applicable):
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here:
gvfs-1.0.3-2.fc10 has been submitted as an update for Fedora 10.
Please test the updated packages, read the notes posted in the link above and report any issues.
gvfs-1.0.3-2.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update gvfs'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2008-10848
Now it is failing in different way: when I double-click on domain, I get a message "Unable to mount location. Failed to retrieve share list from server".
(In reply to comment #5)
> Now it is failing in different way: when I double-click on domain, I get a
> message "Unable to mount location. Failed to retrieve share list from server".
OK, can you please provide the domain controller specification? I.e. what SW is the server running, configuration (security) of the domain, domain name and domain controller (machine) name, etc. I'm trying to find reproducer for this issue; a list of steps on how to set up similar structure would be great. And, if possible, attach a debug log produced by gvfsd as described in the notes of the gvfs update.
It looks like you are required to authenticate first in order to get the list of computers in the domain, which, as I was told, should not be needed.
Created attachment 326299 [details]
I tried same operation on CentOS 5.2 and there I can list domain computers without authorization. Also, from gvfs log, it looks like it actually gets list of computers, but has some kind of error after that. Anyway, I'm attaching the log.
Concerning server software and configuration, I couldn't find what is domain controller. All I can say, that it is AD and not NT4 domain. Any tips how to get this information are appreciated.
(In reply to comment #7)
> I tried same operation on CentOS 5.2 and there I can list domain computers
> without authorization.
CentOS 5.2 (resp. RHEL 5.2) is gnome-vfs2 based, just like Fedora <= 8.
> Concerning server software and configuration, I couldn't find what is domain
> controller. All I can say, that it is AD and not NT4 domain. Any tips how to
> get this information are appreciated.
You should ask your network administrator, I'm not a windows expert either. What to look for is any special security setting requiring clients to authenticate first for browsing.
Also, can you please post an output of 'smbtree'? I can't see any exact error in the gvfsd log, perhaps you just reached timeout during browsing.
Created attachment 326322 [details]
> CentOS 5.2 (resp. RHEL 5.2) is gnome-vfs2 based, just like Fedora <= 8.
Yes, but it does not require authorization to list domain, so I guess there is no special setting requiring it.
gvfs-1.0.3-3.fc10 has been submitted as an update for Fedora 10.
gvfs-1.0.3-3.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update gvfs'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2008-11176
gvfs-1.0.3-4.fc10 has been submitted as an update for Fedora 10.
I've turned some more debug printouts on by default, can you please grab the output of gvfsd again? This time without setting any env. variables, the samba debug should be set automatically. Hopefully this will show what's really happening there.
Oh, and one important thing - please disable firewall.
Created attachment 327247 [details]
log for version 1.0.3-4
Firewall is disabled.
Ok, I can see that getting list of neighbour computer works but accessing particular domains or computers fails.
### SMB-BROWSE: do_mount - [smb://sdcorp/; 0] dir = (nil), cancelled = 0, errno =  'Connection refused'
### SMB-BROWSE: do_mount - [smb://MYGROUP/; 0] dir = (nil), cancelled = 0, errno =  'Connection refused'
1. can you please check you can connect to these machines via smbclient? If MYGROUP is a workgroup containing some computers, smbtree or smbclient would most probably fail as well (as seen in your previous attachments, where MYGROUP nor SDCORP has no children).
2. can you please try resolving the hostname and open that IP address in Nautilus (e.g. smb://10.0.0.2/)? Some people reported issues with hostname resolving (which is weird, it's done by libsmbclient internally and cannot be changed, as it uses broadcasts).
All we can do for now is to display better error message instead of the universal one but that wouldn't solve the issue :-)
Created attachment 327301 [details]
output of smbclient -N -L 10.177.9.4
MYGROUP is a workgroup consisting of only one machine - F10 machine itself. SDCORP is a domain (F10 is not a domain member).
I did an nslookup on the domain - it resolves to multiple addresses and tried smbclient -N -L address (I tried few addresses, results are the same, see attachment)
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.