Haven't been able to get SMB working at all.  Based on all the other posts I presumed it was Win10 SMB shenanigans, but when I do a pcap I see the server (10.0.99.30) just blast RST packets on a SYN from the client (10.0.30.250).  Set up a credentialed user in Win10, made sure firewall rules allowed coms (this is evident in that the server is blasting RST packets instead of just timing out, but checked anyway), and tried both flipping to private/secure/public and re-applying along with Tools -> New Permissions -> Shares - Storage / apply which had fixed for others.  Also reset the smb user password to be sure.

 

Can't help but think I misconfigured something but I can't think of what.  The server is obviously rejecting the TCP handshake on ports 139 and 445.  For the record i've never been able to get this to work, I was focused on my linux servers getting their NFS stuff working which hasn't been a problem, only smb.

tower-diagnostics-20240114-1336.zip

Well, apparently I needed to embarass myself here first to figure out the problem.  

 

I trunked and vlan'd my interfaces and after posting here I remembered I set SMB to not listen on the main interface but the br1.10 (10.0.10.250) interface so of course it was going to reject connections on 10.0.99.30; to make it worse I had typo'd br1.20 instead of br1.10 so when I remembered I forced the subinterface to handle the smb connections it still didn't work until I corrected that.

 

TL;DR:  I am at times, an idiot.

 

SMB config that was the culprit:

bind interfaces only =  yes
interfaces = lo br1.10