System not recognized in Windows connection

Adding something to the hosts file does not make it show up in the Network Neighborhood.  But it allows you to use that name when using Windows Explorer to open a device when you specify the new name in an Explorer address bar or assign a drive letter to a device as well as use it with NET USE in a command prompt.

So now try net use j: \\NewName\data /u:admin $#dI>ccOD30g^&wr.

---

Digital999 wrote:

Added the following to the hosts file...

192.168.0.232 NewName

 

Reboot and NewName did not show up during the Network Browse.  Only the existing name of the NETGEAR device which in turn results in an error message.It 

It is very easy to add one or more NAS shares as a network location in file explorer.  Just right-click in the main file explorer pane, and you will see the option. 

It is also very easy to add a desktop shortcut that opens a file explorer pane for the NAS.  Just right-click on the desktop, select "New", and then "shortcut".  Then enter \\192.168.0.232 as the location.  (Or \\nas-name if you get the hosts file working).

IMO both of these options are more convenient than using the Network Browse.  If the NAS IP address is fixed (either static or reserved), then you can forget about the hosts file, since no one will need to remember the NAS IP address once the shortcuts and locations are set up.

Used your suggestion -- cmd response indicated below.

C:\Windows\System32>net use j: \\NewNzz\data /u:admin $#dI>ccOD30g^&wr
System error 85 has occurred.

The local device name is already in use.

The name NewNzz was an arbitrary name selected and never used before.

Same error as other occurrences.

---

Digital999 wrote:

Used your suggestion -- cmd response indicated below.

 

C:\Windows\System32>net use j: \\NewNzz\data /u:admin $#dI>ccOD30g^&wr
System error 85 has occurred.

The local device name is already in use.

 

The name NewNzz was an arbitrary name selected and never used before.

Same error as other occurrences.

 

---

Try net use * /d /y first.

Maybe also try ping NewNZZ - that will see if the PC can resolve the correct host address

Never thought of ping..

ping works on other LAN devices as would be expected

ping works on the NETGEAR IP address as would be expected

ping works on the NETGEAR device name (??) -- sort of a surprise

Using the Windows GUI the NETGEAR device does not display -- see prior error messages.

As I have mentioned we focus on making and selling widgets not technology.  Consequently one of the overriding characteristics of any systems we deploy is that then must be managed by the GUI interface of that device.  No command lines, no ssh -- just the device GUI. 

It is my view that we should stop this thread and consider the issue as unresolved. 

I appreciate your help and Sandshark's help but at this point I am putting together a RFP for a bunch of Synology devices. 

As the Snyology NAS units are deployed we will be selling the NETGEAR devices.  We have almost 19 left and they are available for anyone who wants them at bargain prices so I do not have to turn to eBay. 

Your issue is a Windows one, not a ReadyNAS one, but you are refusing to accept that.  In addition, I believe much of it is of your own making, but I can't tell for sure just what it is because you keep resisting our efforts to determine that. If I'm diagnosing right, it's not really even a "Windows Problem" per se, it's just a lack of knowing how Windows works (and sometimes doesn't work as you'd like/expect it to). Nonetheless, we are trying to help you.  If you search the Synology forum, you will find similar issues reported.

Once we use the command prompt to figure out what causes the problem, we can likely tell you how to fix it such that you don't continue to have to use it.  But the GUI does not give the tools necessary to do the diagnosis.

This is my diagnosis so far:  You have mapped multiple drives on the ReadyNAS using either one or two sets of credentials, which are not the Windows user's credentials or NAS admin credentials, and you are trying to access the NAS with those credentials.  That makes it two sets of credentials for the same device, whihc simply is not allowed by Windows -- it has nothing at all to do with the ReadyNAS.  You have not done the same on the Synology, so you don't yet have the problem there.

