I set up a file-sharing server on my raspberry pi using samba and tailscale to connect to it from networks that aren’t the same as the raspberry pi’s.
Recently I added a second user so that they can backup their stuff.
On linux everything works fine but on Micro$hit’s Windows 10 it doesn’t let them connect to the file server. Or rather, at first I tried with an unrelated person who only accessed the public folder as a “guest” (rather: no user) from windows and it worked. Then we tried with this person and it let her access the server at first but wouldn’t let her log in with her credentials. Turns out I forgot to add the user to samba, so I do that, reboot the server, and then it just doesn’t let her connect to the server in the first place, giving an 0x80004005 unspecified error.
I should also point out that she’s accessing the machine as an external tailscale user with the device being shared to her.
What could be the cause of this and how can we go about solving it? I’d love to just tell her to just install linux and be on with our day but that simply isn’t much of an option.
Sorry if the information isn’t too precise, I’m still a bit of a noob.
EDIT: It works through the local network after disabling the firewall but connecting through tailscale doesn’t work.
there’s quite a few logs. Most say nothing at all or nothing useful.
running cat /var/log/samba/log.* the relevant parts (those datestamped at today) are probably these:
[2023/08/30 19:14:11.706304, 0] …/…/source3/smbd/server.c:1784(main)
smbd version 4.13.13-Debian started.
Copyright Andrew Tridgell and the Samba Team 1992-2020
[2023/08/30 19:14:12.011725, 0] …/…/lib/util/become_daemon.c:135(daemon_ready)
daemon_ready: daemon ‘smbd’ finished starting up and ready to serve connections
[2023/08/30 19:20:39.232740, 0] …/…/source3/smbd/server.c:1784(main)
smbd version 4.13.13-Debian started.
Copyright Andrew Tridgell and the Samba Team 1992-2020
[2023/08/30 19:20:39.301393, 0] …/…/lib/util/become_daemon.c:135(daemon_ready)
daemon_ready: daemon ‘smbd’ finished starting up and ready to serve connections
[2023/08/30 19:38:34.162744, 0] …/…/source3/smbd/server.c:1784(main)
smbd version 4.13.13-Debian started.
Copyright Andrew Tridgell and the Samba Team 1992-2020
[2023/08/30 19:38:34.231542, 0] …/…/lib/util/become_daemon.c:135(daemon_ready)
daemon_ready: daemon ‘smbd’ finished starting up and ready to serve connections
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
stupid question but where exactly can I find these logs?
Server uses linux so I can probably find them somehow but idk about the windows client
/var/log/samba/there’s quite a few logs. Most say nothing at all or nothing useful.
running
cat /var/log/samba/log.*the relevant parts (those datestamped at today) are probably these: