Bug 34429

Summary:	Samba4 DFS: prefer logon DC
Product:	UCS	Reporter:	Arvid Requate <requate>
Component:	Samba4	Assignee:	Samba maintainers <samba-maintainers>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P5	CC:	bj, gohmann
Version:	UCS 4.2	Flags:	requate: Patch_Available+
Target Milestone:	---
Hardware:	Other
OS:	Linux
What kind of report is it?:	Bug Report	What type of bug is this?:	2: Improvement: Would be a product improvement
Who will be affected by this bug?:	3: Will affect average number of installed domains	How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.069	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:	dfs_samba4_preferlogondc.patch

Description Arvid Requate

2014-03-31 20:00:04 CEST

Created attachment 5842 [details]
dfs_samba4_preferlogondc.patch

Currently, dfs_samba4 checks for the subnet/site a MS client is in, and sorts the list of DCs returned to the client, putting the in-site DCs on top and DCs from other sites below. Bug 34370 randomizes the DCs within each of these two sets.

The MS DFS client protocol also specifies the possibility to configure a DFS server in such a way that he puts the logon server of the client/user on top. The attached patch basically implements this. It's a bit rough, as it literally simply additionally puts the logon DC on top of the list (so he ends up on the list twice). Don't know if upstream would be happy about this but it conforms to the words of the spec. The patch also introduces a new smb.conf share parameter, which currently needs to be put into the [IPC$] section. I guess upstream will not approve to that, as IPC$ is configured internally in Samba4:

 dfs_samba4:preferLogonDC = yes

Default is false.

Comment 1 Ingo Steuwer

2020-07-03 20:51:17 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.