Windows 10: I can't get Win10 PC to Access Ubuntu 18.10 Samba Shares

Actually, I don't know if I have a Windows problem or a Ubuntu problem here.

I've been using a Ubuntu server for years accessing it with Windows computers with no problems. Then I upgraded to Ubuntu 18.10
I'm trying to share several folders from my Ubuntu server with my Win10 machines. Three of my four PCs are running Win10 ver 1809 and one is running ver 1803.
Two of my vers 1809s can access and write to the Ubuntu's Samba Shares perfectly, no problemo. One of the vers 1809 can see the shares, but cannot access them. Neither can the vers 1803. However, just to make things more confusing, of the multitude of Samba shares that I've created during this whole head-banging experience, all 4 of the Win10 PCs can access one of the Samba Shares.
Of the two PCs that are not having difficulty, one has SMB 1.0/CIFS checked and one does not. The 1803 has it checked.
I have tried turning off the Windows firewall.


Do I have a windows problem or a Ubuntu problem?

Where do I go from here? I am open to any suggestions.

Thank you in advance for any help.
John H

:)

 

Sharing folder in Ubuntu system to Win10 PC

I've been going through just about every guide I can find on how to setup a shared network connection between my Ubuntu install on my laptop and my main Win10 PC.
I've gotten to the point where the Ubuntu system can see my Win10 machine in Networks. But not the other way around.

In Ubuntu, I've configured Samba to connect to the same workgroup as my PC is set to. And I've enabled Share on the folders in Ubuntu that I want to access on Windows. And given that the Windows machine is visible on the laptop, I assume that the issue lies on Windows for not finding the Ubuntu connection? Not sure..

Anyway, on the Windows machine I've enabled every network share option available: "Allow network sharing on public domains", "Allow filetransfer on ... etc".
And I've enabled the 'File & Printer Share' rule for public domains in Windows Firewall. (Both outgoing and incoming).

And still, my Ubuntu machine doesn't pop up in the networks list in Windows.

Thanks in advance! (Hope the info included is enough)

EDIT:
As commented, my question got a bit messy along the way it seems. To clarify:
I'm not prone to any specific "method", all I wish to achieve is to be able to Read/Write from/to; a folder on my laptop(Ubuntu), from the comfort of my Windows PC in the easiest way possible.
Why I meantioned Samba was because one of the many guides I read suggested using that, though I guess I didn't manage to follow it correctly. And other terminology meantioned that might be off is simply caused by my novice abilities. (shared network etc..).

The one I caught as being the simplest method was to just enable "Share" on the folder(s) in Ubuntu and access them from the Networks List in Windows.

 

Windows 10 Pro no longer connects to Samba Share on Linux Workstation

Hello Simon,

To better assist you, kindly provide the following information:

• What version of Samba Share are you using?
• What troubleshooting steps have your done so far?

We look forward to your response.

Thank you.

 

Windows 10 having trouble access samba shared with upper case name

I have several windows 10 computer on the LAN and a linux file server with a samba share. On two laptops, when I open the file explorer, it list all the computers on the network, including the samba server, all in upper case, both on the left hand side
panel and also in the top right side 'Computers' section.

When I click these computer names, most of them work as expected, asks credential and then let me access shared drive. Only on the samba server, when I click on it's name, it always shows an error message: "Windows cannot access \\SERVER" where server is
the name of the samba server. In the details box, it shows an error code '0x80070035', the network path was not found.

But, if I type \\SERVER (in upper or lower case) into the address bar in the file explorer, it works as expected, shows me all the shared contents from the server. And also, after this initial connection, clicking on the upper case SERVER name on the left
side panel works.