asked on
Windows Server 2016 gets "System error 58 has occurred" when I use the" net use" connect to another server
I upgraded from Windows Server 2012 R2 to Windows Server 2016. Now I get "System error 58 has occurred" when I use the" net use" command to connect to a SUSE server. The SMB 1.0 is already enabled on the 2016 server, but it still fails to connect. I need to be able to read\write\execute to the same servers as I did with my Server 2012.
Is there any way to get my 2016 server to use SMB1.0 to connect? If not, is there a workaround I can use to perform the same task without updated my SUSE servers?
Is there any way to get my 2016 server to use SMB1.0 to connect? If not, is there a workaround I can use to perform the same task without updated my SUSE servers?
Windows OSWindows 10AzureWindows Server 2012Windows Server 2016
Last Comment
rich brown
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Thanks all.
The server I'm trying to connect to are more likely running older versions of Linux, Samba, or other types of third-party software to provide SMB services. Often, these versions of Linux and Samba are, themselves, no longer supported.
Is there a workaround that does not include getting the server I am trying to connect to make an update on their end? Is there something other than SMB I can use that operates the same way as SMB?