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?
rich brownAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Iradat SiddiquiManager OperationsCommented:
SMB 1.0 is not available by default in Windows Server 2016 and you may go to Server Manager >Manage>Add Role and Features> Select "SMB 1.0 /CIFS File sharing Supporting" under features and install it.
DevAdminSystem Engineer | .NET Developer | Microsoft MVP | Technical SpeakerCommented:
But you have this error on client that access to the share on Windows Server 2016 really?
On the client you have enable SMB1?
https://support.microsoft.com/en-us/help/4034314/smbv1-is-not-installed-by-default-in-windows

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
rich brownAuthor Commented:
These devices are not likely running Windows. They 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.

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?
Shaun VermaakTechnical SpecialistCommented:
The SMB 1.0 is already enabled on the 2016 server, but it still fails to connect.
Enabling it and recommending you enable it is really a bad idea. Fix it so that it does not rely on SMB1
rich brownAuthor Commented:
Thanks all.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2016

From novice to tech pro — start learning today.