Please read this: [HowTo] Provide System Information
and post some more information so we can see what’s really going on. Now we know the symptom of the disease, but we need some more probing to know where the origin lies…
An inxi --admin --verbosity=7 --filter --no-host --width would be the minimum required information… (Personally Identifiable Information like serial numbers and MAC addresses will be filtered out by the above command)
Also, please copy-paste that output in-between 3 backticks ``` at the beginning and end of the code/text.
Did you enter your Windows user name and password???
P.S. If you enter a bit more details in your profile, we can also see which Desktop Environment you’re using, which CPU/GPU or Kernel, … you have without typing it every time
maybe - just maybe - this is easy
(cave: I have not much experience with samba …)
What username is already filled in?
The one on your Linux system or the one on your Windows system?
Which password did you use?
Did you even set one to access shares on Windows?
Something isn’t right.
I mean in the way you approach this.
You want to access a share.
This share has no password on it.
Not sure about the user name - whether it’s the same as in Linux.
Why would you enter your Linux credentials (usename/password) to access a share which is not on Linux but on Windows and which doesn’t have a password set
and expect it to succeed?
it seems illogical
… but this question/advise comes from someone (me) who doesn’t have any Windows shares to try and play with …
I have the same issue. My sis doesn’t have password on her Win10 system (no idea how she set it that way, it’s not auto loging, it’s actual no password) and because of that samba on Linux won’t work, because there is no credintials and samba won’t accept that…
If someone knows the way out of this, please, let us know.
i have a shared folder on windows 10 with full access to read & write with no password.
files > other locations > smb://ipaddress pops up an authentication required window with
a username box where my linux username is already there, domain = workgroup & an empty box for password.
when i enter my linux, in this case, the password for my manjaro username the pop-window disappears & re-appears.
when i do the exact same procedure with ubuntu i am given access to my shared folder on windows.
That difference in behavior between Ubuntu and Manjaro would indicate to me
to me!
that there is a difference in what software is installed and how it is configured.
But:
I can’t be of real help here - since I cannot test how and why either one system behaves like it does
because I have no Windows share to test with.
Someone else might know more, have experience with this.
PWD: nothing! (As in: don’t type anything and hit enter)
If that doesn’t work, enter:
UID: \\m.n.o.p\WinUserName
PWD: WinUserPWD
Where, obviously m.n.o.p is the LAN IP address of the Windows machine, WinUserName is any username on said Windows machine and WinUserPWD is the password of WinUserName.
One thing that worked for me was to edit group policies in windows. It looks complicated but, in fact, was quite easy.
On the Windows computer:
Win +R
type gpedit.msc and press Enter
Go to Machine settings→Administrative templates→Network→Lanman workstation
There should be an option called something like “enable insecure guests login” which is disabled by default. You must enable this policy.
After doing that, remember to change the network options to share without using passwords