Skip to content

Fix: idmap range not specified for domain '*' #25

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 14, 2024
Merged

Fix: idmap range not specified for domain '*' #25

merged 1 commit into from
Nov 14, 2024

Conversation

JBlond
Copy link
Contributor

@JBlond JBlond commented Nov 14, 2024

Fix: idmap range not specified for domain '*' from #11

Error message:
idmap range not specified for domain '*'
parse_dfs_path_strict: Hostname is not ours.

idmap config settings control how Security Identifiers (SIDs) identifying Windows accounts (users, groups, and computers) are mapped to UIDs and GIDs on various Unix-like platforms. From the "Identity Mapping" chapter of the official Samba documentation: The specific setting idmap config * : range = - specifies how users that are not specific to a Windows domain are mapped; the "*" means "all accounts not covered by other idmap config statements." Having this in smb.conf is very important, as all the Windows "builtin" accounts and groups use this setting.

The and numbers simply refer to a range of otherwise unused UIDs/GIDs on the Linux server running Samba. It's important that none of these IDs be assigned to a local account or group, ever.

Error message:
idmap range not specified for domain '*'
parse_dfs_path_strict: Hostname <IP> is not ours.

idmap config settings control how Security Identifiers (SIDs) identifying
Windows accounts (users, groups, and computers) are mapped to UIDs and GIDs on various Unix-like platforms.
From the "Identity Mapping" chapter of the official Samba documentation:
The specific setting idmap config * : range = <low> - <high> specifies how users that
are not specific to a Windows domain are mapped; the "*" means "all accounts not covered by other idmap config statements."
Having this in smb.conf is very important, as all the Windows "builtin" accounts and groups use this setting.

The <low> and <high> numbers simply refer to a range of otherwise unused UIDs/GIDs on the Linux server running Samba.
It's important that none of these IDs be assigned to a local account or group, ever.
@kroese
Copy link
Contributor

kroese commented Nov 14, 2024

Thanks. I see how this could fix the error:

idmap range not specified for domain '*'

but in what way is it related to the error:

parse_dfs_path_strict: Hostname is not ours.

as it complains about an unknown hostname (nothing to do with user id's).

And if I Google for that error in combination with idmap I get 0 hits. So where did you learn that idmap has something to do with hostname is not ours?

@JBlond
Copy link
Contributor Author

JBlond commented Nov 14, 2024

Once you set the range the other error comes up. Because a windows client with SMB 2 or newer will try to use DFS.
So the user might have to replace server string = smb with the host name from the docker server. However using the IP will no longer show an error.

@kroese kroese merged commit 8ed9e45 into dockur:master Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants