SMB share from RHEL access issues ...
-
We're installing an inventory management system and the vendor is using a RHEL server. They have installed a Samba share to put client installation files to install on windows machines.
I'm not having any issues on a Windows 7 machine but the Windows 10 machines are not able to see the share. It does not allow access. I'm thinking this is some kind of SMB version issue but I'm not familiar with Samba shares from Linux so not 100% sure. I did enable SMB v1 on the windows 10 clients thinking that would be necessary but that did not have any effect.
Does anyone know of anything I could check on the Windows clients so that I can see the share?
Thanks
-
You need to find out if the server is supplying SMBv1 or SMBv2, if your Windows 10 clients are using SMBv2 and have SMBv1 disabled they won't be able to connect.
I suspect that the server is only offering V1 and the Windows 10 clients are only using V2.
-
You could attempt enabling SMBv1 on a Windows 10 client and reattempt the connection, but SMBv1 has been depreciated for a few major reasons.
-
@BraswellJay said in SMB share from RHEL access issues ...:
I'm not familiar with Samba shares from Linux so not 100% sure.
The simple thing is that SMB is SMB. Linux and Windows SMB are both the same SMB. That it is Linux isn't a factor. Nor that it is Samba. But the SMB versions do matter, as do default settings. Windows 10 will have issues accessing older Windows SMB in the same way.
-
If you needed to install and enable SMBv1 (which I don't recommend) I'd change the server to use SMBv2, this should work for Windows 10.
-
@BraswellJay said in SMB share from RHEL access issues ...:
I did enable SMB v1 on the windows 10 clients thinking that would be necessary but that did not have any effect.
On Windows 10, did you enable SMB v1 server or client? In this case, you would need to enable only client to make this work, assuming this is the problem.
