S
StinsmanJ
So we are setting up a new backup software at two locations.
The First Location has Windows Server 2012 R2 and a Lenovo PX4-400r NAS Unit.
The Second Location has Windows Server 2012 and a Lenovo PX4-400r NAS Unit.
The First Location the VM is installed in Hyper-V and the VHDX mounted on the NAS, everything boots and work fine.
The Second Location The VM is installed in Hyper-V and the VHDX Mounted on the NAS, but the VM Fails to boot. When the Event log is checked it gives the reason for the error as "Remote SMB share does not support resiliency."
Upon researching this error it seems to indicate that the Windows Server 2012 machine think the Lenovo NAS does not support SMB 3.00+
So I fired up Powershell as Administrator on Both Machines and ran the Get-SMBConnection Command which returned some very peculiar results.
The First Machine (The one that works) States that the Windows Server 2012 R2 Machine is communicating with the Lenovo NAS Using SMB Dialect 1.50?
The Second Machine (The one that does not boot) States that the Windows Server 2012 Machine is communicating with the Lenovo NAS Using SMB Dialect 3.02.
So it would appear that the "Remote Share" does indeed support resiliency but for some reason the Hyper-V in Server 2012 Thinks otherwise.
Has this behavior been seen before? Is there a resolution to the situation or was it resolved in some feature upgrade in Windows Server 2012 R2 that is not Available in Windows Server 2012?
Edit: Spelling.
Continue reading...
The First Location has Windows Server 2012 R2 and a Lenovo PX4-400r NAS Unit.
The Second Location has Windows Server 2012 and a Lenovo PX4-400r NAS Unit.
The First Location the VM is installed in Hyper-V and the VHDX mounted on the NAS, everything boots and work fine.
The Second Location The VM is installed in Hyper-V and the VHDX Mounted on the NAS, but the VM Fails to boot. When the Event log is checked it gives the reason for the error as "Remote SMB share does not support resiliency."
Upon researching this error it seems to indicate that the Windows Server 2012 machine think the Lenovo NAS does not support SMB 3.00+
So I fired up Powershell as Administrator on Both Machines and ran the Get-SMBConnection Command which returned some very peculiar results.
The First Machine (The one that works) States that the Windows Server 2012 R2 Machine is communicating with the Lenovo NAS Using SMB Dialect 1.50?
The Second Machine (The one that does not boot) States that the Windows Server 2012 Machine is communicating with the Lenovo NAS Using SMB Dialect 3.02.
So it would appear that the "Remote Share" does indeed support resiliency but for some reason the Hyper-V in Server 2012 Thinks otherwise.
Has this behavior been seen before? Is there a resolution to the situation or was it resolved in some feature upgrade in Windows Server 2012 R2 that is not Available in Windows Server 2012?
Edit: Spelling.
Continue reading...