Share authentication failure

I'm not a commandline smarty, but I was wondering if there were a way to try to access the share from the commandline instead of the GUI file manager, then when the authentication failed, there might be some kind of failure message that could be useful.

Or, maybe I should look at the situation of the desired share w/o using the Webmin, so I could tell if there were something 'wrong w/ it' - the share condition.

W dniu 19.08.2026 o 21:48, druck pisze:

I see something like this years ago on Discovery. Must be expensive.

-- Z totaliztycznym salutem! Jacek Marcin Jaworski, Pruszcz Gd., woj. Pomorskie, Polska 🇵🇱, UE 🇪🇺; tel.: +48-609-170-742, najlepiej w godz.: 5:00-5:55 lub 16:00-17:25; snipped-for-privacy@energokod.gda.pl>, gpg: 4A541AA7A6E872318B85D7F6A651CC39244B0BFA; Domowa s. WWW:

Possibly not. A Windows update may have screwed with the security settings.

My Windows 11 PC connects quite happily to my Pi5 and my Pi4 based RISC OS device.

Fairly (!) simple to check on Windows 11:

1. Go to Control Panel
2. Open Network and Sharing Centre
3. In the left column, click on Changed Advanced Sharing settings
4. Make sure firstly that sharing is enabled
5. Expand the All Networks section

I have the Encryption set to 40- or 56-bit, but Windows may have defaulted to 128-bit. I don't know enough about older Pis as per the OP, but it's probably worth exploring the above settings on the Windows side.

I'm getting deja vu. M$ brought out a service pack for Windows 2000 which included a patch that made its SMB server issue an invalid command to clients trying to connect, and then check the error message that came back. If the error message returned by the client (in this case Samba) wasn't worded exactly the way an M$ client would do it, then the server would refuse to connect.

(I might have server and client backwards here, it was a long time ago.)

It took the Samba authors about two days to fix that one, and I continued happily connecting to Windows shares from my Amiga.

I just don't get this stuff. I have a Win 11 pro workstation, 4 Pis, and two mini PCS, one Intel, one AMD - both with Ubuntu LTS

I have samba on all and I don't have any problems at all. OK if I want linux to linux comms, I would just use NFS

There are quite a few useful tools at the client end to test connections, authentication etc: nmblookup, smbtree, and in particular smbclient.

E.g. to get a listing of shares visible to a given username/password:

smbclient -U «username»%«password» -L «server-addr»

Specify domain as well:

smbclient -U «username»%«password» -W «domain» ...

Access a particular share:

smbclient //«server/«share-name» -U «username» «password»

(Hmm, there might be a typo in my notes ... might need a “%” instead of a blank between «username» and «password».)

Here’s a tip for troublesome Windows clients: they could be trying to use an obsolete connection protocol version or authentication protocol version that your Samba server is not configured to allow.

Expensive and tiring, all that pushing.

---druck