TOS 6.0.535 (X86) is Released for Update

[star]

After installing version 6.0.535 I can't find TNAS by local name, only by IP address

if you have released 80 and 443 you need to add ports like this TNAS.local:xxxx <-- insert port

[ellowsmile]

After installing version 6.0.535 I can't find TNAS by local name, only by IP address

if you have released 80 and 443 you need to add ports like this TNAS.local:xxxx <-- insert port

I know I should use nameserver.local:5443 but it stopped working

[ellowsmile]

I turned off the NAS, waited 5 minutes and then turned it on. This helped solve the problem.

[fcs001fcs]

I'm upgrading from 519, how come not a word that SSH port automatically changes from 22 to 9222 without warning user !??

It's always been 9222 as far as I have known.

Regards

I had the same issue of the SSH port revering back to its default 9222 setting on the last few TOS updates. I reported it via this forum, but I guess that TM has not got around to fixing it yet.

I now just check it after each update and reset it to the port number I had set for it prior to the upgrade.

TM: This is a relatively minor issue, but can this be fixed in the next TOS update?

[Gremlin]

It is not so minor. Over the (many) updates I have performed, I have come to expect some things will have been reset, but not always the same things. It is a great shame that @TM cannot respect customers' settings. Unfortunately we cannot even rely on a 'save configuration' and restore to get settings back to what we want. Makes upgrades more of an annoyance than a blessing.

[DekkaR]

*** BUG REPORT ***

Each TOS update improves and fixes errors, but there is still some instability in the TCP/IP stack and network protocols such as SMB.

Since at least version 519, a specific issue has persisted: when one or more "Remote Folders" are configured using the SMB protocol, if the source becomes inaccessible for any reason, the overall performance of the NAS (F8 in my case) is negatively affected, becoming slow and unstable.

Accessing folders via SMB becomes slow and unpredictable, with frequent errors and unreliable transfers.

However, when the source of the "Remote Folders" becomes accessible again, the NAS functionality returns to normal.

[adam12345]

*** BUG REPORT ***

Each TOS update improves and fixes errors, but there is still some instability in the TCP/IP stack and network protocols such as SMB.

Since at least version 519, a specific issue has persisted: when one or more "Remote Folders" are configured using the SMB protocol, if the source becomes inaccessible for any reason, the overall performance of the NAS (F8 in my case) is negatively affected, becoming slow and unstable.

Accessing folders via SMB becomes slow and unpredictable, with frequent errors and unreliable transfers.

However, when the source of the "Remote Folders" becomes accessible again, the NAS functionality returns to normal.

i am have problems with smb as well ,my mapped drives stops working , i suspect dns issue but im not sure

i haven't able to configure remote folders at all actually , after i mount it fails to enable the remote share

[Gremlin]

and AUTO POWER ON failed this morning despite being set and enabled. Auto shutdown worked last night.

[DekkaR]

The shutdown and startup scheduling has never worked for me.

[Gremlin]

and just for the record:
UPS support disabled after update (although the settings have been maintained).