All Windows users joining LAN reported as attempted login

[dsmithdewarcom]

Slightly annoying issue:

Whenever a Windows user on our LAN boots up their pc, they are reported in QTS as a login "error", even though they did not attempt to access any shares or otherwise connect to the NAS (TS-451, 4.1.1 Build 1101).

Any way to fix this?

Thanks

[pwilson]

Slightly annoying issue:

Whenever a Windows user on our LAN boots up their pc, they are reported in QTS as a login "error", even though they did not attempt to access any shares or otherwise connect to the NAS (TS-451, 4.1.1 Build 1101).

Any way to fix this?

Thanks

Create "users" on the NAS with the exact same username/password pair as used by your "users" on their Windows machines. As long as their username/password pairs "match" between Windows and the NAS, they will get access to the NAS.

I'd help more, but you provided no useful information to work with. Going forward: Please review: When you're asking a question, please include the following. Is your Windows network just a standard "WORKGROUP" or it is using "Active Directory"?

What type of login "error"?
Thanks for not providing the error text, Log entries, or screenshots for us to work with.

[dsmithdewarcom]

Patrick,

You misunderstood my question. Nobody is trying to login to the QNAP.

All users connect as "guest", without needing to login.

Are we clear?

I do not want alerts from the NAS about people who have (only) joined the workgroup reported as "login fails".

[pwilson]

Patrick,

You misunderstood my question. Nobody is trying to login to the QNAP.

All users connect as "guest", without needing to login.

Are we clear?

I do not want alerts from the NAS about people who have (only) joined the workgroup reported as "login fails".

We were clear in the first place. Create your users properly on the NAS, and your "login fails" messages will go away.

Your users are "trying to login" to your Workgroup on the QNAP, whether you (or they) know it or not. This is how Windows networking works. If you don't like the way Microsoft does it, please complain to Microsoft. Samba has been emulating Windows networks for over 25 years, and it is completely transparent to the end-user if configured properly.

This is a NetworkAdmin issue, rather than a QNAP/Samba issue.

[dsmithdewarcom]

Oh looky.

log-options.gif

[Eraser-EMC2-]

And what does the picture means ?

[pwilson]

Oh looky.

log-options.gif

What is that image supposed to do for us?

We actually want information about your network and NAS configuration. Please review: When you're asking a question, please include the following

[Briain]

And what does the picture means ?

Isn't there some saying about 'a picture being worth more than a thousand words'?

Of course, Inappropriate for me to comment as I can't draw (so nobody can follow my diagrams) and I'm also Scottish (so nobody can understand a word that I'm saying), so in my case, I'm at my most comprehensible when I shut up and draw nothing

All the best
Bri

[dsmithdewarcom]

What is that image supposed to do for us?

Problem solved, nothing more to say, really.

Thanks all.

[pwilson]

What is that image supposed to do for us?

Problem solved, nothing more to say, really.

Thanks all.

Thanks for sharing what the "problem" and "resolution" were. I'm sure this lack of information will be beneficial to other community members.

[dsmithdewarcom]

Patrick:

Briain ^^^ sussed it. I'm sure you can too, if you put your mind to it.

Have a great day.

[Briain]

Hi

Yes, I see what you have done (as indeed will the others who have responded) but I must admit that I was also poking a little fun at the extreme brevity of your answer (I was just trying to raise a few smiles by being a little cheeky). Patrick makes a very good point about a few words also being necessary, as including a short explanation can really help others who might be searching for a solution to a similar issue (and chance upon this thread); detailed answers are what can make this forum such a useful resource (or the lack thereof can make it frustrating to new members seeking answers to problems).

All the best
Bri

[dsmithdewarcom]

TL;DR version

Problem: false SAMBA "Login Fail" reports in System Connection Logs.

Solution:* unclick "SAMBA" checkbox in "System Connection Logs/Options" dialog.




*Works for me, YMMV.

[Eraser-EMC2-]

This is not a solution
The error is still existing, but you will not see it anymore.

[schumaku]

All users connect as "guest", without needing to login.¨

Windows standard - guest (anonymous access) is used to browse the NAS shared folders if there is no matching account.

I do not want alerts from the NAS about people who have (only) joined the workgroup reported as "login fails".

A workgroup is no management entity permitting or denying any access - so there is no join of a workgroup - it's just a name. Much more, the workgroup system was defined just to differentiate multiple "work groups" on a bigger network. Simple check: Configure a Windows system to a different workgroup name. You still can see and access the same resources, regardless of the workgroup setting. Interesting these weird ideas still exist almost 22 years since the Windows Workgroup concept was introduced.

Complain to Microsoft about their design.