Qnap [Firmware Release] QTS 4.3.3.0404 build 20171213

Gravitys

Chevalier Jedi
27 Août 2015
351
1
18
Code:
QTS 4.3.3.0404 build 20171213
 
[Important Notes] 
- For the status of QTS updates and maintenance for your NAS model, visit https://www.qnap.com/en/product/eol.php
- When QTS 4.3.x is installed on NAS models running on 64-bit Intel and AMD processors, some applications may not be supported. To check if installed apps on your NAS are compatible with QTS 4.3.x, download the QTS 64-bit compatibility tool and install it on your current QTS build. (https://download.qnap.com/QPKG/CF64_0.1-1114.qpkg.zip)
- QTS 4.3.3 is the final available firmware update for the following models: 
  TS-112P, TS-212P, TS-212-E, HS-210, TS-112, TS-212, TS-121, TS-221, TS-421 TS-120, TS-220, TS-420, TS-420U, TS-421U TS-412, TS-412U, TS-419U, TS-419U+, TS-419U II, TS-119P II, TS-219P II, TS-419P II, TS-119P+, TS-219P+, TS-419P+, TS-119P, TS-219P, TS-419P, TS-119, TS-219, TS-419 
 
[Fixed Issues]
- The transcoding wizard in File Station would indicate an incorrect path for managing transcoding tasks.
- Disconnecting an external storage device from the NAS might occasionally cause videos to stop playing when users accessed a shared folder via Samba.
- Media Library could not generate correct thumbnails for certain CR2 files.
- QTS would display messages about the exFAT license on the TAS-x68 and TS-x28, which do not support the exFAT format.
- Users that were created when Android Station was enabled could not access the "Android" shared folder.
- Users could not successfully download files with certain Chinese filenames via share links when accessing the myQNAPcloud website via Internet Explorer.
- Users could not restart certain NAS models after connecting to the NAS from Windows using iSCSI Initiator and then updating QTS to 4.3.3.0396 Build 20171205.

Voilou..
 
Bonsoir,

version installée chez moi aussi.
Pas vu de problème pour l'instant.

Bonne soirée.
 
Hello,

Impossible de faire marcher le serveur VPN L2TP/IPsec depuis l'upgrade à cette version (marchait très bien en 4.2), qqn d'autre a eu le problème?