TOS 6.0.555 (X86) is Released for Update

[star]

We have noticed that some DNS servers are unable to correctly resolve our email server address. We are working on optimizing the email sending process to address this issue.
In the meantime, you can try the following steps: go to the network module in the TOS control panel, edit the LAN settings, and change the DNS server to one commonly used in your area or a public DNS server, such as 8.8.8.8.

did not work with changeing dns to 8.8.8.8 or similar 1.1.1.1 or such. notifications cannot get a handshake it says

[RyanYang]

You can check if SPC is enabled. If it is, try disabling it and then check if the network is functioning properly.

[RyanYang]

I am currently with version 535 and having a bit of issue when heavy smb file transfer, my network maps disappear and the transfer fails

16.Optimized the handling strategy for SMB configuration files that increases reliability.

might be this can help with the issue ?

The recent changes are not closely related to the transmission interruption.
It's advisable to check the hardware resource usage of the TNAS during file transfers.
Additionally, certain incompatible memory configurations and using an SSD as cache might also lead to this issue.

[adam12345]

I am currently with version 535 and having a bit of issue when heavy smb file transfer, my network maps disappear and the transfer fails

16.Optimized the handling strategy for SMB configuration files that increases reliability.

might be this can help with the issue ?

The recent changes are not closely related to the transmission interruption.
It's advisable to check the hardware resource usage of the TNAS during file transfers.
Additionally, certain incompatible memory configurations and using an SSD as cache might also lead to this issue.

i am using f2-424 with not additional ram or ssd , only the network seems to be 100%

[RyanYang]

Can you describe your situation in detail?

[RyanYang]

You can try enabling debug mode through 'Support and Help' on the TOS desktop. After an issue occurs, please send us the logs for further analysis.

[lsoto]

OMG
Thta post fixed everything
NOTE: PUT YOUR real ADMIN user on the query below
NOTE: do a su to postgres user and save the contents of the db with a pg_dumpall (I hope it could be restored from it if needed)

To view my shares again:
tersql -sql "Update share set owner = 'ADMIN' "

In my case, the lost shares were owner by the "super" user (?? not even root or admin...)

[lsoto]

Sorry
I was referring to this post, under a NFS shares problem
viewtopic.php?p=40886#p40886

I checked the shares database and saw that a new created one has the proper user and try to modify all of them... voila!! after restarting samba I could see again my shares!!

[OttO1916]

After the update cannot (SMB)connect or PING to both NASses using the hosname.
DNS is fine, used various DNSservers, flushed DNScache, restarted SMB on NAS, restarted all swiches and connecting devices.
Somehow it doesn't register anymore. Connecting using IP works OK.
I changed the hostname to IP -address on all connecting devices, or where possible added entries in the hosts file.
For the time being i'm OK, but this workaround is a bit of a nuisance...

[mrslother]

Active Directory problem after upgrading from 6.0.535.

My Active Directory domain was not enabled (checkbox in Settings--> Domain --> Join Domain option is not checked).
I enabled it (selected checkbox) and it showed all my previous domain details. Put in my domain password and waited...

Code: Select all

+Checking DNS records: Success
+Check Network: Success	
-Check domain service: FAIL!
	Displayed: "Failed to enable domain service!"

Rebooted & tried again. Fail
Reset the device's domain account (on the AD controller) & tried again. Fail.
Deleted the device's domain account (on the AD controller) & tried again. Fail.

Then monitored with journalctl -f:

Code: Select all

Dec 07 21:26:26 NAS TOSDaemon[10379]: domain_model.go:domain.(*Service).ConnectToAdServer.func1:228 value=domain joinAdDomain failed, connectToAdServer error: Failed to join domain: Invalid configuration ("workgroup" set to 'INTRA', should be 'mydomain') and configuration modification was not requested
Dec 07 21:26:26 NAS TOSDaemon[10379]: ERROR | 2024-12-07 21:26:26 | 200 |   POST |    192.168.1.99 | /domain/DomainServiceDetection? | 5.397213579s | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36 Edg/131.0.0.0 | connectToAdServer error: Failed to join domain: Invalid configuration ("workgroup" set to 'INTRA', should be 'mydomain') and configuration modification was not requested

Note: my domain name is "intra.xxx.com" and it's netbios name is "mydomain".
Note2: Settings-->File Services-->SMB-->Workgroup is set to "mydomain"

What has changed since 6.0.535??