MX Linux Forum

Sorry to jump on this thread but have same problem.

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

x-user wrote: Mon Jun 19, 2023 4:02 am 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.

Many thanks.

WSDD service is running.

But i am using passwordless anonymous sharing. Any possible fixes

Please start your own thread for your own problems next time, instead of tacking on to other people's.

Thread split to make your own topic @x-user

Eadwine Rose wrote: Mon Jun 19, 2023 4:22 am Please start your own thread for your own problems next time, instead of tacking on to other people's.

Thread split to make your own topic @x-user

Why on earth is that so important to you?

An old thread, not used for months, and my problem exactly identical? My God you're pedantic

Please read the Forum rules.

I will highlight: "Do not reply to others' existing topics to ask for help nor post multiple issues in one topic. Start a new topic for each issue. This helps to avoid confusion and chaos."

Well thanks so much, we now have a fully forum rules compliant thread

that the flow of good support/debugging assistance I *was* receiving has gone down the drain, is i'm sure in your view not important

1) so I deleted my anonymous no password shares, and created a password share => the mxshare vanished in windows (could see them previously)

2) Set up another anonymous password less share in Thunar => The mxshare was back in windows, but same old inability to access


I find this really very disappointing. The fact that Samba shares worked in MX without having to manually edit smb.conf was one of its attractions in the first place. Does anybody know if there is anything that can be achieved going that route?

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

j2mcgreg wrote: Mon Jun 19, 2023 10:14 am 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

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.

x-user wrote: Mon Jun 19, 2023 10:17 am

j2mcgreg wrote: Mon Jun 19, 2023 10:14 am 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

timkb4cq wrote: Mon Jun 19, 2023 12:52 pm 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

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

4 is just a small piece of the puzzle!

FullScale4Me wrote: Mon Jun 19, 2023 4:12 am

x-user wrote: Mon Jun 19, 2023 4:02 am 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.

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!

CharlesV wrote: Mon Jun 19, 2023 1:57 pm 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

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.

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

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

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

x-user wrote: Thu Jun 22, 2023 11:27 am 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

The MX-Samba config utility in its help file mentions the share configurations are stored elsewhere.

The /etc/samba/smb.config file is used by most of the core Samba utilities supplied by Samba.org for the running of the Samba services.

There is ZERO reason since the MX-Samba config utility was created for 99% of MX end users to edit that file. There are a few old device exceptions for editing it in that one percent, a few end up there after reading internet documents focused on other distros.

Editing smb.config almost always gives a SLOWER and MUCH less secure Samba (by not using Samba 2.x or Samba 3.x). In a few cases in recent threads here it totally broke Samba, even though "testparm" was happy to say all was OK.

Wow! Didn't take CharlesV long to start waving his new powers around.

nomad wrote: Thu Jun 22, 2023 6:55 pm Wow! Didn't take CharlesV long to start waving his new powers around.

What didn't take long to show up was the OP's bad attitude. I am often impressed with the patience of the advisers on this forum.

ditto

As this issue is solved I am throwing the lock on this topic. If the issue is not solved in hindsight, OP can send me a pm asking me to reopen.

Since @Eadwine Rose has seen fit to lock my earlier thread no doubt having seen me logged in drafting a response to @Antediluvian here it is:

Attitude is in the eye of the beholder, my new interjecting friend.

What is an objective fact is that the system info would have contributed diddly squat to debugging the ufw issue. Also that in searching threads for other problems I certainly didn't see the system info having been proffered or demanded; one attitude for all seemingly not the custom here.

While I'm at it, let me add that a big part of the reason for my gripe was the forum practice of confining support threads to one issue per user, which I will in the interests of refraining from pejorative language confine myself to describing as suboptimal.

The atomisation of debugging support creates a universe of similarly themed and unsearchable support threads and ensures there is a fragmentation of support. As I see it that simply makes forum threads unusable for the majority of users and creates much more unnecessary work for mods and those trying to help. Very, very suboptimal

Topics merged, we do not open new topics when one has been locked. You could have asked to reopen.

Thank you for your input on the forum mechanics issues.

As your problem has been solved, from what I can see in your writing, I am relocking this topic.