Connect to/from Windows network

My efforts so far to connect to Windows home network:

In reading how others have set up samba, etc, the main thing I'm learning is just how much I do NOT understand. I have a good Windows background, but I'm getting lost very quickly in Zorin-Land.

I have installed Zorin 17.2 Core to parallel boot on an old Win10 pc. I hope to make Zorin my main OS on half my pcs (Win 11 installed on the other 2) but I must be able to access my home network. I have not been successful.

Here's what I tried so far:

  1. I tried to join the Windows workgroup (named KUCHSPOT).

sudo nano /etc/samba/smb.conf
"First, edit the workgroup parameter in the [global] section of /etc/samba/smb.conf and change it to better match your environment:"

workgroup = KUCHSPOT

"...add"
[share]
comment = Zorin File Server Share
path = /srv/samba/share
browsable = yes
guest ok = yes
read only = no
create mask = 0755

"then in Terminal:"

  1. create the directory
    sudo mkdir -p /srv/samba/share
    sudo chown nobody:nogroup /srv/samba/share/

  2. restart Samba service to take effect
    sudo systemctl restart smbd.service nmbd.service


I am still not able to access any Windows pcs or the Zorin pc from either direction. I don't even see Zorin on my home network, although it does have an IP address.

  1. I went to Home-Public folder; Right click to share this folder; Allow others to create...; Guest access
    ...but I cannot access it...

  2. Someone's suggestion I followed:
    sudo apt install cifs-utils
    ...don't know why or what it does... didn't see that it did anything.

  3. I go to Other Locations in the File Manager. I click on Windows Network--after thinking for a minute, it finally returns "Folder is Empty."

Is it really this hard to connect Windows pcs with Zorin? I find I am lost when I read links to Ubuntu articles. Can someone lay it out clearly the necessary steps for me to take?

I'm not at home right now to test, so I can't test specifically, but do you have your firewall on and blocking things? This could be an issue that could be blocking you from seeing anything.

Here's an article that may help a bit, which states how to allow it if the firewall is enabled:
Sharing Files between Ubuntu 22.04 and Windows Systems with Samba – Answertopia

I did find the firewall settings. Incoming & Outgoing are both "Allow."

Does the firewall need to be told to give Samba access per the article you referenced?
ufw allow samba

I did discover that I did something right and can access one of my Win 11 pcs from Zorin, but not the other way round. Zorin cannot see the other computers on my network, but could connect with smb://ip address

I did a little digging and it appears there's a pretty well investigated post about this exact sort of issue in regards to TrueNAS (although it applies to other OSs as well):

It might be worth a read through that, it's quite well done. There's also another Ubuntu post that references it, and the script that corresponds with it:

This sounds exactly like what you're talking about, how you can't see them in network discovery but CAN see them if you manually connect.

1 Like

It's taking some time, but these articles are very informative. I'm learning that Windows is the problem, and I want to learn how to manage it...

I'm making progress. Today for the first time I saw my Zorin box on Network Neighborhood on Win11. BUT even though I set the workgroup in the smb.conf, it still shows as WORKGROUP on Win11, which is not the name of my workgroup. Therefore, I cannot access the Z-box.

Any suggestions besides the smb.conf that I might need to change the workgroup?

From recollection it should just be the smb.conf (/etc/samba/smb.conf) and then as you said, change workgroup = to yours (KUCHSPOT). Then save the file, and reboot the samba service :

sudo systemctl restart smbd

If you look in your smb.conf file, did it save the contents correctly after restarting the service? Sometimes something as simple as it not saving could possibly cause that. Could also post a shot of the config just to make sure of that as well.

Here's that line from smb.conf. Looks right to me.

I've restarted the samba service and also rebooted since then... also have rebooted Win11.

That's a weird one to me then, to be honest. I couldn't explain why it wouldn't want to given you've got that setup as far as I can tell correctly.

I'm unfortunately out of ideas at this point. Hopefully someone else has run into this and can give a possible fix to try.

Another strange quirk is that i CAN access a shared folder on Win11 from Zorin... just not from Win11 to Zorin.

I have set up a Mint VM on Hyper-v on Win11. I have the same issue there: smb.conf workgroup = KUCHSPOT.

Zorin machine sees and transfers with Mint, but neither with Win11. This is a major sticking point to being able to use Zorin (or Mint) on my home network. Linux is beating me up... or, perhaps it's really Windows and I just don't know it yet...

From the brief googling I had done, this seemed like it may actually be a windows issue more than a Linux one. Unfortunately I don't really have any windows shares or even VMs setup at the moment, so I can't even test.

I know my shares between multiple Linux machines works fine without much hastle, so my hunch is on the windows side. But I could be wrong on that front.

EDIT: If I get some time I'll take a look at spinning up a windows instance and see about it connecting to my existing stuff.

On my vm Mint, I just did two things:
I changed smb.conf for workgroup = KUCHSPOT2

and tried to install wsdd

apt install wsdd

I don't think I did wsdd correctly; BUT
I now see my whole network and I can access both my Win11 AND Win 10 AND Zorin...

but I cannot access either Linux box from Windows.

What forum can help on THIS ongoing challenge???

When in comes to WSDD, it requires some firewall setup:

Firewall Setup

Traffic for the following ports, directions and addresses must be allowed.

  • incoming and outgoing traffic to udp/3702 with multicast destination:
    • 239.255.255.250 for IPv4
    • ff02::c for IPv6
  • outgoing unicast traffic from udp/3702
  • incoming to tcp/5357

It then also defaults to the workgroup of WORKGROUP, you may need to manually change it as it shows here (as an example)

Example Usage

  • handle traffic on eth0 only, but only with IPv6 addresses

wsdd -i eth0 -6orwsdd --interface eth0 --ipv6only

  • set the Workgroup according to smb.conf and be verbose

SMB_GROUP=$(grep -i '^\s*workgroup\s*=' smb.conf | cut -f2 -d= | tr -d '[:blank:]')

wsdd -v -w $SMB_GROUP

The file location as far as I can tell should be located at :
/etc/default/wsdd

EDIT to add: Might need to enabled discovery with WSDD as well

Client / Discovery Operation Mode

This mode allows to search for other WSD-compatible devices.

  • -D, --discovery

I'm thinking more and more it's on the Windows side. I just opened my Win10Pro pc. On it's network, it can both see and access my Zorin box, no trouble at all.
(but it doesn't see the VM Mint; though Mint sees and accesses Win10)

Win10 also shows it is on a different workgroup than Zorin, which I'm beginning to think the workgroup is NOT the issue.

That is still my thought process, as well, that windows is doing some funny business and is making this harder than it needs to be (definitely not a recurring theme in life lol).

I've begun my research with Windows. Seems Win11 Pro (which I have) has been having problems since some of the latest updates. I'll post here if/when I figure it out.

1 Like

Take a look here about forcing SMB3:

I successfully can see Zorin from Win11Pro.

On Accessing third-party NAS with SMB in Windows 11 24H2 may fail | Windows 11 Forum
I believe these 2 steps changed my ability to access Zorin:

Because I have used Windows for so long, and Linux is strange to me, I initially assumed it must be the fault of the "Unknown." But then, Win11 is pretty unknown, too, and so much is hidden out of sight from users. Crazy stuff.

I will consider this SOLVED.

2 Likes

Glad you've got a solution figured out, I marked your post as the solution for now. Feel free to let us know if it needs changing if something else happens in the future.

Hopefully this helps someone else with the same problem in the future :slight_smile: