Windows 10 Standard User cannot connect to Red Hat Linux Share

Eagle51 · 13 Sep 2018

Yes, the group is WORKGROUP. All users are a member of WORKGROUP. JOHN is a member of WORKGROUP.

I wasn't referring to the WORKGROUP, but what appears to be GROUPS (i.e. work06,work13, etc) and I could be wrong about the GROUPS.

When I ran smbstatus it returned this:
Samba Version 3.6.23-51.elb
Username Group Machine ip address
debby workgroup work06 10.168.101.06
debby workgroup work13 10.168.101.13
....

Is there a command I can use to see if JOHN is a member of samba? That is where I think the problem is.

I believe you can list all Samba users with ... sudo pdbedit -L or sudo pdbedit -L -v for more info

If you look at the smbstatus output, you will see 4 Machines are using the Dexx username (and corresponding password), which is a Linux admin user, and two are using the user debby username (and password). All machines have their own usernames and passwords, so this should not be.
If I had to guess, I would say these machines have the same issue as JOHN and they just used the admin user and password to connect.

You're probably correct in your assessment, but I can't really advise you on how to straighten things out.

bro67 · 13 Sep 2018

Artman62, download Webmin and use it for creating Samba users, etc.. Use this guide. Samba Administration Guide - Manipulating Group Memberships Google eBooks also allow you to see a lot of guides for free. Keep this one in your bookmarks. Linux Samba Server Administration: Craig Hunt Linux Library - Roderick W. Smith - Google Books

Artman62 · 13 Sep 2018

Unfortunately, the admin name and password is not on the sudo list, so I cannot run the sudo pdbedit commands.
I cannot even run the pdbedit command itself.
So I have hit a dead end for the moment.

bro67 · 16 Sep 2018

Artman62 said:

Unfortunately, the admin name and password is not on the sudo list, so I cannot run the sudo pdbedit commands.
I cannot even run the pdbedit command itself.
So I have hit a dead end for the moment.

That is because you have to install it. http://www.cbs.dtu.dk/cgi-bin/nph-runsafe?man=pdbedit
pdbedit

Install Webmin.

Artman62 · 13 Oct 2018

So it turns out the issue lies in the user names for WORKGROUP and SAMBA. Over the years, NO ONE has updated the names in these two areas. So out of 14 computers connected to the server, there are only 4 usernames and passwords being used to connect. Most are using the admin username and password. The rest are people who have not worked there for over a decade.
It is just a mess! What I think needs to be done is make all new standard users on the Windows machines and then create these users with new passwords on the server.
But, not my call. So we just have to deal with this mess.

bro67 · 13 Oct 2018

Samba is set to work in a workgroup not a domain. Read Setting up Samba as a Domain Member - SambaWiki and ChapterÂ*4.Â*Using Samba for ActiveÂ*Directory Integration - Red Hat Customer Portal From there, I would suggest asking the business to pay for you to attend a Redhat Linux conference to learn about the in's and out of security with Linux in a Windows environment, along with getting them to hire on a consultant to help you straighten out the mess.