1709 and SMB1 Issue from only 1 Server

[ITGURU]

i updated my workstation to Windows 10 1709 release (clean install) and found out that 1 server (2012 r2) will no longer access the client via UNC path by DNS name, or IP address

All other servers including other 2012 R2 servers will access the 1709 client without any issues.

 

Looking at the 1709 update details i discovered SMB1 is disabled by default so I ran powershell and enabled SMB1 and rebooted the client.

 

The 2012 r2 server which couldnt access the 1709 client before CAN now..

 

Why would this particular server only be trying to connect to the 1709 client via SMB1 where as all other 2012 servers will connect to it with SMB1 disabled on the client.

 

PLease could anyone shed any light on this?

 

Thanks

 

For some odd reason, running get-smbconnection from the problematic server with SMB1 enabled on the WIndows PC it is conncting at version 1.50

However, if i leave SMB1 enabled on the windows 10 client and run get-smbconnection from another 2012 r2 server it is using version 3.02

 

For some reason the problematic server only seems to want to connect at 1.5 so when it's disabled that server is the only one which will not connect.

Edited November 25, 2017 by ITGURU

[ITGURU]

Finally Resolved this myself! Just not sure why I had one server that did't have SMB2 and 3 configured - despite it being enabled via powershell, i had to run the commands to change the lanmanworkstation dependancies.

 

Noticed in the Event viewer for Microsoft > SMB Client, the following error:

 

The SMB 3 and SMB 2 driver is not configured with the default start type.

 

Default Start Type: DEMAND_START

Configured Start Type: DISABLED

 

Guidance:

You should expect this event when disabling SMB2/SMB3 for the client using SC.EXE or editing the Windows registry. Microsoft does not recommend disabling SMB2/SMB3. Disabling SMB2/SMB3 prevents use of features such as SMB Transparent Failover, SMB Scale Out, SMB Multichannel, SMB Direct (RDMA), SMB Encryption, VSS for SMB file shares, and SMB Directory Leasing. SMB provides alternative troubleshooting workarounds to disabling SMB2/SMB3 in most cases.

 

Therefore, i ran the commands:

 

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

sc.exe config mrxsmb20 start= auto

 

Rebooted the server and bingo, could access the windows 10 creators fall Pc with SMB 1 disabled!