And this is the basis of my diagnosis:  Your error message is that the device name is already in use (how you have interpreted that to mean it may be misspelled, I have no idea).  Your NET USE command shows that both the NAS name and IP are, in fact, in use in drive mappings.  I assume that's from network mappings you've made using the options to map using a different account and the checkbox to remember it (thus, it's of your own making).   I do not know if you are using the same credentials for those mappings, but it's pretty clear that it's not the Windows user's credentials (which are presented automatically when you type the share name into the Windows Explorer address window) or NAS admin account (which you used in a NET USE mapping) since your attempts to use those credentials now fail.  Whether the credentials for the mappings by IP and by name are the same or different from each other, I do not know, but we have a way to find out.  The message Windows gives when you try to use a second set of credentials to access a device that's already connected (aka In use) is exactly the one you are getting. 

I would still like to see what happens when you clear out all the existing connections.  I believe it will make your new connection work and will be the next pointer to the root cause.  This is what you can do next to better diagnose the problem.  If you've already run the command to delete the existing connections, re-boot to re-establish them.  Then, enter this command in the windows CMD prompt for each mapped drive:  wmic netuse where LocalName="M:" get UserName /value.  Run it for M, then replace M with each of the drives in the NET USE list and post the results here.  If you are concerned about the user name given being posted publicly, you can replace it with something generic.  But use the same generic name for each instance of the real one.  E.G., replace every instance of "Tom" with "Jerry".

While you are not a technology company, expecting technology to "run itself" is a naïve position.  When your whole IT infrastructure comes tumbling down and you can't fix it because you have no idea how it works and you cannot conduct business as usual, you will wish you'd learned more about it.  If you choose not to learn yourself, there are consultants who can help.  Unfortunately, many are not willing to work with what you have, so you may have to replace some of the hardware (the ReadyNAS likely being one, since it's no longer supported by Netgear).  Trust me that it's far cheaper than calling in a "strike team" to fix a major problem while your employees' productivity is reduced but they are still getting paid.

Thank you for you long reply. 

Most likely you are correct -- there is some Windows related problem.  That said, the Synology NAS units that are on the same network(s) do not exhibit this problem.  More importantly, on the rare occasion that we need Synology technical support it is readily available and at very modest cost.  Quite frankly I do not care whose problem it is, I just want it fixed.

We make widgets and occasionally have to deal with some technology and related problems.  We have offices across the nation that use these systems.  These offices also have heating systems and telephone systems.  Our expectation is that they work and that we can find local vendors that will fix/upgrade/refurbish those systems when they break.

In the 1980s it was necessary to have specialized technology folks for networking and computer installation.  Forty years latter my expectation is that this type of specialized support is no longer required.  Think about your automobile -- you just use it.  The notion that you should understand all of the interdependence and technical issues with that vehicle went away in the 1950s -- about 40 years after the mass market adoption in the early 1930s.

You hit on the critical issue -- finding specialized consultants who can deal with NETGEAR related problems.  We have found none and that is to be expected since the product is no longer sold or supported.  The economics are in favor of discarding the obsolete merchandise and replacing with more modern merchandise that can be configured and managed with a reasonable GUI interface. 

If I am correct, you simply haven't seen the problem on the Synology connections because you've not (yet?) done the same thing on them that Windows simply does not allow.  And if I'm correct, there is an easy fix.  But I need the information I'm asking for to know I am correct and give you precise instructions on how to fix it.

Thank you for your reply.   I certainly apprediate your generous offer to continue helping me. 

We are expecting a shipment of Synology units today.  When we configure and install them I will report back if the problem is occurring.

I appreciate your offer -- give me several days to have some of them configured. 

I believe the problem is related to your drive mappings.  If I am correct and you do them the same way on the Synology, you will experience the same issue.  But if you do them differently (do what I am trying to help you change), then  you will not.

Due to lack of support, you most likely were going to eventually need to retire the ReadyNAS.  Feel free to use this as your excuse.

Thanks again for your reply.  FYI, I do not need an excuse -- have adequate budget and I am able to call the shots,

We have nine units being delivered today.  By Monday I will know if the problem appears with the new units.. 

Have an RFP for 30 additional units in the future as ReadyNAS replacements.

Chat next week.. 

We did not need to wait for several days to determine the results. 

Took the new Synology test system, installed drives, set up storage pools, etc.  Let it do 'long' format of two RAID 1 volumes.

Established several directories for testing.

Windows recognized the device with a FileManager browse approach without any error messages.  I was able to map network drives from any of our workstations to the directories that were set up. 

The READYNAS system is still on the same network and throws the same error ...

        "Windows cannot access \\READYNAS"

        "Check the spelling of the name"

None of the workstations on the network can access the READYNAS system -- same error message.   

My former characterization was that the READYNAS has contaminated the network -- at least it is not available to any workstations with the FileManager browse process. 

I certainly do not understand the underlying issue but this approach gets us back to making and selling widgets.

---

Digital999 wrote:

 

the READYNAS has contaminated the network 

 

---

No idea what you mean by "contaminated".   They are not bringing down the network or interfering with access generally.

What clearly has happened is that the ReadyNAS hostnames aren't being resolved by the PCs.  We don't know why that is happening, but with more effort we could maybe sort it out.  But since you are ok just taking them out of service, we could just stop now.

As an aside - do you have a backup plan in place for the Synologies?  You could potentially repurpose the ReadyNAS as backup devices.  The PC issue you ran into won't prevent their use for Synology->ReadyNAS backups.

"Contaminated" was my term -- meant to refer to the fact that workstations that used to work properly all started to fail with trying to access the  ReadyNAS with the FileManager browse and mapped drives.  This is definitely impacting system performance and file access from the existing workstations.  Possibly incorrect terminology but seemed to capture the essence of the issue. 

You are correct, the ReadyNAS systems could be used for backup except Rsynch does not work as an exposed application in the Synology system.  They have their own approach entitled "Active Backup for Business".  I have Rysync working from the ReadyNAS system as a 'pull' service.  It does work but it is clearly a work around.

That said, here is the list of my priorities...

   System capability that integrates with our software and processes -- make and sell widgets

   Systems that can be maintained by others in various locations -- availability of skilled personnel

   GUI for management -- helps average non technical folks to maintenance and understand the system

    Product life with a future

The  unfortunate fact is that the Netgear systems fails on four out of the four criteria listed. 

As far as I am concerned this thread should close -- no actual resolution but an interesting discussion that others may be interested in. 

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.