{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-375-check-the-client-encoding-before-renaming-an-unfamiliar-netapp-filename/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-375-check-the-client-encoding-before-renaming-an-unfamiliar-netapp-filename/", "slug": "dse-20260909-375-check-the-client-encoding-before-renaming-an-unfamiliar-netapp-filename", "url": "https://update.dsesecurity.com/updates/dse-20260909-375-check-the-client-encoding-before-renaming-an-unfamiliar-netapp-filename/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-375-check-the-client-encoding-before-renaming-an-unfamiliar-netapp-filename.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-375-check-the-client-encoding-before-renaming-an-unfamiliar-netapp-filename/" }, "title": "Check the client encoding before renaming an unfamiliar NetApp filename", "summary": "A different terminal view can change how the same stored name appears without establishing that the file was renamed.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "continuity-recovery", "label": "Continuity & recovery", "alt": "Paired infrastructure paths converging on a stable recovered service.", "card_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "business-continuity", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-10T00:25:41+00:00", "modified_at": "2026-09-10T02:01:56+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 2, "word_count": 230, "potentially_affected": "Azure NetApp Files NFS or SMB access involving special-character filenames.", "dse_recommendation": "Compare client, terminal, and protocol encoding before proposing a filename repair.", "primary_source": { "name": "Understand volume languages in Azure NetApp Files | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/azure-netapp-files/understand-volume-languages", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

Azure NetApp Files uses C.UTF-8 as its default volume language, and the source says the volume-language setting cannot currently be changed.

\n

Remote connection tools using different encodings can display the same stored filename differently. The source also distinguishes NFSv3, which does not enforce UTF encoding on names, from NFSv4.x, which enforces UTF-8. A rejected or unexpected name therefore needs protocol and client context. Microsoft Learn.

\n

Applicability

\n

Identify the affected volume, exact file, access protocol, client locale, terminal encoding, and display font. Keep the filename investigation separate from the encoding of the file’s contents. Preserve the original object before any conversion or rename experiment.

\n

DSE recommendation

\n

DSE recommends reproducing the display difference with the same object through a known client configuration. Ask the application owner which characters and access paths must work, then test a nonsensitive representative name. Avoid treating a screenshot alone as permission to normalize or replace production names; first establish whether the discrepancy is in display, input, or stored data.

\n

Verification

\n

Compare the object through the intended clients and record the protocol and encoding used for each observation. Test listing and exact-name access without modifying the production object. If a rename is later approved, verify dependent application references separately and retain a reversible mapping of the original and replacement names.

\n

Official references

\n

Microsoft Learn: Understand volume languages in Azure NetApp Files. Source retrieved September 9, 2026.

", "content_text": "Source facts\nAzure NetApp Files uses C.UTF-8 as its default volume language, and the source says the volume-language setting cannot currently be changed.\nRemote connection tools using different encodings can display the same stored filename differently. The source also distinguishes NFSv3, which does not enforce UTF encoding on names, from NFSv4.x, which enforces UTF-8. A rejected or unexpected name therefore needs protocol and client context. Microsoft Learn.\nApplicability\nIdentify the affected volume, exact file, access protocol, client locale, terminal encoding, and display font. Keep the filename investigation separate from the encoding of the file’s contents. Preserve the original object before any conversion or rename experiment.\nDSE recommendation\nDSE recommends reproducing the display difference with the same object through a known client configuration. Ask the application owner which characters and access paths must work, then test a nonsensitive representative name. Avoid treating a screenshot alone as permission to normalize or replace production names; first establish whether the discrepancy is in display, input, or stored data.\nVerification\nCompare the object through the intended clients and record the protocol and encoding used for each observation. Test listing and exact-name access without modifying the production object. If a rename is later approved, verify dependent application references separately and retain a reversible mapping of the original and replacement names.\nOfficial references\nMicrosoft Learn: Understand volume languages in Azure NetApp Files. Source retrieved September 9, 2026.", "content_markdown": "## Source facts\n\nAzure NetApp Files uses C.UTF-8 as its default volume language, and the source says the volume-language setting cannot currently be changed.\n\nRemote connection tools using different encodings can display the same stored filename differently. The source also distinguishes NFSv3, which does not enforce UTF encoding on names, from NFSv4.x, which enforces UTF-8. A rejected or unexpected name therefore needs protocol and client context. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/azure-netapp-files/understand-volume-languages).\n\n## Applicability\n\nIdentify the affected volume, exact file, access protocol, client locale, terminal encoding, and display font. Keep the filename investigation separate from the encoding of the file’s contents. Preserve the original object before any conversion or rename experiment.\n\n## DSE recommendation\n\nDSE recommends reproducing the display difference with the same object through a known client configuration. Ask the application owner which characters and access paths must work, then test a nonsensitive representative name. Avoid treating a screenshot alone as permission to normalize or replace production names; first establish whether the discrepancy is in display, input, or stored data.\n\n## Verification\n\nCompare the object through the intended clients and record the protocol and encoding used for each observation. Test listing and exact-name access without modifying the production object. If a rename is later approved, verify dependent application references separately and retain a reversible mapping of the original and replacement names.\n\n## Official references\n\n[Microsoft Learn: Understand volume languages in Azure NetApp Files](https://learn.microsoft.com/en-us/azure/azure-netapp-files/understand-volume-languages). Source retrieved September 9, 2026." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260909-375-check-the-client-encoding-before-renaming-an-unfamiliar-netapp-filename/", "url": "https://update.dsesecurity.com/updates/dse-20260909-375-check-the-client-encoding-before-renaming-an-unfamiliar-netapp-filename/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-375-check-the-client-encoding-before-renaming-an-unfamiliar-netapp-filename/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Check the client encoding before renaming an unfamiliar NetApp filename", "item": "https://update.dsesecurity.com/updates/dse-20260909-375-check-the-client-encoding-before-renaming-an-unfamiliar-netapp-filename/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-375-check-the-client-encoding-before-renaming-an-unfamiliar-netapp-filename/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-375-check-the-client-encoding-before-renaming-an-unfamiliar-netapp-filename/", "url": "https://update.dsesecurity.com/updates/dse-20260909-375-check-the-client-encoding-before-renaming-an-unfamiliar-netapp-filename/", "headline": "Check the client encoding before renaming an unfamiliar NetApp filename", "description": "A different terminal view can change how the same stored name appears without establishing that the file was renamed.", "abstract": "A different terminal view can change how the same stored name appears without establishing that the file was renamed.", "articleBody": "Source facts\nAzure NetApp Files uses C.UTF-8 as its default volume language, and the source says the volume-language setting cannot currently be changed.\nRemote connection tools using different encodings can display the same stored filename differently. The source also distinguishes NFSv3, which does not enforce UTF encoding on names, from NFSv4.x, which enforces UTF-8. A rejected or unexpected name therefore needs protocol and client context. Microsoft Learn.\nApplicability\nIdentify the affected volume, exact file, access protocol, client locale, terminal encoding, and display font. Keep the filename investigation separate from the encoding of the file’s contents. Preserve the original object before any conversion or rename experiment.\nDSE recommendation\nDSE recommends reproducing the display difference with the same object through a known client configuration. Ask the application owner which characters and access paths must work, then test a nonsensitive representative name. Avoid treating a screenshot alone as permission to normalize or replace production names; first establish whether the discrepancy is in display, input, or stored data.\nVerification\nCompare the object through the intended clients and record the protocol and encoding used for each observation. Test listing and exact-name access without modifying the production object. If a rename is later approved, verify dependent application references separately and retain a reversible mapping of the original and replacement names.\nOfficial references\nMicrosoft Learn: Understand volume languages in Azure NetApp Files. Source retrieved September 9, 2026.", "datePublished": "2026-09-10T00:25:41+00:00", "dateModified": "2026-09-10T02:01:56+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-375-check-the-client-encoding-before-renaming-an-unfamiliar-netapp-filename/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260909-375-check-the-client-encoding-before-renaming-an-unfamiliar-netapp-filename/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Check the client encoding before renaming an unfamiliar NetApp filename" }, "articleSection": [ "Business Continuity", "IT" ], "keywords": [ "Business Continuity", "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 230, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Understand volume languages in Azure NetApp Files | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/azure-netapp-files/understand-volume-languages" } } ] } }