Hallo,
We are using centos 7 and samba in combination with Win10 1903. The problem: Some systems are able to map a share and some can t. Any ideas and hints?
Thanks
Ralf
We have the same setup and have had no problems with clients mapping shares.
Some simple tips:
double check spelling of all usernames and that passwords on the clients match that of the samba shares
try setting up a user that can connect on their pc with a login on one that cannot, see if the problem follows the user or the pc
Check firewall rules on the windows clients to make sure there isn't a block set up.
Best of luck.
Chris
On 11/14/2019 9:09 AM, Ralf Prengel wrote:
Hallo,
We are using centos 7 and samba in combination with Win10 1903. The problem: Some systems are able to map a share and some can t. Any ideas and hints?
Thanks
Ralf _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Am 14.11.2019 um 16:23 schrieb Christopher Wensink:
We have the same setup and have had no problems with clients mapping shares.
Some simple tips:
double check spelling of all usernames and that passwords on the clients match that of the samba shares
try setting up a user that can connect on their pc with a login on one that cannot, see if the problem follows the user or the pc
Check firewall rules on the windows clients to make sure there isn't a block set up.
Best of luck.
Hallo, thanks for the hints. Firewalls are down and the share is configured for access without login. Works fine with Win7 and some Win10 systems. I m afraid that there is a mix of versions and patches active in the Win10 installations. I need a solution that works without any changes on the Win10 sytstems.
Ralf
On Thu, Nov 14, 2019 at 05:20:24PM +0100, Ralf Prengel wrote:
Firewalls are down and the share is configured for access without login. Works fine with Win7 and some Win10 systems. I m afraid that there is a mix of versions and patches active in the Win10 installations. I need a solution that works without any changes on the Win10 sytstems.
Are you sure you have SMBv1 turned off?
-----"CentOS" centos-bounces@centos.org wrote: -----
To: centos@centos.org From: "Jonathan Billings" Sent by: "CentOS" Date: 11/14/2019 01:30PM Subject: Re: [CentOS] Centos 7 + samba / some win 10 systems can mount and some not
On Thu, Nov 14, 2019 at 05:20:24PM +0100, Ralf Prengel wrote:
Firewalls are down and the share is configured for access without
login.
Works fine with Win7 and some Win10 systems. I m afraid that there is a mix of versions and patches active in
the Win10
installations. I need a solution that works without any changes on the Win10
sytstems.
Are you sure you have SMBv1 turned off?
-- Jonathan Billings billings@negate.org _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Could it be this?
In Windows 10, version 1709, Windows 10, version 1903, Windows Server, version 1709, Windows Server, version 1903, and later versions of Windows, the SMB2 client no longer allows the following actions:
Guest account access to a remote server Fallback to the Guest account after invalid credentials are provided https://support.microsoft.com/en-us/help/4046019/guest-access-in-smb2-disabl... https://www.claudiokuenzler.com/blog/879/windows-10-server-2016-access-samba...
Zitat von tbuchanan@vinu.edu:
-----"CentOS" centos-bounces@centos.org wrote: -----
To: centos@centos.org From: "Jonathan Billings" Sent by: "CentOS" Date: 11/14/2019 01:30PM Subject: Re: [CentOS] Centos 7 + samba / some win 10 systems can mount and some not
On Thu, Nov 14, 2019 at 05:20:24PM +0100, Ralf Prengel wrote:
Firewalls are down and the share is configured for access without
login.
Works fine with Win7 and some Win10 systems. I m afraid that there is a mix of versions and patches active in
the Win10
installations. I need a solution that works without any changes on the Win10
sytstems.
Are you sure you have SMBv1 turned off?
-- Jonathan Billings billings@negate.org _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Could it be this?
In Windows 10, version 1709, Windows 10, version 1903, Windows Server, version 1709, Windows Server, version 1903, and later versions of Windows, the SMB2 client no longer allows the following actions:
Guest account access to a remote server Fallback to the Guest account after invalid credentials are provided https://support.microsoft.com/en-us/help/4046019/guest-access-in-smb2-disabl... https://www.claudiokuenzler.com/blog/879/windows-10-server-2016-access-samba...
Yeap,
first step is now to integrate the smb-server into our windows-domain.
Ralf
Ralf Prengel writes:
Hallo,
We are using centos 7 and samba in combination with Win10 1903. The problem: Some systems are able to map a share and some can t. Any ideas and hints?
Make sure server and all clients are on the same page wrt smb protocol versions. Clients should have SMBv1 disabled. The server should enforce SMBv2 minimum. What you describe sounds like the server uses v1 and some clients, i.e. the ones that can't map shares, require v2.
On Thu, Nov 14, 2019 at 04:09:36PM +0100, Ralf Prengel wrote:
Hallo,
We are using centos 7 and samba in combination with Win10 1903. The problem: Some systems are able to map a share and some can t. Any ideas and hints?
Yes. Verify that selinux is not blocking the incoming connection from windows. I've had that problem in the past and it's a pain.
For testing purposes only, on the linux system(s) that reject windows SMB connection attempts, issue "setenforce 0" and see if it then works.
If it does then work, reset that setting to "setenforce 1" (you don't want to leave selinux disabled) then look in /var/logs to see if you can find a log of the failure. If you can find the selinux record for the failure it should tell you how to apply a work-around for that specific issue, so you do not need to totally disable selinux.
this page may prove helpful: https://www.serverlab.ca/tutorials/linux/administration-linux/troubleshootin...
Good luck!