Hide Forgot
Description of problem: In my home network I've a network share on a Windows XP client. In nautilus no network elements are shown, neither the XP client nor any shares. Entering explicitly the location with goto smb://server/share yields an error messagebox. The translation of the german message: "receiving memory list from server failed". findsmb also isn't able to find anything. But smbclient works fine and mounting the share with filetype cifs also works fine!!! Version-Release number of selected component (if applicable): nautilus in Fedora 16 How reproducible: new installed Fedora 16, small home network with several shares on Windows XP client similar problem with Windows Server 2008, but failes with authentication error Steps to Reproduce: 1.Select Network in Nautilus -> nothing is seen 2.optionally select GoTo location -> error message (s. text above) 3.mounting the shares explicitly or using smbclient works fine Actual results: Expected results: Additional info:
I tried to connect to a Windows file share running on a Windows 2008 Server through the *Connect to server* in Nautilus. I have entered the correct username, password and domain name. But it gives me an authentication failed with the following message: *Please verify your user details* However, I was able to mount the same share with the same username/password using the following command: mount -t cifs //192.168.202.20/data$ -o username=xxxxx,password=****** /home/tmp I guess this is something related to the original bug report. Otherwise, I can report another bug for this.
Try domain/user in Nautilus, also see Bug 756316, and Bug 753023. Does this help?
Thanks Brian, Your suggestion worked for me.
Hi, Brian, where should I try it ? In the File-menu, item "Connect with server..." (hope, that's the correct translation, I'm using the German Fedora-Version)?? That still doesn't work for me! Also GoTo Network doesn't see anything (and doesn't have options to enter usernames or domainnames). My environment is a simple WLAN network controlled by a DSL-router without a domain (the Windows clients are in a workgroup and my Fedora-client has the same name as dns-domainname, nis-domainname is empty). The router is the DNS-server and appends the string "fritz.box" as domainname to all the hostnames in the network when doing e.g. a traceroute. I think, that's a pretty common environment in many home networks and should be handled by Nautilus without any user intervention. Still mounting and connection via smbclient is no problem !!! Are there any log/trace-files generated by nautilus which would be helpful?
(In reply to comment #4) > Are there any log/trace-files generated by nautilus which would be helpful? Yes, please run `GVFS_DEBUG=1 GVFS_SMB_DEBUG=99 /usr/libexec/gvfsd -r` and attach the output here. Make sure the firewall is turned off.
(In reply to comment #5) > (In reply to comment #4) > > Are there any log/trace-files generated by nautilus which would be helpful? > > Yes, please run `GVFS_DEBUG=1 GVFS_SMB_DEBUG=99 /usr/libexec/gvfsd -r` and > attach the output here. Make sure the firewall is turned off. The result from root prompt --------------------------------------------- #GVFS_DEBUG=1 GVFS_SMB_DEBUG=99 /usr/libexec/gvfsd -r Failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ---------------------------------------------- Maybe it's my fault because I just switched from SuSE to Fedora and I'm not sure how to switch of firewall in Fedora. What I did: I stopped the services "iptables" and "ip6tables" via services-GUI.
(In reply to comment #6) > The result from root prompt Please don't run Gnome applications as root (or a different user than your running desktop session) - most things won't work that way. > Maybe it's my fault because I just switched from SuSE to Fedora and I'm not > sure how to switch of firewall in Fedora. What I did: > > I stopped the services "iptables" and "ip6tables" via services-GUI. Not sure what's the right way in systemd world, perhaps something like 'systemctl firewall.service stop' ?
Created attachment 546710 [details] logfile to comment 8 logfile to comment 8
(In reply to comment #7) > > Not sure what's the right way in systemd world, perhaps something like > 'systemctl firewall.service stop' ? In Fedora Security guide I'found the command "system-config-firewall" which starts up a GUI with a disable-button. I then entered your command with output redirection and dtried the following: 1) click in Nautilus in the left area on "Netzwerk durchsuchen" (translation maybe : scan/search network") 2) from menu File->Connect with server... I filled in the parameters for a network share in my home network The logfile is attached. During the run I got an error message at the console(stderr ?) ** (process:3080): WARNING **: Couldn't create directory monitor on smb://x-gnome-default-workgroup/. Error: Der angegebene Ort ist nicht eingehängt:
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.