Connecting NAS - mapping of drives

Ok,

If you want, we can do a step by step troubleshooting of your current situation:

If you are able to ping your Machine and it responds.

Code:

Ping MachineName

Try to view if your NAS appears on the Network List:

Code:

Net view

If Your NAS appears on the list, try to view it:

Code:

Net View MachineName

The available shares will be listed there.

Then Try to List the content of one of the directories:

Code:

Dir \\MachineName\ShareName

This should list the content of the directory,

If all this works Try to map a drive on one share:

Code:

Net use Y: \\MachineName\ShareName

Pls reply with the "response" of the first "encounter" of a non positive output.

This exercise should reveal if you have a Network or Protocol or Cipher or Authentication problem.

OK ... step by step all worked.
I have now mapped the 2 volumes as Y & Z and can access the files on them

Any idea why the Command line would work yet the Easy Find Utility that has worked for years does not ?

Hey that's good news...

Honestly... Forget the utility and create a CMD that you can reuse at will...

Thanks for your help.

We say run the PNTP... "Plain Network Troubleshooting Process".

1st: No utilities involved. The aim is to get an error message during the step by step process...

But loll... It was a "Utility Program" problem...

You probably wont be able to use it in subsequent Windows versions. But still, as long as SMB1 will be available... You're ok.

sygnus21 said:

Yes...


The "My Cloud" drives are my NAS drives. Also note my NAS appears under Network.

Anyway, again my post was simply FYI. I wasn't saying you were wrong

Loll this part was not really meant for you... Sorry, I should be more specific on who my replies are addressed...

But most of the time, If I don't quote... I'm responding to the last Op's post. Note taken I'll try to be more precise

One thought ... I enabled SMB 1.0
Is there an easy way to tell if the NAS actually needs this enabled (other than simply disabling and trying to connect)

I know most sources advise SMB 1.0 should be disabled due to security vulnerability