diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.de-de.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.de-de.md index c9271b52408..6ae5925c3ce 100644 --- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.de-de.md +++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.de-de.md @@ -1,7 +1,7 @@ --- title: "Enterprise File Storage - Private network configuration" excerpt: "Find out how to set up a private network for your Enterprise File Storage service from your OVHcloud Control Panel" -updated: 2025-10-21 +updated: 2025-10-23 --- ## Objective @@ -84,9 +84,9 @@ You can now follow the guides below to create and manage your volumes, snapshots > - The IP address of your Service Endpoint must be unique in your subnet and must be excluded from your DHCP server if you use one. > - Example: vRack Services 10.0.0.0/24 subnet - Service Endpoint 10.0.0.16/29 - Your service will therefore be accessible at IP address 10.0.0.16 in subnet 10.0.0.0/24. -- The **arping ** command must return only one MAC address. -- The **traceroute -T -p 2049** command must not return an error. -- The **nmap -sV -T4 -p111,635,2049,4045,4046 ** command must return ports in the OPEN state (essential for the proper functioning of NFSv3). +- The **arping IP_Endpoint** command must return only one MAC address. +- The **traceroute -T IP_Endpoint -p 2049** command must not return an error. +- The **nmap -sV -T4 -p111,635,2049,4045,4046 IP_Endpoint** command must return ports in the OPEN state (essential for the proper functioning of NFSv3). ## Go further @@ -102,4 +102,4 @@ You can now follow the guides below to create and manage your volumes, snapshots 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](/links/community). +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.en-asia.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.en-asia.md index c9271b52408..6ae5925c3ce 100644 --- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.en-asia.md +++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.en-asia.md @@ -1,7 +1,7 @@ --- title: "Enterprise File Storage - Private network configuration" excerpt: "Find out how to set up a private network for your Enterprise File Storage service from your OVHcloud Control Panel" -updated: 2025-10-21 +updated: 2025-10-23 --- ## Objective @@ -84,9 +84,9 @@ You can now follow the guides below to create and manage your volumes, snapshots > - The IP address of your Service Endpoint must be unique in your subnet and must be excluded from your DHCP server if you use one. > - Example: vRack Services 10.0.0.0/24 subnet - Service Endpoint 10.0.0.16/29 - Your service will therefore be accessible at IP address 10.0.0.16 in subnet 10.0.0.0/24. -- The **arping ** command must return only one MAC address. -- The **traceroute -T -p 2049** command must not return an error. -- The **nmap -sV -T4 -p111,635,2049,4045,4046 ** command must return ports in the OPEN state (essential for the proper functioning of NFSv3). +- The **arping IP_Endpoint** command must return only one MAC address. +- The **traceroute -T IP_Endpoint -p 2049** command must not return an error. +- The **nmap -sV -T4 -p111,635,2049,4045,4046 IP_Endpoint** command must return ports in the OPEN state (essential for the proper functioning of NFSv3). ## Go further @@ -102,4 +102,4 @@ You can now follow the guides below to create and manage your volumes, snapshots 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](/links/community). +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.en-au.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.en-au.md index c9271b52408..6ae5925c3ce 100644 --- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.en-au.md +++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.en-au.md @@ -1,7 +1,7 @@ --- title: "Enterprise File Storage - Private network configuration" excerpt: "Find out how to set up a private network for your Enterprise File Storage service from your OVHcloud Control Panel" -updated: 2025-10-21 +updated: 2025-10-23 --- ## Objective @@ -84,9 +84,9 @@ You can now follow the guides below to create and manage your volumes, snapshots > - The IP address of your Service Endpoint must be unique in your subnet and must be excluded from your DHCP server if you use one. > - Example: vRack Services 10.0.0.0/24 subnet - Service Endpoint 10.0.0.16/29 - Your service will therefore be accessible at IP address 10.0.0.16 in subnet 10.0.0.0/24. -- The **arping ** command must return only one MAC address. -- The **traceroute -T -p 2049** command must not return an error. -- The **nmap -sV -T4 -p111,635,2049,4045,4046 ** command must return ports in the OPEN state (essential for the proper functioning of NFSv3). +- The **arping IP_Endpoint** command must return only one MAC address. +- The **traceroute -T IP_Endpoint -p 2049** command must not return an error. +- The **nmap -sV -T4 -p111,635,2049,4045,4046 IP_Endpoint** command must return ports in the OPEN state (essential for the proper functioning of NFSv3). ## Go further @@ -102,4 +102,4 @@ You can now follow the guides below to create and manage your volumes, snapshots 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](/links/community). +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.en-ca.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.en-ca.md index c9271b52408..6ae5925c3ce 100644 --- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.en-ca.md +++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.en-ca.md @@ -1,7 +1,7 @@ --- title: "Enterprise File Storage - Private network configuration" excerpt: "Find out how to set up a private network for your Enterprise File Storage service from your OVHcloud Control Panel" -updated: 2025-10-21 +updated: 2025-10-23 --- ## Objective @@ -84,9 +84,9 @@ You can now follow the guides below to create and manage your volumes, snapshots > - The IP address of your Service Endpoint must be unique in your subnet and must be excluded from your DHCP server if you use one. > - Example: vRack Services 10.0.0.0/24 subnet - Service Endpoint 10.0.0.16/29 - Your service will therefore be accessible at IP address 10.0.0.16 in subnet 10.0.0.0/24. -- The **arping ** command must return only one MAC address. -- The **traceroute -T -p 2049** command must not return an error. -- The **nmap -sV -T4 -p111,635,2049,4045,4046 ** command must return ports in the OPEN state (essential for the proper functioning of NFSv3). +- The **arping IP_Endpoint** command must return only one MAC address. +- The **traceroute -T IP_Endpoint -p 2049** command must not return an error. +- The **nmap -sV -T4 -p111,635,2049,4045,4046 IP_Endpoint** command must return ports in the OPEN state (essential for the proper functioning of NFSv3). ## Go further @@ -102,4 +102,4 @@ You can now follow the guides below to create and manage your volumes, snapshots 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](/links/community). +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.en-gb.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.en-gb.md index c9271b52408..4d2cc44f31e 100644 --- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.en-gb.md +++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.en-gb.md @@ -1,7 +1,7 @@ --- title: "Enterprise File Storage - Private network configuration" excerpt: "Find out how to set up a private network for your Enterprise File Storage service from your OVHcloud Control Panel" -updated: 2025-10-21 +updated: 2025-10-23 --- ## Objective @@ -84,9 +84,9 @@ You can now follow the guides below to create and manage your volumes, snapshots > - The IP address of your Service Endpoint must be unique in your subnet and must be excluded from your DHCP server if you use one. > - Example: vRack Services 10.0.0.0/24 subnet - Service Endpoint 10.0.0.16/29 - Your service will therefore be accessible at IP address 10.0.0.16 in subnet 10.0.0.0/24. -- The **arping ** command must return only one MAC address. -- The **traceroute -T -p 2049** command must not return an error. -- The **nmap -sV -T4 -p111,635,2049,4045,4046 ** command must return ports in the OPEN state (essential for the proper functioning of NFSv3). +- The **arping IP_Endpoint** command must return only one MAC address. +- The **traceroute -T IP_Endpoint -p 2049** command must not return an error. +- The **nmap -sV -T4 -p111,635,2049,4045,4046 IP_Endpoint** command must return ports in the OPEN state (essential for the proper functioning of NFSv3). ## Go further diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.en-ie.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.en-ie.md index c9271b52408..6ae5925c3ce 100644 --- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.en-ie.md +++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.en-ie.md @@ -1,7 +1,7 @@ --- title: "Enterprise File Storage - Private network configuration" excerpt: "Find out how to set up a private network for your Enterprise File Storage service from your OVHcloud Control Panel" -updated: 2025-10-21 +updated: 2025-10-23 --- ## Objective @@ -84,9 +84,9 @@ You can now follow the guides below to create and manage your volumes, snapshots > - The IP address of your Service Endpoint must be unique in your subnet and must be excluded from your DHCP server if you use one. > - Example: vRack Services 10.0.0.0/24 subnet - Service Endpoint 10.0.0.16/29 - Your service will therefore be accessible at IP address 10.0.0.16 in subnet 10.0.0.0/24. -- The **arping ** command must return only one MAC address. -- The **traceroute -T -p 2049** command must not return an error. -- The **nmap -sV -T4 -p111,635,2049,4045,4046 ** command must return ports in the OPEN state (essential for the proper functioning of NFSv3). +- The **arping IP_Endpoint** command must return only one MAC address. +- The **traceroute -T IP_Endpoint -p 2049** command must not return an error. +- The **nmap -sV -T4 -p111,635,2049,4045,4046 IP_Endpoint** command must return ports in the OPEN state (essential for the proper functioning of NFSv3). ## Go further @@ -102,4 +102,4 @@ You can now follow the guides below to create and manage your volumes, snapshots 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](/links/community). +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.en-sg.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.en-sg.md index c9271b52408..6ae5925c3ce 100644 --- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.en-sg.md +++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.en-sg.md @@ -1,7 +1,7 @@ --- title: "Enterprise File Storage - Private network configuration" excerpt: "Find out how to set up a private network for your Enterprise File Storage service from your OVHcloud Control Panel" -updated: 2025-10-21 +updated: 2025-10-23 --- ## Objective @@ -84,9 +84,9 @@ You can now follow the guides below to create and manage your volumes, snapshots > - The IP address of your Service Endpoint must be unique in your subnet and must be excluded from your DHCP server if you use one. > - Example: vRack Services 10.0.0.0/24 subnet - Service Endpoint 10.0.0.16/29 - Your service will therefore be accessible at IP address 10.0.0.16 in subnet 10.0.0.0/24. -- The **arping ** command must return only one MAC address. -- The **traceroute -T -p 2049** command must not return an error. -- The **nmap -sV -T4 -p111,635,2049,4045,4046 ** command must return ports in the OPEN state (essential for the proper functioning of NFSv3). +- The **arping IP_Endpoint** command must return only one MAC address. +- The **traceroute -T IP_Endpoint -p 2049** command must not return an error. +- The **nmap -sV -T4 -p111,635,2049,4045,4046 IP_Endpoint** command must return ports in the OPEN state (essential for the proper functioning of NFSv3). ## Go further @@ -102,4 +102,4 @@ You can now follow the guides below to create and manage your volumes, snapshots 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](/links/community). +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.en-us.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.en-us.md index c9271b52408..6ae5925c3ce 100644 --- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.en-us.md +++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.en-us.md @@ -1,7 +1,7 @@ --- title: "Enterprise File Storage - Private network configuration" excerpt: "Find out how to set up a private network for your Enterprise File Storage service from your OVHcloud Control Panel" -updated: 2025-10-21 +updated: 2025-10-23 --- ## Objective @@ -84,9 +84,9 @@ You can now follow the guides below to create and manage your volumes, snapshots > - The IP address of your Service Endpoint must be unique in your subnet and must be excluded from your DHCP server if you use one. > - Example: vRack Services 10.0.0.0/24 subnet - Service Endpoint 10.0.0.16/29 - Your service will therefore be accessible at IP address 10.0.0.16 in subnet 10.0.0.0/24. -- The **arping ** command must return only one MAC address. -- The **traceroute -T -p 2049** command must not return an error. -- The **nmap -sV -T4 -p111,635,2049,4045,4046 ** command must return ports in the OPEN state (essential for the proper functioning of NFSv3). +- The **arping IP_Endpoint** command must return only one MAC address. +- The **traceroute -T IP_Endpoint -p 2049** command must not return an error. +- The **nmap -sV -T4 -p111,635,2049,4045,4046 IP_Endpoint** command must return ports in the OPEN state (essential for the proper functioning of NFSv3). ## Go further @@ -102,4 +102,4 @@ You can now follow the guides below to create and manage your volumes, snapshots 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](/links/community). +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.es-es.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.es-es.md index c9271b52408..6ae5925c3ce 100644 --- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.es-es.md +++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.es-es.md @@ -1,7 +1,7 @@ --- title: "Enterprise File Storage - Private network configuration" excerpt: "Find out how to set up a private network for your Enterprise File Storage service from your OVHcloud Control Panel" -updated: 2025-10-21 +updated: 2025-10-23 --- ## Objective @@ -84,9 +84,9 @@ You can now follow the guides below to create and manage your volumes, snapshots > - The IP address of your Service Endpoint must be unique in your subnet and must be excluded from your DHCP server if you use one. > - Example: vRack Services 10.0.0.0/24 subnet - Service Endpoint 10.0.0.16/29 - Your service will therefore be accessible at IP address 10.0.0.16 in subnet 10.0.0.0/24. -- The **arping ** command must return only one MAC address. -- The **traceroute -T -p 2049** command must not return an error. -- The **nmap -sV -T4 -p111,635,2049,4045,4046 ** command must return ports in the OPEN state (essential for the proper functioning of NFSv3). +- The **arping IP_Endpoint** command must return only one MAC address. +- The **traceroute -T IP_Endpoint -p 2049** command must not return an error. +- The **nmap -sV -T4 -p111,635,2049,4045,4046 IP_Endpoint** command must return ports in the OPEN state (essential for the proper functioning of NFSv3). ## Go further @@ -102,4 +102,4 @@ You can now follow the guides below to create and manage your volumes, snapshots 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](/links/community). +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.es-us.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.es-us.md index c9271b52408..6ae5925c3ce 100644 --- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.es-us.md +++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.es-us.md @@ -1,7 +1,7 @@ --- title: "Enterprise File Storage - Private network configuration" excerpt: "Find out how to set up a private network for your Enterprise File Storage service from your OVHcloud Control Panel" -updated: 2025-10-21 +updated: 2025-10-23 --- ## Objective @@ -84,9 +84,9 @@ You can now follow the guides below to create and manage your volumes, snapshots > - The IP address of your Service Endpoint must be unique in your subnet and must be excluded from your DHCP server if you use one. > - Example: vRack Services 10.0.0.0/24 subnet - Service Endpoint 10.0.0.16/29 - Your service will therefore be accessible at IP address 10.0.0.16 in subnet 10.0.0.0/24. -- The **arping ** command must return only one MAC address. -- The **traceroute -T -p 2049** command must not return an error. -- The **nmap -sV -T4 -p111,635,2049,4045,4046 ** command must return ports in the OPEN state (essential for the proper functioning of NFSv3). +- The **arping IP_Endpoint** command must return only one MAC address. +- The **traceroute -T IP_Endpoint -p 2049** command must not return an error. +- The **nmap -sV -T4 -p111,635,2049,4045,4046 IP_Endpoint** command must return ports in the OPEN state (essential for the proper functioning of NFSv3). ## Go further @@ -102,4 +102,4 @@ You can now follow the guides below to create and manage your volumes, snapshots 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](/links/community). +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.fr-ca.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.fr-ca.md index 147edf71c0f..0b06f97ee75 100644 --- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.fr-ca.md +++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.fr-ca.md @@ -1,7 +1,7 @@ --- title: "Enterprise File Storage - Configuration du réseau privé" excerpt: Découvrez configurer un réseau privé pour votre service Enterprise File Storage depuis votre espace client OVHcloud -updated: 2025-10-21 +updated: 2025-10-23 --- ## Objectif @@ -86,9 +86,9 @@ Vous pouvez à présent suivre les guides ci-dessous pour créer et gérer vos v > - L'adresse IP de votre Service Endpoint doit être unique dans votre sous-réseau et doit être exclue de votre serveur DHCP si vous en utilisez un. > - Exemple : sous-réseau vRack Services 10.0.0.0/24 - Service Endpoint 10.0.0.16/29 - Votre service sera donc accessible à l'adresse IP 10.0.0.16 dans le sous-réseau 10.0.0.0/24. -- La commande **arping ** ne doit retourner qu'une seule adresse MAC. -- La commande **traceroute -T -p 2049** ne doit pas retourner d'erreur. -- La commande  **nmap -sV -T4 -p111,635,2049,4045,4046 ** doit retourner des ports dans l'état OPEN (indispensable pour le bon fonctionnement de NFSv3). +- La commande **arping IP_Endpoint** ne doit retourner qu'une seule adresse MAC. +- La commande **traceroute -T IP_Endpoint -p 2049** ne doit pas retourner d'erreur. +- La commande  **nmap -sV -T4 -p111,635,2049,4045,4046 IP_Endpoint** doit retourner des ports dans l'état OPEN (indispensable pour le bon fonctionnement de NFSv3). ## Aller plus loin @@ -104,4 +104,4 @@ Vous pouvez à présent suivre les guides ci-dessous pour créer et gérer vos v 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/enterprise_file_storage/netapp_network_config/guide.fr-fr.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.fr-fr.md index 147edf71c0f..0d237394708 100644 --- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.fr-fr.md +++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.fr-fr.md @@ -1,7 +1,7 @@ --- title: "Enterprise File Storage - Configuration du réseau privé" excerpt: Découvrez configurer un réseau privé pour votre service Enterprise File Storage depuis votre espace client OVHcloud -updated: 2025-10-21 +updated: 2025-10-23 --- ## Objectif @@ -86,9 +86,9 @@ Vous pouvez à présent suivre les guides ci-dessous pour créer et gérer vos v > - L'adresse IP de votre Service Endpoint doit être unique dans votre sous-réseau et doit être exclue de votre serveur DHCP si vous en utilisez un. > - Exemple : sous-réseau vRack Services 10.0.0.0/24 - Service Endpoint 10.0.0.16/29 - Votre service sera donc accessible à l'adresse IP 10.0.0.16 dans le sous-réseau 10.0.0.0/24. -- La commande **arping ** ne doit retourner qu'une seule adresse MAC. -- La commande **traceroute -T -p 2049** ne doit pas retourner d'erreur. -- La commande  **nmap -sV -T4 -p111,635,2049,4045,4046 ** doit retourner des ports dans l'état OPEN (indispensable pour le bon fonctionnement de NFSv3). +- La commande **arping IP_Endpoint** ne doit retourner qu'une seule adresse MAC. +- La commande **traceroute -T IP_Endpoint -p 2049** ne doit pas retourner d'erreur. +- La commande  **nmap -sV -T4 -p111,635,2049,4045,4046 IP_Endpoint** doit retourner des ports dans l'état OPEN (indispensable pour le bon fonctionnement de NFSv3). ## Aller plus loin diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.it-it.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.it-it.md index c9271b52408..6ae5925c3ce 100644 --- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.it-it.md +++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.it-it.md @@ -1,7 +1,7 @@ --- title: "Enterprise File Storage - Private network configuration" excerpt: "Find out how to set up a private network for your Enterprise File Storage service from your OVHcloud Control Panel" -updated: 2025-10-21 +updated: 2025-10-23 --- ## Objective @@ -84,9 +84,9 @@ You can now follow the guides below to create and manage your volumes, snapshots > - The IP address of your Service Endpoint must be unique in your subnet and must be excluded from your DHCP server if you use one. > - Example: vRack Services 10.0.0.0/24 subnet - Service Endpoint 10.0.0.16/29 - Your service will therefore be accessible at IP address 10.0.0.16 in subnet 10.0.0.0/24. -- The **arping ** command must return only one MAC address. -- The **traceroute -T -p 2049** command must not return an error. -- The **nmap -sV -T4 -p111,635,2049,4045,4046 ** command must return ports in the OPEN state (essential for the proper functioning of NFSv3). +- The **arping IP_Endpoint** command must return only one MAC address. +- The **traceroute -T IP_Endpoint -p 2049** command must not return an error. +- The **nmap -sV -T4 -p111,635,2049,4045,4046 IP_Endpoint** command must return ports in the OPEN state (essential for the proper functioning of NFSv3). ## Go further @@ -102,4 +102,4 @@ You can now follow the guides below to create and manage your volumes, snapshots 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](/links/community). +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.pl-pl.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.pl-pl.md index c9271b52408..6ae5925c3ce 100644 --- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.pl-pl.md +++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.pl-pl.md @@ -1,7 +1,7 @@ --- title: "Enterprise File Storage - Private network configuration" excerpt: "Find out how to set up a private network for your Enterprise File Storage service from your OVHcloud Control Panel" -updated: 2025-10-21 +updated: 2025-10-23 --- ## Objective @@ -84,9 +84,9 @@ You can now follow the guides below to create and manage your volumes, snapshots > - The IP address of your Service Endpoint must be unique in your subnet and must be excluded from your DHCP server if you use one. > - Example: vRack Services 10.0.0.0/24 subnet - Service Endpoint 10.0.0.16/29 - Your service will therefore be accessible at IP address 10.0.0.16 in subnet 10.0.0.0/24. -- The **arping ** command must return only one MAC address. -- The **traceroute -T -p 2049** command must not return an error. -- The **nmap -sV -T4 -p111,635,2049,4045,4046 ** command must return ports in the OPEN state (essential for the proper functioning of NFSv3). +- The **arping IP_Endpoint** command must return only one MAC address. +- The **traceroute -T IP_Endpoint -p 2049** command must not return an error. +- The **nmap -sV -T4 -p111,635,2049,4045,4046 IP_Endpoint** command must return ports in the OPEN state (essential for the proper functioning of NFSv3). ## Go further @@ -102,4 +102,4 @@ You can now follow the guides below to create and manage your volumes, snapshots 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](/links/community). +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.pt-pt.md b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.pt-pt.md index c9271b52408..6ae5925c3ce 100644 --- a/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.pt-pt.md +++ b/pages/storage_and_backup/file_storage/enterprise_file_storage/netapp_network_config/guide.pt-pt.md @@ -1,7 +1,7 @@ --- title: "Enterprise File Storage - Private network configuration" excerpt: "Find out how to set up a private network for your Enterprise File Storage service from your OVHcloud Control Panel" -updated: 2025-10-21 +updated: 2025-10-23 --- ## Objective @@ -84,9 +84,9 @@ You can now follow the guides below to create and manage your volumes, snapshots > - The IP address of your Service Endpoint must be unique in your subnet and must be excluded from your DHCP server if you use one. > - Example: vRack Services 10.0.0.0/24 subnet - Service Endpoint 10.0.0.16/29 - Your service will therefore be accessible at IP address 10.0.0.16 in subnet 10.0.0.0/24. -- The **arping ** command must return only one MAC address. -- The **traceroute -T -p 2049** command must not return an error. -- The **nmap -sV -T4 -p111,635,2049,4045,4046 ** command must return ports in the OPEN state (essential for the proper functioning of NFSv3). +- The **arping IP_Endpoint** command must return only one MAC address. +- The **traceroute -T IP_Endpoint -p 2049** command must not return an error. +- The **nmap -sV -T4 -p111,635,2049,4045,4046 IP_Endpoint** command must return ports in the OPEN state (essential for the proper functioning of NFSv3). ## Go further @@ -102,4 +102,4 @@ You can now follow the guides below to create and manage your volumes, snapshots 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](/links/community). +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.de-de.md b/pages/storage_and_backup/file_storage/ha_nas/nas_cifs/guide.de-de.md index 27473032dbc..623735cfa35 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-09 +updated: 2025-10-23 --- ## Ziel @@ -15,12 +15,12 @@ updated: 2025-10-09 ## In der praktischen Anwendung -### Einstellungen für Windows +### Einstellungen für Microsoft 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. -- **Windows Server 2016**: Klicken Sie auf `Start`{.action} und dann auf das `Windows PowerShell`{.action} Icon. -- **Windows Server 2019**: Klicken Sie auf `Start`{.action} und dann auf das `Windows PowerShell`{.action} Icon. +- **Windows Server 2016/2019/2022/2025**: Klicken Sie auf `Start`{.action} und dann auf das `Windows PowerShell`{.action} Icon. + Führen Sie dann den folgenden Befehl aus: @@ -41,7 +41,7 @@ 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: +Die folgenden Fehlermeldungen können angezeigt werden: ```console System error 1272 has occurred. @@ -49,11 +49,15 @@ 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. ``` +```console +System error 3227320323 has occurred. +``` + > [!primary] > -> 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). +> Informationen zum Beheben dieser Fehler finden Sie in der offiziellen Microsoft-Dokumentation:
+> [Aktivieren von unsicheren Gastanmeldungen in SMB2 und SMB3](https://learn.microsoft.com/de-de/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3?tabs=powershell) +> [Steuerung des SMB-Signierverhaltens](https://learn.microsoft.com/de-de/windows-server/storage/file-server/smb-signing?tabs=powershell). ### 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 d40031e6c2c..19f5aa37b04 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-09 +updated: 2025-10-23 --- ## Objective @@ -15,12 +15,12 @@ updated: 2025-10-09 ## Instructions -### Settings for Windows +### Settings for Microsoft 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. -- **Windows Server 2016**: Click on the menu `Start`{.action}, then on the `Windows PowerShell`{.action} icon. -- **Windows Server 2019**: Click on the menu `Start`{.action}, then on the `Windows PowerShell`{.action} icon. +- **Windows Server 2016/2019/2022/2025**: Click on the menu `Start`{.action}, then on the `Windows PowerShell`{.action} icon. + Then run the following command: @@ -41,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 messages may appear: ```console System error 1272 has occurred. @@ -49,11 +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. ``` +```console +System error 3227320323 has occurred. +``` + > [!primary] > -> 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`.
-> Then set the value of the parameter `AllowInsecureGuestAuth` to "1".
-> 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). +> To correct these errors, refer to the official Microsoft documentation :
+> [How to enable insecure guest logons in SMB2 and SMB3](https://learn.microsoft.com/en-gb/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3?tabs=powershell).
+> [Control SMB signing behavior](https://learn.microsoft.com/en-gb/windows-server/storage/file-server/smb-signing?tabs=powershell). + ### 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 64f818abac0..19f5aa37b04 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-09 +updated: 2025-10-23 --- ## Objective @@ -15,12 +15,12 @@ updated: 2025-10-09 ## Instructions -### Settings for Windows +### Settings for Microsoft 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. -- **Windows Server 2016**: Click on the menu `Start`{.action}, then on the `Windows PowerShell`{.action} icon. -- **Windows Server 2019**: Click on the menu `Start`{.action}, then on the `Windows PowerShell`{.action} icon. +- **Windows Server 2016/2019/2022/2025**: Click on the menu `Start`{.action}, then on the `Windows PowerShell`{.action} icon. + Then run the following command: @@ -41,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 messages may appear: ```console System error 1272 has occurred. @@ -49,11 +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. ``` +```console +System error 3227320323 has occurred. +``` + > [!primary] > -> 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`.
-> Then set the value of the parameter `AllowInsecureGuestAuth` to "1".
-> 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). +> To correct these errors, refer to the official Microsoft documentation :
+> [How to enable insecure guest logons in SMB2 and SMB3](https://learn.microsoft.com/en-gb/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3?tabs=powershell).
+> [Control SMB signing behavior](https://learn.microsoft.com/en-gb/windows-server/storage/file-server/smb-signing?tabs=powershell). + ### 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 7ab1fac8e50..19f5aa37b04 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-09 +updated: 2025-10-23 --- ## Objective @@ -15,12 +15,12 @@ updated: 2025-10-09 ## Instructions -### Settings for Windows +### Settings for Microsoft 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. -- **Windows Server 2016**: Click on the menu `Start`{.action}, then on the `Windows PowerShell`{.action} icon. -- **Windows Server 2019**: Click on the menu `Start`{.action}, then on the `Windows PowerShell`{.action} icon. +- **Windows Server 2016/2019/2022/2025**: Click on the menu `Start`{.action}, then on the `Windows PowerShell`{.action} icon. + Then run the following command: @@ -41,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 messages may appear: ```console System error 1272 has occurred. @@ -49,11 +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. ``` +```console +System error 3227320323 has occurred. +``` + > [!primary] > -> 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`.
-> Then set the value of the parameter `AllowInsecureGuestAuth` to "1".
-> 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). +> To correct these errors, refer to the official Microsoft documentation :
+> [How to enable insecure guest logons in SMB2 and SMB3](https://learn.microsoft.com/en-gb/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3?tabs=powershell).
+> [Control SMB signing behavior](https://learn.microsoft.com/en-gb/windows-server/storage/file-server/smb-signing?tabs=powershell). + ### 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 09d4278f69f..19f5aa37b04 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-09 +updated: 2025-10-23 --- ## Objective @@ -15,12 +15,12 @@ updated: 2025-10-09 ## Instructions -### Settings for Windows +### Settings for Microsoft 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. -- **Windows Server 2016**: Click on the menu `Start`{.action}, then on the `Windows PowerShell`{.action} icon. -- **Windows Server 2019**: Click on the menu `Start`{.action}, then on the `Windows PowerShell`{.action} icon. +- **Windows Server 2016/2019/2022/2025**: Click on the menu `Start`{.action}, then on the `Windows PowerShell`{.action} icon. + Then run the following command: @@ -41,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 messages may appear: ```console System error 1272 has occurred. @@ -49,11 +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. ``` +```console +System error 3227320323 has occurred. +``` + > [!primary] > -> 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`.
-> Then set the value of the parameter `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). +> To correct these errors, refer to the official Microsoft documentation :
+> [How to enable insecure guest logons in SMB2 and SMB3](https://learn.microsoft.com/en-gb/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3?tabs=powershell).
+> [Control SMB signing behavior](https://learn.microsoft.com/en-gb/windows-server/storage/file-server/smb-signing?tabs=powershell). + ### 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 e3fb1d430fd..19f5aa37b04 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-09 +updated: 2025-10-23 --- ## Objective @@ -15,12 +15,12 @@ updated: 2025-10-09 ## Instructions -### Settings for Windows +### Settings for Microsoft 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. -- **Windows Server 2016**: Click on the menu `Start`{.action}, then on the `Windows PowerShell`{.action} icon. -- **Windows Server 2019**: Click on the menu `Start`{.action}, then on the `Windows PowerShell`{.action} icon. +- **Windows Server 2016/2019/2022/2025**: Click on the menu `Start`{.action}, then on the `Windows PowerShell`{.action} icon. + Then run the following command: @@ -41,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 messages may appear: ```console System error 1272 has occurred. @@ -49,11 +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. ``` +```console +System error 3227320323 has occurred. +``` + > [!primary] > -> 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`.
-> Then set the value of the parameter `AllowInsecureGuestAuth` to "1".
-> 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). +> To correct these errors, refer to the official Microsoft documentation :
+> [How to enable insecure guest logons in SMB2 and SMB3](https://learn.microsoft.com/en-gb/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3?tabs=powershell).
+> [Control SMB signing behavior](https://learn.microsoft.com/en-gb/windows-server/storage/file-server/smb-signing?tabs=powershell). + ### 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 fb460347d44..19f5aa37b04 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-09 +updated: 2025-10-23 --- ## Objective @@ -15,12 +15,12 @@ updated: 2025-10-09 ## Instructions -### Settings for Windows +### Settings for Microsoft 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. -- **Windows Server 2016**: Click on the menu `Start`{.action}, then on the `Windows PowerShell`{.action} icon. -- **Windows Server 2019**: Click on the menu `Start`{.action}, then on the `Windows PowerShell`{.action} icon. +- **Windows Server 2016/2019/2022/2025**: Click on the menu `Start`{.action}, then on the `Windows PowerShell`{.action} icon. + Then run the following command: @@ -41,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 messages may appear: ```console System error 1272 has occurred. @@ -49,11 +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. ``` +```console +System error 3227320323 has occurred. +``` + > [!primary] > -> 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`.
-> Then set the value of the parameter `AllowInsecureGuestAuth` to "1".
-> 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). +> To correct these errors, refer to the official Microsoft documentation :
+> [How to enable insecure guest logons in SMB2 and SMB3](https://learn.microsoft.com/en-gb/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3?tabs=powershell).
+> [Control SMB signing behavior](https://learn.microsoft.com/en-gb/windows-server/storage/file-server/smb-signing?tabs=powershell). + ### 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 08ee1c7c73e..19f5aa37b04 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-09 +updated: 2025-10-23 --- ## Objective @@ -15,12 +15,12 @@ updated: 2025-10-09 ## Instructions -### Settings for Windows +### Settings for Microsoft 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. -- **Windows Server 2016**: Click on the menu `Start`{.action}, then on the `Windows PowerShell`{.action} icon. -- **Windows Server 2019**: Click on the menu `Start`{.action}, then on the `Windows PowerShell`{.action} icon. +- **Windows Server 2016/2019/2022/2025**: Click on the menu `Start`{.action}, then on the `Windows PowerShell`{.action} icon. + Then run the following command: @@ -41,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 messages may appear: ```console System error 1272 has occurred. @@ -49,11 +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. ``` +```console +System error 3227320323 has occurred. +``` + > [!primary] > -> 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`.
-> Then set the value of the parameter `AllowInsecureGuestAuth` to "1".
-> 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). +> To correct these errors, refer to the official Microsoft documentation :
+> [How to enable insecure guest logons in SMB2 and SMB3](https://learn.microsoft.com/en-gb/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3?tabs=powershell).
+> [Control SMB signing behavior](https://learn.microsoft.com/en-gb/windows-server/storage/file-server/smb-signing?tabs=powershell). + ### 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 4304703e6c9..861c61c2188 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-09 +updated: 2025-10-23 --- ## Objetivo @@ -15,12 +15,11 @@ updated: 2025-10-09 ## Procedimiento -### Configuración para Windows +### Configuración para Microsoft 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. -- **Windows Server 2016** : haga clic en el menú `Start`{.action} y seleccione el icono de `Windows PowerShell`{.action}. -- **Windows Server 2019** : haga clic en el menú `Start`{.action} y seleccione el icono de `Windows PowerShell`{.action}. +- **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. +- **Windows Server 2016/2019/2022/2025**: haga clic en el menú `Start`{.action} y seleccione el icono de `Windows PowerShell`{.action}. Ejecute el siguiente comando: @@ -41,7 +40,8 @@ net use z: \\10.16.101.8\zpool-000206_PARTITION_NAME_1 > 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: +Pueden aparecer los siguientes mensajes de error: + ```console System error 1272 has occurred. @@ -49,11 +49,15 @@ 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. ``` +```console +System error 3227320323 has occurred. +``` + > [!primary] > -> 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`.
-> Asigne el valor "1" al parámetro `AllowInsecureGuestAuth`.
-> 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). +> Para corregir estos errores, consulte la documentación oficial de Microsoft:
+> [Cómo habilitar inicios de sesión de invitado no seguros en SMB2 y SMB3](https://learn.microsoft.com/es-es/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3?tabs=powershell).
+> [Control del comportamiento de la firma SMB](https://learn.microsoft.com/es-es/windows-server/storage/file-server/smb-signing?tabs=powershell). ### 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 2a1c9d99141..67c047c5699 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-09 +updated: 2025-10-23 --- ## Objetivo @@ -15,12 +15,11 @@ updated: 2025-10-09 ## Procedimiento -### Configuración para Windows +### Configuración para Micorsoft 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. -- **Windows Server 2016** : haga clic en el menú `Start`{.action} y seleccione el icono de `Windows PowerShell`{.action}. -- **Windows Server 2019** : haga clic en el menú `Start`{.action} y seleccione el icono de `Windows PowerShell`{.action}. +- **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. +- **Windows Server 2016/2019/2022/2025**: haga clic en el menú `Start`{.action} y seleccione el icono de `Windows PowerShell`{.action}. Ejecute el siguiente comando: @@ -41,7 +40,8 @@ net use z: \\10.16.101.8\zpool-000206_PARTITION_NAME_1 > 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: +Pueden aparecer los siguientes mensajes de error: + ```console System error 1272 has occurred. @@ -49,11 +49,15 @@ 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. ``` +```console +System error 3227320323 has occurred. +``` + > [!primary] > -> 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`.
-> Asigne el valor "1" al parámetro `AllowInsecureGuestAuth`.
-> 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). +> Para corregir estos errores, consulte la documentación oficial de Microsoft:
+> [Cómo habilitar inicios de sesión de invitado no seguros en SMB2 y SMB3](https://learn.microsoft.com/es-es/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3?tabs=powershell).
+> [Control del comportamiento de la firma SMB](https://learn.microsoft.com/es-es/windows-server/storage/file-server/smb-signing?tabs=powershell). ### 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 01ab134f4d1..27b92900548 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-09 +updated: 2025-10-23 --- ## Objectif @@ -15,12 +15,12 @@ updated: 2025-10-09 ## En pratique -### Configuration pour Windows +### Configuration pour Microsoft 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. -- **Windows Server 2016** : cliquez sur le menu `Démarrer`{.action}, puis sur l'icône du `Windows PowerShell`{.action}. -- **Windows Server 2019** : cliquez sur le menu `Démarrer`{.action}, puis sur l'icône du `Windows PowerShell`{.action}. +- **Windows Server 2016/2019/2022/2025** : cliquez sur le menu `Démarrer`{.action}, puis sur l'icône du `Windows PowerShell`{.action}. + Exécutez ensuite la commande suivante : @@ -41,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 : +Les messages d'erreur suivants peuvent s'afficher : ```console System error 1272 has occurred. @@ -49,11 +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. ``` +```console +System error 3227320323 has occurred. +``` + > [!primary] > -> 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`.
-> Attribuez ensuite la valeur « 1 » au paramètre `AllowInsecureGuestAuth`.
-> 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). +> Pour corriger ces erreurs, reportez-vous à la documentation officielle de Microsoft :
+> [Comment activer les ouvertures de session invité non sécurisées dans SMB2 et SMB3](https://learn.microsoft.com/fr-fr/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3?tabs=powershell).
+> [Contrôler le comportement de la signature SMB](https://learn.microsoft.com/fr-fr/windows-server/storage/file-server/smb-signing?tabs=powershell). + ### Configuration pour Linux @@ -83,4 +88,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). \ No newline at end of file +Échangez avec notre [communauté d'utilisateurs](/links/community). 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 270d5a62ba0..2521311b9a3 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-09 +updated: 2025-10-23 --- ## Objectif @@ -15,12 +15,12 @@ updated: 2025-10-09 ## En pratique -### Configuration pour Windows +### Configuration pour Microsoft 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. -- **Windows Server 2016** : cliquez sur le menu `Démarrer`{.action}, puis sur l'icône du `Windows PowerShell`{.action}. -- **Windows Server 2019** : cliquez sur le menu `Démarrer`{.action}, puis sur l'icône du `Windows PowerShell`{.action}. +- **Windows Server 2016/2019/2022/2025** : cliquez sur le menu `Démarrer`{.action}, puis sur l'icône du `Windows PowerShell`{.action}. + Exécutez ensuite la commande suivante : @@ -41,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 : +Les messages d'erreur suivants peuvent s'afficher : ```console System error 1272 has occurred. @@ -49,11 +49,15 @@ 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. ``` +```console +System error 3227320323 has occurred. +``` + > [!primary] > -> 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`.
-> Attribuez ensuite la valeur « 1 » au paramètre `AllowInsecureGuestAuth`.
-> 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). +> Pour corriger ces erreurs, reportez-vous à la documentation officielle de Microsoft :
+> [Comment activer les ouvertures de session invité non sécurisées dans SMB2 et SMB3](https://learn.microsoft.com/fr-fr/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3?tabs=powershell).
+> [Contrôler le comportement de la signature SMB](https://learn.microsoft.com/fr-fr/windows-server/storage/file-server/smb-signing?tabs=powershell). ### Configuration pour Linux @@ -84,4 +88,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). \ No newline at end of file +Échangez avec notre [communauté d'utilisateurs](/links/community). 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 283be9fe8c5..ad1c1a23783 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-09 +updated: 2025-10-23 --- ## Obiettivo @@ -15,12 +15,11 @@ updated: 2025-10-09 ## Procedura -### Configurazione per Windows +### Configurazione per Microsoft 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. -- **Windows Server 2016** : clicca sul menu `Start`{.action} e poi sull'icona del `Windows PowerShell`{.action}. -- **Windows Server 2019** : clicca sul menu `Start`{.action} e poi sull'icona del `Windows PowerShell`{.action}. +- **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. +- **Windows Server 2016/2019/2022/2025**: clicca sul menu `Start`{.action} e poi sull'icona del `Windows PowerShell`{.action}. Esegui questo comando: @@ -41,7 +40,7 @@ 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: +Potrebbero essere visualizzati i seguenti messaggi di errore: ```console System error 1272 has occurred. @@ -49,11 +48,15 @@ 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. ``` +```console +System error 3227320323 has occurred. +``` + > [!primary] > -> 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`.
-> Assegnare il valore "1" al parametro `AllowInsecureGuestAuth`.
-> 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). +> Per correggere questi errori, consultare la documentazione ufficiale Microsoft:
+> [Come abilitare gli accessi guest non protetti in SMB2 e SMB3](https://learn.microsoft.com/it-it/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3?tabs=powershell).
+> [Controllare il comportamento di firma SMB](https://learn.microsoft.com/it-it/windows-server/storage/file-server/smb-signing?tabs=powershell). ### 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 8b12a5bb90b..5529822d230 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-09 +updated: 2025-10-23 --- ## Wprowadzenie @@ -15,12 +15,11 @@ updated: 2025-10-09 ## W praktyce -### Ustawienia dla systemu Windows +### Ustawienia dla systemu Microsoft 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ń. -- **Windows Server 2016**: Kliknij menu `Start`{.action}, a następnie na ikonę `Windows PowerShell`{.action}. -- **Windows Server 2019**: Kliknij menu `Start`{.action}, a następnie na ikonę `Windows PowerShell`{.action}. +- **Windows Server 2016/2019/2022/2025**: Kliknij menu `Start`{.action}, a następnie na ikonę `Windows PowerShell`{.action}. Teraz wprowadź następującą komendę: @@ -41,7 +40,7 @@ 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: +Mogą pojawić się następujące komunikaty o błędach: ```console System error 1272 has occurred. @@ -49,11 +48,15 @@ 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. ``` +```console +System error 3227320323 has occurred. +``` + > [!primary] > -> 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`.
-> Ustaw wartość parametru `AllowInsecureGuestAuth` na "1".
-> 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). +> Aby skorygować te błędy, zapoznaj się z oficjalną dokumentacją firmy Microsoft:
+> [Jak włączyć niezabezpieczone logowania gościa w protokołach SMB2 i SMB3](https://learn.microsoft.com/pl-pl/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3?tabs=powershell).
+> [Kontrolowanie zachowania podpisywania protokołu SMB](https://learn.microsoft.com/pl-pl/windows-server/storage/file-server/smb-signing?tabs=powershell). ### 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 5c5da19cf19..bd8012094da 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-09 +updated: 2025-10-23 --- ## Objetivo @@ -15,12 +15,11 @@ updated: 2025-10-09 ## Instruções -### Configuração para Windows +### Configuração para Microsoft 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. -- **Windows Server 2016** : clique no menu `Start`{.action} e, a seguir, no ícone do `Windows PowerShell`{.action}. -- **Windows Server 2019** : clique no menu `Start`{.action} e, a seguir, no ícone do `Windows PowerShell`{.action}. +- **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. +- **Windows Server 2016/2019/2022/2025**: clique no menu `Start`{.action} e, a seguir, no ícone do `Windows PowerShell`{.action}. De seguida, execute o seguinte comando: @@ -41,7 +40,7 @@ net use z: \\10.16.101.8\zpool-000206_PARTITION_NAME_1 > 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: +As seguintes mensagens de erro podem ser exibidas: ```console System error 1272 has occurred. @@ -49,11 +48,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. ``` +```console +System error 3227320323 has occurred. +``` + > [!primary] > -> 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`.
-> Atribua o valor "1" ao parâmetro `AllowInsecureGuestAuth`.
-> 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). +> Para corrigir esses erros, consulte a documentação oficial da Microsoft:
+> [Como ativar logons convidados inseguros no SMB2 e SMB3](https://learn.microsoft.com/pt-pt/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3?tabs=powershell).
+> [Controlar o comportamento de assinatura do SMB](https://learn.microsoft.com/pt-pt/windows-server/storage/file-server/smb-signing?tabs=powershell). + ### Configuração para Linux