So i know this topic has been discussed. I found the bug report, and the numerous posts saying it is fixed. So maybe i'm just doing something wrong.
MY Freenas Box
8gb DDR3
Dual Core Intel Something
4x2TB WD Red
Gigabit nic
8gb sandisk flash drive
MY Hyper V Box
Server 2012 (Not R2)
SSD for os
4tb Mirror to play with
Dual 6212 Processors
72GB ram
Gigabit Nic
I built a freenas box just to test this. It is a RAID 10 of 2tb WD Red.
All the settings are default.
After setting up the share, i copied a VHD over to the share. When i attach it i get the classic message saying it cannot be done.
Digging around i noticed SMB 2.0 was the default max. I changed that to 3.0_00.
Same error.
If i change the minimum to 3.0, free nas is no longer accessible. Only when minimum is 2.x or below or 3.0_00 will it show freenas as being part of the network.
As you can see Server 2012 sees the SMB 3.0 protocol.
MY Freenas Box
8gb DDR3
Dual Core Intel Something
4x2TB WD Red
Gigabit nic
8gb sandisk flash drive
MY Hyper V Box
Server 2012 (Not R2)
SSD for os
4tb Mirror to play with
Dual 6212 Processors
72GB ram
Gigabit Nic
I built a freenas box just to test this. It is a RAID 10 of 2tb WD Red.
All the settings are default.
After setting up the share, i copied a VHD over to the share. When i attach it i get the classic message saying it cannot be done.
Digging around i noticed SMB 2.0 was the default max. I changed that to 3.0_00.
Same error.
If i change the minimum to 3.0, free nas is no longer accessible. Only when minimum is 2.x or below or 3.0_00 will it show freenas as being part of the network.
As you can see Server 2012 sees the SMB 3.0 protocol.