Description of problem: I can't add a Windows printer that is shared from a Windows 7 host joined to another domain. Version-Release number of selected component (if applicable): control-center-3.14.2-2.fc21.x86_64 samba-libs-4.1.15-1.fc21.x86_64 How reproducible: Reproducible every time. Steps to Reproduce: 1. Go to Activities. 2. Type Printers and select "Printers Add printers, view printer jobs and decide how you want to print". 3. Click the Unlock button at the top right. 4. Enter your password. 5. Click the + at the bottom left. 6. Type the hostname of the Windows machine. 7. Wait. Actual results: Printer attached to the Windows machine never appears. Expected results: Windows printer to appear. Additional info: The Windows machine in question is reachable by Nautilus by going to Browse Network -> Windows Network -> <Domain of Windows Machine> -> <Name of Windows Machine>. A "Password required for <Name of Windows Machine>" dialog will pop up and it's possible to enter an appropriate Username, Domain and Password. Tick remember forever and the shares on that machine will be shown but not its printer. It is also possible to use smbclient -U<Domain of Windows Machine>/<appropriate username> -L//<Name of Windows Machine>/ and it will give back information like: Domain=[<Domain of Windows Machine>] OS=[Windows 7 Ultimate 7601 Service Pack 1] Server=[Windows 7 Ultimate 6.1] Sharename Type Comment --------- ---- ------- [...] Name Of Printer Share With Spaces (Location Too) Printer Description IF one is determined enough it is possible to system-config-printer, click unlock, click Add, Open the Network Printer dropdown, select Windows Printer via SAMBA, paste an url like <Name of Windows Machine>/Name%20Of%20Printer%20Share%20With%20Spaces%20%28Location%20Too%29 tick Set authentication details now enter a username of <Domain of Windows Machine>/<appropriate username> and the passsword (notice how the Browse... and Verify... buttons remain disabled forever) click Forward, manually select the appropriate manufacturer in the Choose driver window and click Forward, choose an appropriate Model in the Choose driver window and click Forward, select appropriate Installable Options and click Forward, Click Apply on the last screen, authenticate for the last time and the printer will have been added. The problem is this series of steps is not very discoverable and is much harder than adding the printer using Mac OS X 1.9 or Windows 7...
It turns out that Windows machines do turn up but you have to wait around 5 minutes before they appear. Additionally this issue has persisted into Fedora 22's control-center-3.16.2-1.fc22.x86_64 samba-client-libs-4.2.1-8.fc22.x86_64 Changing version.
Still here in Fedora 23.
Filed upstream: https://bugzilla.gnome.org/show_bug.cgi?id=758146 .
Still here in Fedora 24 with control-center-3.20.1-1.fc24.x86_64 samba-client-libs-4.4.4-3.fc24.x86_64
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 EOL if it remains open with a Fedora 'version' of '24'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.