-
Notifications
You must be signed in to change notification settings - Fork 51
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
Can see my server, but not connect from OSx #67
Comments
Hi, Unfortunately you're right there is no easy solution. At least I haven't found one and I have exactly the same issue. I see the server in macOS - sometimes with randomly changing icon (despite the fact that I specifically set one icon to display) and I established myself the workaround cmd+k to connect manually to the server It became the new normal and I didn't really recognize this as a bug I still suspect that a macOS update interprets something differently than before. Or maybe I need to update the avahi config. Comparing to a local non docker install would help - if it works there something's wrong with my container 🙈 Unfortunately this will need around 2-3 weeks for me since I'm pretty busy at the moment If you find something new just update the ticket Thanks and kind regards |
Your nmbloopup is interesting, there is no nmbd running inside my container... maybe macOS uses it as some fallback 🤔 Can you connect manually? |
Thanks for the comments. And sorry for the long post below. I'm not sure what you mean by "manually", but I can not connect by using the "go" drop-down from Finder and then entering my address (smb://192.168....); I get "There was a problem connecting to the server...." Frankly, if that worked I'd probably do exactly what you've done :) . I did get that to connect at one point maybe a month or six weeks ago, but I've never reproduced that again. I'm similar to you in terms of time; I can only spend an hour or so a week on it. A couple more data points: we know the TCP/IP level between the systems is fine, because I'm manipulating the samba server from an ssh session that's initiated on my mac. For an even more manual attempt to mount, I've tried mounting at the command line:
That command line works fine with my other samba host (which is a bit hard to compare with; it's a ~10 year old Fedora box). OTOH, one thing I checked: yup, the old one's running nmbd. I guess I'll see if that helps.... Well, more data, no fix. I exec'ed into my container and ran And... now the nmblookup returns the host. Even when I run it from my other samba host. MacOS still won't mount it. But here's another data point. From that Fedora machine:
But as you can see from my original post, I get a good response to that command line when I run it on the new samba host with the container setup. So I Googled that and found https://www.linuxquestions.org/questions/linux-networking-3/samba-min-protocol-%3D-smb2-causes-protocol-negotiation-failed-nt_status_invalid_network_response-4175597669/ . OTOH, when I tried to set the MIN protocol, I probably screwed up the syntax in the docker-compose.yml; I added
but didn't see any change in my smb.conf even after a Thanks for your help! |
Super interesting, so it's still different from my issue. I'll prioritize this issue and try to evaluate this problem within the next few days. Yeah this problem with the minimum samba versions is annoying, at the early days of this container I had a flag to simply enable older versions. maybe big sur has problems with the new server version...
this is the correct and hacky way to configure the server_min_protocol version on my container, you can try it. would be interesting if it works :) |
did it work? |
Well, no and yes: OSx still doesn't connect. Thanks for the syntax; it definitely changed the settings. And, from my other Samba server:
which is different from |
More information: I can mount the drive from my other Linux box (the same one as that
So this is something about requirements for OSx (security? protocol version?); Samba is "working" for an old (Fedora Core 20) definition of working :) . One point, though: it takes a long time to succeed:
So let's see if I can adjust OSx's timeout... and that 20s is a suspiciously round number (also quite repeatable; in three tries the time only differs by 0.003s). |
Looking for a way to adjust that timeout... it appears to be ~10s (samples at 11, 13, and 12s)... After more googling, I found https://developer.apple.com/forums/thread/680252, so I created an
and that makes things different, not quite successful yet:
Nothing gets logged at the output of my samba container during these transactions (i.e., Further evidence: I got prompted for authentication when trying to mount from the I tried a few other options, including
and probably a dozen other things. Same basic answer: it appears I can get authenticated, but once I do, I get
(I can get that error message from |
I'm going to give up on the Samba approach for my problem, at least for a bit; I've made more progress with NFSv4 in an hour than I did in four sessions playing w/ Samba, and it's likely to fit my initial use cases just as well. Closing; will re-open if I get brave enough to try again. Thank you for your help! It's been interesting! |
I'm pretty clueless on Samba configuration. And I'm stymied with getting the setup to work.
Current behavior on my Mac OSx Big Sur client is that I can discover the server ("newsounds"), but I can't connect.
I'm only setting it up as guest right now. When I connect, a "Loading..." box is briefly displayed before I get "Connection Failed".
I think I've got about the dead simplest setup: not disabling anything, just trying to mount one directory.
docker-compose.yml:
If I
docker exec -it ...
into the container, the/home/shares/Music
folder exists, has files, and I can read all files in it.When run from my host,
nmblookup '*'
does not show the host, though the other samba server on my net does show up.From the host:
My host is modern Ubuntu server, headless:
The ubuntu firewall is disabled:
I've posted the startup log as a gist at https://gist.github.com/cobbr2/328fce96e3e2be2fea34a73f74ae86a7
Thanks for looking, it seems there must be something completely obvious I'm missing.
The text was updated successfully, but these errors were encountered: