From 31f0b03d8877bb0a29a9350aee6ab3d317e53705 Mon Sep 17 00:00:00 2001
From: Cyril MARCHAL <139960138+CyrilmarchalP17@users.noreply.github.com>
Date: Tue, 7 Oct 2025 11:42:28 +0200
Subject: [PATCH 01/16] Update guide FTPBACK

Update of the url associated with microsoft support
---
 .../dedicated_servers/services_backup_storage/guide.fr-fr.md  | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.fr-fr.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.fr-fr.md
index 4435af47fa1..034e6e19402 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.fr-fr.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.fr-fr.md
@@ -1,7 +1,7 @@
 ---
 title: 'Utiliser Backup Storage sur un serveur dédié'
 excerpt: 'Découvrez comment activer et accéder à votre espace de stockage supplémentaire'
-updated: 2025-07-21
+updated: 2025-10-07
 ---
 
 ## Objectif
@@ -346,7 +346,7 @@ System error 1272 has occurred.
 You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
 ```
 
-Ce problème peut être résolu en modifiant le Registre Windows : ouvrez l'utilitaire Windows *regedit* et recherchez l'entrée `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`. Définissez la valeur de `AllowInsecureGuestAuth` sur « 1 ». Retrouvez plus d'informations sur ce sujet sur les [pages de support Microsoft](https://answer.microsoft.com/en-us/windows/forum/all/you-cant-access-this-shared-folder-because-your/01d15775-2cbe-41f8-beb8-84ce588b34ab).
+Ce problème peut être résolu en modifiant le Registre Windows : ouvrez l'utilitaire Windows *regedit* et recherchez l'entrée `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`. Définissez la valeur de `AllowInsecureGuestAuth` sur « 1 ». Retrouvez plus d'informations sur ce sujet sur les [pages de support Microsoft](https://learn.microsoft.com/fr-fr/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3?tabs=group-policy).
 
 ##### Linux
 

From 3df267472753e1b6f863f13c13716a0e4b266452 Mon Sep 17 00:00:00 2001
From: Cyril MARCHAL <139960138+CyrilmarchalP17@users.noreply.github.com>
Date: Tue, 7 Oct 2025 11:47:34 +0200
Subject: [PATCH 02/16] Update Guide FTPBACK - EN

Update of the url associated with microsoft support
---
 .../services_backup_storage/guide.en-gb.md                  | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-gb.md
index 5030385f4be..06f164f62ee 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-gb.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-gb.md
@@ -1,7 +1,7 @@
 ---
 title: How to use the backup storage on a dedicated server
 excerpt: 'Find out how to enable and access your additional storage space'
-updated: 2025-07-21
+updated: 2025-10-07
 ---
 
 ## Objective
@@ -339,7 +339,7 @@ System error 1272 has occurred.
 You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
 ```
 
-This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`. Set the value of `AllowInsecureGuestAuth` to "1". You can find more information on this issue on the [Microsoft support pages](https://answers.microsoft.com/en-us/windows/forum/all/you-cant-access-this-shared-folder-because-your/01d15775-2cbe-41f8-beb8-84ce588b34ab).
+This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`. Set the value of `AllowInsecureGuestAuth` to "1". You can find more information on this issue on the [Microsoft support pages](https://learn.microsoft.com/en-gb/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ##### Linux
 
@@ -374,4 +374,4 @@ The code example above contains variables, which you will need to substitute wit
 
 ## Go further
 
-Join our [community of users](/links/community).
\ No newline at end of file
+Join our [community of users](/links/community).

From 2ea5008b1b778cffd751e02f20a856c66a70a580 Mon Sep 17 00:00:00 2001
From: Cyril MARCHAL <139960138+CyrilmarchalP17@users.noreply.github.com>
Date: Tue, 7 Oct 2025 12:09:44 +0200
Subject: [PATCH 03/16] Update Guide NAS-HA

Add-in for Linux client
---
 .../ha_nas/nas_cifs/guide.fr-fr.md            | 41 +++++++++++++++++--
 1 file changed, 37 insertions(+), 4 deletions(-)

diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-fr.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-fr.md
index 4f164a9c5c2..152aed9a3af 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-fr.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-fr.md
@@ -1,7 +1,7 @@
 ---
 title: Monter un NAS-HA sur Windows Server via CIFS
 excerpt: Decouvrez comment monter un NAS-HA sur Windows Server via CIFS
-updated: 2021-11-22
+updated: 2025-10-07
 ---
 
 ## Objectif
@@ -13,7 +13,7 @@ Configurez et montez votre espace de stockage NAS-HA OVHcloud sur Windows Server
 - Un [serveur dédié](/links/bare-metal/bare-metal) **ou** un [VPS](/links/bare-metal/vps) **ou** une [instance Public Cloud](/links/public-cloud/public-cloud) avec une distribution Windows.
 - Une offre [NAS-HA](/links/storage/nas-ha).
 
-### Configuration
+### Configuration pour Windows
 
 - **Windows Server 2008** : cliquez sur le menu `Démarrer`{.action} > `Tous les programmes`{.action} > `Accessoires`{.action} > `Invite de commandes`{.action}.
 - **Windows Server 2012** : cliquez sur l'icône `Windows PowerShell`{.action} dans la barre de tâches.
@@ -26,7 +26,7 @@ Exécutez ensuite la commande suivante :
 net use z: \\IP_SERVEUR_CIFS\CHEMIN_CIFS
 ```
 
-### Exemple
+#### Exemple
 
 - Montage CIFS pour un NAS-HA :
 
@@ -39,10 +39,43 @@ net use z: \\10.16.101.8\zpool-000206_NOM_PARTITION_1
 > L'utilisateur SMB/CIFS est `nobody`, toute modification de droits effectuée par cet utilisateur peut générer des conflits avec des droits NFS existants.
 > 
 
+Le message d'erreur suivant peut s'afficher :  
+
+```console
+System error 1272 has occurred.
+
+You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
+```
+
+Ce problème peut être résolu en modifiant le Registre Windows : ouvrez l'utilitaire Windows *regedit* et recherchez l'entrée `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`. Définissez la valeur de `AllowInsecureGuestAuth` sur « 1 ». Retrouvez plus d'informations sur ce sujet sur les [pages de support Microsoft](https://learn.microsoft.com/fr-fr/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3?tabs=group-policy).
+
+
+### Configuration pour Linux
+
+Ouvrez une connexion SSH à votre serveur et tapez la commande suivante :
+
+```sh
+mount -t cifs -o uid=root,gid=100,dir_mode=0700,username=root,password= //IP_SERVEUR_CIFS/CHEMIN_CIFS /mnt/FolderMount
+```
+
+> [!warning]
+>
+> Afin de monter des partages par nom d'hôte (par opposition aux adresses IP), l'utilitaire `mount.cifs` est requis. Il fait généralement partie du paquet `cifs-utils`.
+>
+> `mount.cifs` est un wrapper qui résout les noms d'hôte et ajoute le paramètre `ip=` aux paramètres de montage transmis au noyau.
+>
+> Sans `mount.cifs`, les tentatives de montage par nom d'hôte entraîneront l'erreur suivante :
+>
+> ```text
+> mount: /mnt/FolderMount: mount(2) system call failed: No route to host.
+>        dmesg(1) may have more information after failed mount system call.
+> ```
+
+
 ## Aller plus loin
 
 [Les questions fréquentes concernant le NAS](/pages/storage_and_backup/file_storage/ha_nas/nas_faq)
 
 Si vous avez besoin d'une formation ou d'une assistance technique pour la mise en oeuvre de nos solutions, contactez votre commercial ou cliquez sur [ce lien](/links/professional-services) pour obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l’équipe Professional Services.
 
-Échangez avec notre [communauté d'utilisateurs](/links/community).
\ No newline at end of file
+Échangez avec notre [communauté d'utilisateurs](/links/community).

From 2d641d4b5376d6a9a8134218af79e0e855b7cb2f Mon Sep 17 00:00:00 2001
From: Cyril MARCHAL <139960138+CyrilmarchalP17@users.noreply.github.com>
Date: Tue, 7 Oct 2025 12:15:37 +0200
Subject: [PATCH 04/16] Update Guide NAS-HA

add informations for CIFS under Linux
---
 .../ha_nas/nas_cifs/guide.en-gb.md            | 38 +++++++++++++++++--
 1 file changed, 35 insertions(+), 3 deletions(-)

diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-gb.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-gb.md
index 6dfbeb64426..1ce6d6f653b 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-gb.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-gb.md
@@ -1,7 +1,7 @@
 ---
 title: Mount your HA-NAS on Windows Server via CIFS
 excerpt: This guide shows you how to mount your HA-NAS on Windows Server via CIFS.
-updated: 2021-11-22
+updated: 2025-10-07
 ---
 
 ## Objective
@@ -13,7 +13,7 @@ Configure and mount an OVHcloud HA-NAS storage space on your Windows Server usin
 - a [Dedicated Server](/links/bare-metal/bare-metal) **or** a [VPS](/links/bare-metal/vps) **or** a [Public Cloud Instance](/links/public-cloud/public-cloud) with a Windows distribution
 - a [HA-NAS solution](/links/storage/nas-ha)
 
-### Settings
+### Settings for Windows
 
 - **Windows Server 2008**: Click on the menu `Start`{.action} > `All the programs`{.action} > `Accessories`{.action} > `Command prompt`{.action}.
 - **Windows Server 2012**: Click the `Windows PowerShell`{.action} icon at the bottom of the screen in the taskbar.
@@ -26,7 +26,7 @@ Then run the following command:
 net use z: \\CIFS_SERVER_IP\CIFS_PATH
 ```
 
-### Example
+#### Example
 
 - CIFS mounting for a NAS-HA:
 
@@ -39,6 +39,38 @@ net use z: \\10.16.101.8\zpool-000206_PARTITION_NAME_1
 > The SMB/CIFS user is `nobody`. Changing permissions with this user may generate conflicts with existing NFS permissions. 
 > 
 
+The following error message may appear: 
+
+```console
+System error 1272 has occurred.
+
+You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
+```
+
+This problem can be solved by changing the Windows Registry. Open the Windows utility *regedit* and search for the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.
+Set the value of `AllowInsecureGuestAuth` to "1".
+Find more information on this topic on the [Microsoft support pages](https://learn.microsoft.com/en-gb/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+
+### Settings for Linux
+
+Open an SSH connection to your server and type the following command:
+
+```sh
+mount -t cifs -o uid=root,gid=100,dir_mode=0700,username=root,password= //IP_SERVEUR_CIFS/CHEMIN_CIFS /mnt/FolderMount
+```
+
+> [!warning]
+>
+> In order to mount shares by host name (as opposed to IP addresses), the `mount.cifs` utility is required. It is usually part of the `cifs-utils` package.
+> `mount.cifs` is a wrapper that resolves host names and adds the parameter `ip=` to the mount parameters transmitted to the kernel.
+> Without `mount.cifs`, attempts to mount by host name will result in the following error:
+
+> ```text
+> mount: /mnt/FolderMount: mount(2) system call failed: No route to host.
+>        dmesg(1) may have more information after failed mount system call.
+> ```
+
+
 ## Go further
 
 [NAS - Frequently Asked Questions](/pages/storage_and_backup/file_storage/ha_nas/nas_faq)

From d865986c9515b0593e2e469a516fe7be4646d7f0 Mon Sep 17 00:00:00 2001
From: Cyril MARCHAL <139960138+CyrilmarchalP17@users.noreply.github.com>
Date: Wed, 8 Oct 2025 11:01:35 +0200
Subject: [PATCH 05/16] Update Guide NAS-HA

Correction of the title
---
 .../file_storage/ha_nas/nas_cifs/guide.fr-fr.md             | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-fr.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-fr.md
index 152aed9a3af..126e7f4ed1c 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-fr.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-fr.md
@@ -1,12 +1,12 @@
 ---
-title: Monter un NAS-HA sur Windows Server via CIFS
-excerpt: Decouvrez comment monter un NAS-HA sur Windows Server via CIFS
+title: Monter un NAS-HA via partage CIFS
+excerpt: Decouvrez comment monter un NAS-HA via le protocole CIFS
 updated: 2025-10-07
 ---
 
 ## Objectif
 
-Configurez et montez votre espace de stockage NAS-HA OVHcloud sur Windows Server via CIFS.
+Configurez et montez votre espace de stockage NAS-HA OVHcloud via le protocole CIFS.
 
 ## Prérequis
 

From f45ca399fa28082e33f5e9433bc178d1eca75eb4 Mon Sep 17 00:00:00 2001
From: Cyril MARCHAL <139960138+CyrilmarchalP17@users.noreply.github.com>
Date: Wed, 8 Oct 2025 11:04:57 +0200
Subject: [PATCH 06/16] Update Guide NAS-HA - EN

Update of the title
---
 .../file_storage/ha_nas/nas_cifs/guide.en-gb.md             | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-gb.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-gb.md
index 1ce6d6f653b..86cc16db989 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-gb.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-gb.md
@@ -1,12 +1,12 @@
 ---
-title: Mount your HA-NAS on Windows Server via CIFS
-excerpt: This guide shows you how to mount your HA-NAS on Windows Server via CIFS.
+title: Mount your HA-NAS via CIFS share
+excerpt: This guide shows you how to mount your HA-NAS using CIFS protocol.
 updated: 2025-10-07
 ---
 
 ## Objective
 
-Configure and mount an OVHcloud HA-NAS storage space on your Windows Server using CIFS.
+Configure and mount an OVHcloud HA-NAS storage space using CIFS protocol.
 
 ## Requirements
 

From 0683eb485af13c8a83bcc235e5fbd2f07618f96d Mon Sep 17 00:00:00 2001
From: Cyril MARCHAL <139960138+CyrilmarchalP17@users.noreply.github.com>
Date: Wed, 8 Oct 2025 11:06:40 +0200
Subject: [PATCH 07/16] Update Guide NAS-HA - EN

Modification of prerequisites
---
 .../file_storage/ha_nas/nas_cifs/guide.en-gb.md                 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-gb.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-gb.md
index 86cc16db989..8c41629f105 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-gb.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-gb.md
@@ -10,7 +10,7 @@ Configure and mount an OVHcloud HA-NAS storage space using CIFS protocol.
 
 ## Requirements
 
-- a [Dedicated Server](/links/bare-metal/bare-metal) **or** a [VPS](/links/bare-metal/vps) **or** a [Public Cloud Instance](/links/public-cloud/public-cloud) with a Windows distribution
+- a [Dedicated Server](/links/bare-metal/bare-metal) **or** a [VPS](/links/bare-metal/vps) **or** a [Public Cloud Instance](/links/public-cloud/public-cloud)
 - a [HA-NAS solution](/links/storage/nas-ha)
 
 ### Settings for Windows

From b84181cfe101dde02b433262dad59948d1aebba2 Mon Sep 17 00:00:00 2001
From: Cyril MARCHAL <139960138+CyrilmarchalP17@users.noreply.github.com>
Date: Wed, 8 Oct 2025 11:07:48 +0200
Subject: [PATCH 08/16] Update Guide NAS-HA

Modification of prerequisites
---
 .../file_storage/ha_nas/nas_cifs/guide.fr-fr.md                 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-fr.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-fr.md
index 126e7f4ed1c..d6cfbd3f755 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-fr.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-fr.md
@@ -10,7 +10,7 @@ Configurez et montez votre espace de stockage NAS-HA OVHcloud via le protocole C
 
 ## Prérequis
 
-- Un [serveur dédié](/links/bare-metal/bare-metal) **ou** un [VPS](/links/bare-metal/vps) **ou** une [instance Public Cloud](/links/public-cloud/public-cloud) avec une distribution Windows.
+- Un [serveur dédié](/links/bare-metal/bare-metal) **ou** un [VPS](/links/bare-metal/vps) **ou** une [instance Public Cloud](/links/public-cloud/public-cloud).
 - Une offre [NAS-HA](/links/storage/nas-ha).
 
 ### Configuration pour Windows

From d48de17c935e8b37a7fa69685f9766f42fcd14d3 Mon Sep 17 00:00:00 2001
From: Cyril MARCHAL <139960138+CyrilmarchalP17@users.noreply.github.com>
Date: Wed, 8 Oct 2025 11:49:29 +0200
Subject: [PATCH 09/16] Update Guide NAS-HA

Add information about Windows clients
---
 .../ha_nas/nas_nfs/guide.fr-fr.md             | 20 ++++++++++++++++++-
 1 file changed, 19 insertions(+), 1 deletion(-)

diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.fr-fr.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.fr-fr.md
index 95c647a2b39..f99cddd24f8 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.fr-fr.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.fr-fr.md
@@ -1,7 +1,7 @@
 ---
 title: Montage d'un NAS-HA via partage NFS
 excerpt: Découvrez comment vous connecter à votre NAS-HA en utilisant un partage NFS
-updated: 2024-11-08
+updated: 2025-10-08
 ---
 
 ## Objectif
@@ -134,6 +134,24 @@ root@server:~$ sudo mount -t nfs 10.1.1.1:/zpool-123456/partition01 /mount/ha_na
 
 Vous pouvez maintenant accéder à votre partition montée dans le dossier spécifié.
 
+### Microsoft Windows - Particularités
+
+Assurez-vous que l'utilisateur Windows qui est utilisé pour accéder à votre NAS-HA dispose de droits suffisants.
+
+En effet, le couple UID/GID doit être configuré à 0 (droit unix root).
+
+Si ce n'est pas le cas, vous aurez des erreurs d'accès à votre NAS-HA car, lorsque NFS est autorisé sur une machine Windows, un utilisateur UNIX est créé avec l'UID et le GID par défaut à -2 (ou 4294967294).
+
+Comme solution de contournement, l'UID et le GID peuvent être forcés à 0 sur la machine Windows qui accède à votre NAS-HA.
+
+- Démarrez l'éditeur de registre sur la machine cliente.
+- Localisez `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
+- Créez deux valeurs DWORD, à savoir AnonymousUid et AnonymousGid.
+- Définissez ces valeurs sur l'UID et le GID à 0.
+- Redémarrez le service NFS sur la machine cliente.
+
+Toutes les options de montage sont disponibles sur le site de Microsoft : https://learn.microsoft.com/fr-fr/windows-server/administration/windows-commands/mount
+
 ### Proxmox
 
 Dans l’interface d’administration Proxmox, cliquez sur `Storage`{.action} dans le menu vertical.

From 36da5481bb64f8a6f11384295b8eb808d1407e14 Mon Sep 17 00:00:00 2001
From: Cyril MARCHAL <139960138+CyrilmarchalP17@users.noreply.github.com>
Date: Wed, 8 Oct 2025 11:54:46 +0200
Subject: [PATCH 10/16] Update Guide NAS-HA - EN

Addition specification for the windows clients
---
 .../ha_nas/nas_nfs/guide.en-gb.md             | 24 ++++++++++++++++++-
 1 file changed, 23 insertions(+), 1 deletion(-)

diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-gb.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-gb.md
index b351852f39d..998b8db235c 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-gb.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-gb.md
@@ -1,7 +1,7 @@
 ---
 title: Mounting HA-NAS via NFS share
 excerpt: Find out how to connect to your HA-NAS using an NFS share
-updated: 2024-11-08
+updated: 2025-10-08
 ---
 
 ## Objective 
@@ -133,6 +133,28 @@ root@server:~$ sudo mount -t nfs 10.1.1.1:/zpool-123456/partition01 /mount/ha_na
 
 You can now access your mounted partition at the specified folder.
 
+### Microsoft Windows - specificity
+
+Make sure that the Windows user who is used to access your NAS-HA has sufficient rights.
+
+Indeed, the UID/GID pair must be configured to 0 (right unix root).
+
+If this is not the case, you will have access errors to your NAS-HA because, when NFS is authorised on a Windows machine, a UNIX user is created with the default UID and GID at -2 (or 4294967294).
+
+As a workaround, the UID and GID can be forced to 0 on the Windows machine that accesses your NAS-HA.
+
+- Start the registry editor on the client machine.
+
+- Locate `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
+
+- Create two DWORD values, namely AnonymousUid and AnonymousGid.
+
+- Set these values on the UID and the GID to 0.
+
+- Restart the NFS service on the client machine.
+
+All mounting options are available on the Microsoft website: https://learn.microsoft.com/fr-fr/windows-server/administration/windows-commands/mount
+
 ### Proxmox
 
 In the Proxmox administration interface, click on `Storage`{.action} in the vertical menu.

From 127f912934120a8a1be85d454b5ddcc27002dd9d Mon Sep 17 00:00:00 2001
From: benchbzh <benoit.chuchla@ovhcloud.com>
Date: Wed, 8 Oct 2025 16:40:59 +0200
Subject: [PATCH 11/16] proofreading & translations

---
 .../services_backup_storage/guide.de-de.md    |  8 ++-
 .../services_backup_storage/guide.en-asia.md  |  8 ++-
 .../services_backup_storage/guide.en-au.md    |  8 ++-
 .../services_backup_storage/guide.en-ca.md    |  8 ++-
 .../services_backup_storage/guide.en-gb.md    |  8 ++-
 .../services_backup_storage/guide.en-ie.md    |  8 ++-
 .../services_backup_storage/guide.en-sg.md    |  8 ++-
 .../services_backup_storage/guide.en-us.md    |  8 ++-
 .../services_backup_storage/guide.es-es.md    |  8 ++-
 .../services_backup_storage/guide.es-us.md    |  8 ++-
 .../services_backup_storage/guide.fr-ca.md    |  8 ++-
 .../services_backup_storage/guide.fr-fr.md    |  8 ++-
 .../services_backup_storage/guide.it-it.md    |  8 ++-
 .../services_backup_storage/guide.pl-pl.md    |  8 ++-
 .../services_backup_storage/guide.pt-pt.md    |  8 ++-
 .../ha_nas/nas_cifs/guide.de-de.md            | 62 ++++++++++++++-----
 .../ha_nas/nas_cifs/guide.en-asia.md          | 54 +++++++++++++---
 .../ha_nas/nas_cifs/guide.en-au.md            | 54 +++++++++++++---
 .../ha_nas/nas_cifs/guide.en-ca.md            | 54 +++++++++++++---
 .../ha_nas/nas_cifs/guide.en-gb.md            | 26 +++++---
 .../ha_nas/nas_cifs/guide.en-ie.md            | 54 +++++++++++++---
 .../ha_nas/nas_cifs/guide.en-sg.md            | 54 +++++++++++++---
 .../ha_nas/nas_cifs/guide.en-us.md            | 54 +++++++++++++---
 .../ha_nas/nas_cifs/guide.es-es.md            | 58 +++++++++++++----
 .../ha_nas/nas_cifs/guide.es-us.md            | 58 +++++++++++++----
 .../ha_nas/nas_cifs/guide.fr-ca.md            | 56 ++++++++++++++---
 .../ha_nas/nas_cifs/guide.fr-fr.md            | 20 +++---
 .../ha_nas/nas_cifs/guide.it-it.md            | 58 +++++++++++++----
 .../ha_nas/nas_cifs/guide.pl-pl.md            | 58 +++++++++++++----
 .../ha_nas/nas_cifs/guide.pt-pt.md            | 54 +++++++++++++---
 .../file_storage/ha_nas/nas_cifs/meta.yaml    |  3 +-
 .../ha_nas/nas_nfs/guide.de-de.md             | 20 +++++-
 .../ha_nas/nas_nfs/guide.en-asia.md           | 20 +++++-
 .../ha_nas/nas_nfs/guide.en-au.md             | 20 +++++-
 .../ha_nas/nas_nfs/guide.en-ca.md             | 20 +++++-
 .../ha_nas/nas_nfs/guide.en-gb.md             | 20 +++---
 .../ha_nas/nas_nfs/guide.en-ie.md             | 20 +++++-
 .../ha_nas/nas_nfs/guide.en-sg.md             | 20 +++++-
 .../ha_nas/nas_nfs/guide.en-us.md             | 20 +++++-
 .../ha_nas/nas_nfs/guide.es-es.md             | 20 +++++-
 .../ha_nas/nas_nfs/guide.es-us.md             | 20 +++++-
 .../ha_nas/nas_nfs/guide.fr-ca.md             | 20 +++++-
 .../ha_nas/nas_nfs/guide.fr-fr.md             | 18 +++---
 .../ha_nas/nas_nfs/guide.it-it.md             | 20 +++++-
 .../ha_nas/nas_nfs/guide.pl-pl.md             | 20 +++++-
 .../ha_nas/nas_nfs/guide.pt-pt.md             | 20 +++++-
 46 files changed, 984 insertions(+), 211 deletions(-)

diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.de-de.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.de-de.md
index 1ebbdaf6915..30a47177015 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.de-de.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.de-de.md
@@ -1,7 +1,7 @@
 ---
 title: 'Backup Storage auf einem Dedicated Server verwenden'
 excerpt: 'Erfahren Sie hier, wie Sie zusätzlichen Speicherplatz aktivieren und auf diesen zugreifen'
-updated: 2025-07-21
+updated: 2025-10-08
 ---
 
 ## Ziel
@@ -345,7 +345,11 @@ System error 1272 has occurred.
 You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
 ```
 
-Dieser Fehler sollte durch Bearbeiten der Windows-Registrierung lösbar sein: Öffnen Sie das Windows-Dienstprogramm *regedit*, und suchen Sie nach dem Eintrag `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`. Setzen Sie den Wert von `AllowInsecureGuestAuth` auf "1". Weitere Informationen zu diesem Thema finden Sie auf den [Microsoft Support-Seiten](https://answer.microsoft.com/en-us/windows/forum/all/you-cant-access-this-shared-folder-because-your/01d15775-2cbe-41f8-beb8-84ce588b34ab).
+> [!primary]
+>
+> Dieser Fehler sollte durch Bearbeiten der Windows-Registrierung lösbar sein: Öffnen Sie das Windows-Dienstprogramm *regedit*, und suchen Sie nach dem Eintrag `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Setzen Sie den Wert von `AllowInsecureGuestAuth` auf „1“.<br>
+> Weitere Informationen zu diesem Thema finden Sie auf den [Microsoft Support-Seiten](https://learn.microsoft.com/de-de/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ##### Linux
 
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-asia.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-asia.md
index 2b48a1189b9..2878db9ef77 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-asia.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-asia.md
@@ -1,7 +1,7 @@
 ---
 title: How to use the backup storage on a dedicated server
 excerpt: 'Find out how to enable and access your additional storage space'
-updated: 2025-07-21
+updated: 2025-10-08
 ---
 
 ## Objective
@@ -341,7 +341,11 @@ System error 1272 has occurred.
 You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
 ```
 
-This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`. Set the value of `AllowInsecureGuestAuth` to "1". You can find more information on this issue on the [Microsoft support pages](https://answers.microsoft.com/en-us/windows/forum/all/you-cant-access-this-shared-folder-because-your/01d15775-2cbe-41f8-beb8-84ce588b34ab).
+> [!primary]
+>
+> This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Set the value of `AllowInsecureGuestAuth` to "1".<br>
+> You can find more information on this issue on the [Microsoft support pages](https://learn.microsoft.com/en-in/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ##### Linux
 
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-au.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-au.md
index 5030385f4be..5d6e4e292f4 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-au.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-au.md
@@ -1,7 +1,7 @@
 ---
 title: How to use the backup storage on a dedicated server
 excerpt: 'Find out how to enable and access your additional storage space'
-updated: 2025-07-21
+updated: 2025-10-08
 ---
 
 ## Objective
@@ -339,7 +339,11 @@ System error 1272 has occurred.
 You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
 ```
 
-This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`. Set the value of `AllowInsecureGuestAuth` to "1". You can find more information on this issue on the [Microsoft support pages](https://answers.microsoft.com/en-us/windows/forum/all/you-cant-access-this-shared-folder-because-your/01d15775-2cbe-41f8-beb8-84ce588b34ab).
+> [!primary]
+>
+> This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Set the value of `AllowInsecureGuestAuth` to "1".<br>
+> You can find more information on this issue on the [Microsoft support pages](https://learn.microsoft.com/en-au/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ##### Linux
 
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-ca.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-ca.md
index 5030385f4be..153c9a282d2 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-ca.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-ca.md
@@ -1,7 +1,7 @@
 ---
 title: How to use the backup storage on a dedicated server
 excerpt: 'Find out how to enable and access your additional storage space'
-updated: 2025-07-21
+updated: 2025-10-08
 ---
 
 ## Objective
@@ -339,7 +339,11 @@ System error 1272 has occurred.
 You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
 ```
 
-This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`. Set the value of `AllowInsecureGuestAuth` to "1". You can find more information on this issue on the [Microsoft support pages](https://answers.microsoft.com/en-us/windows/forum/all/you-cant-access-this-shared-folder-because-your/01d15775-2cbe-41f8-beb8-84ce588b34ab).
+> [!primary]
+>
+> This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Set the value of `AllowInsecureGuestAuth` to "1".<br>
+> You can find more information on this issue on the [Microsoft support pages](https://learn.microsoft.com/en-ca/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ##### Linux
 
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-gb.md
index 06f164f62ee..1abd70effe3 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-gb.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-gb.md
@@ -1,7 +1,7 @@
 ---
 title: How to use the backup storage on a dedicated server
 excerpt: 'Find out how to enable and access your additional storage space'
-updated: 2025-10-07
+updated: 2025-10-08
 ---
 
 ## Objective
@@ -339,7 +339,11 @@ System error 1272 has occurred.
 You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
 ```
 
-This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`. Set the value of `AllowInsecureGuestAuth` to "1". You can find more information on this issue on the [Microsoft support pages](https://learn.microsoft.com/en-gb/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+> [!primary]
+>
+> This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Set the value of `AllowInsecureGuestAuth` to "1".<br>
+> You can find more information on this issue on the [Microsoft support pages](https://learn.microsoft.com/en-gb/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ##### Linux
 
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-ie.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-ie.md
index 5030385f4be..886da71d61f 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-ie.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-ie.md
@@ -1,7 +1,7 @@
 ---
 title: How to use the backup storage on a dedicated server
 excerpt: 'Find out how to enable and access your additional storage space'
-updated: 2025-07-21
+updated: 2025-10-08
 ---
 
 ## Objective
@@ -339,7 +339,11 @@ System error 1272 has occurred.
 You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
 ```
 
-This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`. Set the value of `AllowInsecureGuestAuth` to "1". You can find more information on this issue on the [Microsoft support pages](https://answers.microsoft.com/en-us/windows/forum/all/you-cant-access-this-shared-folder-because-your/01d15775-2cbe-41f8-beb8-84ce588b34ab).
+> [!primary]
+>
+> This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Set the value of `AllowInsecureGuestAuth` to "1".<br>
+> You can find more information on this issue on the [Microsoft support pages](https://learn.microsoft.com/en-ie/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ##### Linux
 
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-sg.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-sg.md
index 5030385f4be..92b1ca21a13 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-sg.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-sg.md
@@ -1,7 +1,7 @@
 ---
 title: How to use the backup storage on a dedicated server
 excerpt: 'Find out how to enable and access your additional storage space'
-updated: 2025-07-21
+updated: 2025-10-08
 ---
 
 ## Objective
@@ -339,7 +339,11 @@ System error 1272 has occurred.
 You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
 ```
 
-This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`. Set the value of `AllowInsecureGuestAuth` to "1". You can find more information on this issue on the [Microsoft support pages](https://answers.microsoft.com/en-us/windows/forum/all/you-cant-access-this-shared-folder-because-your/01d15775-2cbe-41f8-beb8-84ce588b34ab).
+> [!primary]
+>
+> This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Set the value of `AllowInsecureGuestAuth` to "1".<br>
+> You can find more information on this issue on the [Microsoft support pages](https://learn.microsoft.com/en-sg/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ##### Linux
 
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-us.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-us.md
index 5030385f4be..e0345d2d353 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-us.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-us.md
@@ -1,7 +1,7 @@
 ---
 title: How to use the backup storage on a dedicated server
 excerpt: 'Find out how to enable and access your additional storage space'
-updated: 2025-07-21
+updated: 2025-10-08
 ---
 
 ## Objective
@@ -339,7 +339,11 @@ System error 1272 has occurred.
 You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
 ```
 
-This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`. Set the value of `AllowInsecureGuestAuth` to "1". You can find more information on this issue on the [Microsoft support pages](https://answers.microsoft.com/en-us/windows/forum/all/you-cant-access-this-shared-folder-because-your/01d15775-2cbe-41f8-beb8-84ce588b34ab).
+> [!primary]
+>
+> This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Set the value of `AllowInsecureGuestAuth` to "1".<br>
+> You can find more information on this issue on the [Microsoft support pages](https://learn.microsoft.com/en-us/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ##### Linux
 
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.es-es.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.es-es.md
index 124fa33a5a9..9063fad6297 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.es-es.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.es-es.md
@@ -1,7 +1,7 @@
 ---
 title: 'Utilizar Backup Storage en un servidor dedicado'
 excerpt: 'Cómo activar y acceder al espacio de almacenamiento adicional'
-updated: 2025-07-21
+updated: 2025-10-08
 ---
 
 ## Objetivo
@@ -345,7 +345,11 @@ System error 1272 has occurred.
 You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
 ```
 
-Este problema se puede solucionar editando el Registro de Windows: abra la utilidad Windows *regedit* y busque la entrada `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`. Establezca el valor de `AllowInsecureGuestAuth` en "1". Más información sobre este tema en [páginas de soporte técnico de Microsoft](https://answer.microsoft.com/en-us/windows/forum/all/you-cant-access-this-shared-folder-because-your/01d15775-2cbe-41f8-beb8-84ce588b34ab).
+> [!primary]
+>
+> Este problema se puede solucionar editando el Registro de Windows: abra la utilidad Windows *regedit* y busque la entrada `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Establezca el valor de `AllowInsecureGuestAuth` en "1".<br>
+> Más información sobre este tema en [páginas de soporte técnico de Microsoft](https://learn.microsoft.com/es-es/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 
 ##### Linux
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.es-us.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.es-us.md
index 124fa33a5a9..cb0378fadc7 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.es-us.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.es-us.md
@@ -1,7 +1,7 @@
 ---
 title: 'Utilizar Backup Storage en un servidor dedicado'
 excerpt: 'Cómo activar y acceder al espacio de almacenamiento adicional'
-updated: 2025-07-21
+updated: 2025-10-08
 ---
 
 ## Objetivo
@@ -345,7 +345,11 @@ System error 1272 has occurred.
 You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
 ```
 
-Este problema se puede solucionar editando el Registro de Windows: abra la utilidad Windows *regedit* y busque la entrada `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`. Establezca el valor de `AllowInsecureGuestAuth` en "1". Más información sobre este tema en [páginas de soporte técnico de Microsoft](https://answer.microsoft.com/en-us/windows/forum/all/you-cant-access-this-shared-folder-because-your/01d15775-2cbe-41f8-beb8-84ce588b34ab).
+> [!primary]
+>
+> Este problema se puede solucionar editando el Registro de Windows: abra la utilidad Windows *regedit* y busque la entrada `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Establezca el valor de `AllowInsecureGuestAuth` en "1".<br>
+> Más información sobre este tema en [páginas de soporte técnico de Microsoft](https://learn.microsoft.com/es-mx/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 
 ##### Linux
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.fr-ca.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.fr-ca.md
index 21ef095849c..6dd71123fcc 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.fr-ca.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.fr-ca.md
@@ -1,7 +1,7 @@
 ---
 title: 'Utiliser Backup Storage sur un serveur dédié'
 excerpt: 'Découvrez comment activer et accéder à votre espace de stockage supplémentaire'
-updated: 2025-07-21
+updated: 2025-10-08
 ---
 
 ## Objectif
@@ -346,7 +346,11 @@ System error 1272 has occurred.
 You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
 ```
 
-Ce problème peut être résolu en modifiant le Registre Windows : ouvrez l'utilitaire Windows *regedit* et recherchez l'entrée `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`. Définissez la valeur de `AllowInsecureGuestAuth` sur « 1 ». Retrouvez plus d'informations sur ce sujet sur les [pages de support Microsoft](https://answer.microsoft.com/en-us/windows/forum/all/you-cant-access-this-shared-folder-because-your/01d15775-2cbe-41f8-beb8-84ce588b34ab).
+> [!primary]
+>
+> Ce problème peut être résolu en modifiant le Registre Windows : ouvrez l'utilitaire Windows *regedit* et recherchez l'entrée `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Définissez la valeur de `AllowInsecureGuestAuth` sur « 1 ».<br>
+> Retrouvez plus d'informations sur ce sujet sur les [pages de support Microsoft](https://learn.microsoft.com/fr-ca/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ##### Linux
 
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.fr-fr.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.fr-fr.md
index 034e6e19402..5ca68e16796 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.fr-fr.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.fr-fr.md
@@ -1,7 +1,7 @@
 ---
 title: 'Utiliser Backup Storage sur un serveur dédié'
 excerpt: 'Découvrez comment activer et accéder à votre espace de stockage supplémentaire'
-updated: 2025-10-07
+updated: 2025-10-08
 ---
 
 ## Objectif
@@ -346,7 +346,11 @@ System error 1272 has occurred.
 You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
 ```
 
-Ce problème peut être résolu en modifiant le Registre Windows : ouvrez l'utilitaire Windows *regedit* et recherchez l'entrée `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`. Définissez la valeur de `AllowInsecureGuestAuth` sur « 1 ». Retrouvez plus d'informations sur ce sujet sur les [pages de support Microsoft](https://learn.microsoft.com/fr-fr/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3?tabs=group-policy).
+> [!primary]
+>
+> Ce problème peut être résolu en modifiant le Registre Windows : ouvrez l'utilitaire Windows *regedit* et recherchez l'entrée `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Définissez la valeur de `AllowInsecureGuestAuth` sur « 1 ».<br>
+> Retrouvez plus d'informations sur ce sujet sur les [pages de support Microsoft](https://learn.microsoft.com/fr-fr/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3?tabs=group-policy).
 
 ##### Linux
 
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.it-it.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.it-it.md
index 187e4a55295..391aa1b1049 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.it-it.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.it-it.md
@@ -1,7 +1,7 @@
 ---
 title: Utilizzare il Backup Storage su un server dedicato
 excerpt: Come attivare e accedere allo spazio di storage aggiuntivo
-updated: 2025-07-21
+updated: 2025-10-08
 ---
 
 ## Obiettivo
@@ -345,7 +345,11 @@ System error 1272 has occurred.
 You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
 ```
 
-Questo problema può essere risolto modificando il Registro di sistema di Windows: aprire l'utilità Windows *regedit* e cercare la voce `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`. Impostare il valore di `AllowInsecureGuestAuth` su "1". Per maggiori informazioni al riguardo, visitare le [pagine di supporto Microsoft](https://answer.microsoft.com/en-us/windows/forum/all/you-cant-access-this-shared-folder-because-your/01d15775-2cbe-41f8-beb8-84ce588b34ab).
+> [!primary]
+>
+> Questo problema può essere risolto modificando il Registro di sistema di Windows: aprire l'utilità Windows *regedit* e cercare la voce `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Impostare il valore di `AllowInsecureGuestAuth` su "1".<br>
+> Per maggiori informazioni al riguardo, visitare le [pagine di supporto Microsoft](https://learn.microsoft.com/it-it/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ##### Linux
 
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.pl-pl.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.pl-pl.md
index 3df3486935f..45bfa1359a6 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.pl-pl.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.pl-pl.md
@@ -1,7 +1,7 @@
 ---
 title: 'Korzystanie z Backup Storage na serwerze dedykowanym'
 excerpt: 'Dowiedz się, jak aktywować i uzyskać dostęp do dodatkowej przestrzeni dyskowej'
-updated: 2025-07-21
+updated: 2025-10-08
 ---
 
 ## Wprowadzenie
@@ -347,7 +347,11 @@ System error 1272 has occurred.
 You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
 ```
 
-Ten problem można rozwiązać, modyfikując rejestr systemu Windows: otwórz narzędzie systemu Windows *regedit* i wyszukaj wpis `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`. Ustaw dla parametru `AllowInsecureGuestAuth` wartość "1". Więcej informacji na ten temat można znaleźć na [stronach pomocy technicznej firmy Microsoft](https://answer.microsoft.com/en-us/windows/forum/all/you-cant-access-this-shared-folder-because-your/01d15775-2cbe-41f8-beb8-84ce588b34ab).
+> [!primary]
+>
+> Ten problem można rozwiązać, modyfikując rejestr systemu Windows: otwórz narzędzie systemu Windows *regedit* i wyszukaj wpis `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Ustaw dla parametru `AllowInsecureGuestAuth` wartość "1".<br>
+> Więcej informacji na ten temat można znaleźć na [stronach pomocy technicznej firmy Microsoft](https://learn.microsoft.com/pl-pl/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ##### Linux
 
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.pt-pt.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.pt-pt.md
index ee4c74a9d6b..13f68b78708 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.pt-pt.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.pt-pt.md
@@ -1,7 +1,7 @@
 ---
 title: 'Utilizar o Backup Storage num servidor dedicado'
 excerpt: 'Saiba como ativar e aceder ao espaço de armazenamento adicional'
-updated: 2025-07-21
+updated: 2025-10-08
 ---
 
 ## Objetivo
@@ -345,7 +345,11 @@ System error 1272 has occurred.
 You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
 ```
 
-É possível resolver este problema alterando o registo do Windows: abra o utilitário Windows *regedit* e procure a entrada `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`. Defina o valor de `AllowInsecureGuestAuth` como "1". Encontre mais informações sobre este assumpto nas [páginas de suporte da Microsoft](https://answer.microsoft.com/en-us/windows/forum/all/you-cant-access-this-shared-folder-because-your/01d15775-2cbe-41f8-beb8-84ce588b34ab).
+> [!primary]
+>
+> É possível resolver este problema alterando o registo do Windows: abra o utilitário Windows *regedit* e procure a entrada `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Defina o valor de `AllowInsecureGuestAuth` como "1".<br>
+> Encontre mais informações sobre este assumpto nas [páginas de suporte da Microsoft](https://learn.microsoft.com/pt-pt/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ##### Linux
 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.de-de.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.de-de.md
index e8c86d3917e..fd593b0e073 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.de-de.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.de-de.md
@@ -1,23 +1,21 @@
 ---
-title: HA-NAS auf Windows Server über CIFS mounten
-excerpt: Erfahren Sie hier, wie Sie Ihr HA-NAS unter Windows Server über CIFS mounten können
-updated: 2021-11-22
+title: Mounten Sie Ihr HA-NAS über eine CIFS-Freigabe
+excerpt: Diese Anleitung zeigt Ihnen, wie Sie Ihr HA-NAS über das CIFS-Protokoll einbinden können
+updated: 2025-10-08
 ---
 
-> [!primary]
-> Diese Übersetzung wurde durch unseren Partner SYSTRAN automatisch erstellt. In manchen Fällen können ungenaue Formulierungen verwendet worden sein, z.B. bei der Beschriftung von Schaltflächen oder technischen Details. Bitte ziehen Sie im Zweifelsfall die englische oder französische Fassung der Anleitung zu Rate. Möchten Sie mithelfen, diese Übersetzung zu verbessern? Dann nutzen Sie dazu bitte den Button "Beitragen" auf dieser Seite.
->
-
 ## Ziel
 
-Konfigurieren und mounten Sie einen OVHcloud HA-NAS-Speicherraum auf Ihrem Windows Server mit CIFS.
+Konfigurieren und mounten Sie einen OVHcloud HA-NAS-Speicherplatz mithilfe des CIFS-Protokolls.
 
 ## Voraussetzungen
 
-- Sie haben einen [Dedicated Server](/links/bare-metal/bare-metal) **oder** einen [VPS](/links/bare-metal/vps) **oder** eine [Public Cloud Instanz](/links/public-cloud/public-cloud) mit einer Windows-Distribution in Ihrem Kunden-Account.
+- Sie haben einen [Dedicated Server](/links/bare-metal/bare-metal) **oder** einen [VPS](/links/bare-metal/vps) **oder** eine [Public Cloud Instanz](/links/public-cloud/public-cloud).
 - Sie verfügen über eine [HA-NAS Lösung](/links/storage/nas-ha).
 
-### Einstellungen
+## In der praktischen Anwendung
+
+### Einstellungen für Windows
 
 - **Windows Server 2008**: Klicken Sie auf `Start`{.action}, `All the programs`{.action}, `Accessories`{.action}, `Command prompt`{.action}.
 - **Windows Server 2012**: Klicken Sie auf das `Windows PowerShell`{.action} Icon am unteren Bildschirmrand in der Taskleiste.
@@ -26,15 +24,15 @@ Konfigurieren und mounten Sie einen OVHcloud HA-NAS-Speicherraum auf Ihrem Windo
 
 Führen Sie dann den folgenden Befehl aus:
 
-```powershell
+```bash
 net use z: \\CIFS_SERVER_IP\CIFS_PATH
 ```
 
-### Beispiele
+#### Beispiele
 
 - CIFS Mount für HA-NAS:
 
-```powershell
+```bash
 net use z: \\10.16.101.8\zpool-000206_PARTITION_NAME_1
 ```
 
@@ -43,10 +41,46 @@ net use z: \\10.16.101.8\zpool-000206_PARTITION_NAME_1
 > Der SMB/CIFS Benutzer ist `nobody`. Das Ändern von Berechtigungen mit diesem Benutzer kann Konflikte mit bestehenden NFS-Berechtigungen verursachen.
 >
 
+Die folgende Fehlermeldung kann angezeigt werden:
+
+```console
+System error 1272 has occurred.
+
+You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
+```
+
+> [!primary]
+>
+> Dieser Fehler sollte durch Bearbeiten der Windows-Registrierung lösbar sein: Öffnen Sie das Windows-Dienstprogramm *regedit*, und suchen Sie nach dem Eintrag `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Setzen Sie den Wert von `AllowInsecureGuestAuth` auf „1“.<br>
+> Weitere Informationen zu diesem Thema finden Sie auf den [Microsoft Support-Seiten](https://learn.microsoft.com/de-de/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+
+### Einstellungen für Linux
+
+Öffnen Sie eine SSH-Verbindung zu Ihrem Server und geben Sie den folgenden Befehl ein:
+
+```sh
+mount -t cifs -o uid=root,gid=100,dir_mode=0700,username=root,password= //IP_SERVEUR_CIFS/CHEMIN_CIFS /mnt/FolderMount
+```
+
+> [!warning]
+>
+> Um Freigaben über den Hostnamen (anstelle der IP-Adresse) zu mounten, ist das Dienstprogramm `mount.cifs` erforderlich. Es ist in der Regel Teil des Pakets `cifs-utils`.
+>
+> `mount.cifs` ist ein Wrapper, der Hostnamen auflöst und den Parameter `ip=` zu den an den Kernel übermittelten Mount-Parametern hinzufügt.
+>
+> Ohne `mount.cifs` führen Versuche, über den Hostnamen zu mounten, zu folgendem Fehler:
+>
+> ```text
+> mount: /mnt/FolderMount: mount(2) system call failed: No route to host.
+>        dmesg(1) may have more information after failed mount system call.
+> ```
+>
+
 ## Weiterführende Informationen
 
 [Häufig gestellte Fragen zu HA-NAS](/pages/storage_and_backup/file_storage/ha_nas/nas_faq)
 
 Wenn Sie Schulungen oder technische Unterstützung bei der Implementierung unserer Lösungen benötigen, wenden Sie sich an Ihren Vertriebsmitarbeiter oder klicken Sie auf [diesen Link](/links/professional-services), um einen Kostenvoranschlag zu erhalten und eine persönliche Analyse Ihres Projekts durch unsere Experten des Professional Services Teams anzufordern.
 
-Für den Austausch mit unserer Community gehen Sie auf <https://community.ovh.com/en/>.
+Treten Sie unserer [User Community](/links/community) bei.
\ No newline at end of file
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-asia.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-asia.md
index 6dfbeb64426..f1fc4ec4068 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-asia.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-asia.md
@@ -1,19 +1,21 @@
 ---
-title: Mount your HA-NAS on Windows Server via CIFS
-excerpt: This guide shows you how to mount your HA-NAS on Windows Server via CIFS.
-updated: 2021-11-22
+title: Mount your HA-NAS via a CIFS share
+excerpt: This guide shows you how to mount your HA-NAS using CIFS protocol
+updated: 2025-10-08
 ---
 
 ## Objective
 
-Configure and mount an OVHcloud HA-NAS storage space on your Windows Server using CIFS.
+Configure and mount an OVHcloud HA-NAS storage space using CIFS protocol.
 
 ## Requirements
 
-- a [Dedicated Server](/links/bare-metal/bare-metal) **or** a [VPS](/links/bare-metal/vps) **or** a [Public Cloud Instance](/links/public-cloud/public-cloud) with a Windows distribution
+- a [Dedicated Server](/links/bare-metal/bare-metal) **or** a [VPS](/links/bare-metal/vps) **or** a [Public Cloud Instance](/links/public-cloud/public-cloud)
 - a [HA-NAS solution](/links/storage/nas-ha)
 
-### Settings
+## Instructions
+
+### Settings for Windows
 
 - **Windows Server 2008**: Click on the menu `Start`{.action} > `All the programs`{.action} > `Accessories`{.action} > `Command prompt`{.action}.
 - **Windows Server 2012**: Click the `Windows PowerShell`{.action} icon at the bottom of the screen in the taskbar.
@@ -26,7 +28,7 @@ Then run the following command:
 net use z: \\CIFS_SERVER_IP\CIFS_PATH
 ```
 
-### Example
+#### Example
 
 - CIFS mounting for a NAS-HA:
 
@@ -39,10 +41,46 @@ net use z: \\10.16.101.8\zpool-000206_PARTITION_NAME_1
 > The SMB/CIFS user is `nobody`. Changing permissions with this user may generate conflicts with existing NFS permissions. 
 > 
 
+The following error message may appear:
+
+```console
+System error 1272 has occurred.
+
+You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
+```
+
+> [!primary]
+>
+> This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Set the value of `AllowInsecureGuestAuth` to "1".<br>
+> You can find more information on this issue on the [Microsoft support pages](https://learn.microsoft.com/en-in/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+
+### Settings for Linux
+
+Open an SSH connection to your server and type the following command:
+
+```sh
+mount -t cifs -o uid=root,gid=100,dir_mode=0700,username=root,password= //IP_SERVEUR_CIFS/CHEMIN_CIFS /mnt/FolderMount
+```
+
+> [!warning]
+>
+> In order to mount shares by host name (as opposed to IP addresses), the `mount.cifs` utility is required. It is usually part of the `cifs-utils` package.
+>
+> `mount.cifs` is a wrapper that resolves host names and adds the parameter `ip=` to the mount parameters transmitted to the kernel.
+>
+> Without `mount.cifs`, attempts to mount by host name will result in the following error:
+>
+> ```text
+> mount: /mnt/FolderMount: mount(2) system call failed: No route to host.
+>        dmesg(1) may have more information after failed mount system call.
+> ```
+>
+
 ## Go further
 
 [NAS - Frequently Asked Questions](/pages/storage_and_backup/file_storage/ha_nas/nas_faq)
 
 If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project.
 
-Join our community of users on <https://community.ovh.com/en/>.
+Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-au.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-au.md
index 6dfbeb64426..acbf96552de 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-au.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-au.md
@@ -1,19 +1,21 @@
 ---
-title: Mount your HA-NAS on Windows Server via CIFS
-excerpt: This guide shows you how to mount your HA-NAS on Windows Server via CIFS.
-updated: 2021-11-22
+title: Mount your HA-NAS via a CIFS share
+excerpt: This guide shows you how to mount your HA-NAS using CIFS protocol
+updated: 2025-10-08
 ---
 
 ## Objective
 
-Configure and mount an OVHcloud HA-NAS storage space on your Windows Server using CIFS.
+Configure and mount an OVHcloud HA-NAS storage space using CIFS protocol.
 
 ## Requirements
 
-- a [Dedicated Server](/links/bare-metal/bare-metal) **or** a [VPS](/links/bare-metal/vps) **or** a [Public Cloud Instance](/links/public-cloud/public-cloud) with a Windows distribution
+- a [Dedicated Server](/links/bare-metal/bare-metal) **or** a [VPS](/links/bare-metal/vps) **or** a [Public Cloud Instance](/links/public-cloud/public-cloud)
 - a [HA-NAS solution](/links/storage/nas-ha)
 
-### Settings
+## Instructions
+
+### Settings for Windows
 
 - **Windows Server 2008**: Click on the menu `Start`{.action} > `All the programs`{.action} > `Accessories`{.action} > `Command prompt`{.action}.
 - **Windows Server 2012**: Click the `Windows PowerShell`{.action} icon at the bottom of the screen in the taskbar.
@@ -26,7 +28,7 @@ Then run the following command:
 net use z: \\CIFS_SERVER_IP\CIFS_PATH
 ```
 
-### Example
+#### Example
 
 - CIFS mounting for a NAS-HA:
 
@@ -39,10 +41,46 @@ net use z: \\10.16.101.8\zpool-000206_PARTITION_NAME_1
 > The SMB/CIFS user is `nobody`. Changing permissions with this user may generate conflicts with existing NFS permissions. 
 > 
 
+The following error message may appear:
+
+```console
+System error 1272 has occurred.
+
+You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
+```
+
+> [!primary]
+>
+> This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Set the value of `AllowInsecureGuestAuth` to "1".<br>
+> You can find more information on this issue on the [Microsoft support pages](https://learn.microsoft.com/en-au/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+
+### Settings for Linux
+
+Open an SSH connection to your server and type the following command:
+
+```sh
+mount -t cifs -o uid=root,gid=100,dir_mode=0700,username=root,password= //IP_SERVEUR_CIFS/CHEMIN_CIFS /mnt/FolderMount
+```
+
+> [!warning]
+>
+> In order to mount shares by host name (as opposed to IP addresses), the `mount.cifs` utility is required. It is usually part of the `cifs-utils` package.
+>
+> `mount.cifs` is a wrapper that resolves host names and adds the parameter `ip=` to the mount parameters transmitted to the kernel.
+>
+> Without `mount.cifs`, attempts to mount by host name will result in the following error:
+>
+> ```text
+> mount: /mnt/FolderMount: mount(2) system call failed: No route to host.
+>        dmesg(1) may have more information after failed mount system call.
+> ```
+>
+
 ## Go further
 
 [NAS - Frequently Asked Questions](/pages/storage_and_backup/file_storage/ha_nas/nas_faq)
 
 If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project.
 
-Join our community of users on <https://community.ovh.com/en/>.
+Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-ca.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-ca.md
index 6dfbeb64426..bbf50edc7fc 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-ca.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-ca.md
@@ -1,19 +1,21 @@
 ---
-title: Mount your HA-NAS on Windows Server via CIFS
-excerpt: This guide shows you how to mount your HA-NAS on Windows Server via CIFS.
-updated: 2021-11-22
+title: Mount your HA-NAS via a CIFS share
+excerpt: This guide shows you how to mount your HA-NAS using CIFS protocol
+updated: 2025-10-08
 ---
 
 ## Objective
 
-Configure and mount an OVHcloud HA-NAS storage space on your Windows Server using CIFS.
+Configure and mount an OVHcloud HA-NAS storage space using CIFS protocol.
 
 ## Requirements
 
-- a [Dedicated Server](/links/bare-metal/bare-metal) **or** a [VPS](/links/bare-metal/vps) **or** a [Public Cloud Instance](/links/public-cloud/public-cloud) with a Windows distribution
+- a [Dedicated Server](/links/bare-metal/bare-metal) **or** a [VPS](/links/bare-metal/vps) **or** a [Public Cloud Instance](/links/public-cloud/public-cloud)
 - a [HA-NAS solution](/links/storage/nas-ha)
 
-### Settings
+## Instructions
+
+### Settings for Windows
 
 - **Windows Server 2008**: Click on the menu `Start`{.action} > `All the programs`{.action} > `Accessories`{.action} > `Command prompt`{.action}.
 - **Windows Server 2012**: Click the `Windows PowerShell`{.action} icon at the bottom of the screen in the taskbar.
@@ -26,7 +28,7 @@ Then run the following command:
 net use z: \\CIFS_SERVER_IP\CIFS_PATH
 ```
 
-### Example
+#### Example
 
 - CIFS mounting for a NAS-HA:
 
@@ -39,10 +41,46 @@ net use z: \\10.16.101.8\zpool-000206_PARTITION_NAME_1
 > The SMB/CIFS user is `nobody`. Changing permissions with this user may generate conflicts with existing NFS permissions. 
 > 
 
+The following error message may appear:
+
+```console
+System error 1272 has occurred.
+
+You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
+```
+
+> [!primary]
+>
+> This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Set the value of `AllowInsecureGuestAuth` to "1".<br>
+> You can find more information on this issue on the [Microsoft support pages](https://learn.microsoft.com/en-ca/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+
+### Settings for Linux
+
+Open an SSH connection to your server and type the following command:
+
+```sh
+mount -t cifs -o uid=root,gid=100,dir_mode=0700,username=root,password= //IP_SERVEUR_CIFS/CHEMIN_CIFS /mnt/FolderMount
+```
+
+> [!warning]
+>
+> In order to mount shares by host name (as opposed to IP addresses), the `mount.cifs` utility is required. It is usually part of the `cifs-utils` package.
+>
+> `mount.cifs` is a wrapper that resolves host names and adds the parameter `ip=` to the mount parameters transmitted to the kernel.
+>
+> Without `mount.cifs`, attempts to mount by host name will result in the following error:
+>
+> ```text
+> mount: /mnt/FolderMount: mount(2) system call failed: No route to host.
+>        dmesg(1) may have more information after failed mount system call.
+> ```
+>
+
 ## Go further
 
 [NAS - Frequently Asked Questions](/pages/storage_and_backup/file_storage/ha_nas/nas_faq)
 
 If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project.
 
-Join our community of users on <https://community.ovh.com/en/>.
+Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-gb.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-gb.md
index 8c41629f105..17147242552 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-gb.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-gb.md
@@ -1,7 +1,7 @@
 ---
-title: Mount your HA-NAS via CIFS share
-excerpt: This guide shows you how to mount your HA-NAS using CIFS protocol.
-updated: 2025-10-07
+title: Mount your HA-NAS via a CIFS share
+excerpt: This guide shows you how to mount your HA-NAS using CIFS protocol
+updated: 2025-10-08
 ---
 
 ## Objective
@@ -13,6 +13,8 @@ Configure and mount an OVHcloud HA-NAS storage space using CIFS protocol.
 - a [Dedicated Server](/links/bare-metal/bare-metal) **or** a [VPS](/links/bare-metal/vps) **or** a [Public Cloud Instance](/links/public-cloud/public-cloud)
 - a [HA-NAS solution](/links/storage/nas-ha)
 
+## Instructions
+
 ### Settings for Windows
 
 - **Windows Server 2008**: Click on the menu `Start`{.action} > `All the programs`{.action} > `Accessories`{.action} > `Command prompt`{.action}.
@@ -39,7 +41,7 @@ net use z: \\10.16.101.8\zpool-000206_PARTITION_NAME_1
 > The SMB/CIFS user is `nobody`. Changing permissions with this user may generate conflicts with existing NFS permissions. 
 > 
 
-The following error message may appear: 
+The following error message may appear:
 
 ```console
 System error 1272 has occurred.
@@ -47,9 +49,11 @@ System error 1272 has occurred.
 You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
 ```
 
-This problem can be solved by changing the Windows Registry. Open the Windows utility *regedit* and search for the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.
-Set the value of `AllowInsecureGuestAuth` to "1".
-Find more information on this topic on the [Microsoft support pages](https://learn.microsoft.com/en-gb/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+> [!primary]
+>
+> This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Set the value of `AllowInsecureGuestAuth` to "1".<br>
+> You can find more information on this issue on the [Microsoft support pages](https://learn.microsoft.com/en-gb/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ### Settings for Linux
 
@@ -62,14 +66,16 @@ mount -t cifs -o uid=root,gid=100,dir_mode=0700,username=root,password= //IP_SER
 > [!warning]
 >
 > In order to mount shares by host name (as opposed to IP addresses), the `mount.cifs` utility is required. It is usually part of the `cifs-utils` package.
+>
 > `mount.cifs` is a wrapper that resolves host names and adds the parameter `ip=` to the mount parameters transmitted to the kernel.
+>
 > Without `mount.cifs`, attempts to mount by host name will result in the following error:
-
+>
 > ```text
 > mount: /mnt/FolderMount: mount(2) system call failed: No route to host.
 >        dmesg(1) may have more information after failed mount system call.
 > ```
-
+>
 
 ## Go further
 
@@ -77,4 +83,4 @@ mount -t cifs -o uid=root,gid=100,dir_mode=0700,username=root,password= //IP_SER
 
 If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project.
 
-Join our community of users on <https://community.ovh.com/en/>.
+Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-ie.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-ie.md
index 6dfbeb64426..de00e18f494 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-ie.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-ie.md
@@ -1,19 +1,21 @@
 ---
-title: Mount your HA-NAS on Windows Server via CIFS
-excerpt: This guide shows you how to mount your HA-NAS on Windows Server via CIFS.
-updated: 2021-11-22
+title: Mount your HA-NAS via a CIFS share
+excerpt: This guide shows you how to mount your HA-NAS using CIFS protocol
+updated: 2025-10-08
 ---
 
 ## Objective
 
-Configure and mount an OVHcloud HA-NAS storage space on your Windows Server using CIFS.
+Configure and mount an OVHcloud HA-NAS storage space using CIFS protocol.
 
 ## Requirements
 
-- a [Dedicated Server](/links/bare-metal/bare-metal) **or** a [VPS](/links/bare-metal/vps) **or** a [Public Cloud Instance](/links/public-cloud/public-cloud) with a Windows distribution
+- a [Dedicated Server](/links/bare-metal/bare-metal) **or** a [VPS](/links/bare-metal/vps) **or** a [Public Cloud Instance](/links/public-cloud/public-cloud)
 - a [HA-NAS solution](/links/storage/nas-ha)
 
-### Settings
+## Instructions
+
+### Settings for Windows
 
 - **Windows Server 2008**: Click on the menu `Start`{.action} > `All the programs`{.action} > `Accessories`{.action} > `Command prompt`{.action}.
 - **Windows Server 2012**: Click the `Windows PowerShell`{.action} icon at the bottom of the screen in the taskbar.
@@ -26,7 +28,7 @@ Then run the following command:
 net use z: \\CIFS_SERVER_IP\CIFS_PATH
 ```
 
-### Example
+#### Example
 
 - CIFS mounting for a NAS-HA:
 
@@ -39,10 +41,46 @@ net use z: \\10.16.101.8\zpool-000206_PARTITION_NAME_1
 > The SMB/CIFS user is `nobody`. Changing permissions with this user may generate conflicts with existing NFS permissions. 
 > 
 
+The following error message may appear:
+
+```console
+System error 1272 has occurred.
+
+You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
+```
+
+> [!primary]
+>
+> This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Set the value of `AllowInsecureGuestAuth` to "1".<br>
+> You can find more information on this issue on the [Microsoft support pages](https://learn.microsoft.com/en-ie/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+
+### Settings for Linux
+
+Open an SSH connection to your server and type the following command:
+
+```sh
+mount -t cifs -o uid=root,gid=100,dir_mode=0700,username=root,password= //IP_SERVEUR_CIFS/CHEMIN_CIFS /mnt/FolderMount
+```
+
+> [!warning]
+>
+> In order to mount shares by host name (as opposed to IP addresses), the `mount.cifs` utility is required. It is usually part of the `cifs-utils` package.
+>
+> `mount.cifs` is a wrapper that resolves host names and adds the parameter `ip=` to the mount parameters transmitted to the kernel.
+>
+> Without `mount.cifs`, attempts to mount by host name will result in the following error:
+>
+> ```text
+> mount: /mnt/FolderMount: mount(2) system call failed: No route to host.
+>        dmesg(1) may have more information after failed mount system call.
+> ```
+>
+
 ## Go further
 
 [NAS - Frequently Asked Questions](/pages/storage_and_backup/file_storage/ha_nas/nas_faq)
 
 If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project.
 
-Join our community of users on <https://community.ovh.com/en/>.
+Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-sg.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-sg.md
index 6dfbeb64426..62dcf6c64cb 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-sg.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-sg.md
@@ -1,19 +1,21 @@
 ---
-title: Mount your HA-NAS on Windows Server via CIFS
-excerpt: This guide shows you how to mount your HA-NAS on Windows Server via CIFS.
-updated: 2021-11-22
+title: Mount your HA-NAS via a CIFS share
+excerpt: This guide shows you how to mount your HA-NAS using CIFS protocol
+updated: 2025-10-08
 ---
 
 ## Objective
 
-Configure and mount an OVHcloud HA-NAS storage space on your Windows Server using CIFS.
+Configure and mount an OVHcloud HA-NAS storage space using CIFS protocol.
 
 ## Requirements
 
-- a [Dedicated Server](/links/bare-metal/bare-metal) **or** a [VPS](/links/bare-metal/vps) **or** a [Public Cloud Instance](/links/public-cloud/public-cloud) with a Windows distribution
+- a [Dedicated Server](/links/bare-metal/bare-metal) **or** a [VPS](/links/bare-metal/vps) **or** a [Public Cloud Instance](/links/public-cloud/public-cloud)
 - a [HA-NAS solution](/links/storage/nas-ha)
 
-### Settings
+## Instructions
+
+### Settings for Windows
 
 - **Windows Server 2008**: Click on the menu `Start`{.action} > `All the programs`{.action} > `Accessories`{.action} > `Command prompt`{.action}.
 - **Windows Server 2012**: Click the `Windows PowerShell`{.action} icon at the bottom of the screen in the taskbar.
@@ -26,7 +28,7 @@ Then run the following command:
 net use z: \\CIFS_SERVER_IP\CIFS_PATH
 ```
 
-### Example
+#### Example
 
 - CIFS mounting for a NAS-HA:
 
@@ -39,10 +41,46 @@ net use z: \\10.16.101.8\zpool-000206_PARTITION_NAME_1
 > The SMB/CIFS user is `nobody`. Changing permissions with this user may generate conflicts with existing NFS permissions. 
 > 
 
+The following error message may appear:
+
+```console
+System error 1272 has occurred.
+
+You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
+```
+
+> [!primary]
+>
+> This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Set the value of `AllowInsecureGuestAuth` to "1".<br>
+> You can find more information on this issue on the [Microsoft support pages](https://learn.microsoft.com/en-sg/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+
+### Settings for Linux
+
+Open an SSH connection to your server and type the following command:
+
+```sh
+mount -t cifs -o uid=root,gid=100,dir_mode=0700,username=root,password= //IP_SERVEUR_CIFS/CHEMIN_CIFS /mnt/FolderMount
+```
+
+> [!warning]
+>
+> In order to mount shares by host name (as opposed to IP addresses), the `mount.cifs` utility is required. It is usually part of the `cifs-utils` package.
+>
+> `mount.cifs` is a wrapper that resolves host names and adds the parameter `ip=` to the mount parameters transmitted to the kernel.
+>
+> Without `mount.cifs`, attempts to mount by host name will result in the following error:
+>
+> ```text
+> mount: /mnt/FolderMount: mount(2) system call failed: No route to host.
+>        dmesg(1) may have more information after failed mount system call.
+> ```
+>
+
 ## Go further
 
 [NAS - Frequently Asked Questions](/pages/storage_and_backup/file_storage/ha_nas/nas_faq)
 
 If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project.
 
-Join our community of users on <https://community.ovh.com/en/>.
+Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-us.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-us.md
index 6dfbeb64426..3bd82df2fd7 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-us.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-us.md
@@ -1,19 +1,21 @@
 ---
-title: Mount your HA-NAS on Windows Server via CIFS
-excerpt: This guide shows you how to mount your HA-NAS on Windows Server via CIFS.
-updated: 2021-11-22
+title: Mount your HA-NAS via a CIFS share
+excerpt: This guide shows you how to mount your HA-NAS using CIFS protocol
+updated: 2025-10-08
 ---
 
 ## Objective
 
-Configure and mount an OVHcloud HA-NAS storage space on your Windows Server using CIFS.
+Configure and mount an OVHcloud HA-NAS storage space using CIFS protocol.
 
 ## Requirements
 
-- a [Dedicated Server](/links/bare-metal/bare-metal) **or** a [VPS](/links/bare-metal/vps) **or** a [Public Cloud Instance](/links/public-cloud/public-cloud) with a Windows distribution
+- a [Dedicated Server](/links/bare-metal/bare-metal) **or** a [VPS](/links/bare-metal/vps) **or** a [Public Cloud Instance](/links/public-cloud/public-cloud)
 - a [HA-NAS solution](/links/storage/nas-ha)
 
-### Settings
+## Instructions
+
+### Settings for Windows
 
 - **Windows Server 2008**: Click on the menu `Start`{.action} > `All the programs`{.action} > `Accessories`{.action} > `Command prompt`{.action}.
 - **Windows Server 2012**: Click the `Windows PowerShell`{.action} icon at the bottom of the screen in the taskbar.
@@ -26,7 +28,7 @@ Then run the following command:
 net use z: \\CIFS_SERVER_IP\CIFS_PATH
 ```
 
-### Example
+#### Example
 
 - CIFS mounting for a NAS-HA:
 
@@ -39,10 +41,46 @@ net use z: \\10.16.101.8\zpool-000206_PARTITION_NAME_1
 > The SMB/CIFS user is `nobody`. Changing permissions with this user may generate conflicts with existing NFS permissions. 
 > 
 
+The following error message may appear:
+
+```console
+System error 1272 has occurred.
+
+You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
+```
+
+> [!primary]
+>
+> This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Set the value of `AllowInsecureGuestAuth` to "1".<br>
+> You can find more information on this issue on the [Microsoft support pages](https://learn.microsoft.com/en-us/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+
+### Settings for Linux
+
+Open an SSH connection to your server and type the following command:
+
+```sh
+mount -t cifs -o uid=root,gid=100,dir_mode=0700,username=root,password= //IP_SERVEUR_CIFS/CHEMIN_CIFS /mnt/FolderMount
+```
+
+> [!warning]
+>
+> In order to mount shares by host name (as opposed to IP addresses), the `mount.cifs` utility is required. It is usually part of the `cifs-utils` package.
+>
+> `mount.cifs` is a wrapper that resolves host names and adds the parameter `ip=` to the mount parameters transmitted to the kernel.
+>
+> Without `mount.cifs`, attempts to mount by host name will result in the following error:
+>
+> ```text
+> mount: /mnt/FolderMount: mount(2) system call failed: No route to host.
+>        dmesg(1) may have more information after failed mount system call.
+> ```
+>
+
 ## Go further
 
 [NAS - Frequently Asked Questions](/pages/storage_and_backup/file_storage/ha_nas/nas_faq)
 
 If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project.
 
-Join our community of users on <https://community.ovh.com/en/>.
+Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.es-es.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.es-es.md
index 748f2a32bda..fd96847e234 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.es-es.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.es-es.md
@@ -1,23 +1,21 @@
 ---
-title: Montar un NAS-HA en Windows Server a través de CIFS
-excerpt: Esta guía explica cómo montar un NAS-HA en Windows Server a través de CIFS.
-updated: 2021-11-22
+title: Montar un NAS-HA a través de un recurso compartido CIFS
+excerpt: Descubra cómo montar un NAS-HA a través del protocolo CIFS
+updated: 2025-10-08
 ---
 
-> [!primary]
-> Esta traducción ha sido generada de forma automática por nuestro partner SYSTRAN. En algunos casos puede contener términos imprecisos, como en las etiquetas de los botones o los detalles técnicos. En caso de duda, le recomendamos que consulte la versión inglesa o francesa de la guía. Si quiere ayudarnos a mejorar esta traducción, por favor, utilice el botón «Contribuir» de esta página.
->
-
 ## Objetivo
 
-Configure e monte su espacio de almacenamiento NAS-HA OVHcloud en Windows Server a través de CIFS.
+Configure y monte su espacio de almacenamiento NAS-HA OVHcloud a través del protocolo CIFS.
 
 ## Requisitos
 
-- Un [servidor dedicado](/links/bare-metal/bare-metal) **o** un [VPS](/links/bare-metal/vps) **o** una [instancia de Public Cloud](/links/public-cloud/public-cloud) con una distribución Windows.
+- Un [servidor dedicado](/links/bare-metal/bare-metal) **o** un [VPS](/links/bare-metal/vps) **o** una [instancia de Public Cloud](/links/public-cloud/public-cloud).
 - Una oferta [NAS-HA](/links/storage/nas-ha).
 
-### Configuración
+## Procedimiento
+
+### Configuración para Windows
 
 - **Windows Server 2008** : haga clic en el menú `Start`{.action} > `All the programs`{.action} > `Accesories`{.action} > `Command prompt`{.action}.
 - **Windows Server 2012** : haga clic en el icono `Windows PowerShell`{.action} en la barra de tareas.
@@ -30,7 +28,7 @@ Ejecute el siguiente comando:
 net use z: \\CIFS_SERVER_IP\CIFS_PATH
 ```
 
-### Ejemplo
+#### Ejemplo
 
 - Montaje CIFS para un NAS-HA:
 
@@ -41,7 +39,43 @@ net use z: \\10.16.101.8\zpool-000206_PARTITION_NAME_1
 > [!alert]
 >
 > El usuario SMB/CIFS es `nobody`, cualquier cambio de permisos efectuado por este usuario puede generar conflictos con los permisos NFS existentes.
+>
+
+Puede aparecer el siguiente mensaje de error:
+
+```console
+System error 1272 has occurred.
+
+You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
+```
+
+> [!primary]
+>
+> Este problema se puede solucionar editando el Registro de Windows: abra la utilidad Windows *regedit* y busque la entrada `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Establezca el valor de `AllowInsecureGuestAuth` en "1".<br>
+> Más información sobre este tema en [páginas de soporte técnico de Microsoft](https://learn.microsoft.com/es-es/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+
+### Configuración para Linux
+
+Conéctese a su servidor a través de SSH y escriba el siguiente comando:
+
+```sh
+mount -t cifs -o uid=root,gid=100,dir_mode=0700,username=root,password= //IP_SERVEUR_CIFS/CHEMIN_CIFS /mnt/FolderMount
+```
+
+> [!warning]
+>
+> Para montar recursos compartidos por nombre de host (en lugar de por direcciones IP), se necesita la utilidad `mount.cifs`. Suele formar parte del paquete `cifs-utils`.
+>
+> `mount.cifs` es un envoltorio que resuelve los nombres de host y añade el parámetro `ip=` a los parámetros de montaje transmitidos al núcleo.
 > 
+> Sin `mount.cifs`, los intentos de montaje por nombre de host darán lugar al siguiente error:
+>
+> ```text
+> mount: /mnt/FolderMount: mount(2) system call failed: No route to host.
+>        dmesg(1) may have more information after failed mount system call.
+> ```
+>
 
 ## Más información
 
@@ -49,4 +83,4 @@ net use z: \\10.16.101.8\zpool-000206_PARTITION_NAME_1
 
 Si necesita formación o asistencia técnica para implantar nuestras soluciones, póngase en contacto con su representante de ventas o haga clic en [este enlace](/links/professional-services) para obtener un presupuesto y solicitar un análisis personalizado de su proyecto a nuestros expertos del equipo de Servicios Profesionales.
 
-Interactúe con nuestra comunidad de usuarios en <https://community.ovh.com/en/>.
+Interactúe con nuestra [comunidad de usuarios](/links/community).
\ No newline at end of file
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.es-us.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.es-us.md
index 748f2a32bda..6e6ea6dbcf8 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.es-us.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.es-us.md
@@ -1,23 +1,21 @@
 ---
-title: Montar un NAS-HA en Windows Server a través de CIFS
-excerpt: Esta guía explica cómo montar un NAS-HA en Windows Server a través de CIFS.
-updated: 2021-11-22
+title: Montar un NAS-HA a través de un recurso compartido CIFS
+excerpt: Descubra cómo montar un NAS-HA a través del protocolo CIFS
+updated: 2025-10-08
 ---
 
-> [!primary]
-> Esta traducción ha sido generada de forma automática por nuestro partner SYSTRAN. En algunos casos puede contener términos imprecisos, como en las etiquetas de los botones o los detalles técnicos. En caso de duda, le recomendamos que consulte la versión inglesa o francesa de la guía. Si quiere ayudarnos a mejorar esta traducción, por favor, utilice el botón «Contribuir» de esta página.
->
-
 ## Objetivo
 
-Configure e monte su espacio de almacenamiento NAS-HA OVHcloud en Windows Server a través de CIFS.
+Configure y monte su espacio de almacenamiento NAS-HA OVHcloud a través del protocolo CIFS.
 
 ## Requisitos
 
-- Un [servidor dedicado](/links/bare-metal/bare-metal) **o** un [VPS](/links/bare-metal/vps) **o** una [instancia de Public Cloud](/links/public-cloud/public-cloud) con una distribución Windows.
+- Un [servidor dedicado](/links/bare-metal/bare-metal) **o** un [VPS](/links/bare-metal/vps) **o** una [instancia de Public Cloud](/links/public-cloud/public-cloud).
 - Una oferta [NAS-HA](/links/storage/nas-ha).
 
-### Configuración
+## Procedimiento
+
+### Configuración para Windows
 
 - **Windows Server 2008** : haga clic en el menú `Start`{.action} > `All the programs`{.action} > `Accesories`{.action} > `Command prompt`{.action}.
 - **Windows Server 2012** : haga clic en el icono `Windows PowerShell`{.action} en la barra de tareas.
@@ -30,7 +28,7 @@ Ejecute el siguiente comando:
 net use z: \\CIFS_SERVER_IP\CIFS_PATH
 ```
 
-### Ejemplo
+#### Ejemplo
 
 - Montaje CIFS para un NAS-HA:
 
@@ -41,7 +39,43 @@ net use z: \\10.16.101.8\zpool-000206_PARTITION_NAME_1
 > [!alert]
 >
 > El usuario SMB/CIFS es `nobody`, cualquier cambio de permisos efectuado por este usuario puede generar conflictos con los permisos NFS existentes.
+>
+
+Puede aparecer el siguiente mensaje de error:
+
+```console
+System error 1272 has occurred.
+
+You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
+```
+
+> [!primary]
+>
+> Este problema se puede solucionar editando el Registro de Windows: abra la utilidad Windows *regedit* y busque la entrada `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Establezca el valor de `AllowInsecureGuestAuth` en "1".<br>
+> Más información sobre este tema en [páginas de soporte técnico de Microsoft](https://learn.microsoft.com/es-mx/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+
+### Configuración para Linux
+
+Conéctese a su servidor a través de SSH y escriba el siguiente comando:
+
+```sh
+mount -t cifs -o uid=root,gid=100,dir_mode=0700,username=root,password= //IP_SERVEUR_CIFS/CHEMIN_CIFS /mnt/FolderMount
+```
+
+> [!warning]
+>
+> Para montar recursos compartidos por nombre de host (en lugar de por direcciones IP), se necesita la utilidad `mount.cifs`. Suele formar parte del paquete `cifs-utils`.
+>
+> `mount.cifs` es un envoltorio que resuelve los nombres de host y añade el parámetro `ip=` a los parámetros de montaje transmitidos al núcleo.
 > 
+> Sin `mount.cifs`, los intentos de montaje por nombre de host darán lugar al siguiente error:
+>
+> ```text
+> mount: /mnt/FolderMount: mount(2) system call failed: No route to host.
+>        dmesg(1) may have more information after failed mount system call.
+> ```
+>
 
 ## Más información
 
@@ -49,4 +83,4 @@ net use z: \\10.16.101.8\zpool-000206_PARTITION_NAME_1
 
 Si necesita formación o asistencia técnica para implantar nuestras soluciones, póngase en contacto con su representante de ventas o haga clic en [este enlace](/links/professional-services) para obtener un presupuesto y solicitar un análisis personalizado de su proyecto a nuestros expertos del equipo de Servicios Profesionales.
 
-Interactúe con nuestra comunidad de usuarios en <https://community.ovh.com/en/>.
+Interactúe con nuestra [comunidad de usuarios](/links/community).
\ No newline at end of file
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-ca.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-ca.md
index 0f2b4753ed6..efb2a31a2a2 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-ca.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-ca.md
@@ -1,19 +1,21 @@
 ---
-title: Monter un NAS-HA sur Windows Server via CIFS
-excerpt: Decouvrez comment monter un NAS-HA sur Windows Server via CIFS
-updated: 2021-11-22
+title: Monter un NAS-HA via un partage CIFS
+excerpt: Decouvrez comment monter un NAS-HA via le protocole CIFS
+updated: 2025-10-08
 ---
 
 ## Objectif
 
-Configurez et montez votre espace de stockage NAS-HA OVHcloud sur Windows Server via CIFS.
+Configurez et montez votre espace de stockage NAS-HA OVHcloud via le protocole CIFS.
 
 ## Prérequis
 
-- Un [serveur dédié](/links/bare-metal/bare-metal) **ou** un [VPS](/links/bare-metal/vps) **ou** une [instance Public Cloud](/links/public-cloud/public-cloud) avec une distribution Windows.
+- Un [serveur dédié](/links/bare-metal/bare-metal) **ou** un [VPS](/links/bare-metal/vps) **ou** une [instance Public Cloud](/links/public-cloud/public-cloud).
 - Une offre [NAS-HA](/links/storage/nas-ha).
 
-### Configuration
+## En pratique
+
+### Configuration pour Windows
 
 - **Windows Server 2008** : cliquez sur le menu `Démarrer`{.action} > `Tous les programmes`{.action} > `Accessoires`{.action} > `Invite de commandes`{.action}.
 - **Windows Server 2012** : cliquez sur l'icône `Windows PowerShell`{.action} dans la barre de tâches.
@@ -26,7 +28,7 @@ Exécutez ensuite la commande suivante :
 net use z: \\IP_SERVEUR_CIFS\CHEMIN_CIFS
 ```
 
-### Exemple
+#### Exemple
 
 - Montage CIFS pour un NAS-HA :
 
@@ -37,7 +39,43 @@ net use z: \\10.16.101.8\zpool-000206_NOM_PARTITION_1
 > [!alert]
 >
 > L'utilisateur SMB/CIFS est `nobody`, toute modification de droits effectuée par cet utilisateur peut générer des conflits avec des droits NFS existants.
-> 
+>
+
+Le message d'erreur suivant peut s'afficher :
+
+```console
+System error 1272 has occurred.
+
+You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
+```
+
+> [!primary]
+>
+> Ce problème peut être résolu en modifiant le Registre Windows : ouvrez l'utilitaire Windows *regedit* et recherchez l'entrée `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Définissez la valeur de `AllowInsecureGuestAuth` sur « 1 ».<br>
+> Retrouvez plus d'informations sur ce sujet sur les [pages de support Microsoft](https://learn.microsoft.com/fr-ca/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+
+### Configuration pour Linux
+
+Connectez-vous via SSH à votre serveur et tapez la commande suivante :
+
+```sh
+mount -t cifs -o uid=root,gid=100,dir_mode=0700,username=root,password= //IP_SERVEUR_CIFS/CHEMIN_CIFS /mnt/FolderMount
+```
+
+> [!warning]
+>
+> Afin de monter des partages par nom d'hôte (par opposition aux adresses IP), l'utilitaire `mount.cifs` est requis. Il fait généralement partie du paquet `cifs-utils`.
+>
+> `mount.cifs` est un wrapper qui résout les noms d'hôte et ajoute le paramètre `ip=` aux paramètres de montage transmis au noyau.
+>
+> Sans `mount.cifs`, les tentatives de montage par nom d'hôte entraîneront l'erreur suivante :
+>
+> ```text
+> mount: /mnt/FolderMount: mount(2) system call failed: No route to host.
+>        dmesg(1) may have more information after failed mount system call.
+> ```
+>
 
 ## Aller plus loin
 
@@ -45,4 +83,4 @@ net use z: \\10.16.101.8\zpool-000206_NOM_PARTITION_1
 
 Si vous avez besoin d'une formation ou d'une assistance technique pour la mise en oeuvre de nos solutions, contactez votre commercial ou cliquez sur [ce lien](/links/professional-services) pour obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l’équipe Professional Services.
 
-Échangez avec notre [communauté d'utilisateurs](/links/community).
+Échangez avec notre [communauté d'utilisateurs](/links/community).
\ No newline at end of file
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-fr.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-fr.md
index d6cfbd3f755..7c08a90f5c1 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-fr.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-fr.md
@@ -1,7 +1,7 @@
 ---
-title: Monter un NAS-HA via partage CIFS
+title: Monter un NAS-HA via un partage CIFS
 excerpt: Decouvrez comment monter un NAS-HA via le protocole CIFS
-updated: 2025-10-07
+updated: 2025-10-08
 ---
 
 ## Objectif
@@ -13,6 +13,8 @@ Configurez et montez votre espace de stockage NAS-HA OVHcloud via le protocole C
 - Un [serveur dédié](/links/bare-metal/bare-metal) **ou** un [VPS](/links/bare-metal/vps) **ou** une [instance Public Cloud](/links/public-cloud/public-cloud).
 - Une offre [NAS-HA](/links/storage/nas-ha).
 
+## En pratique
+
 ### Configuration pour Windows
 
 - **Windows Server 2008** : cliquez sur le menu `Démarrer`{.action} > `Tous les programmes`{.action} > `Accessoires`{.action} > `Invite de commandes`{.action}.
@@ -39,7 +41,7 @@ net use z: \\10.16.101.8\zpool-000206_NOM_PARTITION_1
 > L'utilisateur SMB/CIFS est `nobody`, toute modification de droits effectuée par cet utilisateur peut générer des conflits avec des droits NFS existants.
 > 
 
-Le message d'erreur suivant peut s'afficher :  
+Le message d'erreur suivant peut s'afficher :
 
 ```console
 System error 1272 has occurred.
@@ -47,12 +49,16 @@ System error 1272 has occurred.
 You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
 ```
 
-Ce problème peut être résolu en modifiant le Registre Windows : ouvrez l'utilitaire Windows *regedit* et recherchez l'entrée `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`. Définissez la valeur de `AllowInsecureGuestAuth` sur « 1 ». Retrouvez plus d'informations sur ce sujet sur les [pages de support Microsoft](https://learn.microsoft.com/fr-fr/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3?tabs=group-policy).
+> [!primary]
+>
+> Ce problème peut être résolu en modifiant le Registre Windows : ouvrez l'utilitaire Windows *regedit* et recherchez l'entrée `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Définissez la valeur de `AllowInsecureGuestAuth` sur « 1 ».<br>
+> Retrouvez plus d'informations sur ce sujet sur les [pages de support Microsoft](https://learn.microsoft.com/fr-fr/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3?tabs=group-policy).
 
 
 ### Configuration pour Linux
 
-Ouvrez une connexion SSH à votre serveur et tapez la commande suivante :
+Connectez-vous via SSH à votre serveur et tapez la commande suivante :
 
 ```sh
 mount -t cifs -o uid=root,gid=100,dir_mode=0700,username=root,password= //IP_SERVEUR_CIFS/CHEMIN_CIFS /mnt/FolderMount
@@ -70,7 +76,7 @@ mount -t cifs -o uid=root,gid=100,dir_mode=0700,username=root,password= //IP_SER
 > mount: /mnt/FolderMount: mount(2) system call failed: No route to host.
 >        dmesg(1) may have more information after failed mount system call.
 > ```
-
+>
 
 ## Aller plus loin
 
@@ -78,4 +84,4 @@ mount -t cifs -o uid=root,gid=100,dir_mode=0700,username=root,password= //IP_SER
 
 Si vous avez besoin d'une formation ou d'une assistance technique pour la mise en oeuvre de nos solutions, contactez votre commercial ou cliquez sur [ce lien](/links/professional-services) pour obtenir un devis et demander une analyse personnalisée de votre projet à nos experts de l’équipe Professional Services.
 
-Échangez avec notre [communauté d'utilisateurs](/links/community).
+Échangez avec notre [communauté d'utilisateurs](/links/community).
\ No newline at end of file
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.it-it.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.it-it.md
index 629a197a1a1..91c11f6ce10 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.it-it.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.it-it.md
@@ -1,23 +1,21 @@
 ---
-title: Configura il tuo NAS-HA su Windows Server tramite CIFS
-excerpt: Questa guida ti mostra come configurare un NAS-HA su Windows Server tramite CIFS.
-updated: 2021-11-22
+title: Montare un NAS-HA tramite condivisione CIFS
+excerpt: Scopri come montare un NAS-HA tramite il protocollo CIFS
+updated: 2025-10-08
 ---
 
-> [!primary]
-> Questa traduzione è stata generata automaticamente dal nostro partner SYSTRAN. I contenuti potrebbero presentare imprecisioni, ad esempio la nomenclatura dei pulsanti o alcuni dettagli tecnici. In caso di dubbi consigliamo di fare riferimento alla versione inglese o francese della guida. Per aiutarci a migliorare questa traduzione, utilizza il pulsante "Contribuisci" di questa pagina.
->
-
 ## Obiettivo
 
-Configura e monta il tuo spazio di storage NAS-HA OVHcloud su Windows Server tramite CIFS.
+Configura e monta il tuo spazio di archiviazione NAS-HA OVHcloud tramite il protocollo CIFS.
 
 ## Prerequisiti
 
-- Un [server dedicato](/links/bare-metal/bare-metal) **o** un [VPS](/links/bare-metal/vps) **o** un'[istanza Public Cloud](/links/public-cloud/public-cloud) con distribuzione Windows.
+- Un [server dedicato](/links/bare-metal/bare-metal) **o** un [VPS](/links/bare-metal/vps) **o** un'[istanza Public Cloud](/links/public-cloud/public-cloud).
 - Un'offerta [NAS-HA](/links/storage/nas-ha).
 
-### Configurazione
+## Procedura
+
+### Configurazione per Windows
 
 - **Windows Server 2008** : clicca sul menu `Start`{.action} > `All the programs`{.action} > `Accessories`{.action} > `Command prompt`{.action}.
 - **Windows Server 2012** : clicca sull'icona `Windows PowerShell`{.action} nella barra dei task.
@@ -30,7 +28,7 @@ Esegui questo comando:
 net use z: \\CIFS_SERVER_IP\CIFS_PATH
 ```
 
-### Esempi
+#### Esempi
 
 - Montaggio CIFS per un NAS-HA:
 
@@ -43,10 +41,46 @@ net use z: \\10.16.101.8\zpool-000206_PARTITION_NAME_1
 > L'utente SMB/CIFS è `nobody`, qualsiasi modifica dei diritti effettuata da questo utente può generare conflitti con i diritti NFS esistenti.
 > 
 
+Potrebbe essere visualizzato il seguente messaggio di errore:
+
+```console
+System error 1272 has occurred.
+
+You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
+```
+
+> [!primary]
+>
+> Questo problema può essere risolto modificando il Registro di sistema di Windows: aprire l'utilità Windows *regedit* e cercare la voce `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Impostare il valore di `AllowInsecureGuestAuth` su "1".<br>
+> Per maggiori informazioni al riguardo, visitare le [pagine di supporto Microsoft](https://learn.microsoft.com/it-it/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+
+### Configurazione per Linux
+
+Connettiti tramite SSH al tuo server e digita il seguente comando:
+
+```sh
+mount -t cifs -o uid=root,gid=100,dir_mode=0700,username=root,password= //IP_SERVEUR_CIFS/CHEMIN_CIFS /mnt/FolderMount
+```
+
+> [!warning]
+> 
+> Per montare le condivisioni tramite nome host (anziché indirizzo IP), è necessario l'utilità `mount.cifs`. Di solito è inclusa nel pacchetto `cifs-utils`.
+>
+> `mount.cifs` è un wrapper che risolve i nomi host e aggiunge il parametro `ip=` ai parametri di montaggio trasmessi al kernel.
+> 
+> Senza `mount.cifs`, i tentativi di montaggio tramite nome host genereranno il seguente errore:
+>
+> ```text
+> mount: /mnt/FolderMount: mount(2) system call failed: No route to host.
+>        dmesg(1) may have more information after failed mount system call.
+> ```
+>
+
 ## Per saperne di più
 
 [Domande frequenti sul NAS](/pages/storage_and_backup/file_storage/ha_nas/nas_faq)
 
 Se avete bisogno di formazione o di assistenza tecnica per implementare le nostre soluzioni, contattate il vostro rappresentante o cliccate su [questo link](/links/professional-services) per ottenere un preventivo e richiedere un'analisi personalizzata del vostro progetto da parte dei nostri esperti del team Professional Services.
 
-Contatta la nostra Community di utenti all’indirizzo <https://community.ovh.com/en/>.
\ No newline at end of file
+Contatta la nostra [Community di utenti](/links/community).
\ No newline at end of file
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.pl-pl.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.pl-pl.md
index 60544dffd22..b36b9abac4f 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.pl-pl.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.pl-pl.md
@@ -1,23 +1,21 @@
 ---
-title: Skonfigurować NAS-HA na serwerze Windows poprzez CIFS
-excerpt: Ten przewodnik pokazuje, jak zamontować NAS-HA w systemie Windows Server poprzez CIFS.
-updated: 2021-11-22
+title: Podłącz HA-NAS za pomocą udziału CIFS
+excerpt: Ten przewodnik pokazuje, jak podłączyć HA-NAS za pomocą protokołu CIFS
+updated: 2025-10-08
 ---
 
-> [!primary]
-> Tłumaczenie zostało wygenerowane automatycznie przez system naszego partnera SYSTRAN. W niektórych przypadkach mogą wystąpić nieprecyzyjne sformułowania, na przykład w tłumaczeniu nazw przycisków lub szczegółów technicznych. W przypadku jakichkolwiek wątpliwości zalecamy zapoznanie się z angielską/francuską wersją przewodnika. Jeśli chcesz przyczynić się do ulepszenia tłumaczenia, kliknij przycisk "Zgłóś propozycję modyfikacji" na tej stronie.
->
-
 ## Wprowadzenie
 
-Konfiguracja i zamontowanie przestrzeni dyskowej NAS-HA OVHcloud na serwerze Windows przy użyciu systemu CIFS.
+Skonfiguruj i zamontuj przestrzeń dyskową OVHcloud HA-NAS przy użyciu protokołu CIFS.
 
 ## Wymagania początkowe
 
-- Posiadanie [Serwer dedykowany](/links/bare-metal/bare-metal), **lub**  [VPS](/links/bare-metal/vps) **lub** [instancja Public Cloud](/links/public-cloud/public-cloud) z dystrybucją Windows.
+- Posiadanie [Serwer dedykowany](/links/bare-metal/bare-metal), **lub**  [VPS](/links/bare-metal/vps) **lub** [instancja Public Cloud](/links/public-cloud/public-cloud).
 - Posiadanie usługi [NAS-HA](/links/storage/nas-ha)
 
-### Ustawienia
+## W praktyce
+
+### Ustawienia dla systemu Windows
 
 - **Windows Server 2008**: Kliknij menu `Start`{.action} > `All the programs`{.action} > `Accessories`{.action} > `Command prompt`{.action}.
 - **Windows Server 2012**: Kliknij ikonę `Windows PowerShell`{.action} u dołu ekranu na pasku zadań.
@@ -30,7 +28,7 @@ Teraz wprowadź następującą komendę:
 net use z: \\CIFS_SERVER_IP\CIFS_PATH
 ```
 
-### Przykłady
+#### Przykłady
 
 - Montowanie CIFS dla NAS-HA:
 
@@ -43,10 +41,46 @@ net use z: \\10.16.101.8\zpool-000206_PARTITION_NAME_1
 > Użytkownikiem SMB/CIFS jest `nobody`. Zmiana uprawnień tego użytkownika może spowodować konflikty z istniejącymi uprawnieniami systemu plików NFS 
 > 
 
+Może pojawić się następujący komunikat o błędzie:
+
+```console
+System error 1272 has occurred.
+
+You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
+```
+
+> [!primary]
+>
+> Ten problem można rozwiązać, modyfikując rejestr systemu Windows: otwórz narzędzie systemu Windows *regedit* i wyszukaj wpis `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Ustaw dla parametru `AllowInsecureGuestAuth` wartość "1".<br>
+> Więcej informacji na ten temat można znaleźć na [stronach pomocy technicznej firmy Microsoft](https://learn.microsoft.com/pl-pl/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+
+### Ustawienia dla systemu Linux
+
+Otwórz połączenie SSH z serwerem i wpisz następujące polecenie:
+
+```sh
+mount -t cifs -o uid=root,gid=100,dir_mode=0700,username=root,password= //IP_SERVEUR_CIFS/CHEMIN_CIFS /mnt/FolderMount
+```
+
+> [!warning]
+>
+> Aby zamontować udziały według nazwy hosta (w przeciwieństwie do adresów IP), wymagane jest narzędzie `mount.cifs`. Zazwyczaj jest ono częścią pakietu `cifs-utils`.
+> 
+> `mount.cifs` jest opakowaniem, które rozpoznaje nazwy hostów i dodaje parametr `ip=` do parametrów montowania przesyłanych do jądra.
+>
+> Bez `mount.cifs` próby zamontowania według nazwy hosta spowodują następujący błąd:
+>
+> ```text
+> mount: /mnt/FolderMount: mount(2) system call failed: No route to host.
+>        dmesg(1) may have more information after failed mount system call.
+> ```
+>
+
 ## Sprawdź również
 
 [Najczęściej zadawane pytania dotyczące technologii NAS](/pages/storage_and_backup/file_storage/ha_nas/nas_faq)
 
 Jeśli potrzebujesz szkolenia lub pomocy technicznej w celu wdrożenia naszych rozwiązań, skontaktuj się z przedstawicielem handlowym lub kliknij [ten link](/links/professional-services), aby uzyskać wycenę i poprosić o spersonalizowaną analizę projektu od naszych ekspertów z zespołu Professional Services.
 
-Dołącz do społeczności naszych użytkowników na stronie <https://community.ovh.com/en/>.
+Dołącz do [grona naszych użytkowników](/links/community).
\ No newline at end of file
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.pt-pt.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.pt-pt.md
index b0e77fa179e..eed7c9fcbc6 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.pt-pt.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.pt-pt.md
@@ -1,23 +1,21 @@
 ---
 title: Configure o seu NAS-HA no Windows Server através do CIFS
 excerpt: Saiba como montar um NAS-HA no Windows Server através do CIFS.
-updated: 2021-11-22
+updated: 2025-10-08
 ---
 
-> [!primary]
-> Esta tradução foi automaticamente gerada pelo nosso parceiro SYSTRAN. Em certos casos, poderão ocorrer formulações imprecisas, como por exemplo nomes de botões ou detalhes técnicos. Recomendamos que consulte a versão inglesa ou francesa do manual, caso tenha alguma dúvida. Se nos quiser ajudar a melhorar esta tradução, clique em "Contribuir" nesta página.
->
-
 ## Objetivo
 
 Configure e monte o seu espaço de armazenamento NAS-HA OVHcloud no Windows Server através de CIFS.
 
 ## Requisitos
 
-- Um [servidor dedicado](/links/bare-metal/bare-metal) **ou** um [VPS](/links/bare-metal/vps) **ou** uma [instância Public Cloud](/links/public-cloud/public-cloud) com uma distribuição Windows.
+- Um [servidor dedicado](/links/bare-metal/bare-metal) **ou** um [VPS](/links/bare-metal/vps) **ou** uma [instância Public Cloud](/links/public-cloud/public-cloud).
 - Uma oferta [NAS-HA](/links/storage/nas-ha).
 
-### Configuração
+## Instruções
+
+### Configuração para Windows
 
 - **Windows Server 2008** : clique no menu `Start`{.action} > `All the programs`{.action} > `Accessories`{.action} > `Command prompt`{.action}.
 - **Windows Server 2012** : clique no ícone `Windows PowerShell`{.action} na barra de tarefas.
@@ -30,7 +28,7 @@ De seguida, execute o seguinte comando:
 net use z: \\CIFS_SERVER_IP\CIFS_PATH
 ```
 
-### Exemplo
+#### Exemplo
 
 - Montagem CIFS para um NAS-HA:
 
@@ -41,7 +39,43 @@ net use z: \\10.16.101.8\zpool-000206_PARTITION_NAME_1
 > [!alert]
 >
 > O utilizador SMB/CIFS é `nobody`, qualquer modificação de direitos efetuada por este utilizador pode gerar conflitos com direitos NFS existentes.
-> 
+>
+
+A seguinte mensagem de erro pode aparecer:
+
+```console
+System error 1272 has occurred.
+
+You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.
+```
+
+> [!primary]
+>
+> É possível resolver este problema alterando o registo do Windows: abra o utilitário Windows *regedit* e procure a entrada `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Defina o valor de `AllowInsecureGuestAuth` como "1".<br>
+> Encontre mais informações sobre este assumpto nas [páginas de suporte da Microsoft](https://learn.microsoft.com/pt-pt/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+
+### Configuração para Linux
+
+Conecte-se via SSH ao seu servidor e digite o seguinte comando:
+
+```sh
+mount -t cifs -o uid=root,gid=100,dir_mode=0700,username=root,password= //IP_SERVEUR_CIFS/CHEMIN_CIFS /mnt/FolderMount
+```
+
+> [!warning]
+>
+> Para montar partilhas por nome de host (em oposição a endereços IP), é necessário o utilitário `mount.cifs`. Ele geralmente faz parte do pacote `cifs-utils`.
+>
+> O `mount.cifs` é um wrapper que resolve os nomes de host e adiciona o parâmetro `ip=` aos parâmetros de montagem transmitidos ao kernel.
+>
+> Sem o `mount.cifs`, as tentativas de montagem por nome de host resultarão no seguinte erro:
+>
+> ```text
+> mount: /mnt/FolderMount: mount(2) system call failed: No route to host.
+>        dmesg(1) may have more information after failed mount system call.
+> ```
+>
 
 ## Quer saber mais?
 
@@ -49,4 +83,4 @@ net use z: \\10.16.101.8\zpool-000206_PARTITION_NAME_1
 
 Se precisar de formação ou de assistência técnica para implementar as nossas soluções, contacte o seu representante comercial ou clique em [esta ligação](/links/professional-services) para obter um orçamento e solicitar uma análise personalizada do seu projecto aos nossos especialistas da equipa de Serviços Profissionais.
 
-Fale com a nossa comunidade de utilizadores: <https://community.ovh.com/en/>.
\ No newline at end of file
+Fale com a nossa [comunidade de utilizadores](/links/community).
\ No newline at end of file
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/meta.yaml b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/meta.yaml
index b07543417a9..49bb5305037 100755
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/meta.yaml
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/meta.yaml
@@ -1,2 +1,3 @@
 id: 8cf1948c-be58-440e-b4ee-c798b16654b9
-full_slug: public-cloud-storage-nas-cifs
\ No newline at end of file
+full_slug: public-cloud-storage-nas-cifs
+translation_banner: true
\ No newline at end of file
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.de-de.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.de-de.md
index 49eafa3a345..40f0b19af78 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.de-de.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.de-de.md
@@ -1,7 +1,7 @@
 ---
 title: HA-NAS über NFS mounten
 excerpt: "Erfahren Sie hier, wie sich mit Ihrem HA-NAS unter Verwendung einer NFS-Freigabe verbinden"
-updated: 2024-11-08
+updated: 2025-10-08
 ---
 
 ## Ziel 
@@ -134,6 +134,24 @@ root@server:~$ sudo mount -t nfs 10.1.1.1:/zpool-123456/partition01 /mount/ha_na
 
 Sie können nun über den angegebenen Ordner auf Ihre gemountete Partition zugreifen.
 
+### Microsoft Windows - Besonderheiten
+
+Stellen Sie sicher, dass der Windows-Benutzer, der für den Zugriff auf Ihr HA-NAS verwendet wird, ausreichende Rechte hat.
+
+Der UID/GID-Paar muss auf 0 konfiguriert werden (UNIX-Rechte root).
+
+Andernfalls erhalten Sie Zugriffsfehler auf Ihr HA-NAS, da bei aktiviertem NFS auf einem Windows-System ein UNIX-Benutzer mit der Standard-UID und GID -2 (oder 4294967294) erstellt wird.
+
+Als Lösung können UID und GID auf 0 gesetzt werden, um den Zugriff auf Ihr HA-NAS zu ermöglichen:
+
+1. Starten Sie den Registrierungseditor auf dem Client-System.
+1. Navigieren Sie zu `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
+1. Erstellen Sie zwei DWORD-Werte: **AnonymousUid** und **AnonymousGid**.
+1. Setzen Sie diese Werte auf 0 für UID und GID.
+1. Starten Sie den NFS-Dienst auf dem Client-System neu.
+
+Alle Einhängeoptionen sind auf der [Microsoft-Website](https://learn.microsoft.com/de-de/windows-server/administration/windows-commands/mount) verfügbar.
+
 ### Proxmox
 
 Klicken Sie im Verwaltungsinterface von Proxmox im vertikalen Menü auf `Storage`{.action}.
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-asia.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-asia.md
index b351852f39d..d2b9489f3b9 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-asia.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-asia.md
@@ -1,7 +1,7 @@
 ---
 title: Mounting HA-NAS via NFS share
 excerpt: Find out how to connect to your HA-NAS using an NFS share
-updated: 2024-11-08
+updated: 2025-10-08
 ---
 
 ## Objective 
@@ -133,6 +133,24 @@ root@server:~$ sudo mount -t nfs 10.1.1.1:/zpool-123456/partition01 /mount/ha_na
 
 You can now access your mounted partition at the specified folder.
 
+### Microsoft Windows - specificity
+
+Make sure that the Windows user who is used to access your NAS-HA has sufficient rights.
+
+Indeed, the UID/GID pair must be configured to 0 (right UNIX root).
+
+If this is not the case, you will have access errors to your NAS-HA because, when NFS is authorised on a Windows machine, a UNIX user is created with the default UID and GID at -2 (or 4294967294).
+
+As a workaround, the UID and GID can be forced to 0 on the Windows machine that accesses your NAS-HA:
+
+1. Start the registry editor on the client machine.
+1. Locate `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
+1. Create two DWORD values, namely **AnonymousUid** and **AnonymousGid**.
+1. Set these values on the UID and the GID to 0.
+1. Restart the NFS service on the client machine.
+
+All mounting options are available on the [Microsoft website](https://learn.microsoft.com/en-in/windows-server/administration/windows-commands/mount).
+
 ### Proxmox
 
 In the Proxmox administration interface, click on `Storage`{.action} in the vertical menu.
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-au.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-au.md
index b351852f39d..1219ce71f3f 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-au.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-au.md
@@ -1,7 +1,7 @@
 ---
 title: Mounting HA-NAS via NFS share
 excerpt: Find out how to connect to your HA-NAS using an NFS share
-updated: 2024-11-08
+updated: 2025-10-08
 ---
 
 ## Objective 
@@ -133,6 +133,24 @@ root@server:~$ sudo mount -t nfs 10.1.1.1:/zpool-123456/partition01 /mount/ha_na
 
 You can now access your mounted partition at the specified folder.
 
+### Microsoft Windows - specificity
+
+Make sure that the Windows user who is used to access your NAS-HA has sufficient rights.
+
+Indeed, the UID/GID pair must be configured to 0 (right UNIX root).
+
+If this is not the case, you will have access errors to your NAS-HA because, when NFS is authorised on a Windows machine, a UNIX user is created with the default UID and GID at -2 (or 4294967294).
+
+As a workaround, the UID and GID can be forced to 0 on the Windows machine that accesses your NAS-HA:
+
+1. Start the registry editor on the client machine.
+1. Locate `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
+1. Create two DWORD values, namely **AnonymousUid** and **AnonymousGid**.
+1. Set these values on the UID and the GID to 0.
+1. Restart the NFS service on the client machine.
+
+All mounting options are available on the [Microsoft website](https://learn.microsoft.com/en-au/windows-server/administration/windows-commands/mount).
+
 ### Proxmox
 
 In the Proxmox administration interface, click on `Storage`{.action} in the vertical menu.
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-ca.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-ca.md
index b351852f39d..7f139088334 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-ca.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-ca.md
@@ -1,7 +1,7 @@
 ---
 title: Mounting HA-NAS via NFS share
 excerpt: Find out how to connect to your HA-NAS using an NFS share
-updated: 2024-11-08
+updated: 2025-10-08
 ---
 
 ## Objective 
@@ -133,6 +133,24 @@ root@server:~$ sudo mount -t nfs 10.1.1.1:/zpool-123456/partition01 /mount/ha_na
 
 You can now access your mounted partition at the specified folder.
 
+### Microsoft Windows - specificity
+
+Make sure that the Windows user who is used to access your NAS-HA has sufficient rights.
+
+Indeed, the UID/GID pair must be configured to 0 (right UNIX root).
+
+If this is not the case, you will have access errors to your NAS-HA because, when NFS is authorised on a Windows machine, a UNIX user is created with the default UID and GID at -2 (or 4294967294).
+
+As a workaround, the UID and GID can be forced to 0 on the Windows machine that accesses your NAS-HA:
+
+1. Start the registry editor on the client machine.
+1. Locate `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
+1. Create two DWORD values, namely **AnonymousUid** and **AnonymousGid**.
+1. Set these values on the UID and the GID to 0.
+1. Restart the NFS service on the client machine.
+
+All mounting options are available on the [Microsoft website](https://learn.microsoft.com/en-ca/windows-server/administration/windows-commands/mount).
+
 ### Proxmox
 
 In the Proxmox administration interface, click on `Storage`{.action} in the vertical menu.
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-gb.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-gb.md
index 998b8db235c..f2017e8d4d9 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-gb.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-gb.md
@@ -137,23 +137,19 @@ You can now access your mounted partition at the specified folder.
 
 Make sure that the Windows user who is used to access your NAS-HA has sufficient rights.
 
-Indeed, the UID/GID pair must be configured to 0 (right unix root).
+Indeed, the UID/GID pair must be configured to 0 (right UNIX root).
 
 If this is not the case, you will have access errors to your NAS-HA because, when NFS is authorised on a Windows machine, a UNIX user is created with the default UID and GID at -2 (or 4294967294).
 
-As a workaround, the UID and GID can be forced to 0 on the Windows machine that accesses your NAS-HA.
+As a workaround, the UID and GID can be forced to 0 on the Windows machine that accesses your NAS-HA:
 
-- Start the registry editor on the client machine.
+1. Start the registry editor on the client machine.
+1. Locate `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
+1. Create two DWORD values, namely **AnonymousUid** and **AnonymousGid**.
+1. Set these values on the UID and the GID to 0.
+1. Restart the NFS service on the client machine.
 
-- Locate `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
-
-- Create two DWORD values, namely AnonymousUid and AnonymousGid.
-
-- Set these values on the UID and the GID to 0.
-
-- Restart the NFS service on the client machine.
-
-All mounting options are available on the Microsoft website: https://learn.microsoft.com/fr-fr/windows-server/administration/windows-commands/mount
+All mounting options are available on the [Microsoft website](https://learn.microsoft.com/en-gb/windows-server/administration/windows-commands/mount).
 
 ### Proxmox
 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-ie.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-ie.md
index b351852f39d..4a3766cb470 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-ie.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-ie.md
@@ -1,7 +1,7 @@
 ---
 title: Mounting HA-NAS via NFS share
 excerpt: Find out how to connect to your HA-NAS using an NFS share
-updated: 2024-11-08
+updated: 2025-10-08
 ---
 
 ## Objective 
@@ -133,6 +133,24 @@ root@server:~$ sudo mount -t nfs 10.1.1.1:/zpool-123456/partition01 /mount/ha_na
 
 You can now access your mounted partition at the specified folder.
 
+### Microsoft Windows - specificity
+
+Make sure that the Windows user who is used to access your NAS-HA has sufficient rights.
+
+Indeed, the UID/GID pair must be configured to 0 (right UNIX root).
+
+If this is not the case, you will have access errors to your NAS-HA because, when NFS is authorised on a Windows machine, a UNIX user is created with the default UID and GID at -2 (or 4294967294).
+
+As a workaround, the UID and GID can be forced to 0 on the Windows machine that accesses your NAS-HA:
+
+1. Start the registry editor on the client machine.
+1. Locate `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
+1. Create two DWORD values, namely **AnonymousUid** and **AnonymousGid**.
+1. Set these values on the UID and the GID to 0.
+1. Restart the NFS service on the client machine.
+
+All mounting options are available on the [Microsoft website](https://learn.microsoft.com/en-ie/windows-server/administration/windows-commands/mount).
+
 ### Proxmox
 
 In the Proxmox administration interface, click on `Storage`{.action} in the vertical menu.
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-sg.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-sg.md
index b351852f39d..5ae1bbe54a4 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-sg.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-sg.md
@@ -1,7 +1,7 @@
 ---
 title: Mounting HA-NAS via NFS share
 excerpt: Find out how to connect to your HA-NAS using an NFS share
-updated: 2024-11-08
+updated: 2025-10-08
 ---
 
 ## Objective 
@@ -133,6 +133,24 @@ root@server:~$ sudo mount -t nfs 10.1.1.1:/zpool-123456/partition01 /mount/ha_na
 
 You can now access your mounted partition at the specified folder.
 
+### Microsoft Windows - specificity
+
+Make sure that the Windows user who is used to access your NAS-HA has sufficient rights.
+
+Indeed, the UID/GID pair must be configured to 0 (right UNIX root).
+
+If this is not the case, you will have access errors to your NAS-HA because, when NFS is authorised on a Windows machine, a UNIX user is created with the default UID and GID at -2 (or 4294967294).
+
+As a workaround, the UID and GID can be forced to 0 on the Windows machine that accesses your NAS-HA:
+
+1. Start the registry editor on the client machine.
+1. Locate `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
+1. Create two DWORD values, namely **AnonymousUid** and **AnonymousGid**.
+1. Set these values on the UID and the GID to 0.
+1. Restart the NFS service on the client machine.
+
+All mounting options are available on the [Microsoft website](https://learn.microsoft.com/en-sg/windows-server/administration/windows-commands/mount).
+
 ### Proxmox
 
 In the Proxmox administration interface, click on `Storage`{.action} in the vertical menu.
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-us.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-us.md
index b351852f39d..6aa23998d9f 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-us.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-us.md
@@ -1,7 +1,7 @@
 ---
 title: Mounting HA-NAS via NFS share
 excerpt: Find out how to connect to your HA-NAS using an NFS share
-updated: 2024-11-08
+updated: 2025-10-08
 ---
 
 ## Objective 
@@ -133,6 +133,24 @@ root@server:~$ sudo mount -t nfs 10.1.1.1:/zpool-123456/partition01 /mount/ha_na
 
 You can now access your mounted partition at the specified folder.
 
+### Microsoft Windows - specificity
+
+Make sure that the Windows user who is used to access your NAS-HA has sufficient rights.
+
+Indeed, the UID/GID pair must be configured to 0 (right UNIX root).
+
+If this is not the case, you will have access errors to your NAS-HA because, when NFS is authorised on a Windows machine, a UNIX user is created with the default UID and GID at -2 (or 4294967294).
+
+As a workaround, the UID and GID can be forced to 0 on the Windows machine that accesses your NAS-HA:
+
+1. Start the registry editor on the client machine.
+1. Locate `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
+1. Create two DWORD values, namely **AnonymousUid** and **AnonymousGid**.
+1. Set these values on the UID and the GID to 0.
+1. Restart the NFS service on the client machine.
+
+All mounting options are available on the [Microsoft website](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/mount).
+
 ### Proxmox
 
 In the Proxmox administration interface, click on `Storage`{.action} in the vertical menu.
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.es-es.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.es-es.md
index f2a34251da0..b417005d33d 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.es-es.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.es-es.md
@@ -1,7 +1,7 @@
 ---
 title: "Montaje de un NAS-HA mediante NFS compartido"
 excerpt: "Cómo conectarse a un NAS-HA utilizando un recurso compartido por NFS"
-updated: 2024-11-08
+updated: 2025-10-08
 ---
 
 ## Objetivo 
@@ -133,6 +133,24 @@ root@server:~$ sudo mount -t nfs 10.1.1.1:/zpool-123456/partition01 /mount/ha_na
 
 Ahora puede acceder a la partición montada en la carpeta especificada.
 
+### Microsoft Windows - Particularidades
+
+Asegúrese de que el usuario de Windows utilizado para acceder a su NAS-HA tenga permisos suficientes.
+
+El par UID/GID debe configurarse en 0 (permisos root UNIX).
+
+De lo contrario, obtendrá errores de acceso a su NAS-HA, ya que cuando se habilita NFS en una máquina Windows, se crea un usuario UNIX con UID y GID predeterminados -2 (o 4294967294).
+
+Como solución alternativa, puede forzar UID y GID a 0 en la máquina Windows que accede a su NAS-HA:
+
+1. Inicie el editor del registro en la máquina cliente.
+1. Localice `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
+1. Cree dos valores DWORD: **AnonymousUid** y **AnonymousGid**.
+1. Establezca estos valores en UID y GID 0.
+1. Reinicie el servicio NFS en la máquina cliente.
+
+Todas las opciones de montaje están disponibles en el [sitio de Microsoft](https://learn.microsoft.com/es-es/windows-server/administration/windows-commands/mount).
+
 ### Proxmox
 
 En el panel de administración de Proxmox, haga clic en `Storage`{.action} en el menú vertical.
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.es-us.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.es-us.md
index f2a34251da0..f24acf8b302 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.es-us.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.es-us.md
@@ -1,7 +1,7 @@
 ---
 title: "Montaje de un NAS-HA mediante NFS compartido"
 excerpt: "Cómo conectarse a un NAS-HA utilizando un recurso compartido por NFS"
-updated: 2024-11-08
+updated: 2025-10-08
 ---
 
 ## Objetivo 
@@ -133,6 +133,24 @@ root@server:~$ sudo mount -t nfs 10.1.1.1:/zpool-123456/partition01 /mount/ha_na
 
 Ahora puede acceder a la partición montada en la carpeta especificada.
 
+### Microsoft Windows - Particularidades
+
+Asegúrese de que el usuario de Windows utilizado para acceder a su NAS-HA tenga permisos suficientes.
+
+El par UID/GID debe configurarse en 0 (permisos root UNIX).
+
+De lo contrario, obtendrá errores de acceso a su NAS-HA, ya que cuando se habilita NFS en una máquina Windows, se crea un usuario UNIX con UID y GID predeterminados -2 (o 4294967294).
+
+Como solución alternativa, puede forzar UID y GID a 0 en la máquina Windows que accede a su NAS-HA:
+
+1. Inicie el editor del registro en la máquina cliente.
+1. Localice `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
+1. Cree dos valores DWORD: **AnonymousUid** y **AnonymousGid**.
+1. Establezca estos valores en UID y GID 0.
+1. Reinicie el servicio NFS en la máquina cliente.
+
+Todas las opciones de montaje están disponibles en el [sitio de Microsoft](https://learn.microsoft.com/es-us/windows-server/administration/windows-commands/mount).
+
 ### Proxmox
 
 En el panel de administración de Proxmox, haga clic en `Storage`{.action} en el menú vertical.
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.fr-ca.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.fr-ca.md
index 95c647a2b39..c02c8a7aa1e 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.fr-ca.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.fr-ca.md
@@ -1,7 +1,7 @@
 ---
 title: Montage d'un NAS-HA via partage NFS
 excerpt: Découvrez comment vous connecter à votre NAS-HA en utilisant un partage NFS
-updated: 2024-11-08
+updated: 2025-10-08
 ---
 
 ## Objectif
@@ -134,6 +134,24 @@ root@server:~$ sudo mount -t nfs 10.1.1.1:/zpool-123456/partition01 /mount/ha_na
 
 Vous pouvez maintenant accéder à votre partition montée dans le dossier spécifié.
 
+### Microsoft Windows - Particularités
+
+Assurez-vous que l'utilisateur Windows qui est utilisé pour accéder à votre NAS-HA dispose de droits suffisants.
+
+En effet, le couple UID/GID doit être configuré à 0 (droit root UNIX).
+
+Si ce n'est pas le cas, vous obtiendrez des erreurs d'accès à votre NAS-HA, car lorsque NFS est autorisé sur une machine Windows, un utilisateur UNIX est créé avec l'UID et le GID par défaut à -2 (ou 4294967294).
+
+Comme solution de contournement, l'UID et le GID peuvent être forcés à 0 sur la machine Windows qui accède à votre NAS-HA :
+
+1. Démarrez l'éditeur de registre sur la machine cliente.
+1. Localisez `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
+1. Créez deux valeurs DWORD, à savoir **AnonymousUid** et **AnonymousGid**.
+1. Définissez ces valeurs sur l'UID et le GID à 0.
+1. Redémarrez le service NFS sur la machine cliente.
+
+Toutes les options de montage sont disponibles sur le [site de Microsoft](https://learn.microsoft.com/fr-ca/windows-server/administration/windows-commands/mount).
+
 ### Proxmox
 
 Dans l’interface d’administration Proxmox, cliquez sur `Storage`{.action} dans le menu vertical.
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.fr-fr.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.fr-fr.md
index f99cddd24f8..af2cdb68539 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.fr-fr.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.fr-fr.md
@@ -138,19 +138,19 @@ Vous pouvez maintenant accéder à votre partition montée dans le dossier spéc
 
 Assurez-vous que l'utilisateur Windows qui est utilisé pour accéder à votre NAS-HA dispose de droits suffisants.
 
-En effet, le couple UID/GID doit être configuré à 0 (droit unix root).
+En effet, le couple UID/GID doit être configuré à 0 (droit root UNIX).
 
-Si ce n'est pas le cas, vous aurez des erreurs d'accès à votre NAS-HA car, lorsque NFS est autorisé sur une machine Windows, un utilisateur UNIX est créé avec l'UID et le GID par défaut à -2 (ou 4294967294).
+Si ce n'est pas le cas, vous obtiendrez des erreurs d'accès à votre NAS-HA, car lorsque NFS est autorisé sur une machine Windows, un utilisateur UNIX est créé avec l'UID et le GID par défaut à -2 (ou 4294967294).
 
-Comme solution de contournement, l'UID et le GID peuvent être forcés à 0 sur la machine Windows qui accède à votre NAS-HA.
+Comme solution de contournement, l'UID et le GID peuvent être forcés à 0 sur la machine Windows qui accède à votre NAS-HA :
 
-- Démarrez l'éditeur de registre sur la machine cliente.
-- Localisez `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
-- Créez deux valeurs DWORD, à savoir AnonymousUid et AnonymousGid.
-- Définissez ces valeurs sur l'UID et le GID à 0.
-- Redémarrez le service NFS sur la machine cliente.
+1. Démarrez l'éditeur de registre sur la machine cliente.
+1. Localisez `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
+1. Créez deux valeurs DWORD, à savoir **AnonymousUid** et **AnonymousGid**.
+1. Définissez ces valeurs sur l'UID et le GID à 0.
+1. Redémarrez le service NFS sur la machine cliente.
 
-Toutes les options de montage sont disponibles sur le site de Microsoft : https://learn.microsoft.com/fr-fr/windows-server/administration/windows-commands/mount
+Toutes les options de montage sont disponibles sur le [site de Microsoft](https://learn.microsoft.com/fr-fr/windows-server/administration/windows-commands/mount).
 
 ### Proxmox
 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.it-it.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.it-it.md
index 9bf06658379..74e8ffb7ccd 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.it-it.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.it-it.md
@@ -1,7 +1,7 @@
 ---
 title: "Installazione di un NAS-HA tramite condivisione NFS"
 excerpt: "Come connettersi al tuo NAS-HA utilizzando una condivisione NFS"
-updated: 2024-11-08
+updated: 2025-10-08
 ---
 
 ## Obiettivo 
@@ -133,6 +133,24 @@ root@server:~$ sudo mount -t nfs 10.1.1.1:/zpool-123456/partition01 /mount/ha_na
 
 Adesso puoi accedere alla tua partizione montata nella cartella specificata.
 
+### Microsoft Windows - Particolari
+
+Assicurarsi che l'utente Windows utilizzato per accedere al proprio NAS-HA abbia i diritti sufficienti.
+
+La coppia UID/GID deve essere configurata su 0 (diritti root UNIX).
+
+Altrimenti, si otterranno errori di accesso al proprio NAS-HA, poiché quando NFS è abilitato su una macchina Windows, viene creato un utente UNIX con UID e GID predefiniti -2 (o 4294967294).
+
+Come soluzione alternativa, UID e GID possono essere forzati a 0 sulla macchina Windows che accede al proprio NAS-HA:
+
+1. Avviare l'editor del registro sulla macchina client.
+1. Localizzare `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
+1. Creare due valori DWORD: **AnonymousUid** e **AnonymousGid**.
+1. Impostare questi valori su UID e GID 0.
+1. Riavviare il servizio NFS sulla macchina client.
+
+Tutte le opzioni di montaggio sono disponibili sul [sito di Microsoft](https://learn.microsoft.com/it-it/windows-server/administration/windows-commands/mount).
+
 ### Proxmox
 
 Nell'interfaccia di amministrazione Proxmox, clicca su `Storage`{.action} nel menu verticale.
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.pl-pl.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.pl-pl.md
index f5daff86170..f2bf67f0616 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.pl-pl.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.pl-pl.md
@@ -1,7 +1,7 @@
 ---
 title: "Montowanie NAS-HA przy użyciu zasobów NFS"
 excerpt: "Dowiedz się, jak się zalogować do usługi NAS-HA przy użyciu protokołu NFS"
-updated: 2024-11-08
+updated: 2025-10-08
 ---
 
 ## Wprowadzenie
@@ -133,6 +133,24 @@ root@server:~$ sudo mount -t nfs 10.1.1.1:/zpool-123456/partition01 /mount/ha_na
 
 Teraz możesz przejść do partycji zamontowanej w określonym folderze.
 
+### Microsoft Windows - Cechy szczególne
+
+Upewnij się, że użytkownik Windows, który jest używany do uzyskiwania dostępu do Twojego NAS-HA, ma odpowiednie uprawnienia.
+
+Para UID/GID musi być skonfigurowana na 0 (uprawnienia root UNIX).
+
+W przeciwnym razie otrzymasz błędy dostępu do swojego NAS-HA, ponieważ gdy NFS jest włączony na maszynie Windows, tworzony jest użytkownik UNIX z UID i GID domyślnie -2 (lub 4294967294).
+
+Jako rozwiązanie awaryjne UID i GID można zmusić do 0 na maszynie Windows, która uzyskuje dostęp do Twojego NAS-HA:
+
+1. Uruchom edytor rejestru na maszynie klienckiej.
+1. Zlokalizuj 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default'.
+1. Utwórz dwa wartości DWORD: **AnonymousUid** i **AnonymousGid**.
+1. Ustaw te wartości na UID i GID 0.
+1. Uruchom ponownie usługę NFS na maszynie klienckiej.
+
+Wszystkie opcje montowania są dostępne na [stronie Microsoft](https://learn.microsoft.com/pl-pl/windows-server/administration/windows-commands/mount).
+
 ### Proxmox
 
 W interfejsie administracyjnym Proxmox kliknij `Storage`{.action} w menu pionowym.
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.pt-pt.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.pt-pt.md
index 70f95d6e8fd..4354c6e3411 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.pt-pt.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.pt-pt.md
@@ -1,7 +1,7 @@
 ---
 title: "Montagem de NAS-HA através de NFS"
 excerpt: "Saiba como conectar-se ao NAS-HA através de NFS"
-updated: 2024-11-08
+updated: 2025-10-08
 ---
 
 ## Objetivo 
@@ -133,6 +133,24 @@ root@server:~$ sudo mount -t nfs 10.1.1.1:/zpool-123456/partition01 /mount/ha_na
 
 Já pode aceder à sua partição montada na pasta especificada.
 
+### Microsoft Windows - Particularidades
+
+Certifique-se de que o usuário do Windows utilizado para acessar seu NAS-HA tenha permissões suficientes.
+
+O par UID/GID deve ser configurado para 0 (permissões root UNIX).
+
+Caso contrário, você obterá erros de acesso ao seu NAS-HA, pois quando o NFS é habilitado em uma máquina Windows, um usuário UNIX é criado com UID e GID padrão -2 (ou 4294967294).
+
+Como solução alternativa, UID e GID podem ser forçados a 0 na máquina Windows que acessa seu NAS-HA:
+
+1. Inicie o editor do registro na máquina cliente.
+1. Localize `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
+1. Crie dois valores DWORD: **AnonymousUid** e **AnonymousGid**.
+1. Defina esses valores para UID e GID 0.
+1. Reinicie o serviço NFS na máquina cliente.
+
+Todas as opções de montagem estão disponíveis no [site da Microsoft](https://learn.microsoft.com/pt-pt/windows-server/administration/windows-commands/mount).
+
 ### Proxmox
 
 Na interface de administração Proxmox, clique em `Storage`{.action} no menu vertical.

From 3f35345518befdc0390f688c4b95a9754305d39b Mon Sep 17 00:00:00 2001
From: benchbzh <benoit.chuchla@ovhcloud.com>
Date: Thu, 9 Oct 2025 11:05:24 +0200
Subject: [PATCH 12/16] additional proofreading

---
 .../services_backup_storage/guide.de-de.md     |  6 +++---
 .../services_backup_storage/guide.en-asia.md   |  6 +++---
 .../services_backup_storage/guide.en-au.md     |  6 +++---
 .../services_backup_storage/guide.en-ca.md     |  6 +++---
 .../services_backup_storage/guide.en-gb.md     |  6 +++---
 .../services_backup_storage/guide.en-ie.md     |  6 +++---
 .../services_backup_storage/guide.en-sg.md     |  6 +++---
 .../services_backup_storage/guide.en-us.md     |  6 +++---
 .../services_backup_storage/guide.es-es.md     |  7 +++----
 .../services_backup_storage/guide.es-us.md     |  6 +++---
 .../services_backup_storage/guide.fr-ca.md     |  6 +++---
 .../services_backup_storage/guide.fr-fr.md     |  6 +++---
 .../services_backup_storage/guide.it-it.md     |  6 +++---
 .../services_backup_storage/guide.pl-pl.md     |  6 +++---
 .../services_backup_storage/guide.pt-pt.md     |  6 +++---
 .../ha_nas/nas_cifs/guide.de-de.md             | 10 +++++-----
 .../ha_nas/nas_cifs/guide.en-asia.md           |  8 ++++----
 .../ha_nas/nas_cifs/guide.en-au.md             |  8 ++++----
 .../ha_nas/nas_cifs/guide.en-ca.md             |  8 ++++----
 .../ha_nas/nas_cifs/guide.en-gb.md             |  8 ++++----
 .../ha_nas/nas_cifs/guide.en-ie.md             |  8 ++++----
 .../ha_nas/nas_cifs/guide.en-sg.md             |  8 ++++----
 .../ha_nas/nas_cifs/guide.en-us.md             |  8 ++++----
 .../ha_nas/nas_cifs/guide.es-es.md             | 10 +++++-----
 .../ha_nas/nas_cifs/guide.es-us.md             | 10 +++++-----
 .../ha_nas/nas_cifs/guide.fr-ca.md             | 12 ++++++------
 .../ha_nas/nas_cifs/guide.fr-fr.md             | 12 ++++++------
 .../ha_nas/nas_cifs/guide.it-it.md             | 10 +++++-----
 .../ha_nas/nas_cifs/guide.pl-pl.md             | 10 +++++-----
 .../ha_nas/nas_cifs/guide.pt-pt.md             | 10 +++++-----
 .../file_storage/ha_nas/nas_nfs/guide.de-de.md | 18 +++++++++---------
 .../ha_nas/nas_nfs/guide.en-asia.md            | 18 +++++++++---------
 .../file_storage/ha_nas/nas_nfs/guide.en-au.md | 18 +++++++++---------
 .../file_storage/ha_nas/nas_nfs/guide.en-ca.md | 18 +++++++++---------
 .../file_storage/ha_nas/nas_nfs/guide.en-gb.md | 18 +++++++++---------
 .../file_storage/ha_nas/nas_nfs/guide.en-ie.md | 18 +++++++++---------
 .../file_storage/ha_nas/nas_nfs/guide.en-sg.md | 18 +++++++++---------
 .../file_storage/ha_nas/nas_nfs/guide.en-us.md | 18 +++++++++---------
 .../file_storage/ha_nas/nas_nfs/guide.es-es.md | 18 +++++++++---------
 .../file_storage/ha_nas/nas_nfs/guide.es-us.md | 18 +++++++++---------
 .../file_storage/ha_nas/nas_nfs/guide.fr-ca.md | 18 +++++++++---------
 .../file_storage/ha_nas/nas_nfs/guide.fr-fr.md | 18 +++++++++---------
 .../file_storage/ha_nas/nas_nfs/guide.it-it.md | 18 +++++++++---------
 .../file_storage/ha_nas/nas_nfs/guide.pl-pl.md | 18 +++++++++---------
 .../file_storage/ha_nas/nas_nfs/guide.pt-pt.md | 18 +++++++++---------
 45 files changed, 250 insertions(+), 251 deletions(-)

diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.de-de.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.de-de.md
index 30a47177015..316a1bf907e 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.de-de.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.de-de.md
@@ -347,9 +347,9 @@ You can't access this shared folder because your organization's security policie
 
 > [!primary]
 >
-> Dieser Fehler sollte durch Bearbeiten der Windows-Registrierung lösbar sein: Öffnen Sie das Windows-Dienstprogramm *regedit*, und suchen Sie nach dem Eintrag `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
-> Setzen Sie den Wert von `AllowInsecureGuestAuth` auf „1“.<br>
-> Weitere Informationen zu diesem Thema finden Sie auf den [Microsoft Support-Seiten](https://learn.microsoft.com/de-de/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+> Um diesen Fehler zu beheben, muss die Windows-Registrierungsdatenbank geändert werden. Öffnen Sie dazu den Registrierungseditor (regedit) und navigieren Sie zum Schlüssel `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters navigieren`.<br>
+> Setzen Sie den Wert des Parameters `AllowInsecureGuestAuth` auf "1".<br>
+> Weitere Informationen zu diesem Thema finden Sie auf den [Microsoft Supportseiten](https://learn.microsoft.com/de-de/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ##### Linux
 
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-asia.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-asia.md
index 2878db9ef77..1c03a44fded 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-asia.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-asia.md
@@ -343,9 +343,9 @@ You can't access this shared folder because your organization's security policie
 
 > [!primary]
 >
-> This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
-> Set the value of `AllowInsecureGuestAuth` to "1".<br>
-> You can find more information on this issue on the [Microsoft support pages](https://learn.microsoft.com/en-in/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+> To correct this error, you need to modify the Windows registry. To do this, open the Registry Editor (regedit), then navigate to the key `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Then set the value of the parameter `AllowInsecureGuestAuth` to "1".<br>
+> Find more information on this topic on the [Microsoft support pages](https://learn.microsoft.com/en-in/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ##### Linux
 
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-au.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-au.md
index 5d6e4e292f4..29d6673427e 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-au.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-au.md
@@ -341,9 +341,9 @@ You can't access this shared folder because your organization's security policie
 
 > [!primary]
 >
-> This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
-> Set the value of `AllowInsecureGuestAuth` to "1".<br>
-> You can find more information on this issue on the [Microsoft support pages](https://learn.microsoft.com/en-au/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+> To correct this error, you need to modify the Windows registry. To do this, open the Registry Editor (regedit), then navigate to the key `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Then set the value of the parameter `AllowInsecureGuestAuth` to "1".<br>
+> Find more information on this topic on the [Microsoft support pages](https://learn.microsoft.com/en-au/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ##### Linux
 
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-ca.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-ca.md
index 153c9a282d2..9f3ff1fa1db 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-ca.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-ca.md
@@ -341,9 +341,9 @@ You can't access this shared folder because your organization's security policie
 
 > [!primary]
 >
-> This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
-> Set the value of `AllowInsecureGuestAuth` to "1".<br>
-> You can find more information on this issue on the [Microsoft support pages](https://learn.microsoft.com/en-ca/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+> To correct this error, you need to modify the Windows registry. To do this, open the Registry Editor (regedit), then navigate to the key `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Then set the value of the parameter `AllowInsecureGuestAuth` to "1".<br>
+> Find more information on this topic on the [Microsoft support pages](https://learn.microsoft.com/en-ca/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ##### Linux
 
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-gb.md
index 1abd70effe3..6738d5691de 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-gb.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-gb.md
@@ -341,9 +341,9 @@ You can't access this shared folder because your organization's security policie
 
 > [!primary]
 >
-> This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
-> Set the value of `AllowInsecureGuestAuth` to "1".<br>
-> You can find more information on this issue on the [Microsoft support pages](https://learn.microsoft.com/en-gb/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+> To correct this error, you need to modify the Windows registry. To do this, open the Registry Editor (regedit), then navigate to the key `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Then set the value of the parameter `AllowInsecureGuestAuth` to "1".<br>
+> Find more information on this topic on the [Microsoft support pages](https://learn.microsoft.com/en-gb/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ##### Linux
 
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-ie.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-ie.md
index 886da71d61f..fb527c8cb69 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-ie.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-ie.md
@@ -341,9 +341,9 @@ You can't access this shared folder because your organization's security policie
 
 > [!primary]
 >
-> This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
-> Set the value of `AllowInsecureGuestAuth` to "1".<br>
-> You can find more information on this issue on the [Microsoft support pages](https://learn.microsoft.com/en-ie/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+> To correct this error, you need to modify the Windows registry. To do this, open the Registry Editor (regedit), then navigate to the key `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Then set the value of the parameter `AllowInsecureGuestAuth` to "1".<br>
+> Find more information on this topic on the [Microsoft support pages](https://learn.microsoft.com/en-ie/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ##### Linux
 
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-sg.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-sg.md
index 92b1ca21a13..5b4a3768b89 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-sg.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-sg.md
@@ -341,9 +341,9 @@ You can't access this shared folder because your organization's security policie
 
 > [!primary]
 >
-> This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
-> Set the value of `AllowInsecureGuestAuth` to "1".<br>
-> You can find more information on this issue on the [Microsoft support pages](https://learn.microsoft.com/en-sg/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+> To correct this error, you need to modify the Windows registry. To do this, open the Registry Editor (regedit), then navigate to the key `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Then set the value of the parameter `AllowInsecureGuestAuth` to "1".<br>
+> Find more information on this topic on the [Microsoft support pages](https://learn.microsoft.com/en-sg/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ##### Linux
 
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-us.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-us.md
index e0345d2d353..e8db6734d4d 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-us.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-us.md
@@ -341,9 +341,9 @@ You can't access this shared folder because your organization's security policie
 
 > [!primary]
 >
-> This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
-> Set the value of `AllowInsecureGuestAuth` to "1".<br>
-> You can find more information on this issue on the [Microsoft support pages](https://learn.microsoft.com/en-us/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+> To correct this error, you need to modify the Windows registry. To do this, open the Registry Editor (regedit), then navigate to the key `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Then set the value of the parameter `AllowInsecureGuestAuth` to "1".<br>
+> Find more information on this topic on the [Microsoft support pages](https://learn.microsoft.com/en-us/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ##### Linux
 
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.es-es.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.es-es.md
index 9063fad6297..04768f5ddcf 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.es-es.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.es-es.md
@@ -347,10 +347,9 @@ You can't access this shared folder because your organization's security policie
 
 > [!primary]
 >
-> Este problema se puede solucionar editando el Registro de Windows: abra la utilidad Windows *regedit* y busque la entrada `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
-> Establezca el valor de `AllowInsecureGuestAuth` en "1".<br>
-> Más información sobre este tema en [páginas de soporte técnico de Microsoft](https://learn.microsoft.com/es-es/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
-
+> Para corregir este error, es necesario modificar el registro de Windows. Para ello, abra el editor del registro (regedit) y acceda a la clave `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Asigne el valor "1" al parámetro `AllowInsecureGuestAuth`.<br>
+> Encuentre más información sobre este tema en las [páginas de asistencia de Microsoft](https://learn.microsoft.com/es-es/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ##### Linux
 
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.es-us.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.es-us.md
index cb0378fadc7..e60be5f55b5 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.es-us.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.es-us.md
@@ -347,9 +347,9 @@ You can't access this shared folder because your organization's security policie
 
 > [!primary]
 >
-> Este problema se puede solucionar editando el Registro de Windows: abra la utilidad Windows *regedit* y busque la entrada `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
-> Establezca el valor de `AllowInsecureGuestAuth` en "1".<br>
-> Más información sobre este tema en [páginas de soporte técnico de Microsoft](https://learn.microsoft.com/es-mx/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+> Para corregir este error, es necesario modificar el registro de Windows. Para ello, abra el editor del registro (regedit) y acceda a la clave `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Asigne el valor "1" al parámetro `AllowInsecureGuestAuth`.<br>
+> Encuentre más información sobre este tema en las [páginas de asistencia de Microsoft](https://learn.microsoft.com/es-mx/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 
 ##### Linux
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.fr-ca.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.fr-ca.md
index 6dd71123fcc..81752749050 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.fr-ca.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.fr-ca.md
@@ -348,9 +348,9 @@ You can't access this shared folder because your organization's security policie
 
 > [!primary]
 >
-> Ce problème peut être résolu en modifiant le Registre Windows : ouvrez l'utilitaire Windows *regedit* et recherchez l'entrée `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
-> Définissez la valeur de `AllowInsecureGuestAuth` sur « 1 ».<br>
-> Retrouvez plus d'informations sur ce sujet sur les [pages de support Microsoft](https://learn.microsoft.com/fr-ca/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+> Pour corriger cette erreur, il convient de modifier le registre Windows. Pour cela, ouvrez l’éditeur de registre (regedit), puis accédez à la clé `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Attribuez ensuite la valeur « 1 » au paramètre `AllowInsecureGuestAuth`.<br>
+> Retrouvez plus d'informations sur ce sujet sur les [pages d'assistance de Microsoft](https://learn.microsoft.com/fr-ca/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ##### Linux
 
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.fr-fr.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.fr-fr.md
index 5ca68e16796..5e78064aaaf 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.fr-fr.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.fr-fr.md
@@ -348,9 +348,9 @@ You can't access this shared folder because your organization's security policie
 
 > [!primary]
 >
-> Ce problème peut être résolu en modifiant le Registre Windows : ouvrez l'utilitaire Windows *regedit* et recherchez l'entrée `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
-> Définissez la valeur de `AllowInsecureGuestAuth` sur « 1 ».<br>
-> Retrouvez plus d'informations sur ce sujet sur les [pages de support Microsoft](https://learn.microsoft.com/fr-fr/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3?tabs=group-policy).
+> Pour corriger cette erreur, il convient de modifier la base de registre de Windows. Pour cela, ouvrez l’éditeur de registre (regedit), puis accédez à la clé `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Attribuez ensuite la valeur « 1 » au paramètre `AllowInsecureGuestAuth`.<br>
+> Retrouvez plus d'informations sur ce sujet sur les [pages d'assistance de Microsoft](https://learn.microsoft.com/fr-fr/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ##### Linux
 
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.it-it.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.it-it.md
index 391aa1b1049..7d9cb8596ff 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.it-it.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.it-it.md
@@ -347,9 +347,9 @@ You can't access this shared folder because your organization's security policie
 
 > [!primary]
 >
-> Questo problema può essere risolto modificando il Registro di sistema di Windows: aprire l'utilità Windows *regedit* e cercare la voce `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
-> Impostare il valore di `AllowInsecureGuestAuth` su "1".<br>
-> Per maggiori informazioni al riguardo, visitare le [pagine di supporto Microsoft](https://learn.microsoft.com/it-it/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+> Per correggere questo errore, è necessario modificare il registro di sistema di Windows. A tal fine, aprire l'editor del registro (regedit), quindi accedere alla chiave `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Assegnare il valore "1" al parametro `AllowInsecureGuestAuth`.<br>
+> Trova ulteriori informazioni su questo argomento sulle [pagine di supporto Microsoft](https://learn.microsoft.com/it-it/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ##### Linux
 
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.pl-pl.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.pl-pl.md
index 45bfa1359a6..a9ef71944a7 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.pl-pl.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.pl-pl.md
@@ -349,9 +349,9 @@ You can't access this shared folder because your organization's security policie
 
 > [!primary]
 >
-> Ten problem można rozwiązać, modyfikując rejestr systemu Windows: otwórz narzędzie systemu Windows *regedit* i wyszukaj wpis `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
-> Ustaw dla parametru `AllowInsecureGuestAuth` wartość "1".<br>
-> Więcej informacji na ten temat można znaleźć na [stronach pomocy technicznej firmy Microsoft](https://learn.microsoft.com/pl-pl/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+> Aby skorygować ten błąd, należy zmodyfikować rejestr systemu Windows. W tym celu należy otworzyć Edytor rejestru (regedit), a następnie przejść do klucza `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Ustaw wartość parametru `AllowInsecureGuestAuth` na "1".<br>
+> Znajdź więcej informacji na ten temat na [stronach pomocy Microsoft](https://learn.microsoft.com/pl-pl/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ##### Linux
 
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.pt-pt.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.pt-pt.md
index 13f68b78708..c95b3b2e954 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.pt-pt.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.pt-pt.md
@@ -347,9 +347,9 @@ You can't access this shared folder because your organization's security policie
 
 > [!primary]
 >
-> É possível resolver este problema alterando o registo do Windows: abra o utilitário Windows *regedit* e procure a entrada `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
-> Defina o valor de `AllowInsecureGuestAuth` como "1".<br>
-> Encontre mais informações sobre este assumpto nas [páginas de suporte da Microsoft](https://learn.microsoft.com/pt-pt/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+> Para corrigir este erro, é necessário alterar o registo do Windows. Para tal, abra o editor do registo (regedit) e aceda à chave `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Atribua o valor "1" ao parâmetro `AllowInsecureGuestAuth`.<br>
+> Encontre mais informações sobre este tópico nas [páginas de suporte da Microsoft](https://learn.microsoft.com/pt-pt/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ##### Linux
 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.de-de.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.de-de.md
index fd593b0e073..ee587d64c9c 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.de-de.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.de-de.md
@@ -1,12 +1,12 @@
 ---
 title: Mounten Sie Ihr HA-NAS über eine CIFS-Freigabe
-excerpt: Diese Anleitung zeigt Ihnen, wie Sie Ihr HA-NAS über das CIFS-Protokoll einbinden können
+excerpt: In dieser Anleitung erfahren Sie, wie Sie Ihr HA-NAS über das CIFS-Protokoll mounten können.
 updated: 2025-10-08
 ---
 
 ## Ziel
 
-Konfigurieren und mounten Sie einen OVHcloud HA-NAS-Speicherplatz mithilfe des CIFS-Protokolls.
+**Diese Anleitung erklärt, wie Sie einen OVHcloud HA-NAS-Speicherplatz über das CIFS-Protokoll konfigurieren und mounten können.**
 
 ## Voraussetzungen
 
@@ -51,9 +51,9 @@ You can't access this shared folder because your organization's security policie
 
 > [!primary]
 >
-> Dieser Fehler sollte durch Bearbeiten der Windows-Registrierung lösbar sein: Öffnen Sie das Windows-Dienstprogramm *regedit*, und suchen Sie nach dem Eintrag `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
-> Setzen Sie den Wert von `AllowInsecureGuestAuth` auf „1“.<br>
-> Weitere Informationen zu diesem Thema finden Sie auf den [Microsoft Support-Seiten](https://learn.microsoft.com/de-de/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+> Um diesen Fehler zu beheben, muss die Windows-Registrierungsdatenbank geändert werden. Öffnen Sie dazu den Registrierungseditor (regedit) und navigieren Sie zum Schlüssel `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters navigieren`.<br>
+> Setzen Sie den Wert des Parameters `AllowInsecureGuestAuth` auf "1".<br>
+> Weitere Informationen zu diesem Thema finden Sie auf den [Microsoft Supportseiten](https://learn.microsoft.com/de-de/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ### Einstellungen für Linux
 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-asia.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-asia.md
index f1fc4ec4068..226e311c8f3 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-asia.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-asia.md
@@ -6,7 +6,7 @@ updated: 2025-10-08
 
 ## Objective
 
-Configure and mount an OVHcloud HA-NAS storage space using CIFS protocol.
+**Find out how to configure and mount an OVHcloud HA-NAS storage space using CIFS protocol.**
 
 ## Requirements
 
@@ -51,9 +51,9 @@ You can't access this shared folder because your organization's security policie
 
 > [!primary]
 >
-> This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
-> Set the value of `AllowInsecureGuestAuth` to "1".<br>
-> You can find more information on this issue on the [Microsoft support pages](https://learn.microsoft.com/en-in/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+> To correct this error, you need to modify the Windows registry. To do this, open the Registry Editor (regedit), then navigate to the key `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Then set the value of the parameter `AllowInsecureGuestAuth` to "1".<br>
+> Find more information on this topic on the [Microsoft support pages](https://learn.microsoft.com/en-in/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ### Settings for Linux
 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-au.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-au.md
index acbf96552de..f2b34d8462a 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-au.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-au.md
@@ -6,7 +6,7 @@ updated: 2025-10-08
 
 ## Objective
 
-Configure and mount an OVHcloud HA-NAS storage space using CIFS protocol.
+**Find out how to configure and mount an OVHcloud HA-NAS storage space using CIFS protocol.**
 
 ## Requirements
 
@@ -51,9 +51,9 @@ You can't access this shared folder because your organization's security policie
 
 > [!primary]
 >
-> This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
-> Set the value of `AllowInsecureGuestAuth` to "1".<br>
-> You can find more information on this issue on the [Microsoft support pages](https://learn.microsoft.com/en-au/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+> To correct this error, you need to modify the Windows registry. To do this, open the Registry Editor (regedit), then navigate to the key `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Then set the value of the parameter `AllowInsecureGuestAuth` to "1".<br>
+> Find more information on this topic on the [Microsoft support pages](https://learn.microsoft.com/en-au/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ### Settings for Linux
 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-ca.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-ca.md
index bbf50edc7fc..d5cc02bc5e7 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-ca.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-ca.md
@@ -6,7 +6,7 @@ updated: 2025-10-08
 
 ## Objective
 
-Configure and mount an OVHcloud HA-NAS storage space using CIFS protocol.
+**Find out how to configure and mount an OVHcloud HA-NAS storage space using CIFS protocol.**
 
 ## Requirements
 
@@ -51,9 +51,9 @@ You can't access this shared folder because your organization's security policie
 
 > [!primary]
 >
-> This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
-> Set the value of `AllowInsecureGuestAuth` to "1".<br>
-> You can find more information on this issue on the [Microsoft support pages](https://learn.microsoft.com/en-ca/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+> To correct this error, you need to modify the Windows registry. To do this, open the Registry Editor (regedit), then navigate to the key `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Then set the value of the parameter `AllowInsecureGuestAuth` to "1".<br>
+> Find more information on this topic on the [Microsoft support pages](https://learn.microsoft.com/en-ca/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ### Settings for Linux
 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-gb.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-gb.md
index 17147242552..8bcb92a8c69 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-gb.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-gb.md
@@ -6,7 +6,7 @@ updated: 2025-10-08
 
 ## Objective
 
-Configure and mount an OVHcloud HA-NAS storage space using CIFS protocol.
+**Find out how to configure and mount an OVHcloud HA-NAS storage space using CIFS protocol.**
 
 ## Requirements
 
@@ -51,9 +51,9 @@ You can't access this shared folder because your organization's security policie
 
 > [!primary]
 >
-> This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
-> Set the value of `AllowInsecureGuestAuth` to "1".<br>
-> You can find more information on this issue on the [Microsoft support pages](https://learn.microsoft.com/en-gb/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+> To correct this error, you need to modify the Windows registry. To do this, open the Registry Editor (regedit), then navigate to the key `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Then set the value of the parameter `AllowInsecureGuestAuth` to "1".<br>
+> Find more information on this topic on the [Microsoft support pages](https://learn.microsoft.com/en-gb/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ### Settings for Linux
 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-ie.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-ie.md
index de00e18f494..b35fab6f749 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-ie.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-ie.md
@@ -6,7 +6,7 @@ updated: 2025-10-08
 
 ## Objective
 
-Configure and mount an OVHcloud HA-NAS storage space using CIFS protocol.
+**Find out how to configure and mount an OVHcloud HA-NAS storage space using CIFS protocol.**
 
 ## Requirements
 
@@ -51,9 +51,9 @@ You can't access this shared folder because your organization's security policie
 
 > [!primary]
 >
-> This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
-> Set the value of `AllowInsecureGuestAuth` to "1".<br>
-> You can find more information on this issue on the [Microsoft support pages](https://learn.microsoft.com/en-ie/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+> To correct this error, you need to modify the Windows registry. To do this, open the Registry Editor (regedit), then navigate to the key `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Then set the value of the parameter `AllowInsecureGuestAuth` to "1".<br>
+> Find more information on this topic on the [Microsoft support pages](https://learn.microsoft.com/en-ie/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ### Settings for Linux
 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-sg.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-sg.md
index 62dcf6c64cb..265fabe1a57 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-sg.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-sg.md
@@ -6,7 +6,7 @@ updated: 2025-10-08
 
 ## Objective
 
-Configure and mount an OVHcloud HA-NAS storage space using CIFS protocol.
+**Find out how to configure and mount an OVHcloud HA-NAS storage space using CIFS protocol.**
 
 ## Requirements
 
@@ -51,9 +51,9 @@ You can't access this shared folder because your organization's security policie
 
 > [!primary]
 >
-> This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
-> Set the value of `AllowInsecureGuestAuth` to "1".<br>
-> You can find more information on this issue on the [Microsoft support pages](https://learn.microsoft.com/en-sg/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+> To correct this error, you need to modify the Windows registry. To do this, open the Registry Editor (regedit), then navigate to the key `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Then set the value of the parameter `AllowInsecureGuestAuth` to "1".<br>
+> Find more information on this topic on the [Microsoft support pages](https://learn.microsoft.com/en-sg/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ### Settings for Linux
 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-us.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-us.md
index 3bd82df2fd7..c6a9931dafd 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-us.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-us.md
@@ -6,7 +6,7 @@ updated: 2025-10-08
 
 ## Objective
 
-Configure and mount an OVHcloud HA-NAS storage space using CIFS protocol.
+**Find out how to configure and mount an OVHcloud HA-NAS storage space using CIFS protocol.**
 
 ## Requirements
 
@@ -51,9 +51,9 @@ You can't access this shared folder because your organization's security policie
 
 > [!primary]
 >
-> This error should be resolvable by modifying the Windows Registry: Open the Windows utility *regedit* and locate the entry `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
-> Set the value of `AllowInsecureGuestAuth` to "1".<br>
-> You can find more information on this issue on the [Microsoft support pages](https://learn.microsoft.com/en-us/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+> To correct this error, you need to modify the Windows registry. To do this, open the Registry Editor (regedit), then navigate to the key `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Then set the value of the parameter `AllowInsecureGuestAuth` to "1".<br>
+> Find more information on this topic on the [Microsoft support pages](https://learn.microsoft.com/en-us/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ### Settings for Linux
 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.es-es.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.es-es.md
index fd96847e234..c10e6890d35 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.es-es.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.es-es.md
@@ -1,12 +1,12 @@
 ---
 title: Montar un NAS-HA a través de un recurso compartido CIFS
-excerpt: Descubra cómo montar un NAS-HA a través del protocolo CIFS
+excerpt: Configurar y montar un NAS-HA mediante el protocolo CIFS
 updated: 2025-10-08
 ---
 
 ## Objetivo
 
-Configure y monte su espacio de almacenamiento NAS-HA OVHcloud a través del protocolo CIFS.
+**Descubra cómo configurar y montar su espacio de almacenamiento NAS-HA OVHcloud mediante el protocolo CIFS.**
 
 ## Requisitos
 
@@ -51,9 +51,9 @@ You can't access this shared folder because your organization's security policie
 
 > [!primary]
 >
-> Este problema se puede solucionar editando el Registro de Windows: abra la utilidad Windows *regedit* y busque la entrada `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
-> Establezca el valor de `AllowInsecureGuestAuth` en "1".<br>
-> Más información sobre este tema en [páginas de soporte técnico de Microsoft](https://learn.microsoft.com/es-es/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+> Para corregir este error, es necesario modificar el registro de Windows. Para ello, abra el editor del registro (regedit) y acceda a la clave `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Asigne el valor "1" al parámetro `AllowInsecureGuestAuth`.<br>
+> Encuentre más información sobre este tema en las [páginas de asistencia de Microsoft](https://learn.microsoft.com/es-es/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ### Configuración para Linux
 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.es-us.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.es-us.md
index 6e6ea6dbcf8..f69d420a8ae 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.es-us.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.es-us.md
@@ -1,12 +1,12 @@
 ---
 title: Montar un NAS-HA a través de un recurso compartido CIFS
-excerpt: Descubra cómo montar un NAS-HA a través del protocolo CIFS
+excerpt: Configurar y montar un NAS-HA mediante el protocolo CIFS
 updated: 2025-10-08
 ---
 
 ## Objetivo
 
-Configure y monte su espacio de almacenamiento NAS-HA OVHcloud a través del protocolo CIFS.
+**Descubra cómo configurar y montar su espacio de almacenamiento NAS-HA OVHcloud mediante el protocolo CIFS.**
 
 ## Requisitos
 
@@ -51,9 +51,9 @@ You can't access this shared folder because your organization's security policie
 
 > [!primary]
 >
-> Este problema se puede solucionar editando el Registro de Windows: abra la utilidad Windows *regedit* y busque la entrada `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
-> Establezca el valor de `AllowInsecureGuestAuth` en "1".<br>
-> Más información sobre este tema en [páginas de soporte técnico de Microsoft](https://learn.microsoft.com/es-mx/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+> Para corregir este error, es necesario modificar el registro de Windows. Para ello, abra el editor del registro (regedit) y acceda a la clave `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Asigne el valor "1" al parámetro `AllowInsecureGuestAuth`.<br>
+> Encuentre más información sobre este tema en las [páginas de asistencia de Microsoft](https://learn.microsoft.com/es-mx/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ### Configuración para Linux
 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-ca.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-ca.md
index efb2a31a2a2..ad4efd9d204 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-ca.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-ca.md
@@ -1,12 +1,12 @@
 ---
 title: Monter un NAS-HA via un partage CIFS
-excerpt: Decouvrez comment monter un NAS-HA via le protocole CIFS
+excerpt: Configurer et monter un NAS-HA via le protocole CIFS
 updated: 2025-10-08
 ---
 
 ## Objectif
 
-Configurez et montez votre espace de stockage NAS-HA OVHcloud via le protocole CIFS.
+**Découvrez comment configurer et monter votre espace de stockage NAS-HA OVHcloud via le protocole CIFS.**
 
 ## Prérequis
 
@@ -51,9 +51,9 @@ You can't access this shared folder because your organization's security policie
 
 > [!primary]
 >
-> Ce problème peut être résolu en modifiant le Registre Windows : ouvrez l'utilitaire Windows *regedit* et recherchez l'entrée `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
-> Définissez la valeur de `AllowInsecureGuestAuth` sur « 1 ».<br>
-> Retrouvez plus d'informations sur ce sujet sur les [pages de support Microsoft](https://learn.microsoft.com/fr-ca/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+> Pour corriger cette erreur, il convient de modifier le registre Windows. Pour cela, ouvrez l’éditeur de registre (regedit), puis accédez à la clé `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Attribuez ensuite la valeur « 1 » au paramètre `AllowInsecureGuestAuth`.<br>
+> Retrouvez plus d'informations sur ce sujet sur les [pages d'assistance de Microsoft](https://learn.microsoft.com/fr-ca/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ### Configuration pour Linux
 
@@ -65,7 +65,7 @@ mount -t cifs -o uid=root,gid=100,dir_mode=0700,username=root,password= //IP_SER
 
 > [!warning]
 >
-> Afin de monter des partages par nom d'hôte (par opposition aux adresses IP), l'utilitaire `mount.cifs` est requis. Il fait généralement partie du paquet `cifs-utils`.
+> Pour monter des partages par nom d'hôte (par opposition aux adresses IP), l'utilitaire `mount.cifs` est requis. Il fait généralement partie du paquet `cifs-utils`.
 >
 > `mount.cifs` est un wrapper qui résout les noms d'hôte et ajoute le paramètre `ip=` aux paramètres de montage transmis au noyau.
 >
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-fr.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-fr.md
index 7c08a90f5c1..ada534c4cc1 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-fr.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-fr.md
@@ -1,12 +1,12 @@
 ---
 title: Monter un NAS-HA via un partage CIFS
-excerpt: Decouvrez comment monter un NAS-HA via le protocole CIFS
+excerpt: Configurer et monter un NAS-HA via le protocole CIFS
 updated: 2025-10-08
 ---
 
 ## Objectif
 
-Configurez et montez votre espace de stockage NAS-HA OVHcloud via le protocole CIFS.
+**Découvrez comment configurer et monter votre espace de stockage NAS-HA OVHcloud via le protocole CIFS.**
 
 ## Prérequis
 
@@ -51,9 +51,9 @@ You can't access this shared folder because your organization's security policie
 
 > [!primary]
 >
-> Ce problème peut être résolu en modifiant le Registre Windows : ouvrez l'utilitaire Windows *regedit* et recherchez l'entrée `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
-> Définissez la valeur de `AllowInsecureGuestAuth` sur « 1 ».<br>
-> Retrouvez plus d'informations sur ce sujet sur les [pages de support Microsoft](https://learn.microsoft.com/fr-fr/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3?tabs=group-policy).
+> Pour corriger cette erreur, il convient de modifier le registre Windows. Pour cela, ouvrez l’éditeur de registre (regedit), puis accédez à la clé `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Attribuez ensuite la valeur « 1 » au paramètre `AllowInsecureGuestAuth`.<br>
+> Retrouvez plus d'informations sur ce sujet sur les [pages d'assistance de Microsoft](https://learn.microsoft.com/fr-fr/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3?tabs=group-policy).
 
 
 ### Configuration pour Linux
@@ -66,7 +66,7 @@ mount -t cifs -o uid=root,gid=100,dir_mode=0700,username=root,password= //IP_SER
 
 > [!warning]
 >
-> Afin de monter des partages par nom d'hôte (par opposition aux adresses IP), l'utilitaire `mount.cifs` est requis. Il fait généralement partie du paquet `cifs-utils`.
+> Pour monter des partages par nom d'hôte (par opposition aux adresses IP), l'utilitaire `mount.cifs` est requis. Il fait généralement partie du paquet `cifs-utils`.
 >
 > `mount.cifs` est un wrapper qui résout les noms d'hôte et ajoute le paramètre `ip=` aux paramètres de montage transmis au noyau.
 >
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.it-it.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.it-it.md
index 91c11f6ce10..bb12cfec87f 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.it-it.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.it-it.md
@@ -1,12 +1,12 @@
 ---
 title: Montare un NAS-HA tramite condivisione CIFS
-excerpt: Scopri come montare un NAS-HA tramite il protocollo CIFS
+excerpt: Configurare e montare un NAS-HA tramite il protocollo CIFS
 updated: 2025-10-08
 ---
 
 ## Obiettivo
 
-Configura e monta il tuo spazio di archiviazione NAS-HA OVHcloud tramite il protocollo CIFS.
+**Questa guida ti mostra come configurare e montare il tuo spazio di archiviazione NAS-HA OVHcloud tramite il protocollo CIFS.**
 
 ## Prerequisiti
 
@@ -51,9 +51,9 @@ You can't access this shared folder because your organization's security policie
 
 > [!primary]
 >
-> Questo problema può essere risolto modificando il Registro di sistema di Windows: aprire l'utilità Windows *regedit* e cercare la voce `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
-> Impostare il valore di `AllowInsecureGuestAuth` su "1".<br>
-> Per maggiori informazioni al riguardo, visitare le [pagine di supporto Microsoft](https://learn.microsoft.com/it-it/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+> Per correggere questo errore, è necessario modificare il registro di sistema di Windows. A tal fine, aprire l'editor del registro (regedit), quindi accedere alla chiave `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Assegnare il valore "1" al parametro `AllowInsecureGuestAuth`.<br>
+> Trova ulteriori informazioni su questo argomento sulle [pagine di supporto Microsoft](https://learn.microsoft.com/it-it/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ### Configurazione per Linux
 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.pl-pl.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.pl-pl.md
index b36b9abac4f..fbb10eb06e2 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.pl-pl.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.pl-pl.md
@@ -1,12 +1,12 @@
 ---
 title: Podłącz HA-NAS za pomocą udziału CIFS
-excerpt: Ten przewodnik pokazuje, jak podłączyć HA-NAS za pomocą protokołu CIFS
+excerpt: W tym przewodniku opisano sposób montowania HA-NAS przy użyciu protokołu CIFS.
 updated: 2025-10-08
 ---
 
 ## Wprowadzenie
 
-Skonfiguruj i zamontuj przestrzeń dyskową OVHcloud HA-NAS przy użyciu protokołu CIFS.
+**Dowiedz się, jak skonfigurować i zamontować przestrzeń dyskową OVHcloud HA-NAS przy użyciu protokołu CIFS.**
 
 ## Wymagania początkowe
 
@@ -51,9 +51,9 @@ You can't access this shared folder because your organization's security policie
 
 > [!primary]
 >
-> Ten problem można rozwiązać, modyfikując rejestr systemu Windows: otwórz narzędzie systemu Windows *regedit* i wyszukaj wpis `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
-> Ustaw dla parametru `AllowInsecureGuestAuth` wartość "1".<br>
-> Więcej informacji na ten temat można znaleźć na [stronach pomocy technicznej firmy Microsoft](https://learn.microsoft.com/pl-pl/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+> Aby skorygować ten błąd, należy zmodyfikować rejestr systemu Windows. W tym celu należy otworzyć Edytor rejestru (regedit), a następnie przejść do klucza `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Ustaw wartość parametru `AllowInsecureGuestAuth` na "1".<br>
+> Znajdź więcej informacji na ten temat na [stronach pomocy Microsoft](https://learn.microsoft.com/pl-pl/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ### Ustawienia dla systemu Linux
 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.pt-pt.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.pt-pt.md
index eed7c9fcbc6..1191b92d106 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.pt-pt.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.pt-pt.md
@@ -1,12 +1,12 @@
 ---
 title: Configure o seu NAS-HA no Windows Server através do CIFS
-excerpt: Saiba como montar um NAS-HA no Windows Server através do CIFS.
+excerpt: Configurar e montar um NAS-HA através do protocolo CIFS
 updated: 2025-10-08
 ---
 
 ## Objetivo
 
-Configure e monte o seu espaço de armazenamento NAS-HA OVHcloud no Windows Server através de CIFS.
+**Saiba como configurar e montar o seu espaço de armazenamento NAS-HA OVHcloud através do protocolo CIFS.**
 
 ## Requisitos
 
@@ -51,9 +51,9 @@ You can't access this shared folder because your organization's security policie
 
 > [!primary]
 >
-> É possível resolver este problema alterando o registo do Windows: abra o utilitário Windows *regedit* e procure a entrada `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
-> Defina o valor de `AllowInsecureGuestAuth` como "1".<br>
-> Encontre mais informações sobre este assumpto nas [páginas de suporte da Microsoft](https://learn.microsoft.com/pt-pt/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
+> Para corrigir este erro, é necessário alterar o registo do Windows. Para tal, abra o editor do registo (regedit) e aceda à chave `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.<br>
+> Atribua o valor "1" ao parâmetro `AllowInsecureGuestAuth`.<br>
+> Encontre mais informações sobre este tópico nas [páginas de suporte da Microsoft](https://learn.microsoft.com/pt-pt/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ### Configuração para Linux
 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.de-de.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.de-de.md
index 40f0b19af78..9c0a6fa1100 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.de-de.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.de-de.md
@@ -136,19 +136,19 @@ Sie können nun über den angegebenen Ordner auf Ihre gemountete Partition zugre
 
 ### Microsoft Windows - Besonderheiten
 
-Stellen Sie sicher, dass der Windows-Benutzer, der für den Zugriff auf Ihr HA-NAS verwendet wird, ausreichende Rechte hat.
+Stellen Sie sicher, dass der Windows-Benutzer, der auf Ihr NAS-HA zugreifen muss, über die erforderlichen Rechte verfügt.
 
-Der UID/GID-Paar muss auf 0 konfiguriert werden (UNIX-Rechte root).
+Das UID/GID-Paar muss auf „0” (UNIX-Root-Rechte) gesetzt sein.
 
-Andernfalls erhalten Sie Zugriffsfehler auf Ihr HA-NAS, da bei aktiviertem NFS auf einem Windows-System ein UNIX-Benutzer mit der Standard-UID und GID -2 (oder 4294967294) erstellt wird.
+Ist dies nicht der Fall, können beim Zugriff auf das NAS-HA Fehler auftreten. Der Grund dafür ist, dass bei Aktivierung des NFS-Protokolls auf einem Windows-Rechner automatisch ein UNIX-Benutzer mit einer Standard-UID und -GID von „-2” (oder 4294967294) erstellt wird, wodurch der Zugriff eingeschränkt wird.
 
-Als Lösung können UID und GID auf 0 gesetzt werden, um den Zugriff auf Ihr HA-NAS zu ermöglichen:
+Als Workaround können die UID und GID auf dem Windows-Rechner, der auf Ihr NAS-HA zugreift, auf „0“ gesetzt werden:
 
-1. Starten Sie den Registrierungseditor auf dem Client-System.
-1. Navigieren Sie zu `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
-1. Erstellen Sie zwei DWORD-Werte: **AnonymousUid** und **AnonymousGid**.
-1. Setzen Sie diese Werte auf 0 für UID und GID.
-1. Starten Sie den NFS-Dienst auf dem Client-System neu.
+1. Öffnen Sie den Registrierungseditor (regedit) auf dem Client-Rechner.
+1. Navigieren Sie zu folgendem Schlüssel: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
+1. Erstellen Sie die folgenden zwei DWORD-Einträge: **AnonymousUid** und **AnonymousGid**.
+1. Weisen Sie jedem dieser Einträge den Wert „0“ zu.
+1. Starten Sie den NFS-Dienst auf dem Client-Computer neu, um die Änderungen zu übernehmen.
 
 Alle Einhängeoptionen sind auf der [Microsoft-Website](https://learn.microsoft.com/de-de/windows-server/administration/windows-commands/mount) verfügbar.
 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-asia.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-asia.md
index d2b9489f3b9..1c2840e69d9 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-asia.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-asia.md
@@ -135,19 +135,19 @@ You can now access your mounted partition at the specified folder.
 
 ### Microsoft Windows - specificity
 
-Make sure that the Windows user who is used to access your NAS-HA has sufficient rights.
+Ensure that the Windows user who needs to access your NAS-HA has the necessary rights.
 
-Indeed, the UID/GID pair must be configured to 0 (right UNIX root).
+The UID/GID pair must be set to "0" (UNIX root rights).
 
-If this is not the case, you will have access errors to your NAS-HA because, when NFS is authorised on a Windows machine, a UNIX user is created with the default UID and GID at -2 (or 4294967294).
+If this is not the case, errors may occur when accessing the NAS-HA. This is because when the NFS protocol is enabled on a Windows machine, a UNIX user is automatically created with a default UID and GID set to "-2" (or 4294967294), which restricts access.
 
-As a workaround, the UID and GID can be forced to 0 on the Windows machine that accesses your NAS-HA:
+As a workaround, the UID and GID can be forced to "0" on the Windows machine accessing your NAS-HA:
 
-1. Start the registry editor on the client machine.
-1. Locate `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
-1. Create two DWORD values, namely **AnonymousUid** and **AnonymousGid**.
-1. Set these values on the UID and the GID to 0.
-1. Restart the NFS service on the client machine.
+1. Open the Registry Editor (regedit) on the client machine.
+1. Navigate to the following key: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
+1. Create the following two DWORD entries: **AnonymousUid** and **AnonymousGid**.
+1. Assign the value "0" to each of these entries.
+1. Restart the NFS service on the client machine to apply the changes.
 
 All mounting options are available on the [Microsoft website](https://learn.microsoft.com/en-in/windows-server/administration/windows-commands/mount).
 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-au.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-au.md
index 1219ce71f3f..ca077719b95 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-au.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-au.md
@@ -135,19 +135,19 @@ You can now access your mounted partition at the specified folder.
 
 ### Microsoft Windows - specificity
 
-Make sure that the Windows user who is used to access your NAS-HA has sufficient rights.
+Ensure that the Windows user who needs to access your NAS-HA has the necessary rights.
 
-Indeed, the UID/GID pair must be configured to 0 (right UNIX root).
+The UID/GID pair must be set to "0" (UNIX root rights).
 
-If this is not the case, you will have access errors to your NAS-HA because, when NFS is authorised on a Windows machine, a UNIX user is created with the default UID and GID at -2 (or 4294967294).
+If this is not the case, errors may occur when accessing the NAS-HA. This is because when the NFS protocol is enabled on a Windows machine, a UNIX user is automatically created with a default UID and GID set to "-2" (or 4294967294), which restricts access.
 
-As a workaround, the UID and GID can be forced to 0 on the Windows machine that accesses your NAS-HA:
+As a workaround, the UID and GID can be forced to "0" on the Windows machine accessing your NAS-HA:
 
-1. Start the registry editor on the client machine.
-1. Locate `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
-1. Create two DWORD values, namely **AnonymousUid** and **AnonymousGid**.
-1. Set these values on the UID and the GID to 0.
-1. Restart the NFS service on the client machine.
+1. Open the Registry Editor (regedit) on the client machine.
+1. Navigate to the following key: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
+1. Create the following two DWORD entries: **AnonymousUid** and **AnonymousGid**.
+1. Assign the value "0" to each of these entries.
+1. Restart the NFS service on the client machine to apply the changes.
 
 All mounting options are available on the [Microsoft website](https://learn.microsoft.com/en-au/windows-server/administration/windows-commands/mount).
 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-ca.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-ca.md
index 7f139088334..4bd4cc96e41 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-ca.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-ca.md
@@ -135,19 +135,19 @@ You can now access your mounted partition at the specified folder.
 
 ### Microsoft Windows - specificity
 
-Make sure that the Windows user who is used to access your NAS-HA has sufficient rights.
+Ensure that the Windows user who needs to access your NAS-HA has the necessary rights.
 
-Indeed, the UID/GID pair must be configured to 0 (right UNIX root).
+The UID/GID pair must be set to "0" (UNIX root rights).
 
-If this is not the case, you will have access errors to your NAS-HA because, when NFS is authorised on a Windows machine, a UNIX user is created with the default UID and GID at -2 (or 4294967294).
+If this is not the case, errors may occur when accessing the NAS-HA. This is because when the NFS protocol is enabled on a Windows machine, a UNIX user is automatically created with a default UID and GID set to "-2" (or 4294967294), which restricts access.
 
-As a workaround, the UID and GID can be forced to 0 on the Windows machine that accesses your NAS-HA:
+As a workaround, the UID and GID can be forced to "0" on the Windows machine accessing your NAS-HA:
 
-1. Start the registry editor on the client machine.
-1. Locate `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
-1. Create two DWORD values, namely **AnonymousUid** and **AnonymousGid**.
-1. Set these values on the UID and the GID to 0.
-1. Restart the NFS service on the client machine.
+1. Open the Registry Editor (regedit) on the client machine.
+1. Navigate to the following key: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
+1. Create the following two DWORD entries: **AnonymousUid** and **AnonymousGid**.
+1. Assign the value "0" to each of these entries.
+1. Restart the NFS service on the client machine to apply the changes.
 
 All mounting options are available on the [Microsoft website](https://learn.microsoft.com/en-ca/windows-server/administration/windows-commands/mount).
 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-gb.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-gb.md
index f2017e8d4d9..98667df2941 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-gb.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-gb.md
@@ -135,19 +135,19 @@ You can now access your mounted partition at the specified folder.
 
 ### Microsoft Windows - specificity
 
-Make sure that the Windows user who is used to access your NAS-HA has sufficient rights.
+Ensure that the Windows user who needs to access your NAS-HA has the necessary rights.
 
-Indeed, the UID/GID pair must be configured to 0 (right UNIX root).
+The UID/GID pair must be set to "0" (UNIX root rights).
 
-If this is not the case, you will have access errors to your NAS-HA because, when NFS is authorised on a Windows machine, a UNIX user is created with the default UID and GID at -2 (or 4294967294).
+If this is not the case, errors may occur when accessing the NAS-HA. This is because when the NFS protocol is enabled on a Windows machine, a UNIX user is automatically created with a default UID and GID set to "-2" (or 4294967294), which restricts access.
 
-As a workaround, the UID and GID can be forced to 0 on the Windows machine that accesses your NAS-HA:
+As a workaround, the UID and GID can be forced to "0" on the Windows machine accessing your NAS-HA:
 
-1. Start the registry editor on the client machine.
-1. Locate `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
-1. Create two DWORD values, namely **AnonymousUid** and **AnonymousGid**.
-1. Set these values on the UID and the GID to 0.
-1. Restart the NFS service on the client machine.
+1. Open the Registry Editor (regedit) on the client machine.
+1. Navigate to the following key: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
+1. Create the following two DWORD entries: **AnonymousUid** and **AnonymousGid**.
+1. Assign the value "0" to each of these entries.
+1. Restart the NFS service on the client machine to apply the changes.
 
 All mounting options are available on the [Microsoft website](https://learn.microsoft.com/en-gb/windows-server/administration/windows-commands/mount).
 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-ie.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-ie.md
index 4a3766cb470..cdbe0468658 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-ie.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-ie.md
@@ -135,19 +135,19 @@ You can now access your mounted partition at the specified folder.
 
 ### Microsoft Windows - specificity
 
-Make sure that the Windows user who is used to access your NAS-HA has sufficient rights.
+Ensure that the Windows user who needs to access your NAS-HA has the necessary rights.
 
-Indeed, the UID/GID pair must be configured to 0 (right UNIX root).
+The UID/GID pair must be set to "0" (UNIX root rights).
 
-If this is not the case, you will have access errors to your NAS-HA because, when NFS is authorised on a Windows machine, a UNIX user is created with the default UID and GID at -2 (or 4294967294).
+If this is not the case, errors may occur when accessing the NAS-HA. This is because when the NFS protocol is enabled on a Windows machine, a UNIX user is automatically created with a default UID and GID set to "-2" (or 4294967294), which restricts access.
 
-As a workaround, the UID and GID can be forced to 0 on the Windows machine that accesses your NAS-HA:
+As a workaround, the UID and GID can be forced to "0" on the Windows machine accessing your NAS-HA:
 
-1. Start the registry editor on the client machine.
-1. Locate `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
-1. Create two DWORD values, namely **AnonymousUid** and **AnonymousGid**.
-1. Set these values on the UID and the GID to 0.
-1. Restart the NFS service on the client machine.
+1. Open the Registry Editor (regedit) on the client machine.
+1. Navigate to the following key: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
+1. Create the following two DWORD entries: **AnonymousUid** and **AnonymousGid**.
+1. Assign the value "0" to each of these entries.
+1. Restart the NFS service on the client machine to apply the changes.
 
 All mounting options are available on the [Microsoft website](https://learn.microsoft.com/en-ie/windows-server/administration/windows-commands/mount).
 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-sg.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-sg.md
index 5ae1bbe54a4..080b2a057c0 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-sg.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-sg.md
@@ -135,19 +135,19 @@ You can now access your mounted partition at the specified folder.
 
 ### Microsoft Windows - specificity
 
-Make sure that the Windows user who is used to access your NAS-HA has sufficient rights.
+Ensure that the Windows user who needs to access your NAS-HA has the necessary rights.
 
-Indeed, the UID/GID pair must be configured to 0 (right UNIX root).
+The UID/GID pair must be set to "0" (UNIX root rights).
 
-If this is not the case, you will have access errors to your NAS-HA because, when NFS is authorised on a Windows machine, a UNIX user is created with the default UID and GID at -2 (or 4294967294).
+If this is not the case, errors may occur when accessing the NAS-HA. This is because when the NFS protocol is enabled on a Windows machine, a UNIX user is automatically created with a default UID and GID set to "-2" (or 4294967294), which restricts access.
 
-As a workaround, the UID and GID can be forced to 0 on the Windows machine that accesses your NAS-HA:
+As a workaround, the UID and GID can be forced to "0" on the Windows machine accessing your NAS-HA:
 
-1. Start the registry editor on the client machine.
-1. Locate `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
-1. Create two DWORD values, namely **AnonymousUid** and **AnonymousGid**.
-1. Set these values on the UID and the GID to 0.
-1. Restart the NFS service on the client machine.
+1. Open the Registry Editor (regedit) on the client machine.
+1. Navigate to the following key: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
+1. Create the following two DWORD entries: **AnonymousUid** and **AnonymousGid**.
+1. Assign the value "0" to each of these entries.
+1. Restart the NFS service on the client machine to apply the changes.
 
 All mounting options are available on the [Microsoft website](https://learn.microsoft.com/en-sg/windows-server/administration/windows-commands/mount).
 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-us.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-us.md
index 6aa23998d9f..5f3b16fdc96 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-us.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-us.md
@@ -135,19 +135,19 @@ You can now access your mounted partition at the specified folder.
 
 ### Microsoft Windows - specificity
 
-Make sure that the Windows user who is used to access your NAS-HA has sufficient rights.
+Ensure that the Windows user who needs to access your NAS-HA has the necessary rights.
 
-Indeed, the UID/GID pair must be configured to 0 (right UNIX root).
+The UID/GID pair must be set to "0" (UNIX root rights).
 
-If this is not the case, you will have access errors to your NAS-HA because, when NFS is authorised on a Windows machine, a UNIX user is created with the default UID and GID at -2 (or 4294967294).
+If this is not the case, errors may occur when accessing the NAS-HA. This is because when the NFS protocol is enabled on a Windows machine, a UNIX user is automatically created with a default UID and GID set to "-2" (or 4294967294), which restricts access.
 
-As a workaround, the UID and GID can be forced to 0 on the Windows machine that accesses your NAS-HA:
+As a workaround, the UID and GID can be forced to "0" on the Windows machine accessing your NAS-HA:
 
-1. Start the registry editor on the client machine.
-1. Locate `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
-1. Create two DWORD values, namely **AnonymousUid** and **AnonymousGid**.
-1. Set these values on the UID and the GID to 0.
-1. Restart the NFS service on the client machine.
+1. Open the Registry Editor (regedit) on the client machine.
+1. Navigate to the following key: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
+1. Create the following two DWORD entries: **AnonymousUid** and **AnonymousGid**.
+1. Assign the value "0" to each of these entries.
+1. Restart the NFS service on the client machine to apply the changes.
 
 All mounting options are available on the [Microsoft website](https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/mount).
 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.es-es.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.es-es.md
index b417005d33d..6dcc817d4cd 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.es-es.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.es-es.md
@@ -135,19 +135,19 @@ Ahora puede acceder a la partición montada en la carpeta especificada.
 
 ### Microsoft Windows - Particularidades
 
-Asegúrese de que el usuario de Windows utilizado para acceder a su NAS-HA tenga permisos suficientes.
+Asegúrese de que el usuario de Windows que debe acceder a su NAS-HA dispone de los derechos necesarios.
 
-El par UID/GID debe configurarse en 0 (permisos root UNIX).
+El par UID/GID debe estar configurado en "0" (derecho root UNIX).
 
-De lo contrario, obtendrá errores de acceso a su NAS-HA, ya que cuando se habilita NFS en una máquina Windows, se crea un usuario UNIX con UID y GID predeterminados -2 (o 4294967294).
+Si no es así, pueden producirse errores de acceso al NAS-HA. De hecho, cuando el protocolo NFS está activado en un equipo Windows, se crea automáticamente un usuario UNIX con un UID y un GID predeterminados establecidos en "-2" (o 4294967294), lo que restringe el acceso.
 
-Como solución alternativa, puede forzar UID y GID a 0 en la máquina Windows que accede a su NAS-HA:
+Como solución alternativa, el UID y el GID se pueden forzar a "0" en el equipo Windows que accede a su NAS-HA:
 
-1. Inicie el editor del registro en la máquina cliente.
-1. Localice `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
-1. Cree dos valores DWORD: **AnonymousUid** y **AnonymousGid**.
-1. Establezca estos valores en UID y GID 0.
-1. Reinicie el servicio NFS en la máquina cliente.
+1. Abra el editor del registro (regedit) en el equipo cliente.
+1. Vaya a la siguiente clave: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
+1. Cree las dos entradas de tipo DWORD siguientes: **AnonymousUid** y **AnonymousGid**.
+1. Asigne el valor "0" a cada una de estas entradas.
+1. Reinicie el servicio NFS en el equipo cliente para aplicar los cambios.
 
 Todas las opciones de montaje están disponibles en el [sitio de Microsoft](https://learn.microsoft.com/es-es/windows-server/administration/windows-commands/mount).
 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.es-us.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.es-us.md
index f24acf8b302..0103008b5ca 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.es-us.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.es-us.md
@@ -135,19 +135,19 @@ Ahora puede acceder a la partición montada en la carpeta especificada.
 
 ### Microsoft Windows - Particularidades
 
-Asegúrese de que el usuario de Windows utilizado para acceder a su NAS-HA tenga permisos suficientes.
+Asegúrese de que el usuario de Windows que debe acceder a su NAS-HA dispone de los derechos necesarios.
 
-El par UID/GID debe configurarse en 0 (permisos root UNIX).
+El par UID/GID debe estar configurado en "0" (derecho root UNIX).
 
-De lo contrario, obtendrá errores de acceso a su NAS-HA, ya que cuando se habilita NFS en una máquina Windows, se crea un usuario UNIX con UID y GID predeterminados -2 (o 4294967294).
+Si no es así, pueden producirse errores de acceso al NAS-HA. De hecho, cuando el protocolo NFS está activado en un equipo Windows, se crea automáticamente un usuario UNIX con un UID y un GID predeterminados establecidos en "-2" (o 4294967294), lo que restringe el acceso.
 
-Como solución alternativa, puede forzar UID y GID a 0 en la máquina Windows que accede a su NAS-HA:
+Como solución alternativa, el UID y el GID se pueden forzar a "0" en el equipo Windows que accede a su NAS-HA:
 
-1. Inicie el editor del registro en la máquina cliente.
-1. Localice `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
-1. Cree dos valores DWORD: **AnonymousUid** y **AnonymousGid**.
-1. Establezca estos valores en UID y GID 0.
-1. Reinicie el servicio NFS en la máquina cliente.
+1. Abra el editor del registro (regedit) en el equipo cliente.
+1. Vaya a la siguiente clave: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
+1. Cree las dos entradas de tipo DWORD siguientes: **AnonymousUid** y **AnonymousGid**.
+1. Asigne el valor "0" a cada una de estas entradas.
+1. Reinicie el servicio NFS en el equipo cliente para aplicar los cambios.
 
 Todas las opciones de montaje están disponibles en el [sitio de Microsoft](https://learn.microsoft.com/es-us/windows-server/administration/windows-commands/mount).
 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.fr-ca.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.fr-ca.md
index c02c8a7aa1e..856551151b1 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.fr-ca.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.fr-ca.md
@@ -136,19 +136,19 @@ Vous pouvez maintenant accéder à votre partition montée dans le dossier spéc
 
 ### Microsoft Windows - Particularités
 
-Assurez-vous que l'utilisateur Windows qui est utilisé pour accéder à votre NAS-HA dispose de droits suffisants.
+Assurez-vous que l'utilisateur Windows qui doit accéder à votre NAS-HA dispose de droits nécessaires.
 
-En effet, le couple UID/GID doit être configuré à 0 (droit root UNIX).
+Le couple UID/GID doit être configuré sur « 0 » (droit root UNIX).
 
-Si ce n'est pas le cas, vous obtiendrez des erreurs d'accès à votre NAS-HA, car lorsque NFS est autorisé sur une machine Windows, un utilisateur UNIX est créé avec l'UID et le GID par défaut à -2 (ou 4294967294).
+Si ce n'est pas le cas, des erreurs d’accès au NAS-HA peuvent survenir. En effet, lorsque le protocole NFS est activé sur une machine Windows, un utilisateur UNIX est automatiquement créé avec un UID et un GID par défaut définis sur « -2 » (ou 4294967294), ce qui restreint les accès.
 
-Comme solution de contournement, l'UID et le GID peuvent être forcés à 0 sur la machine Windows qui accède à votre NAS-HA :
+Comme solution de contournement, l'UID et le GID peuvent être forcés à « 0 » sur la machine Windows qui accède à votre NAS-HA :
 
-1. Démarrez l'éditeur de registre sur la machine cliente.
-1. Localisez `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
-1. Créez deux valeurs DWORD, à savoir **AnonymousUid** et **AnonymousGid**.
-1. Définissez ces valeurs sur l'UID et le GID à 0.
-1. Redémarrez le service NFS sur la machine cliente.
+1. Ouvrez l'éditeur de registre (regedit) sur la machine cliente.
+1. Accédez à la clé suivante : `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
+1. Créez les deux entrées de type DWORD suivantes : **AnonymousUid** et **AnonymousGid**.
+1. Attibuez la valeur « 0 » à chacune de ces entrées.
+1. Redémarrez le service NFS sur la machine cliente pour appliquer les modifications.
 
 Toutes les options de montage sont disponibles sur le [site de Microsoft](https://learn.microsoft.com/fr-ca/windows-server/administration/windows-commands/mount).
 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.fr-fr.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.fr-fr.md
index af2cdb68539..78628b1c0fe 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.fr-fr.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.fr-fr.md
@@ -136,19 +136,19 @@ Vous pouvez maintenant accéder à votre partition montée dans le dossier spéc
 
 ### Microsoft Windows - Particularités
 
-Assurez-vous que l'utilisateur Windows qui est utilisé pour accéder à votre NAS-HA dispose de droits suffisants.
+Assurez-vous que l'utilisateur Windows qui doit accéder à votre NAS-HA dispose de droits nécessaires.
 
-En effet, le couple UID/GID doit être configuré à 0 (droit root UNIX).
+Le couple UID/GID doit être configuré sur « 0 » (droit root UNIX).
 
-Si ce n'est pas le cas, vous obtiendrez des erreurs d'accès à votre NAS-HA, car lorsque NFS est autorisé sur une machine Windows, un utilisateur UNIX est créé avec l'UID et le GID par défaut à -2 (ou 4294967294).
+Si ce n'est pas le cas, des erreurs d’accès au NAS-HA peuvent survenir. En effet, lorsque le protocole NFS est activé sur une machine Windows, un utilisateur UNIX est automatiquement créé avec un UID et un GID par défaut définis sur « -2 » (ou 4294967294), ce qui restreint les accès.
 
-Comme solution de contournement, l'UID et le GID peuvent être forcés à 0 sur la machine Windows qui accède à votre NAS-HA :
+Comme solution de contournement, l'UID et le GID peuvent être forcés à « 0 » sur la machine Windows qui accède à votre NAS-HA :
 
-1. Démarrez l'éditeur de registre sur la machine cliente.
-1. Localisez `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
-1. Créez deux valeurs DWORD, à savoir **AnonymousUid** et **AnonymousGid**.
-1. Définissez ces valeurs sur l'UID et le GID à 0.
-1. Redémarrez le service NFS sur la machine cliente.
+1. Ouvrez l'éditeur de registre (regedit) sur la machine cliente.
+1. Accédez à la clé suivante : `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
+1. Créez les deux entrées de type DWORD suivantes : **AnonymousUid** et **AnonymousGid**.
+1. Attibuez la valeur « 0 » à chacune de ces entrées.
+1. Redémarrez le service NFS sur la machine cliente pour appliquer les modifications.
 
 Toutes les options de montage sont disponibles sur le [site de Microsoft](https://learn.microsoft.com/fr-fr/windows-server/administration/windows-commands/mount).
 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.it-it.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.it-it.md
index 74e8ffb7ccd..ede2316462b 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.it-it.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.it-it.md
@@ -135,19 +135,19 @@ Adesso puoi accedere alla tua partizione montata nella cartella specificata.
 
 ### Microsoft Windows - Particolari
 
-Assicurarsi che l'utente Windows utilizzato per accedere al proprio NAS-HA abbia i diritti sufficienti.
+Assicurarsi che l'utente Windows che deve accedere al NAS-HA disponga dei diritti necessari.
 
-La coppia UID/GID deve essere configurata su 0 (diritti root UNIX).
+La coppia UID/GID deve essere configurata su "0" (diritti root UNIX).
 
-Altrimenti, si otterranno errori di accesso al proprio NAS-HA, poiché quando NFS è abilitato su una macchina Windows, viene creato un utente UNIX con UID e GID predefiniti -2 (o 4294967294).
+In caso contrario, potrebbero verificarsi errori di accesso al NAS-HA. Infatti, quando il protocollo NFS è attivato su un computer Windows, viene automaticamente creato un utente UNIX con UID e GID predefiniti impostati su "-2" (o 4294967294), il che limita l'accesso.
 
-Come soluzione alternativa, UID e GID possono essere forzati a 0 sulla macchina Windows che accede al proprio NAS-HA:
+Come soluzione alternativa, è possibile forzare l'UID e il GID su "0" sul computer Windows che accede al NAS-HA:
 
-1. Avviare l'editor del registro sulla macchina client.
-1. Localizzare `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
-1. Creare due valori DWORD: **AnonymousUid** e **AnonymousGid**.
-1. Impostare questi valori su UID e GID 0.
-1. Riavviare il servizio NFS sulla macchina client.
+1. Aprire l'editor del Registro di sistema (regedit) sul computer client.
+1. Accedere alla seguente chiave: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
+1. Creare le due voci di tipo DWORD seguenti: **AnonymousUid** e **AnonymousGid**.
+1. Assegnare il valore "0" a ciascuna di queste voci.
+1. Riavviare il servizio NFS sul computer client per applicare le modifiche.
 
 Tutte le opzioni di montaggio sono disponibili sul [sito di Microsoft](https://learn.microsoft.com/it-it/windows-server/administration/windows-commands/mount).
 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.pl-pl.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.pl-pl.md
index f2bf67f0616..9f63eac7f27 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.pl-pl.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.pl-pl.md
@@ -135,19 +135,19 @@ Teraz możesz przejść do partycji zamontowanej w określonym folderze.
 
 ### Microsoft Windows - Cechy szczególne
 
-Upewnij się, że użytkownik Windows, który jest używany do uzyskiwania dostępu do Twojego NAS-HA, ma odpowiednie uprawnienia.
+Upewnij się, że użytkownik systemu Windows, który potrzebuje dostępu do urządzenia NAS-HA, ma niezbędne uprawnienia.
 
-Para UID/GID musi być skonfigurowana na 0 (uprawnienia root UNIX).
+Para UID/GID musi być ustawiona na „0” (uprawnienia administratora systemu UNIX).
 
-W przeciwnym razie otrzymasz błędy dostępu do swojego NAS-HA, ponieważ gdy NFS jest włączony na maszynie Windows, tworzony jest użytkownik UNIX z UID i GID domyślnie -2 (lub 4294967294).
+W przeciwnym razie podczas uzyskiwania dostępu do urządzenia NAS-HA mogą wystąpić błędy. Wynika to z faktu, że po włączeniu protokołu NFS na komputerze z systemem Windows automatycznie tworzony jest użytkownik systemu UNIX z domyślnymi wartościami UID i GID ustawionymi na „-2” (lub 4294967294), co ogranicza dostęp.
 
-Jako rozwiązanie awaryjne UID i GID można zmusić do 0 na maszynie Windows, która uzyskuje dostęp do Twojego NAS-HA:
+Aby obejść ten problem, można wymusić ustawienie UID i GID na „0” na komputerze z systemem Windows uzyskującym dostęp do NAS-HA:
 
-1. Uruchom edytor rejestru na maszynie klienckiej.
-1. Zlokalizuj 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default'.
-1. Utwórz dwa wartości DWORD: **AnonymousUid** i **AnonymousGid**.
-1. Ustaw te wartości na UID i GID 0.
-1. Uruchom ponownie usługę NFS na maszynie klienckiej.
+1. Otwórz Edytor rejestru (regedit) na komputerze klienckim.
+1. Przejdź do następującego klucza: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
+1. Utwórz dwa następujące wpisy DWORD: **AnonymousUid** i **AnonymousGid**.
+1. Przypisz wartość „0” do każdego z tych wpisów.
+1. Uruchom ponownie usługę NFS na komputerze klienckim, aby zastosować zmiany.
 
 Wszystkie opcje montowania są dostępne na [stronie Microsoft](https://learn.microsoft.com/pl-pl/windows-server/administration/windows-commands/mount).
 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.pt-pt.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.pt-pt.md
index 4354c6e3411..03b8688d1b2 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.pt-pt.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.pt-pt.md
@@ -135,19 +135,19 @@ Já pode aceder à sua partição montada na pasta especificada.
 
 ### Microsoft Windows - Particularidades
 
-Certifique-se de que o usuário do Windows utilizado para acessar seu NAS-HA tenha permissões suficientes.
+Certifique-se de que o utilizador Windows que precisa de aceder ao seu NAS-HA tem os direitos necessários.
 
-O par UID/GID deve ser configurado para 0 (permissões root UNIX).
+O par UID/GID deve ser configurado como «0» (direito root UNIX).
 
-Caso contrário, você obterá erros de acesso ao seu NAS-HA, pois quando o NFS é habilitado em uma máquina Windows, um usuário UNIX é criado com UID e GID padrão -2 (ou 4294967294).
+Caso contrário, poderão ocorrer erros de acesso ao NAS-HA. Com efeito, quando o protocolo NFS está ativado numa máquina Windows, é automaticamente criado um utilizador UNIX com um UID e um GID predefinidos como «-2» (ou 4294967294), o que restringe o acesso.
 
-Como solução alternativa, UID e GID podem ser forçados a 0 na máquina Windows que acessa seu NAS-HA:
+Como solução alternativa, o UID e o GID podem ser forçados a «0» na máquina Windows que acede ao seu NAS-HA:
 
-1. Inicie o editor do registro na máquina cliente.
-1. Localize `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
-1. Crie dois valores DWORD: **AnonymousUid** e **AnonymousGid**.
-1. Defina esses valores para UID e GID 0.
-1. Reinicie o serviço NFS na máquina cliente.
+1. Abra o editor de registo (regedit) na máquina cliente.
+1. Aceda à seguinte chave: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default`.
+1. Crie as duas entradas do tipo DWORD seguintes: **AnonymousUid** e **AnonymousGid**.
+1. Atribua o valor «0» a cada uma destas entradas.
+1. Reinicie o serviço NFS na máquina cliente para aplicar as alterações.
 
 Todas as opções de montagem estão disponíveis no [site da Microsoft](https://learn.microsoft.com/pt-pt/windows-server/administration/windows-commands/mount).
 

From c2b4dc8f7a4fda1dc815f73f5ed1f736a5a77b97 Mon Sep 17 00:00:00 2001
From: benchbzh <benoit.chuchla@ovhcloud.com>
Date: Thu, 9 Oct 2025 11:07:51 +0200
Subject: [PATCH 13/16] date update

---
 .../dedicated_servers/services_backup_storage/guide.de-de.md    | 2 +-
 .../dedicated_servers/services_backup_storage/guide.en-asia.md  | 2 +-
 .../dedicated_servers/services_backup_storage/guide.en-au.md    | 2 +-
 .../dedicated_servers/services_backup_storage/guide.en-ca.md    | 2 +-
 .../dedicated_servers/services_backup_storage/guide.en-gb.md    | 2 +-
 .../dedicated_servers/services_backup_storage/guide.en-ie.md    | 2 +-
 .../dedicated_servers/services_backup_storage/guide.en-sg.md    | 2 +-
 .../dedicated_servers/services_backup_storage/guide.en-us.md    | 2 +-
 .../dedicated_servers/services_backup_storage/guide.es-es.md    | 2 +-
 .../dedicated_servers/services_backup_storage/guide.es-us.md    | 2 +-
 .../dedicated_servers/services_backup_storage/guide.fr-ca.md    | 2 +-
 .../dedicated_servers/services_backup_storage/guide.fr-fr.md    | 2 +-
 .../dedicated_servers/services_backup_storage/guide.it-it.md    | 2 +-
 .../dedicated_servers/services_backup_storage/guide.pl-pl.md    | 2 +-
 .../dedicated_servers/services_backup_storage/guide.pt-pt.md    | 2 +-
 .../file_storage/ha_nas/nas_cifs/guide.de-de.md                 | 2 +-
 .../file_storage/ha_nas/nas_cifs/guide.en-asia.md               | 2 +-
 .../file_storage/ha_nas/nas_cifs/guide.en-au.md                 | 2 +-
 .../file_storage/ha_nas/nas_cifs/guide.en-ca.md                 | 2 +-
 .../file_storage/ha_nas/nas_cifs/guide.en-gb.md                 | 2 +-
 .../file_storage/ha_nas/nas_cifs/guide.en-ie.md                 | 2 +-
 .../file_storage/ha_nas/nas_cifs/guide.en-sg.md                 | 2 +-
 .../file_storage/ha_nas/nas_cifs/guide.en-us.md                 | 2 +-
 .../file_storage/ha_nas/nas_cifs/guide.es-es.md                 | 2 +-
 .../file_storage/ha_nas/nas_cifs/guide.es-us.md                 | 2 +-
 .../file_storage/ha_nas/nas_cifs/guide.fr-ca.md                 | 2 +-
 .../file_storage/ha_nas/nas_cifs/guide.fr-fr.md                 | 2 +-
 .../file_storage/ha_nas/nas_cifs/guide.it-it.md                 | 2 +-
 .../file_storage/ha_nas/nas_cifs/guide.pl-pl.md                 | 2 +-
 .../file_storage/ha_nas/nas_cifs/guide.pt-pt.md                 | 2 +-
 .../file_storage/ha_nas/nas_nfs/guide.de-de.md                  | 2 +-
 .../file_storage/ha_nas/nas_nfs/guide.en-asia.md                | 2 +-
 .../file_storage/ha_nas/nas_nfs/guide.en-au.md                  | 2 +-
 .../file_storage/ha_nas/nas_nfs/guide.en-ca.md                  | 2 +-
 .../file_storage/ha_nas/nas_nfs/guide.en-gb.md                  | 2 +-
 .../file_storage/ha_nas/nas_nfs/guide.en-ie.md                  | 2 +-
 .../file_storage/ha_nas/nas_nfs/guide.en-sg.md                  | 2 +-
 .../file_storage/ha_nas/nas_nfs/guide.en-us.md                  | 2 +-
 .../file_storage/ha_nas/nas_nfs/guide.es-es.md                  | 2 +-
 .../file_storage/ha_nas/nas_nfs/guide.es-us.md                  | 2 +-
 .../file_storage/ha_nas/nas_nfs/guide.fr-ca.md                  | 2 +-
 .../file_storage/ha_nas/nas_nfs/guide.fr-fr.md                  | 2 +-
 .../file_storage/ha_nas/nas_nfs/guide.it-it.md                  | 2 +-
 .../file_storage/ha_nas/nas_nfs/guide.pl-pl.md                  | 2 +-
 .../file_storage/ha_nas/nas_nfs/guide.pt-pt.md                  | 2 +-
 45 files changed, 45 insertions(+), 45 deletions(-)

diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.de-de.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.de-de.md
index 316a1bf907e..1765f7972ef 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.de-de.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.de-de.md
@@ -1,7 +1,7 @@
 ---
 title: 'Backup Storage auf einem Dedicated Server verwenden'
 excerpt: 'Erfahren Sie hier, wie Sie zusätzlichen Speicherplatz aktivieren und auf diesen zugreifen'
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Ziel
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-asia.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-asia.md
index 1c03a44fded..99528ff377f 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-asia.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-asia.md
@@ -1,7 +1,7 @@
 ---
 title: How to use the backup storage on a dedicated server
 excerpt: 'Find out how to enable and access your additional storage space'
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objective
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-au.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-au.md
index 29d6673427e..208e344fd71 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-au.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-au.md
@@ -1,7 +1,7 @@
 ---
 title: How to use the backup storage on a dedicated server
 excerpt: 'Find out how to enable and access your additional storage space'
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objective
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-ca.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-ca.md
index 9f3ff1fa1db..15749a0118e 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-ca.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-ca.md
@@ -1,7 +1,7 @@
 ---
 title: How to use the backup storage on a dedicated server
 excerpt: 'Find out how to enable and access your additional storage space'
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objective
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-gb.md
index 6738d5691de..6d9c2e9bdae 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-gb.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-gb.md
@@ -1,7 +1,7 @@
 ---
 title: How to use the backup storage on a dedicated server
 excerpt: 'Find out how to enable and access your additional storage space'
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objective
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-ie.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-ie.md
index fb527c8cb69..f1d96b2e689 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-ie.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-ie.md
@@ -1,7 +1,7 @@
 ---
 title: How to use the backup storage on a dedicated server
 excerpt: 'Find out how to enable and access your additional storage space'
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objective
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-sg.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-sg.md
index 5b4a3768b89..8e1fd40652d 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-sg.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-sg.md
@@ -1,7 +1,7 @@
 ---
 title: How to use the backup storage on a dedicated server
 excerpt: 'Find out how to enable and access your additional storage space'
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objective
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-us.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-us.md
index e8db6734d4d..5d75bcb9567 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-us.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.en-us.md
@@ -1,7 +1,7 @@
 ---
 title: How to use the backup storage on a dedicated server
 excerpt: 'Find out how to enable and access your additional storage space'
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objective
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.es-es.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.es-es.md
index 04768f5ddcf..fdd4cef8be7 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.es-es.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.es-es.md
@@ -1,7 +1,7 @@
 ---
 title: 'Utilizar Backup Storage en un servidor dedicado'
 excerpt: 'Cómo activar y acceder al espacio de almacenamiento adicional'
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objetivo
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.es-us.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.es-us.md
index e60be5f55b5..dd9fbf56704 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.es-us.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.es-us.md
@@ -1,7 +1,7 @@
 ---
 title: 'Utilizar Backup Storage en un servidor dedicado'
 excerpt: 'Cómo activar y acceder al espacio de almacenamiento adicional'
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objetivo
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.fr-ca.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.fr-ca.md
index 81752749050..0984e351791 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.fr-ca.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.fr-ca.md
@@ -1,7 +1,7 @@
 ---
 title: 'Utiliser Backup Storage sur un serveur dédié'
 excerpt: 'Découvrez comment activer et accéder à votre espace de stockage supplémentaire'
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objectif
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.fr-fr.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.fr-fr.md
index 5e78064aaaf..f6ce4f78b81 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.fr-fr.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.fr-fr.md
@@ -1,7 +1,7 @@
 ---
 title: 'Utiliser Backup Storage sur un serveur dédié'
 excerpt: 'Découvrez comment activer et accéder à votre espace de stockage supplémentaire'
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objectif
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.it-it.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.it-it.md
index 7d9cb8596ff..d6886f5eafd 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.it-it.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.it-it.md
@@ -1,7 +1,7 @@
 ---
 title: Utilizzare il Backup Storage su un server dedicato
 excerpt: Come attivare e accedere allo spazio di storage aggiuntivo
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Obiettivo
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.pl-pl.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.pl-pl.md
index a9ef71944a7..861dbcaf550 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.pl-pl.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.pl-pl.md
@@ -1,7 +1,7 @@
 ---
 title: 'Korzystanie z Backup Storage na serwerze dedykowanym'
 excerpt: 'Dowiedz się, jak aktywować i uzyskać dostęp do dodatkowej przestrzeni dyskowej'
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Wprowadzenie
diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.pt-pt.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.pt-pt.md
index c95b3b2e954..b9435fb474a 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.pt-pt.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.pt-pt.md
@@ -1,7 +1,7 @@
 ---
 title: 'Utilizar o Backup Storage num servidor dedicado'
 excerpt: 'Saiba como ativar e aceder ao espaço de armazenamento adicional'
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objetivo
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.de-de.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.de-de.md
index ee587d64c9c..2c19313bfc2 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.de-de.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.de-de.md
@@ -1,7 +1,7 @@
 ---
 title: Mounten Sie Ihr HA-NAS über eine CIFS-Freigabe
 excerpt: In dieser Anleitung erfahren Sie, wie Sie Ihr HA-NAS über das CIFS-Protokoll mounten können.
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Ziel
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-asia.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-asia.md
index 226e311c8f3..d40031e6c2c 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-asia.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-asia.md
@@ -1,7 +1,7 @@
 ---
 title: Mount your HA-NAS via a CIFS share
 excerpt: This guide shows you how to mount your HA-NAS using CIFS protocol
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objective
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-au.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-au.md
index f2b34d8462a..64f818abac0 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-au.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-au.md
@@ -1,7 +1,7 @@
 ---
 title: Mount your HA-NAS via a CIFS share
 excerpt: This guide shows you how to mount your HA-NAS using CIFS protocol
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objective
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-ca.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-ca.md
index d5cc02bc5e7..7ab1fac8e50 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-ca.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-ca.md
@@ -1,7 +1,7 @@
 ---
 title: Mount your HA-NAS via a CIFS share
 excerpt: This guide shows you how to mount your HA-NAS using CIFS protocol
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objective
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-gb.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-gb.md
index 8bcb92a8c69..09d4278f69f 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-gb.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-gb.md
@@ -1,7 +1,7 @@
 ---
 title: Mount your HA-NAS via a CIFS share
 excerpt: This guide shows you how to mount your HA-NAS using CIFS protocol
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objective
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-ie.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-ie.md
index b35fab6f749..e3fb1d430fd 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-ie.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-ie.md
@@ -1,7 +1,7 @@
 ---
 title: Mount your HA-NAS via a CIFS share
 excerpt: This guide shows you how to mount your HA-NAS using CIFS protocol
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objective
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-sg.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-sg.md
index 265fabe1a57..fb460347d44 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-sg.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-sg.md
@@ -1,7 +1,7 @@
 ---
 title: Mount your HA-NAS via a CIFS share
 excerpt: This guide shows you how to mount your HA-NAS using CIFS protocol
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objective
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-us.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-us.md
index c6a9931dafd..08ee1c7c73e 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-us.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.en-us.md
@@ -1,7 +1,7 @@
 ---
 title: Mount your HA-NAS via a CIFS share
 excerpt: This guide shows you how to mount your HA-NAS using CIFS protocol
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objective
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.es-es.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.es-es.md
index c10e6890d35..4304703e6c9 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.es-es.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.es-es.md
@@ -1,7 +1,7 @@
 ---
 title: Montar un NAS-HA a través de un recurso compartido CIFS
 excerpt: Configurar y montar un NAS-HA mediante el protocolo CIFS
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objetivo
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.es-us.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.es-us.md
index f69d420a8ae..2a1c9d99141 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.es-us.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.es-us.md
@@ -1,7 +1,7 @@
 ---
 title: Montar un NAS-HA a través de un recurso compartido CIFS
 excerpt: Configurar y montar un NAS-HA mediante el protocolo CIFS
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objetivo
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-ca.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-ca.md
index ad4efd9d204..01ab134f4d1 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-ca.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-ca.md
@@ -1,7 +1,7 @@
 ---
 title: Monter un NAS-HA via un partage CIFS
 excerpt: Configurer et monter un NAS-HA via le protocole CIFS
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objectif
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-fr.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-fr.md
index ada534c4cc1..270d5a62ba0 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-fr.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.fr-fr.md
@@ -1,7 +1,7 @@
 ---
 title: Monter un NAS-HA via un partage CIFS
 excerpt: Configurer et monter un NAS-HA via le protocole CIFS
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objectif
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.it-it.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.it-it.md
index bb12cfec87f..283be9fe8c5 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.it-it.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.it-it.md
@@ -1,7 +1,7 @@
 ---
 title: Montare un NAS-HA tramite condivisione CIFS
 excerpt: Configurare e montare un NAS-HA tramite il protocollo CIFS
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Obiettivo
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.pl-pl.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.pl-pl.md
index fbb10eb06e2..8b12a5bb90b 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.pl-pl.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.pl-pl.md
@@ -1,7 +1,7 @@
 ---
 title: Podłącz HA-NAS za pomocą udziału CIFS
 excerpt: W tym przewodniku opisano sposób montowania HA-NAS przy użyciu protokołu CIFS.
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Wprowadzenie
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.pt-pt.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.pt-pt.md
index 1191b92d106..5c5da19cf19 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.pt-pt.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.pt-pt.md
@@ -1,7 +1,7 @@
 ---
 title: Configure o seu NAS-HA no Windows Server através do CIFS
 excerpt: Configurar e montar um NAS-HA através do protocolo CIFS
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objetivo
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.de-de.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.de-de.md
index 9c0a6fa1100..742ddd5ad89 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.de-de.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.de-de.md
@@ -1,7 +1,7 @@
 ---
 title: HA-NAS über NFS mounten
 excerpt: "Erfahren Sie hier, wie sich mit Ihrem HA-NAS unter Verwendung einer NFS-Freigabe verbinden"
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Ziel 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-asia.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-asia.md
index 1c2840e69d9..fb95a1548bd 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-asia.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-asia.md
@@ -1,7 +1,7 @@
 ---
 title: Mounting HA-NAS via NFS share
 excerpt: Find out how to connect to your HA-NAS using an NFS share
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objective 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-au.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-au.md
index ca077719b95..d4cfd611e4c 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-au.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-au.md
@@ -1,7 +1,7 @@
 ---
 title: Mounting HA-NAS via NFS share
 excerpt: Find out how to connect to your HA-NAS using an NFS share
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objective 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-ca.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-ca.md
index 4bd4cc96e41..4ebf74842a7 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-ca.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-ca.md
@@ -1,7 +1,7 @@
 ---
 title: Mounting HA-NAS via NFS share
 excerpt: Find out how to connect to your HA-NAS using an NFS share
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objective 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-gb.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-gb.md
index 98667df2941..51e7c3ea93b 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-gb.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-gb.md
@@ -1,7 +1,7 @@
 ---
 title: Mounting HA-NAS via NFS share
 excerpt: Find out how to connect to your HA-NAS using an NFS share
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objective 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-ie.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-ie.md
index cdbe0468658..4bd25f0e64f 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-ie.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-ie.md
@@ -1,7 +1,7 @@
 ---
 title: Mounting HA-NAS via NFS share
 excerpt: Find out how to connect to your HA-NAS using an NFS share
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objective 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-sg.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-sg.md
index 080b2a057c0..19026e6aadb 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-sg.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-sg.md
@@ -1,7 +1,7 @@
 ---
 title: Mounting HA-NAS via NFS share
 excerpt: Find out how to connect to your HA-NAS using an NFS share
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objective 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-us.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-us.md
index 5f3b16fdc96..ecf11a69761 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-us.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.en-us.md
@@ -1,7 +1,7 @@
 ---
 title: Mounting HA-NAS via NFS share
 excerpt: Find out how to connect to your HA-NAS using an NFS share
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objective 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.es-es.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.es-es.md
index 6dcc817d4cd..ec216b1e606 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.es-es.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.es-es.md
@@ -1,7 +1,7 @@
 ---
 title: "Montaje de un NAS-HA mediante NFS compartido"
 excerpt: "Cómo conectarse a un NAS-HA utilizando un recurso compartido por NFS"
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objetivo 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.es-us.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.es-us.md
index 0103008b5ca..1638b890f06 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.es-us.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.es-us.md
@@ -1,7 +1,7 @@
 ---
 title: "Montaje de un NAS-HA mediante NFS compartido"
 excerpt: "Cómo conectarse a un NAS-HA utilizando un recurso compartido por NFS"
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objetivo 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.fr-ca.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.fr-ca.md
index 856551151b1..858a20f1f08 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.fr-ca.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.fr-ca.md
@@ -1,7 +1,7 @@
 ---
 title: Montage d'un NAS-HA via partage NFS
 excerpt: Découvrez comment vous connecter à votre NAS-HA en utilisant un partage NFS
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objectif
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.fr-fr.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.fr-fr.md
index 78628b1c0fe..4d88ac30162 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.fr-fr.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.fr-fr.md
@@ -1,7 +1,7 @@
 ---
 title: Montage d'un NAS-HA via partage NFS
 excerpt: Découvrez comment vous connecter à votre NAS-HA en utilisant un partage NFS
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objectif
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.it-it.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.it-it.md
index ede2316462b..411975bc3c0 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.it-it.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.it-it.md
@@ -1,7 +1,7 @@
 ---
 title: "Installazione di un NAS-HA tramite condivisione NFS"
 excerpt: "Come connettersi al tuo NAS-HA utilizzando una condivisione NFS"
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Obiettivo 
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.pl-pl.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.pl-pl.md
index 9f63eac7f27..a43d47a209b 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.pl-pl.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.pl-pl.md
@@ -1,7 +1,7 @@
 ---
 title: "Montowanie NAS-HA przy użyciu zasobów NFS"
 excerpt: "Dowiedz się, jak się zalogować do usługi NAS-HA przy użyciu protokołu NFS"
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Wprowadzenie
diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.pt-pt.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.pt-pt.md
index 03b8688d1b2..a31641bebda 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.pt-pt.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.pt-pt.md
@@ -1,7 +1,7 @@
 ---
 title: "Montagem de NAS-HA através de NFS"
 excerpt: "Saiba como conectar-se ao NAS-HA através de NFS"
-updated: 2025-10-08
+updated: 2025-10-09
 ---
 
 ## Objetivo 

From e5d47ced350db85e161e80691351efb2733e4faa Mon Sep 17 00:00:00 2001
From: tcpdumpfbacke <63296875+tcpdumpfbacke@users.noreply.github.com>
Date: Thu, 9 Oct 2025 12:04:55 +0200
Subject: [PATCH 14/16] DE proof

---
 .../dedicated_servers/services_backup_storage/guide.de-de.md  | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.de-de.md b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.de-de.md
index 1765f7972ef..2a886944f20 100644
--- a/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.de-de.md
+++ b/pages/bare_metal_cloud/dedicated_servers/services_backup_storage/guide.de-de.md
@@ -347,8 +347,8 @@ You can't access this shared folder because your organization's security policie
 
 > [!primary]
 >
-> Um diesen Fehler zu beheben, muss die Windows-Registrierungsdatenbank geändert werden. Öffnen Sie dazu den Registrierungseditor (regedit) und navigieren Sie zum Schlüssel `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters navigieren`.<br>
-> Setzen Sie den Wert des Parameters `AllowInsecureGuestAuth` auf "1".<br>
+> Dieser Fehler sollte durch Bearbeiten der Windows Registry behebbar sein: Öffnen Sie das Windows Dienstprogramm *regedit*, und suchen Sie nach dem Eintrag `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.  
+> Setzen Sie den Wert des Parameters `AllowInsecureGuestAuth` auf "1".  
 > Weitere Informationen zu diesem Thema finden Sie auf den [Microsoft Supportseiten](https://learn.microsoft.com/de-de/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ##### Linux

From f004fe4287d69aedb64906d6df4fa3fc0be048fe Mon Sep 17 00:00:00 2001
From: tcpdumpfbacke <63296875+tcpdumpfbacke@users.noreply.github.com>
Date: Thu, 9 Oct 2025 12:10:27 +0200
Subject: [PATCH 15/16] DE proof

---
 .../file_storage/ha_nas/nas_cifs/guide.de-de.md             | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.de-de.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.de-de.md
index 2c19313bfc2..27473032dbc 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.de-de.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.de-de.md
@@ -51,8 +51,8 @@ You can't access this shared folder because your organization's security policie
 
 > [!primary]
 >
-> Um diesen Fehler zu beheben, muss die Windows-Registrierungsdatenbank geändert werden. Öffnen Sie dazu den Registrierungseditor (regedit) und navigieren Sie zum Schlüssel `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters navigieren`.<br>
-> Setzen Sie den Wert des Parameters `AllowInsecureGuestAuth` auf "1".<br>
+> Dieser Fehler sollte durch Bearbeiten der Windows Registry behebbar sein: Öffnen Sie das Windows Dienstprogramm *regedit*, und suchen Sie nach dem Eintrag `HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters`.  
+> Setzen Sie den Wert des Parameters `AllowInsecureGuestAuth` auf "1".  
 > Weitere Informationen zu diesem Thema finden Sie auf den [Microsoft Supportseiten](https://learn.microsoft.com/de-de/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3).
 
 ### Einstellungen für Linux
@@ -83,4 +83,4 @@ mount -t cifs -o uid=root,gid=100,dir_mode=0700,username=root,password= //IP_SER
 
 Wenn Sie Schulungen oder technische Unterstützung bei der Implementierung unserer Lösungen benötigen, wenden Sie sich an Ihren Vertriebsmitarbeiter oder klicken Sie auf [diesen Link](/links/professional-services), um einen Kostenvoranschlag zu erhalten und eine persönliche Analyse Ihres Projekts durch unsere Experten des Professional Services Teams anzufordern.
 
-Treten Sie unserer [User Community](/links/community) bei.
\ No newline at end of file
+Treten Sie unserer [User Community](/links/community) bei.

From 9b3144624f8ed2df119872ec65d340d46138a087 Mon Sep 17 00:00:00 2001
From: tcpdumpfbacke <63296875+tcpdumpfbacke@users.noreply.github.com>
Date: Thu, 9 Oct 2025 12:11:28 +0200
Subject: [PATCH 16/16] DE proof

---
 .../file_storage/ha_nas/nas_nfs/guide.de-de.md                  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.de-de.md b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.de-de.md
index 742ddd5ad89..e139c491edd 100644
--- a/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.de-de.md
+++ b/pages/storage_and_backup/file_storage/ha_nas/nas_nfs/guide.de-de.md
@@ -150,7 +150,7 @@ Als Workaround können die UID und GID auf dem Windows-Rechner, der auf Ihr NAS-
 1. Weisen Sie jedem dieser Einträge den Wert „0“ zu.
 1. Starten Sie den NFS-Dienst auf dem Client-Computer neu, um die Änderungen zu übernehmen.
 
-Alle Einhängeoptionen sind auf der [Microsoft-Website](https://learn.microsoft.com/de-de/windows-server/administration/windows-commands/mount) verfügbar.
+Alle Mount-Optionen sind auf der [Microsoft-Website](https://learn.microsoft.com/de-de/windows-server/administration/windows-commands/mount) verfügbar.
 
 ### Proxmox