Sorry to address such an old and obsolete system. A customer is migrating up from Centos 6 but needs to keep it working a little while longer.
The issue now is that Windows users are unable to map a drive letter to a Centos directory. When they go to map the drive (to "\ip\public"), Windows says the connection is rejected, with no further details. I presume some configuration is set wrong but I haven't been able to find it after reading man pages and Google stuff.
Samba is installed and so is samba-swat. But I can't get port 901 open so I can verify proper configuration of SMB. Relevant lines in current files:
/etc/services: swat 901/tcp smpnameres # Samba Web Administration Tool
/etc/samba/smb.conf: [/public] path = /public public = yes writable = yes printable = yes write list = +users
iptables -L: -A INPUT -p tcp -m tcp --dport 901 -j ACCEPT
But: $ nmap -sT -p901 localhost PORT STATE SERVICE 901/tcp closed samba-swat
Please tell me what I've missed or give a pointer to better help.
On Wed, 2025-06-04 at 15:47 -0700, Dave Close wrote:
Sorry to address such an old and obsolete system. A customer is migrating up from Centos 6 but needs to keep it working a little while longer. The issue now is that Windows users are unable to map a drive letter to a Centos directory. When they go to map the drive (to "\ip\public"), Windows says the connection is rejected, with no further details. I presume some configuration is set wrong but I haven't been able to find it after reading man pages and Google stuff.
I have faced this kind of problem before. There is a simple solution. Create a new modern host, NFS mount the volume from the legacy host, share the NFS mount via Samba to Windows clients from the modern host.
On Wed, 4 Jun 2025 at 18:48, Dave Close dave@compata.com wrote:
Sorry to address such an old and obsolete system. A customer is migrating up from Centos 6 but needs to keep it working a little while longer.
The issue now is that Windows users are unable to map a drive letter to a Centos directory. When they go to map the drive (to "\ip\public"), Windows says the connection is rejected, with no further details. I presume some configuration is set wrong but I haven't been able to find it after reading man pages and Google stuff.
Samba is installed and so is samba-swat. But I can't get port 901 open so I can verify proper configuration of SMB. Relevant lines in current files:
/etc/services: swat 901/tcp smpnameres # Samba Web Administration Tool
/etc/samba/smb.conf: [/public] path = /public public = yes writable = yes printable = yes write list = +users
iptables -L: -A INPUT -p tcp -m tcp --dport 901 -j ACCEPT
But: $ nmap -sT -p901 localhost PORT STATE SERVICE 901/tcp closed samba-swat
That means samba-swat started up, opened the port, and then possibly died so it then closed the port. You will need to look at logs to see why the process is dieing or erroring out.
Is it because newer windows clients no longer support the old smb protocols that would have been used in centos 6 days?
Thank you, Terry Bowling Principal Product Manager - Red Hat Insights - image builder and RHEL management Red Hat, Inc.
On Thu, Jun 5, 2025, 7:16 AM Stephen Smoogen via Discuss < discuss@lists.centos.org> wrote:
On Wed, 4 Jun 2025 at 18:48, Dave Close dave@compata.com wrote:
Sorry to address such an old and obsolete system. A customer is migrating up from Centos 6 but needs to keep it working a little while longer.
The issue now is that Windows users are unable to map a drive letter to a Centos directory. When they go to map the drive (to "\ip\public"), Windows says the connection is rejected, with no further details. I presume some configuration is set wrong but I haven't been able to find it after reading man pages and Google stuff.
Samba is installed and so is samba-swat. But I can't get port 901 open so I can verify proper configuration of SMB. Relevant lines in current files:
/etc/services: swat 901/tcp smpnameres # Samba Web Administration Tool
/etc/samba/smb.conf: [/public] path = /public public = yes writable = yes printable = yes write list = +users
iptables -L: -A INPUT -p tcp -m tcp --dport 901 -j ACCEPT
But: $ nmap -sT -p901 localhost PORT STATE SERVICE 901/tcp closed samba-swat
That means samba-swat started up, opened the port, and then possibly died so it then closed the port. You will need to look at logs to see why the process is dieing or erroring out.
-- Stephen Smoogen, Red Hat Automotive Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren _______________________________________________ Discuss mailing list -- discuss@lists.centos.org To unsubscribe send an email to discuss-leave@lists.centos.org
On 2025-06-04 4:47 PM, Dave Close wrote:
The issue now is that Windows users are unable to map a drive letter to a Centos directory. When they go to map the drive (to "\ip\public"), Windows says the connection is rejected, with no further details. I presume some configuration is set wrong but I haven't been able to find it after reading man pages and Google stuff.
Is that how it was working previously, with a direct IP address connection to the share? No local DNS; no NetBIOS name service? Presumably there are no domain controllers in the environment?
Samba is installed and so is samba-swat.
If samba-swat was installed, I'm guessing the installed samba packages are 3.6.x? A parallel set of Samba 4.2 packages (prepended with samba4-*) were made available toward the end of the RHEL/CentOS 6 release cycle which no longer included samba-swat; in theory you could set that up to support higher SMB/CIFS protocol levels and better security, depending on how long the client needs to continue operating with this solution.
I'm ignoring the swat stuff as the web interface isn't really relevant to the issue.
Please tell me what I've missed or give a pointer to better help.
Anything turn up in /var/log/samba/* ?
You probably want to look at the client/server authentication configuration in the [global] section of smb.conf; if the server is configured to cap the protocol and authentication levels lower than what newer Windows clients are willing to negotiate, that could be contributing to the problem.
-
Adam Tauno Williams -
Dave Close -
Nels Lindquist -
Stephen Smoogen -
Terry Bowling