A common thread in my googling that error number and message is issues with security software and/or firewall. Some people also resolve it by enabling NetBIOS over TCP/IP.
I think that is enables but I will double check tonight.
A common thread in my googling that error number and message is issues with security software and/or firewall. Some people also resolve it by enabling NetBIOS over TCP/IP.
I was having this issue as well. If I recall correctly, I think unchecking the 'apply default permissions" option in the CIFS share settings did the trick for me. I can't be certain this will work for you, but maybe it's worth a shot?
On the FreeNAS account, for your user account, is the "disable password login" box checked? If so, that will need to be unchecked - see this page http://doc.freenas.org/9.3/freenas_account.html.
In Services, does the CIFS service show that's it on?
Can you check to see if 1) your workstation is connecting ok and 2) your FreeNAS is supporting CIFS? In each command, there's a pipe command, which is usually found just above the Enter key.
1) Open a command prompt (start / cmd)
Type in the below command and let it run. Then try and connect to the share again. If you see SYN_SENT, either the service isn't running on FreeNAS or there's a firewall on your workstation, between you and FreeNAS, or on FreeNAS. If you see ESTABLISHED, then things should be good.
netstat -an -t 1 | findstr 192.168.1.45:445
Replace the above IP with your server IP, but from what I remember, it was 1.45.
2) From FreeNAS, open a shell (bottom left if you're on the latest version). Type in the below command. You should see a line that has "tcp4 --- *.445 --- LISTEN". If not, your CIFS service isn't running. You should also see the connection from your workstation IP.
netstat -an | grep 445
Please excuse the obvious question, but have you tried disabling all security software and firewalls on the PCs?
Is your existing Windows server still on the same network? If so, have you tried shutting it down?
I find it hard to believe at this stage that the problem lies at the FreeNAS end.