Page 8 of 8
Re: Windows users cannot use SMB file service to access?
Posted: 16 Aug 2025, 05:57
by dleonmag
TMzethar wrote: ↑31 Mar 2025, 19:57
Can other PCs or even mobile devices on the same local network receive SMB broadcasts?
Please provide the TNAS model and TOS version.
It might be that the relevant process/service is not functioning. You can try restarting the TNAS.
Hola. Gracias por las atenciones. Otros equipos de la Red sí son accesibles. Pensé que con la última actualización de W11 se corregiría ese problema, pero no fue así.
Mi NAS es el Terramaster F5-221. Tiene habilitado SMB 1.0 al 3.0
El TOS es la versión 4.2.40-
He reiniciado el NAS e incluso le he cambiado la dirección IP, sin resultados.
Re: Windows users cannot use SMB file service to access?
Posted: 16 Aug 2025, 19:45
by GevinKe
Hello,
We sincerely apologize for the inconvenience you have experienced.
The issue you reported has been forwarded to our product team. It currently requires reproduction and in-depth verification in our lab. We will provide you with the results as soon as there is a clear update.
Re: Windows users cannot use SMB file service to access?
Posted: 16 Aug 2025, 23:46
by Gremlin
Recently I believe someone posted that TOS4 only worked under SMBv1. In which caase SMBv1 would need to be explicitly enabled in Windows 11, I believe. (which it isn't by default).
Re: Windows users cannot use SMB file service to access?
Posted: 17 Aug 2025, 07:18
by sianderson
Gremlin wrote: ↑16 Aug 2025, 23:46
Recently I believe someone posted that TOS4 only worked under SMBv1. In which caase SMBv1 would need to be explicitly enabled in Windows 11, I believe. (which it isn't by default).
my F2-210 is running TOS 4.2.44 and the network share is showing Dialect 3.1.1 so believe it has no problems with SMB3? unless im missing something
Re: Windows users cannot use SMB file service to access?
Posted: 17 Aug 2025, 11:48
by TMnick
sianderson wrote: ↑17 Aug 2025, 07:18
Gremlin wrote: ↑16 Aug 2025, 23:46
Recently I believe someone posted that TOS4 only worked under SMBv1. In which caase SMBv1 would need to be explicitly enabled in Windows 11, I believe. (which it isn't by default).
my F2-210 is running TOS 4.2.44 and the network share is showing Dialect 3.1.1 so believe it has no problems with SMB3? unless im missing something
Hello, although the network sharing displays 'Dialect 3.1.1,' its behavior suggests that it actually falls back to SMB1 through auto-negotiation. The exact reason for this still requires further investigation. I’ve documented this issue and forwarded it to the relevant team for verification.
Re: Windows users cannot use SMB file service to access?
Posted: 18 Aug 2025, 16:17
by TMzethar
dleonmag wrote: ↑16 Aug 2025, 05:57
Se actualizó a la versión 24H2 y ya no se visualizan los equipos de mi red local.
Hi, dleonmag
Previously, no similar feedback was collected, and such anomalies were not observed in similar laboratory environments. Based on your description, the issue appears clearly related to changes in Windows. We can only offer some guesses and suggestions for you.
In Control Panel → Programs and Features → Turn Windows features on or off, ensure that the following options are selected:
·SMB Direct
·Discovery Services (Function Discovery Provider Host / Function Discovery Resource Publication)
Open Services Manager (services.msc) and verify that the following services are started and set to Automatic:
·Function Discovery Provider Host
·Function Discovery Resource Publication
·SSDP Discovery
·UPnP Device Host
Also confirm that the NAS has WS-Discovery or Bonjour/mDNS enabled.
Re: Windows users cannot use SMB file service to access?
Posted: 18 Aug 2025, 18:43
by Gremlin
Google: " pros and cons of enabling upnp device host in win11"
Enabling UPnP (Universal Plug and Play) on a Windows 11 device can simplify network device connectivity but also introduces security risks. While it automates device discovery and configuration, UPnP lacks authentication and can expose devices to potential malware or unauthorized access.
Pros:
Simplified device connectivity:
UPnP automates the process of connecting devices on a network, eliminating the need for manual setup and configuration.
Convenience for certain applications:
It can be useful for gaming, streaming content, and some Internet of Things (IoT) devices that require automatic port forwarding.
Cons:
Security risks:
UPnP's lack of authentication can allow malicious software or devices to connect to your network and potentially access sensitive information or resources.
Potential for malware:
Malicious applications can use UPnP to open ports on your router, creating a backdoor for malware or other attacks.
Increased attack surface:
UPnP can expose your network to external threats if your router is misconfigured to expose UPnP services to the internet.
Unnecessary for many users:
If you don't rely on features that require UPnP, such as hosting game servers, you're better off disabling it for security reasons.
Recommendation:
Unless you have a specific need for UPnP, such as hosting game servers, it's generally recommended to disable it for security reasons. If you do need it, ensure your router is properly configured and consider using static IP addresses and manual port forwarding instead.
Just saying .......
Re: Windows users cannot use SMB file service to access?
Posted: 18 Aug 2025, 23:23
by sianderson
Gremlin wrote: ↑18 Aug 2025, 18:43
Just saying .......
i definitely agree, wasnt UPnP one of the causes of all the ransomware attacks that were happening to the TNAS drives not too long ago?
its one of the first things i disable, and i have no issues with accessing any of the shares on windows 11