Windows can see share, cannot access it [Solved]

[timkb4cq]

While there are issues where the QSI doesn't matter, in a majority of cases it helps us volunteers quickly diagnose the cause of the problem. It's not always obvious to the user with the problem why this is so, but the request is not just officious "rule following". We created QSI so we could avoid long threads of digging out information bit by bit - and it has worked well for that.
Remember this is volunteer community support.

[j2mcgreg]

We need your computer’s complete profile before we can proceed, so you need to post the output from the QSI utility. The Quick System Info (QSI) utility is located in MX Tools and its output is automatically formatted for use here in the forum. Run the QSI utility, click “Copy for Forum” at the bottom and then just paste it here in your thread.
Forum Rules

More officious nonsense, I see.

Looks like MX Linux is the wrong distro for me

From our rules which you tacitly agreed to when you joined our forums:

Help requests must include information about the computer's system and hardware. The best way to do this in MX Linux is to run the Quick System Info (QSI) utility found in the main menu or in MX Tools. antiX users may run inxi -Fxxxrza in a terminal.

The full rule set can be found here:
viewtopic.php?p=255061#p255061

[x-user]

While there are issues where the QSI doesn't matter, in a majority of cases it helps us volunteers quickly diagnose the cause of the problem.

Hand om heart, do you seriously believe there is any chance that info would help to troubleshoot a Samba configuration issue?

Regardless I remain firmly of the opinion that in light of the foregoing history of this thread, the reference to following the rules was snide trolling. Appreciate the volunteer aspect, but given that I would have thought they would have better things to do than play little power trip games. I know I do

[FullScale4Me]

Now that we have agreed to disagree can we get to 1-3 now?

4 is just a small piece of the puzzle!

MX samba config reports everything working fine, and windows can see the share but can not access it. Was fine but stopped working a few months ago. Any ideas?

Edit: Have added the wsdd package but did not fix

1) Expand on cannot access it.

2) Does your share show up and is accessible via MX Linux File Manager.

3) Is there a firewall enabled on either PC?

4) WSDD is what makes the MX Linux share visible on Windows. Is the Linux share seen in Windows File Manager?

Typing in terminal: 'sudo service wsdd status' should result in: '/usr/sbin/wsdd is running.' response.

5) Has the shared folder's owner been given a password in Samba Config?

Password-less IDs on either end have been known to cause Samba difficulties.

[CharlesV]

It is truly very simple... if you ask for help from a community then you should be willing to help them help you.

If your not, then you really shouldnt expect any help. ( why would anyone? )

As Tim pointed out, your QSI tells a story - what Kernel you have (yes that CAN matter), what version of software your running (AGAIN, YES that CAN matter) .. What repo's your using - also CAN tell A LOT.

Being snarky is about the best method to getting your butt kicked. Have respect! If you dont wish too.. .then yes.. some other forum should be your choice!

[x-user]

It is truly very simple... if you ask for help from a community then you should be willing to help them help you.

If your not, then you really shouldnt expect any help. ( why would anyone? )

As Tim pointed out, your QSI tells a story - what Kernel you have (yes that CAN matter), what version of software your running (AGAIN, YES that CAN matter) .. What repo's your using - also CAN tell A LOT.

Being snarky is about the best method to getting your butt kicked. Have respect! If you dont wish too.. .then yes.. some other forum should be your choice!

As I mentioned over the fact that Samba appeared to have been very well implemented was one of the things that initially attracted me to MX Linux. But it appears your black box solution is currently broken. That is a borderline deal breaker for me, and I frankly would much prefer to address the problems that creates for me than get into cock waving contests with you guys

[CharlesV]

Samba on MX 21 ( or 19) works perfect for me ( 6 machines, various hardware, windows 10 and 11) as well as many other people.

No wsdd

If you really want help, instead of waving your own attitude around, then lose the attitude, answer questions asked and provide information what could help.

[FullScale4Me]

Questions 1 thru 3 have answers below. When you are ready to stop waving.....4 posts above this if you need a refresher.

MX Linux and Windows file sharing - How To

[x-user]

Was a ufw permission issue, and I certainly don't recall deleting any rules fwiw

[x-user]

and the other thing I noticed is that the mx-samba config utility does not appear to write anything to smb.conf. That would seem to imply it is not used, in which case maybe you should perhaps consider removing or concealing it to avoid anything going wrong there