Suddenly cannot scan - Server connection error

[Elmojo]

SOLVED: If you happen to be running an unraid server, note that NETBIOS and SMBv1 are the same thing. You must enabled NETBIOS, or scans to a shared folder will not work. This may be in issue for those on other systems as well, especially any Linux or otherwise *nix-based platform.

Ok, this is weird. My K-M 364e is hardwired to my LAN, and accepts print jobs without issue.
Beginning yesterday, it is suddenly unable to scan to the shared folder on my unraid server. It's been scanning to this folder for a couple years now, and nothing has changed on either the server or copier, to my knowledge. I have done no server updates, beyond regular docker and plugin updates, and I don't think any of those were SMB/sharing related.
I can access the shared folder without problem from my Windows desktop.
I can ping the copier from my desktop, and I can log into the copier's web GUI, so I know it has good connectivity.
I can print to the copier, no problem.
I've tried setting up an FTP destination on the copier, pointing to the same shared folder on the server, but it just says "no specified folder", even though I do have the folder entered into the destination path.

Anyone have any clue what would cause this sort of network blindness? It's so odd to me that it would just suddenly forget how to scan. lol
I've fully rebooted both the server and copier, with no improvement.
Here are the SMB settings. Remember that these were working fine until yesterday:
364e SMB Setting.jpg

[tsbservice]

Time to get something more modern as this good but old model now starts to experience problems with modern security settings.
Smb1 is enabled?

[Elmojo]

I wish, but that's not in the budget right now.
I don't think there's really any security settings in the way. At least nothing I'm aware of. Remember that this is interfacing with a shared folder on an unraid server, not a Windows PC. Other than basic user/password authentication, I don't have any additional internal network security in place. It's one of the reasons I specifically chose NOT to run a Windows-based server.
SMB1 is enabled on the copier, if that's what your asking. I think it's set to SMBv1/v2.
I'm not 100% sure how to check that on the server. I'll look. Does the copier require v1? I assumed that since it had a toggle for v1 or v1/v2, that it supported both.
This is what my SMB settings look like. See any problems?
cap 001.jpg cap 003.jpg

[Elmojo]

I found the problem!! It was indeed SMBv1. I had no idea that NETBIOS and SMBv1 were the same thing. I was making config changes to my server a while back, one of the recommended settings was to disable NETBIOS. I guess I just haven't scanned anything since then. I also never really thought much about it, since the 364e appears to support SMBv2. Does it not really?

[Duplicator]

I wish, but that's not in the budget right now.
I don't think there's really any security settings in the way. At least nothing I'm aware of. Remember that this is interfacing with a shared folder on an unraid server, not a Windows PC. Other than basic user/password authentication, I don't have any additional internal network security in place. It's one of the reasons I specifically chose NOT to run a Windows-based server.
SMB1 is enabled on the copier, if that's what your asking. I think it's set to SMBv1/v2.
I'm not 100% sure how to check that on the server. I'll look. Does the copier require v1? I assumed that since it had a toggle for v1 or v1/v2, that it supported both.
This is what my SMB settings look like. See any problems?
cap 001.jpg cap 003.jpg

Set that SMB authentication setting to Kerberos/NTLM v1/v2 and let your SMB server control the minimums.

I found the problem!! It was indeed SMBv1. I had no idea that NETBIOS and SMBv1 were the same thing. I was making config changes to my server a while back, one of the recommended settings was to disable NETBIOS. I guess I just haven't scanned anything since then. I also never really thought much about it, since the 364e appears to support SMBv2. Does it not really?

It has to be updated to a firmware that supports SMB v2. The older firmwares do not. The 4e machines need GDB-M1/GDS-M1 or newer to support SMBv2 with function version 7.

SMBv1 has some quite severe vulnerabilities. I recommend updating the copier and disabling SMBv1 if possible.