LoginSignup

Connect NetDrive 3 with Zata.ai

A comprehensive, step-by-step guide to mount your Zata.ai object storage as a local drive using NetDrive 3 on macOS and Windows.

Overview

This guide helps teams using Zata.ai (S3-compatible storage) set up NetDrive 3 for seamless drag-and-drop file access through Finder/Explorer and desktop applications.

Tested with: NetDrive v3.5.251 (macOS & Windows)

Prerequisites

Before you begin, ensure you have:

  • Zata S3 credentials: Access Key ID and Secret Access Key

  • Zata endpoint: https://idr01.zata.ai (Central India region)

  • Bucket name (optional but recommended): e.g., my-team-backups

  • NetDrive 3 installed: Version 3.x for macOS or Windows

  • Network access: Outbound HTTPS (TCP 443) to your Zata endpoint

  • Correct system time: Significant time drift can break S3 authentication

Tip: If your account has restricted bucket listing permissions, prepare to enter a specific bucket name during setup.

Step 1: Install NetDrive 3

Download NetDrive 3

Visit the official NetDrive download page to get the latest version.

Windows Installation

  1. Download and run the NetDrive 3 installer

  2. Complete the installation process following the setup wizard

  1. Launch NetDrive

  2. If prompted, allow NetDrive through Windows Defender Firewall for private networks

macOS Installation

  1. Download the NetDrive 3 installer for macOS

  2. Install the application

  3. Open NetDrive from Applications folder

Step 2: Create New S3-Compatible Connection

  1. In NetDrive, click the green + button (Add New Drive) as shown in the interface

  1. You'll see the "Add a Personal Drive" configuration screen

  2. Storage type: Select S3 from the dropdown menu

  3. Label: Enter a descriptive name (e.g., Zata)

Note: On macOS, NetDrive mounts drives under Locations in Finder sidebar. On Windows, you can assign a specific drive letter.

Step 3: Configure Connection Details

Fill in the S3 account configuration form with these exact values:

Account Settings

  • Server Address: idr01.zata.ai (without https://)

  • Access ID: Enter your Zata Access Key ID (e.g., DKQLR6NUF7IYG6SFQSU0)

  • Secret Key: Enter your Zata Secret Access Key

  • Save account ID and secret key (recommended)

For Limited Bucket Access

If you have restricted permissions:

  • Bucket name: Enter your specific bucket name (e.g., my-team-backups)

Network Settings

  • Click PROXY SETTINGS if you need to configure proxy settings for your network

Important: Make sure to use the exact server address idr01.zata.ai for Central India region without the https:// prefix.

Step 4: Advanced Configuration

Before connecting, ensure these critical settings are configured:

  • Use HTTPS (SSL/TLS): ON

  • Force path-style addressing: ON (prevents SSL certificate issues)

  • Port: 443

  • Region: CentralIndia (case-sensitive)

  • Signature: V4

  • Connect at login/Mount at boot: ON (optional)

  • Background transfer: ON (recommended)

Click CONNECT to mount the drive.

Step 5: Verify the Connection

  1. Open the mounted Zata drive in Finder (macOS) or Explorer (Windows)

  2. Create a test folder (e.g., netdrive-test)

  3. Copy a small test file into the folder

  4. Verify the file appears in your Zata bucket using your preferred S3 tool

Troubleshooting

Authentication Issues

Problem: SignatureDoesNotMatch or authentication failures

Solutions:

  • Verify Signature is set to V4

  • Enable Force path-style addressing

  • Double-check endpoint URL, Access Key, and Secret Key (no trailing spaces)

  • Ensure system date/time is accurate with automatic sync enabled

  • Verify bucket name spelling and case if specified

SSL/Certificate Issues

Problem: SSL or hostname mismatch errors

Solutions:

  • Keep HTTPS enabled

  • Use the exact Zata endpoint: idr01.zata.ai

  • Ensure Force path-style is ON

Bucket Access Issues

Problem: Can't list buckets or see empty bucket list

Solutions:

  • Your access key may lack ListAllMyBuckets permission

  • Enter the bucket name explicitly in the connection settings

  • Reconnect after specifying the bucket

Problem: 403 AccessDenied errors

Solutions:

  • Check bucket permissions and policies for your access key

  • Verify you're connecting to the correct bucket and account

  • Ensure your key has necessary permissions (list/get/put/delete)

Performance Issues

Problem: Slow file operations (rename/move/copy)

Solutions:

  • Enable background transfer in NetDrive settings

  • Break large file operations into smaller batches

  • For bulk uploads, consider using dedicated tools like rclone, then use NetDrive for daily operations

Security Best Practices

  • Principle of least privilege: Create access keys limited to required buckets and actions

  • Regular key rotation: Update and revoke old access keys periodically

  • Always use HTTPS: Never disable SSL/TLS encryption

  • Restrict access: Limit key usage to authorized machines only

Configuration Summary

Here's a complete example of the settings (replace with your actual values):

textStorage type: S3
Server address: idr01.zata.ai
Access Key ID: DKQLR6NUF7IYG6SFQSU0
Secret Access Key: ************************
Region: CentralIndia
Signature: V4
Bucket: my-team-backups
Use HTTPS: ON
Force path-style URL: ON
Port: 443
Connect at login: ON
Background transfer: ON

Success! You should now have Zata storage mounted as a local drive, accessible through your system's file manager for seamless file operations.

PreviousConnect Vembu Backup with Zata.aiNextConnect GoodSync with Zata.ai

Last updated