parse_dfs_path_strict: can't parse hostname from path \<ip/fqdn>
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- docker, docker-compose, shell
- Domain
- infrastructure, networking
Research direction
Start by comparing the repository's smb.conf with the mounted /etc/samba/smb.conf in the Docker Compose setup, then reproduce the DNS and IP connection attempts on Alpine 3.23. Review the parse_dfs_path_strict log output and the effects of hostname and host msdfs settings. Done means identifying the configuration or container change that allows the existing share to connect successfully from macOS or iOS.
Written by the indexing model from the issue text.
Description
Everything works normally when i don't mount a custom smb.conf in the container. When i do, i get these errors in the docker logs:
Using provided configuration file: /etc/samba/smb.conf.
smbd version 4.23.7 started.
Copyright Andrew Tridgell and the Samba Team 1992-2025
parse_dfs_path_strict: Hostname smb.example.com is not ours.
parse_dfs_path_strict: Hostname smb.example.com is not ours.
parse_dfs_path_strict: can't parse hostname from path \smb.example.com
parse_dfs_path_strict: Hostname 192.168.202.10 is not ours.
parse_dfs_path_strict: Hostname 192.168.202.10 is not ours.
parse_dfs_path_strict: can't parse hostname from path \192.168.202.10
This is two attempts, once via DNS, once via IP.
When i connect from macOS, i get this error:
There was a problem connecting to the server “smb.example.com”.
The share does not exist on the server. Please check the share name, and then try again.
(The share name is correct, also tested on iOS)
My docker compose:
services:
samba:
image: dockurr/samba
container_name: samba
restart: unless-stopped
environment:
- NAME
- USER
- PASS
- UID
- GID
ports:
- "445:445"
volumes:
- ${STORAGE_PATH}:/storage
- ${SMB_CONF_PATH}/smb.conf:/etc/samba/smb.conf
the mounted smb.conf is simply the one from this repo. I've also tried a few different ones without results. I'm running alpine 3.23
Please note that when i add hostname: smb.example.com to the compose like proposed in #50, that error goes away, but the one from the title remains and i still cannot connect. In fact, when i add host msdfs = no to the smb.conf, there's nothing in the logs, but i still get the same error on the client when trying to connect.
- Dominant language
- Shell
- Stars
- 840
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dockur/samba
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Similar issues
-
application-issue
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Installomator/Installomator#3657 · 1 comment ·
Maintainers usually reply within 3 days
-
Own-agent checks: reject the Actions bot id in admit.mjs and test the source label in pr-verifyOpen
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
melodic-software/claude-code-plugins#17374 · 2 comments ·
Maintainers usually reply within 1 day
-
out-of-date
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
CachyOS/CachyOS-PKGBUILDS#2154 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
eip-work/kuboard-press#723 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
nekko-labs/nekko-agent#2998 ·
Maintainers usually reply within 1 day