- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Re: Cannot connect to ReadyNAS with windows 10
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am not able to connect to a new 524X NAS through Windows 10 pro File Explorer.
I CAN connect to the unit through laptop runnning Windows 7.
Here's my details:
NAS firmware = 6.9.3
NAS IP address = 192.168.28.222
Worstation IP address = 192.168.28.151
wokrgroup = WORKGROUP (for both NAS & workstation)
SMB is enabled.
I can see the NAS with RAIRar.
I can access the front screen through Chrome.
Here is the strange part, I have an older ReadyNAS 3100 on the same LAN which has a workgroup setting = WE. I can see the older model on the same workstation that I am trying to access the new NAS from.
Any though on where to look would be greatly appriciated. Thanks!
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Retired_Member wrote:
That works, but I would like to be able to type the name of the NAS into the address bar of file explorer --> \\NAS_Name
Yes. The commands were to make sure that SMB could access the NAS.
The next step is to add NAS credentials into the Windows Credential Manager ( https://support.microsoft.com/en-us/help/4026814/windows-accessing-credential-manager )
You need to add a "windows credential" for NAS_Name, not "web credential". That credential can use the NAS admin account, or you can create a NAS user account to use if you prefer. If you like, you can enter a credential for the NAS IP address also.
Once you've done that, and rebooted the PC, \\NAS_Name should work properly.
All Replies
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Cannot connect to ReadyNAS with windows 10
What happens if you open CMD (command prompt) and enter
net use * /delete
net use t: \\192.168.28.222\data /user:admin nas-admin-password
using the real nas admin password of course. If you use flexraid, substitute your data volume name for data. Be careful about spaces and the slash direction
The first command terminates any open network sessions; the second attempts to mount the NAS data volume as drive letter T.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Cannot connect to ReadyNAS with windows 10
Now I have a "t:" drive maped to the new NAS.
That works, but I would like to be able to type the name of the NAS into the address bar of file explorer --> \\NAS_Name
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Retired_Member wrote:
That works, but I would like to be able to type the name of the NAS into the address bar of file explorer --> \\NAS_Name
Yes. The commands were to make sure that SMB could access the NAS.
The next step is to add NAS credentials into the Windows Credential Manager ( https://support.microsoft.com/en-us/help/4026814/windows-accessing-credential-manager )
You need to add a "windows credential" for NAS_Name, not "web credential". That credential can use the NAS admin account, or you can create a NAS user account to use if you prefer. If you like, you can enter a credential for the NAS IP address also.
Once you've done that, and rebooted the PC, \\NAS_Name should work properly.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Cannot connect to ReadyNAS with windows 10
That fixed it thanks! (and FYI: I didn't need to reboot the PC)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Cannot connect to ReadyNAS with windows 10
@Retired_Member wrote:
(and FYI: I didn't need to reboot the PC)
That's not always needed. Though rebooting the PC does ensure that the NAS is using the newly-entered credential and also prevents any collision with the admin credential that you used when mounting the data volume.
I'm glad you are up and running again.