Bug 40426 – Delay in visibility of new printer shares by Windows clients

Bug 40426 - Delay in visibility of new printer shares by Windows clients


Summary:	Delay in visibility of new printer shares by Windows clients

Status:	RESOLVED DUPLICATE of bug 44153

Product:	UCS
Classification:	Unclassified
Component:	Samba4
Version:	UCS 4.0
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	Samba maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-01-13 19:21 CET by Arvid Requate
Modified:	2017-04-24 14:02 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?:	2: Will only affect a few installed domains
How will those affected feel about the bug?:	1: Nuisance – not a big deal but noticeable
User Pain:	0.034
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Arvid Requate

2016-01-13 19:21:07 CET

Steps to reproduce:
* I joined a client to a UCS Samba/AD DC Master
* I created two printer shares via UMC
* Logged in as Domain Administrator to the Windows Client I open printmanagement.msc and add the Master as printserver.
* When I click on the printers node in that tool I only see printer1
* When I check with smbclient on the Master I see printer1 and printer2
* I hit F5 about x*10 times, no change.
* Feeling irritated I open this bug report (takes some time > 10 sec)
* I hit F5 again and printer2 shows up.

This happend twice now: Yesterday on an UCS@school Multiserver Master and today on a UCS@school Singlemaster. In both cases I always see the typical "PDFDrucker".

Comment 1 Arvid Requate

2017-04-24 14:02:46 CEST


*** This bug has been marked as a duplicate of bug 44153 ***