Skip to content
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

parse_dfs_path_strict: Hostname <hostname> is not ours. #11

Open
yangy30 opened this issue Jul 13, 2024 · 3 comments
Open

parse_dfs_path_strict: Hostname <hostname> is not ours. #11

yangy30 opened this issue Jul 13, 2024 · 3 comments

Comments

@yangy30
Copy link

yangy30 commented Jul 13, 2024

parse_dfs_path_strict: Hostname 192.168.1.1 is not ours.
parse_dfs_path_strict: Hostname 192.168.1.1 is not ours.
parse_dfs_path_strict: Hostname 192.168.1.1 is not ours.
@kroese kroese changed the title May I ask how to eliminate this warning? parse_dfs_path_strict: Hostname <hostname> is not ours. Oct 14, 2024
@kroese
Copy link
Contributor

kroese commented Oct 14, 2024

Maybe by connecting via hostname instead of the IP? I have no clue to be honest

@Rohurd
Copy link

Rohurd commented Oct 23, 2024

Not sure if this is related, but I had the same problem, and this post really helped me: https://superuser.com/a/1829022

Basically I had an entry in my smb.conf with "force user = xyz", but the user did not exist in the container. So I added the user in the users.conf (mapping to the correct uid and gid), and the error disappeared...

@kroese
Copy link
Contributor

kroese commented Oct 26, 2024

I see the same message in my log, but everything works fine. So I guess this not really an error but just a info/notice message that it doesnt recognize the IP (which makes sense since inside Docker the external IP is unknown). So I think it can safely be ignored.

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

No branches or pull requests

3 participants