Fix: idmap range not specified for domain '*' #25
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.