Windows 10: Can't write to Unix CIF shares

I have a Freenas Server (based on FreeBSD Unix) connected to my network. I can't get it to show up in file explorer untill I type "//000.000.000.000" (it's IP address). When I try to drag a file to the window CIF shares (Permissions in Unix are Allow Guest Access and Recursively set sane default windows permissions on share) I get the error "You Need Permission to Perform this Action". Both of these features worked on Win 7 Pro before I did an upgrade to Win 10 Pro. I also did a fresh install of Win 10 Pro and it made no difference so I restored a Macrium image of the Win10 Pro Upgrade.

:)

 

Wanna Cry Ransomware : Update 5/21/2017 FIX

Hi,

The Difference between CIFS and SMB.

SMB :

SMB stands for "Server Message Block." It's a file sharing protocol that was invented by IBM and has been around since the mid-eighties. It was designed to allow computers to read and write files to a remote host over a local area network (LAN). The directories
on the remote hosts made available via SMB are called "shares."

CIFS:

CIFS stands for "Common Internet File System." CIFS is a dialect of SMB. That is, CIFS is a particular implementation of the Server Message Block protocol, created by Microsoft.

So what’s the difference?

Most people, when they use either SMB or CIFS, are talking about the same exact thing. The two are interchangeable not only in discussion, but also in application – i.e., a client speaking CIFS can talk to a server speaking SMB and vice versa. Why? Because
CIFS is a form of SMB.

 

Windows 10 and Server 2003

You should update your unsupported server.

To get your laptops to connect, you need to enable the insecure SMB1 on the laptops.

Control Panel

Programs and Features

Turn Windows features on or off

SMB 1.0/CIFS File Sharing Support

Uncheck SMB 1.0/CIFS Automatic Removal

Check SMB 1.0/CIFS Client

Check SMB 1.0/CIFS Server (only if you need to see Win10 shares from an old OS)

You should update your unsupported server.

 

Other directories in the windows from other CIF shares asked me for a user name and password. So I entered the Freenas username and pw. After doing that I was able to write to the CIF share in question that didn't ask for a username/pw. Not sure what happened.

 

Do you have a user account set up on your NAS? You should do so using the same username\password as you used for your Windows 10 account. This should allow access without the need for Credential Authentication.

 

Linux and Unix uses Samba not CIF. You need to go back through your Freenas settings and also do the following on the Windows machines as an administrator in Powershell:

sc.exe config lanmanworkstation depend=bowser/mrxsmb10/nsi

sc.exe config mrxsmb20 start= disabled

You also have to flush the DNS and reset Winsock to get it to work, then reboot the Windows computers and it should work at that point.

 

Freenas is based on FreeBSD and it uses CIF. I'm sure your correct about Linx and Unix. Here is a picture from my web interface.



The SC.exe command is run from a command prompt on my windows machine?
What does it do?
Is that still correct for a CIF share?

 

Windows uses CIFS. Linux and Unix use Samba to communicate with Windows servers and workstations.

CIFS is Microsoft's way of communicating with Linux and Unix servers.

Common Internet File System

 

PROBLEM - Unable to access CIFS shares on Windows 10 | FreeNAS Community

 

Unable to access FreeNAS cifs share from Windows 2003(R2) | FreeNAS Community

 

Creating a FreeNAS CIFS/SMB Share