Issue: Unable to map the network drive via SDWAN from Windows 10 Clients
book
Article ID: CTX233073
calendar_today
Updated On:
Description
Symptoms:
– Below Errors might be seen when Client at Branch office tries to map the Network Drives from Win 10 machines.
Errors:
– SMB3 acceleration is disabled/unsupported on the partner unit
– Signed Session. Reason: Secure Connection to the peer unit does not exist. To configure secure partner settings. Go to 'Configuration - > Secure partners'.
Resolution
Below are the possible solution/workaround for this issue:
– Protocol version between Win 10 to Win 2016 is SMB 3.1 which we don’t support at present
– However, we should not block the connection and the same is being tracked through an internal bug and planning to address in the upcoming release(s).
– For now, as a workaround, you can exclude the particular client or server from acceleration, go to CIFS service class and exclude that client or server from acceleration.
Problem Cause
Protocol version between Win 10 to Win 2016 is SMB 3.1 which we don’t support at present
Issue/Introduction
Description:
There is no issue reported from Windows 7 machines.
There are few network drives which gets mapped and the difference between the working and non-working drives is:
– Non-working one is mapped via AD and it is the users home drive property
– Working one are mapped via group policy.
Server details are:
All the drives are served from the same server 2016 datacenter edition configuration.
Was this article helpful?
thumb_up
Yes
thumb_down
No