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...
Command prompt initiated in administrative mode.
I did not delete all existing mapped drive names but did pick a new drive letter for the new mapping...
****Cut 'n Paste from Command Prompt Below *****
C:\Windows\System32>net use
New connections will be remembered.
Status Local Remote Network
-------------------------------------------------------------------------------
OK L: \\TROUT-NAS\AccountingFiles
Microsoft Windows Network
OK M: \\TROUT-NAS\PLEX--Media Microsoft Windows Network
OK S: \\TROUT-NAS\SharedFiles Microsoft Windows Network
OK W: \\TROUT-NAS\IYF_DataFiles Microsoft Windows Network
OK X: \\192.168.0.232\MKV-Files Microsoft Windows Network
OK Y: \\192.168.0.232\WorkstationBackups
Microsoft Windows Network
OK \\192.168.0.232\IPC$ Microsoft Windows Network
The command completed successfully.
C:\Windows\System32>net use j: \\192.168.0.232\data /u:admin $#dI>ccOD30g^&wr
System error 85 has occurred.
The local device name is already in use.
******* End of Cut 'n Paste *************
Note some mapped drives to the ReadyNAS device exist because of FileManager access to the ReadyNAS device and subsequent remapping.
I did not delete all mapping as your command prompt suggested -- seemed to not be useful.
Note the IPC$ mapping -- do not know why/how it got there.
Apparently Windows thinks it is in use.
Further testing today indicates that the "ReadyNAS" device that prompts the error is not limited to a single workstation.
I have changed the device name and the device IP address. The problem follows the device for some reason.
The same error occurs on every workstation -- i.e. the Windows network is somehow 'contaminated'.
Other stuff works as expected.
From my limited knowledge of the Windows browse capability it seems like the 'master browser' workstation must keep pushing out some erroneous information to all the other workstations.
The puzzle is that the Synology NAS device(s) on the same network do not exhibit the same issue.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
