SMB Shared Drive from Spectrum Scale on Microsof Windows OS

Important

  • These methods will only work if your computer is connected to the UTEP network or remotely via the UTEP VPN.
  • If you are connected to UTEP WiFi, you must also be connected to the UTEP VPN for this to work.
  • You will need to use your UTEP credentials to access the shared folder.

MS Windows instructions to connect to UTEP VPN if you are outside UTEP campus or in WiFi

Steps to Access an SMB Shared Folder on Windows

  1. Open File Explorer:

    • Click on the File Explorer icon in the taskbar or press Win + E. Open File Explorer

  2. Navigate to This PC:

    • In the File Explorer window, right click on This PC in the left-hand column. Navigate to This PC

  3. Map Network Drive:

    • At the top of the File Explorer window, click on the Map network drive button. Map Network Drive

  4. Choose a Drive Letter:

    • In the Map Network Drive window, choose an available drive letter from the dropdown menu. See figure in step 6.

  5. Enter the Folder Path:

    • In the Folder field, enter the path to the SMB share in the format \\rad.utep.edu\<sharename> (e.g., \\rad.utep.edu\WebGraphics). See figure in step 6.

  6. Reconnect at Sign-in:

    • Check the box labeled Reconnect at sign-in if you want Windows to automatically reconnect to the SMB share every time you log in. 4,5,6,7

  7. Finish:

    • Click the Finish button to establish the connection.
    • If prompted, enter your network credentials to complete the connection. Attempting to connect

  8. If error when trying to connect, go to step 4, else go to step 10: Error

  9. Go back to step 4 and mark "Connect using different credentials":

    • Check mark option "Connect using different credentials".
    • Click on finish.

    Connect using different credentials

  10. Access Shared Files:

    • The shared drive will now appear in your File Explorer under This PC, ready for you to access and use.

Tip

  • Ensure Network Connection: Make sure your computer is connected to the same network as the SMB share.
  • Enable SMB Feature: If you encounter issues, verify that the SMB feature is enabled in Windows Features.
  • Network Credentials: Keep your network credentials handy for a smooth connection process.

Note

  • This method will only work if your computer is connected to the UTEP network or remotely via the UTEP VPN.
  • If you are connected to UTEP WiFi, you must also be connected to the UTEP VPN for this to work.
  • Network Credentials: Keep your UTEP credentials handy for a smooth connection process.

Important

⚠️ Important: Correct Method for Moving Data into SMB Shared Drives (Spectrum Scale)

When transferring data into the SMB shared drive (Spectrum Scale), it is critical to follow the correct procedure to ensure that file and folder permissions are applied properly. Failure to do so can result in incorrect or missing permissions, especially on nested folders (cascade permissions).

❌ Do NOT Move Files Directly

Avoid using drag-and-drop move operations from Windows Explorer or command-line tools such as mv. Moving files in this way can bypass ACL inheritance, causing permission inconsistencies throughout subdirectories.

Always perform the transfer in two steps:

  1. Copy the data to the SMB shared drive.
  2. Verify the copy was successful.
  3. Delete the original source files afterward.

If using the command line, use the following command to preserve all attributes, timestamps, and permissions:

bash cp -a /path/to/source /path/to/destination

The -a flag (archive mode) ensures that ownership, permissions, and symbolic links are correctly preserved during the copy.

🧩 Why This Matters

Spectrum Scale uses specific ACL inheritance mechanisms for managing access control. Directly moving data from local or network sources may break the inheritance chain, leading to:

  • Files or folders becoming inaccessible to collaborators.
  • Lost or mismatched permission sets.
  • Issues with group-based access control.

By copying instead of moving, you ensure that all permissions cascade correctly within the SMB shared environment.