UNC path requirements

A UNC (Universal Naming Convention) path is a network path format that lets you access shared folders and files on remote computers over a network. Understanding UNC path requirements helps you avoid common connection setup issues when configuring file share connections in Fusion Machine Connect.

Forbidden UNC paths

Forbidden UNC paths are technically valid paths that are blocked for security reasons. These paths point to sensitive or administrative areas that should not be accessed through file transfer or automation tools.

Examples of forbidden UNC paths:

• \\localhost\c$
• \\server\admin$
• Any share name ending with a $ (indicating a hidden administrative share)

These paths are blocked to prevent unauthorized access to system drives or internal resources.

To resolve issues with forbidden UNC paths:

• Avoid using hidden or administrative shares (those ending in $) or local-only references like \\localhost.
• Use a regular shared folder that has been explicitly created and granted appropriate permissions. Example: \\servername\sharedfolder.
• If you need to access local files via UNC, create a non-hidden share on your local machine.
• Check with your IT administrator if you're unsure which paths are allowed or need access to a specific location.

Invalid UNC paths

Invalid UNC paths are file or folder paths that don't follow the correct format or contain unsupported elements. These paths may be rejected because they are incomplete, incorrectly structured, or contain characters that are not allowed.

Examples of invalid UNC paths:

• \\ (missing server and share name)
• \\server (missing share name)
• \server\share (contains single backslash instead of double backslash)
• \\server\share. (contains trailing dots or spaces)
• \\server\*share (contains invalid character *)
• C:\folder (local path, not UNC)

To resolve issues with invalid UNC paths:

• Use a complete UNC path that starts with \\, followed by a valid server name and share name. Example: \\server\share.
• Don't use special characters such as ", /, :, |, <, >, *, or ? in the path.
• Don't use any path section ending with dots (.) or spaces.