Koozali.org: home of the SME Server
Obsolete Releases => SME 9.x Contribs => Topic started by: alanh on September 18, 2020, 06:33:42 AM
-
I have a couple of SME servers at my office, were working fine until recently.
I believe it was Win 10 2004 update.
The issue is I can't access shared folders on the server.
I get an error (see attachment)
I can access by IP address but NOT server name -if I restart it may work, it may not.
so \\server1\afiles does not work whereas \\192.168.0.222\afiles works ok.
I have an XP virtual machine, can access from there no issue at all.
SMB1 is enabled. So I am now very concerned that my client's network will soon experience the same problem as their computers update.
-
Couple of options, reset the win10 PCs settiungs back to using SMB1 see this reference one of many - https://www.windowscentral.com/how-access-files-network-devices-using-smbv1-windows-10 there are also a number of discussions here re the issue.
Second and best, as it does not use smb1, see the forum discussions re use of python script using wsdd, https://forums.contribs.org/index.php/topic,54268.msg284028.html#msg284028, our package is only for sme10, however it is simple to use one of the packages ref'd here - https://github.com/christgau/wsdd
WSDD works a treat
Added: there is a centos package for centos 7
Quote
CentOS, Fedora, RHEL
wsdd is included in RedHat/CentOS' EPEL repository. After setting that up, you can install wsdd like on Fedora where it is sufficient to issue
-
I do have a rough personal build of wsdd for v9.
Doesn't always like rotate/restart.
What's it worth??
:-)
-
uncomment