NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
System not recognized in Windows connection
Perfectly operational ReadyNAS 626 system as of one week ago. Installed and recognized for the past three years. Connected and operational on five different Windows workstations. RAIDar can...
Did you map all the drives using a combination of the IP address and network name, as you did on the ReadyNAS? (I expect not.) What credentials do you use in the mappings? Did they all use the same one? Are they the same as the user's Windows credentials? We never got to the point of figuring out what you've done for the ReadyNAS since you declined to do the steps that would have let us know.. I still don't believe you have a problem with the ReadyNAS. What you most likely have is a Windows problem created over time as you (probably not even aware of it) used different ID's and credentials for those mappings. Without you clearing the mappings and trying to connect without any Windows limitations possibly interfering, which you did not do, it's impossible to tell. Having started from scratch in the Synology, you've probably been more consistent and avoided the Windows limitations.
To answer Sandshark's last post and possibly help others...
Yes, I used the identical process to map the network drives to the Synology units as was used to map drives to the ReadyNAS units. No IP address, just system names and associated share/directory names. The configurations established years ago and have been static.
The credentials used were identical for all operations -- a Windows 11 account that used FileManager browse function and then mapped drive letters. No special credentials or any different credentials were used to my knowledge since the NAS accepted the login process once the NAS credentials were entered in the Windows challenge screen. After the initial workstation connection nobody changes anything -- stuff just works.
The ReadyNAS is still currently on the same network with unique name and IP address but not accessible from ANY of the attached workstations with a FileManagement browse. Synology NAS devices easily accessed with Windows tools. I do not care about the 'why' of the problem, just the fact of the problem. It all started to occur after the most recent Windows 11 update from all attached workstations.
The most difficult was to move the data from the Netgear to the Synology devices. If anyone is interested they can PM me for the details.
By all management measures the ReadyNAS device just stopped working unless specialized IP mapping processes were used in FileManagement connection. This approach is not acceptable for average users who only are concerned with making and selling widgets.
The information you provided before differs from what you say you did on the Synology. You showed a mix of IP address and name (I'm assuming TROUT-NAS is at 192.168.0.232 since you never provided that information).
We never got to the point of finding out whether or not you used all the same credentials with the ReadyNAS. What you did on the Synology is very much what I was going to try to get you to do on the ReadyNAS -- replacing your old mix.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
