What's new
Carbonite

South Africa's Top Online Tech Classifieds!
Register a free account today to become a member! (No Under 18's)
Home of C.U.D.

Seagate SRN04D unable to map NAS in windows

KangarooMike

Well Known Member
Rating - 100%
21   0   0
Joined
Dec 5, 2015
Messages
184
Reaction score
31
Points
2,135
Location
Edenvale
I have had this Seagate Business Storage 4-bay NAS for 2 years now and I have been struggling to get it working.

I get to the point where I can log in via a web browser and on one attempt I got it working using FTP but I was never able to get it to work as a mapped drive.

Link to the Seagate

In the manual it states the following

4 Insert the DVD.
a. Windows: The installation wizard opens automatically.
Windows 7: Click Run Setup.exe in the AutoPlay window.
NOTE: If the installation does not begin automatically, launch it manually
by clicking Start and then Run (Windows). Type d:\setup.exe when the
Run dialog box displays (where “d” is the drive letter of your computer’s
CD drive). For Windows 7, click Start > Computer > Devices with
Removable Storage > BlackArmor.
b. Follow the on-screen instructions to complete the installation.
Install both Discovery and Backup software unless you are
already using another backup software program.
c. Open Discovery by double-clicking the icon on your desktop
(Windows) or in your Applications folder (Mac).

Seeing as I bought this nas used I did not get the CD with the software on it. I feel like this is the missing link that I need but if anyone know how I can get this nas as a mapped drive that would be great

Volumes

Shared folders

Shared folder permissions

I have tried to add it using the following in CMD but I get this error

C:\Users\Alder-Lake>net use Z: \\192.168.1.68\NASS
System error 384 has occurred.

You can't connect to the file share because it's not secure. This share requires the obsolete SMB1 protocol, which is unsafe and could expose your system to attack.
Your system requires SMB2 or higher. For more info on resolving this issue, see: SMBv1 is not installed by default in Windows 10 version 1709, Windows Server version 1709 and later versions
 
Last edited:
So it turns out when I actually try I can fix stuff

What I did was go into programs and features then enable SMB1

I then restarted and tried to map it again and hey presto! It worked

Kinda embarrassing that it took me 2 years to do that
 
SMB 1 is off by default as its a security risk. :) Make sure that NAS is running the lastest firmware. Backup critical data before doing the firmware upgrade.
 

Users who are viewing this thread

Latest posts

Back
Top Bottom