Hostname <ip> is not ours

[alex-berliner]

Hi, I'm trying to set up a simple server and I'm having trouble connecting to it with smbclient.
Command and error:

box@box:~$ docker run -it --rm --name box -p 445:445 -e "USER=box" -e "PASS=s" -v "/home:/storage" dockurr/samba
smbd version 4.21.6 started.
Copyright Andrew Tridgell and the Samba Team 1992-2024
parse_dfs_path_strict: Hostname 0.0.0.0 is not ours.
parse_dfs_path_strict: Hostname 192.168.1.101 is not ours.

I use this smbclient command. Here is it attempting with various localhost aliases ("localhost" itself doesn't work btw!)

box@box:~$ smbclient //0.0.0.0/storage -U box%s
tree connect failed: NT_STATUS_BAD_NETWORK_NAME

box@box:~$ smbclient //127.0.0.1/storage -U box%s
tree connect failed: NT_STATUS_BAD_NETWORK_NAME

box@box:~$ smbclient //192.168.1.101/storage -U box%s
tree connect failed: NT_STATUS_BAD_NETWORK_NAME

# different error with bad user, btw
box@box:~$ smbclient //192.168.1.101/storage -U bad%bad
session setup failed: NT_STATUS_LOGON_FAILURE

I'm running on Ubuntu 24.04. My samba package is installed but for this test disabled with sudo systemctl stop smbd.

Can someone please help me tell why this isn't working? Thanks.

[erhuz]

Think might not solve the problem, but to me it looks like you haven't configured a share name, try:

docker run -it --rm --name box -p 445:445 -e "NAME=storage" -e "USER=box" -e "PASS=s" -v "/home:/storage" dockurr/samba

Edit: fixed the passing of env-var NAME

[alex-berliner]

@erhuz Yes, you were right. Thank you!

I'm looking at the default command listed in the repo's readme and it doesn't set the share name to Data:

docker run -it --rm --name samba -p 445:445 -e "USER=samba" -e "PASS=secret" -v "${PWD:-.}/samba:/storage" dockurr/samba

Are the compose and CLI commands actually the same?

[erhuz]

No, --name does not get passed along to the internal workings of the container, it is only for organizing docker.

Yes, Docker Compose pass the arguments under the "environment" attribute to the docker container in just the same way that the '-e' flag does.

For example:

# docker-compose.yml
...
environment:
  - FOO: "bar"
...

Is just the same as '-e "FOO=bar"' in

#!/bin/sh

docker run ... -e "FOO=bar" ...

Ps. I updated the code in my comment above, it had a typo.
And don't copy & paste code from this comment, I wrote on the phone, so it possibly contains weird characters.

[alex-berliner]

So then I think the non-compose command in the README needs -e "NAME=Data". It doesn't have it currently.

[erhuz]

Sounds like a perfect time for you to make a PR ;)

[alex-berliner]

@erhuz I've created the PR

[erhuz]

Nice, I'm just a random guy though, not a maintainer. @kroese might be able to merge if he likes it.

[adit-s]

I had the same issue and was able to get rid of the associated error message in the logs (parse_dfs_path_strict: Hostname x.x.x.x is not ours) by adding the following to the docker run command:
--hostname fqdn
This adds an entry to the container's /etc/hosts file with the fqdn.

And then connecting to the fqdn instead of the IP from the client (smb:fqdn).

Hope this helps anyone else with the same issue.