The Samba-Bugzilla – Bug 11280
printmanagement.msc: Empty printer list on Win7 and Win10
Last modified: 2016-11-24 15:50:33 UTC
Created attachment 11067 [details]
When connecting with printmanagement.msc to a Samba print server, the printer list isn't shown when using Windows 7. In Windows 8.1 it works.
Attached a screenshot showing the empty list in printermanagement.msc on Win7 and the printer list, when accessing the remote printers via \\hostname.
Also attached a level 10 debug log Win7 + Win81 showing a refresh try of the printer list.
Created attachment 11068 [details]
Created attachment 11069 [details]
Uploading the logfiles again.
It contains now not just the refresh of the printer node. Now it also contains opening printmanagement.msc and clicking to the printer list.
I re-tested this with a Samba 4.5.0rc2 print server: The printers are listed only on Windows 8.1, but not on Windows 7 and 10.
Windows 7: fail
Windows 8.1: OK
Windows 10: fail
(all MS updates until Jul 2016 applied)
I had the same issue under Windows 10. It started to work installing RSAT tools.
Please test if it works changing the OSVersion:
spoolss:os_major = 5
spoolss:os_minor = 2
spoolss:os_build = 3790
Also try setting:
spoolss:architecture = Windows x64
Created attachment 12644 [details]
Level 10 debug log
I re-tried it with the settings from comment #4 and comment #5. They don't help.
Find attached a new log capture. It contains:
- opening the printmanagement.msc utility
- selecting the "Printers" node of the server
Win7 64-bit, patch level: Jun 2016
This is a bug in Windows and it looks like it is there since Windows XP.
The Print Management console uses notification to get the printers.
The manager calls
RpcOpenPrinterEx() followed by
This doesn't work. As [MS-RPRN] states:
hPrinter: A handle to a printer object or server object that was opened by
RpcAddPrinter (section 22.214.171.124.3), RpcAddPrinterEx (section 126.96.36.199.15),
RpcOpenPrinter (section 188.8.131.52.2), or RpcOpenPrinterEx (section 184.108.40.206.14).
This handle MUST have been previously used successfully by the client in a call to
RpcRemoteFindFirstPrinterChangeNotification (section 220.127.116.11.3) or
RpcRemoteFindFirstPrinterChangeNotificationEx (section 18.104.22.168.4), and it MUST NOT have been closed by calling RpcFindClosePrinterChangeNotification (section 22.214.171.124.2).
The RpcRemoteFindFirstPrinterChangeNotificationEx() is not issued. The same happens against Windows Server 2003.
I will upload a capture showing the issue tomorrow.
A workaround is to install the RSAT tools.
Created attachment 12690 [details]
This is a Windows bug. Reported to Microsoft ...