I am unable to open a samba share that I have in my network. I tested it with my windows computers and even tried testing with another linux distro “Debian 11” and all are able to access the network share without the login window appearing.
But no matter what I do in openSUSE tumbleweed, it demands a username and password. I have tried pressing enter with username and password boxes blank and even tried entering “anonymous” in the username box with no password and still cannot connect.
Is this a bug? how do i open a share in openSUSE without the login window appearing?
eric@localhost:~> smbclient //192.168.5.2/Downloads
Password for [WORKGROUP\eric]:
tree connect failed: NT_STATUS_INVALID_PARAMETER
eric@localhost:~>
I pressed enter in an attempt to try to log in anonymously but it wont budge. Every other device on my network can access my samba share anonymously without ever having to ask for a login. this computer is the only one running openSUSE and has this issue.
So my guess is that its an openSUSE issue or maybe I need to disable another security setting somewhere in this distro.
Is your samba server using SMB1 (NT1), a now deprecated and insecure ‘legacy’ samba protocol? That might explain the issue you’re having. Try the following…
eric@localhost:~> smbclient //192.168.5.2/wd-red-8tb -m NT1
lp_load_ex: Max protocol NT1 is less than min protocol SMB2_02.
Password for [WORKGROUP\eric]:
protocol negotiation failed: NT_STATUS_INVALID_PARAMETER_MIX
eric@localhost:~> smbclient //192.168.5.2/ -m NT1
lp_load_ex: Max protocol NT1 is less than min protocol SMB2_02.
Password for [WORKGROUP\eric]:
eric@localhost:~>
I checked the server and I can confirm that the lowest version is set to at least smb2.02 highest is smb3.11
I also changed the name of downloads to something else and it looks like it wanted to connect but then brought me back to the main command prompt.
Clarifying here, I am able to access this from any windows computer along with a test computer I installed debian 11 on and was able to access WITHOUT having to use login credentials. this is exactly what I wanted.
With that out of the way, here is the config you wanted.
[global]
log level = 1
netbios name = NASAP
server string =
syslog = 10
encrypt passwords = true
preferred master = yes
use sendfile = yes
aio read size = 2048
aio write size = 2048
large readwrite = yes
security = user
oplocks = yes
mangled names = no
max stat cache size = 64
workgroup =
bind interfaces only = yes
guest account = nobody
map to guest = bad user
smb passwd file = /var/samba/smbpasswd
private dir = /var/samba
passdb backend = smbpasswd
log file = /var/smbd.log
max log size = 1000
socket options = TCP_NODELAY IPTOS_LOWDELAY SO_SNDBUF=262144 SO_RCVBUF=262144
read raw = yes
write raw = yes
max xmit = 65536
dead time = 15
getwd cache = yes
lpq cache time = 30
server min protocol = SMB2_02
server max protocol = SMB3_11
printing = none
load printers = No
usershare allow guests = Yes
smb3 encryption = no
This computer that I have openSUSE running on is literally the only computer being picky about this login credentials thing.
Furthermore, I am able to even access this share from my android phone/s without the need to enter the login credentials. it just connects no questions asked.
Yes, I get that. However from what I can see here, smbclient can’t make a successful connection to the server at all (with or without credentials), right?
when you refer to the samba bug, are you specifically referring to the smbclient itself?
After some amount of testing on all my windows computers and the debian 11 test bed I setup, I believe its got something to do with openSUSE TW specifically.
My experience with connecting to a Windows 10 share (using MB2/SMB3) at least, and set for “Everyone” to access, still results with samba prompting for username/password credentials, even though what is entered does not matter. If I attempt to connect without such credentials, access is denied. Anyway, I can’t replicate what the OP is experiencing with their samba client.
That is exactly what I have been trying to say here. I do not understand why you dont see that. Are you rush reading by any chance?
This is happening to me when I use openSUSE but not when I use windows, debian 11 or android.
the samba share has no password so anyone connecting to it can simply connect to it with full access. openSUSE is the only one that cannot.
Think about it. I have more than 5 computers already able to connect to it. this computer I am on that is running openSUSE cannot connect to it. That, to me, indicates this is an issue with openSUSE.
openSUSE, no matter what I do, keeps asking for a non-existent username and password to connect to the same share.
No, I got that from your opening post. However, you left some details out, leaving us to speculate. I assume that you’re trying to access via a graphical file manager. Which one? It’s not clear whether you succeeded in accessing the share(s) in question (even when presented with an authentication dialogue box)?
Regardless of the above, smbclient should be able to connect similarly. If it is a samba server, configured for anonymous access, then you should be able to do something like
smbclient //<server hostname or IP/<share> -N
openSUSE, no matter what I do, keeps asking for a non-existent username and password to connect to the same share.
For KDE at least, you can set a username and password under
System Settings > Network > Settings > Windows Shares
In your case an arbitrary username and password should suffice, and then Dolphin will use those credentials (with no dialogue box presented).
OS: openSUSE Tumbleweed
DTE: KDE Plasma 5
Fully updated as of 8:12pm 11/7/2021
Using only the GUI instead of CLI. The only time I use the CLI is when you give me CLI commands.
I did find the windows share settings and tried “anonymous” in both username and password. after trying to navigate to the share via “dolphin” it still shows the login screen in vain.
[QUOTE=deano_ferrari;3079787]Regardless of the above, smbclient should be able to connect similarly. If it is a samba server, configured for anonymous access, then you should be able to do something like
smbclient //<server hostname or IP/<share> -N
This actually works. But I dont want to use a command line. I want to connect to the drive in a GUI. not a cli.
eric@localhost:~> smbclient //192.168.5.2/wd-red-8tb -N
Try “help” to get a list of possible commands.
smb: >
In your previous post, you asked if I was using “NT1.0” followed by **"…a now deprecated and insecure ‘legacy’ samba protocol?"
**
Yes I get it, its an old, outdated, possibly now unholy thing to use. But I am trying to connect to a share that allows anonymous login with Read and Write access. The only reason is see this being a concern is if its for compatibility reasons. Deprecated? yeah i agree Insecure? Read the writing on the wall here.
“I am trying to connect to a share that allows anonymous login with Read and Write permissions.”
If I sound mean, I am sorry. openSUSE is pretty much able to cover just about literally everything I want out of a linux distro except for this one little problem and I really want to fix it. It makes my persistant nature restless in these sorts of technological things. You can tell me to take breaks all you want but it will just be like “white noise” to me when the the supposed fixes and solutions in the guides and other peoples posts do not help.
Ok, is this the kwallet authentication dialogue box? (It should show an option to remember password as well.)
This actually works. But I dont want to use a command line. I want to connect to the drive in a GUI. not a cli.
eric@localhost:~> smbclient //192.168.5.2/wd-red-8tb -N
Try “help” to get a list of possible commands.
smb: >
Ok, good to know that works. (Commands and output can be useful to check things more definitively, rather than relying on users descriptions and interpretations.)
In your previous post, you asked if I was using “NT1.0” followed by “…a now deprecated and insecure ‘legacy’ samba protocol?”
Yes I get it, its an old, outdated, possibly now unholy thing to use. But I am trying to connect to a share that allows anonymous login with Read and Write access. The only reason is see this being a concern is if its for compatibility reasons. Deprecated? yeah i agree Insecure? Read the writing on the wall here.
As you confirmed that the samba server uses SMB2+, we don’t need to concern ourselves with this.
