Hi,

since last week after the wannacry virus/worm/whatever fixes I have not been able to connect to the windows shares/printers at work.

 

Both nautilus and dolphin would return an immediate "Server timeout" when connecting to those.

 

Running from the command line, as root:

 

# mount.cifs <windows_share> <local_mount_point> -o ...

 

failed with the following message:

 

Host is down.

 

 

Searching for this message I found:

 

https://serverfault.com/questions/414074/mount-cifs-host-is-down

 

That suggests in the first message that the culprit is that after the last Microsoft patches SMB1 has been disabled. I remember to have read the same at Ars Techica.

 

Following the tip there I run the same command as

 

# mount.cifs <windows_share> <local_mount_point> -o vers=2.0,...

 

the only change was to pass the option vers=2.0 to use SMB2.

 

Now this version succeeds where the previous fails, and what is better part is that as long as this is mounted any call to smb shares in dolphin or nautilus works even for other shares on different machines, but on the same workgroup, not necessarily the same as the one mounted in the command line.

 

I am running an up to date F26, and I would like to have version 2.0 of SMB set as the default for the smb clients. Where should I change this?

 

It would be nice for me to understand why the calls to smb works after the mount.cifs although I am quite happy that this happens.

 

Regards,

--

José Abílio