29A4, 8CD0, FB75, 4D11, D463, 4E49, 2BB9, AEBD, 4DCF, B235, 5CB1, 3B13

2EAA, CA92, F29D, BB9C, 17E9, 50A2, 507D, 1A2B, 56C9, F614, 879B, 1341

1D3F, 22D8, A6B4, B5DE, 13B6, 57DB, 2698, 2EDA, 3693, F762, 25B9, D15F

4315, 6FE1, 7A9E, 7DBA, E639, DD44, 1E7B, 746B, 7158, CF6D, 6EAA, F7EA

CBF5, 45D7, 3E7B, 8287, F27B, 55FF, 47A0, 4143, 2AD3, 1EA9, 8761, 9375

310C, 7CEE, A812, 1914, BFB7, 4BDB, 435A, CDF3, CB9E, 941D, F496, F1E7

6C80, 42B4, 9E55, 566C, EBAD, 4BC0, 8944, 3942, 86E3, BEA8, A682, 127F

9E56, B5A5, 3391, 59D5, DF61, F7C0, 93B6, CCF3, D1B7, A534, 1FEB, 21DC

BAAF, 5DB0, 158D, 8943, 94DA, 9779, 419F, DAC0, 8C93, D2A4, EB9B, 157A

2956, 3287, 1D05, 58A8, 2728, 9CB3, BAD0, 44BE, 455D, 9F15, FD34, 5AF1

83DA, 1CF4, FC00, 4B4F, F363, B79E, 56E3, 5ED3, 21D7, CE07, AE0C, 32FE

29BB, E5CD, 1C05, 8447, 8928, 293C, 4E21, FABC, 82F2, C453, E773, B7D7

59A5, 64C0, F210, 9AAE, FD61, E017, 934A, 12A0, B8C0, 2201, 38F2, 9456

83DD, E52B, F3C8, 19A3, 3D1B, E415, 8799, E568, A382, 6FD7, CDAD, D8DC

F01A, D946, CA52, 53F4, 6C80, 343B, 4683, F097, A489, 94F3, 21D2, 3A81

↑↑↑ THAT’S ↑↑↑ MY short ANSWER

Finally I can access from Windows station to the shared folder (Ubuntu). Great. But the same windows user on other machine has no access to the folder: permissions.

Yet another user from other windows machine has no access too. All these machines are in the same LAN.

That is changed part of my smb.conf

[media] path = /home/xlg/media browsable = yes writable = yes read only = no #valid users = xlg force user = xlg #guest ok = yes
[storm] path = /media/xlg$ cd 36c437d7-81a3-4461-bd61-3b5c892f7cfe/storm #browsable = yes #writable = yes read only = no #valid users = xlg force user = xlg guest ok = Yes

What to check and fix?

correction:

Its 2023 AND people still uses the faulty windows…

Thats right STEVE but.. I would advise do not WASTE your time trying to explain REASONS to any microsoft user who because it doesn’t understand TECHNICAL ISSUES it have been using the WRONG OS aka WINDOWS all his live instead of just using LINUX. Period!

Its 2023 an people still uses the faulty windows and then blame Linux for the bugs and issues caused by that BillyGatezz codeFrankenstein called windows

🙁

Well.. you could “ask” him to get out of the faulty microsoftVerse

🙂

Maybe if Microsoft creators could learn to code correctly you wouldn’t have this faultyVerse issues

Not even Linus Torvalds can save mr. BillyGatezz frrom each new bug in the Microsoft Windows FaultyVerse

Just ADD to your “smb.conf” those 5 LINES that I mentioned above to make the config. changes PERMANENT between reboots

Yes, you’re right, you’re in the Faulty MicrosoftVerse where even a simple SAMBA shared folder can’t work well.

Don’t blame the penguin.

The curious thing here is that in a network 2 LinuxPCs connect without trouble but a windowsPC and a LinuxPC don’t.

And I wonder what OS could be the faulty one?

Hint: starts with W

Anyone who uses the wrong OS a.k.a. “Windows” always have that FRUSTRATION when meet the right OS, Linux, and try to connect both.

That is like trying to mix oil and water.

Just open as ROOT your “/etc/samba/smb.conf” file then ADD the following 5 LINES at the end and then automagically you will have available your SHARED FOLDER each time your LINUX starts, and thats all:

[myShareName]
  path = /media/myUserName/myPartitionName/mySharedFolder
  read only = no
  force user = myUserName
  guest ok = yes

Nobody is asking you to do anything. If you can’t follow this guide, go make your own GUI, because no proper GUI exists.

These guide half working. If I connect linux -> linux using smb://host_ip/share_name linux connect with no problem. But if I try connect linux -> windows, windows say “cannot access”

The above guide DOES NOT work.

It is a Linux problem. The above guide works. Until you reboot the OS. All shared folders and mounts will disappear on reboot and you will have to redo them. Has been a problem for ages and can only be circumvented by ugly workarounds.