{"version":"2.1.233","anchor":"network-path-detection-now-covers-net-automount-paths","canonical_anchor":"network-path-detection-now-covers-net-automount-paths","heading":"Network path detection now covers \/net automount paths","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233\/e\/network-path-detection-now-covers-net-automount-paths","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233","markdown":"### Network path detection now covers \/net automount paths\n\nAutomounted \/net paths now count as network paths for file reads, writes and attachments.\n\n**What**\n\nFile read, file write and attachment handling previously treated only UNC paths (`\\\\server\\share` or `\/\/server\/share`) as network paths. They now share one check that also recognises automounter paths of the form `\/net\/<host>\/...`, and the attachment error text says so.\n\n**Evidence**\n\n`is a network path (UNC or \/net autofs), which is not supported.`\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}