The ARM Version of TOS 7 Public Beta is Now Officially Available

[CursaYang]

thanks for the good news, is Tailscale also available on TOS7 ?

Currently, Tailscale has adapted TOS 7 for the x86 architecture. For TOS based on the ARM architecture, please pay attention to updates from the community application.

[dtbogor]

thanks, I'll keep watching on the Community pages.
once available, I will try the TOS7 beta

[dikol]

Regarding the issue of continuous authorization prompts when connecting to the network on Windows 10 Pro, here is a detailed explanation and suggestions:

I tried all of this, but the result was negative. The only thing that helped was what I described in the message. This problem only occurred on one computer. I tested logging in from a laptop, another computer, and a smartphone, and it connected fine from all of them.
There were no connection problems in TOS5 and TOS6

You should really point out the security implications of handing out this advice.

https://support.microsoft.com/en-au/top ... 81acde6e73

NTLM v1 is insecure and is being phased out by Microsoft.

I know. Samba is configured to work only on a LAN network

[dikol]

NTLM v1 is insecure and is being phased out by Microsoft.

secpol.msc → Send NTLMv2 responses only

[Lukin]

Hello

When transferring data from a hard drive, whether connected via USB to the NAS or even sent over local Wi-Fi, I often experience interruptions after 30 minutes to an hour since updating to TOS7. Sometimes the transfer stops completely. I have to cancel the transfer and start again. My nas is a f4-212 2g ram

[EriChan]

Here are detailed explanations and recommendations regarding the file transfer interruption issue you encountered after upgrading your F4-212 to TOS 7.

Since the F4-212 is equipped with 2GB of memory, resource management becomes critical when running the new generation operating system. Transfers typically interrupt after approximately 30-60 minutes, usually due to system resource exhaustion, high-load background tasks, or network instability.

Recommended Solutions:

1. Check High-Load Background Tasks
When the transfer is interrupted, click the "Dashboard" on the right side of the TOS desktop to check if it displays a "Load operation blocked" message. Alternatively, go to Control Panel > System Information > Resource Monitor to check CPU and memory usage.

2. Change Transfer Protocol: Discontinue Web Interface and Switch to SMB
If you are copying data through a browser (web-based file manager), the connection is limited by browser cache and network timeout settings, making it prone to crashing during prolonged large file transfers. The SMB protocol is better suited for large data volumes and extended transfers, offering stronger error correction and reconnection capabilities.

Steps:

• For Windows users: Press Win + R and enter the NAS IP address (e.g., \\192.168.1.100) to transfer files via SMB protocol.

• For Mac users: In Finder, click "Go > Connect to Server" and enter smb:// followed by your NAS IP address.

3. Optimize Network Connection

Wi-Fi signals may experience packet loss or momentary disconnections when overheated during prolonged high-bandwidth usage. It is strongly recommended to connect your computer to the same switch or router as the NAS using an Ethernet cable, and ensure the cable meets CAT5e or higher standards.

[Lukin]

Hello
Thank you for your reply.

But SMB is enabled. And the internet connection isn't the issue. Even when transferring files from an external hard drive via USB directly to the NAS, it crashes after 30 minutes to an hour.

The NAS itself isn't running at full capacity, as no other applications are running; the only thing doing it is the file transfer. At most, the file transfer uses 40% of the NAS's resources.

This started after I installed TOS 7.

[EriChan]

Since you have ruled out network issues, confirmed that both direct USB transfer and SMB transfer crash within approximately 30 to 60 minutes, and found that the resource utilization is only around 40%, this strongly indicates that the problem is most likely not at the application layer.

To accurately locate and resolve the issue, please go to TOS > Support & Help > Feedback to generate and download the system report, then send it to our technical support email at [email protected]. Our engineers will analyze it and provide a solution upon receipt.

If you fail to send the system report properly, please upload it to a cloud storage first and share the link with us in your email.

[krissan]

Hey,
TOS7 beta you provided installed like a charm replacing v5.
I saw that no iSCSI there is at the moment, but are there any plans to release it later in your roadmap fot this distribution?

[Felix]

Thank you for your interest in and support of our products! Regarding the iSCSI feature you mentioned, we fully understand its importance in specific application scenarios. Currently, this feature is not included in our near-term product roadmap.