Network & NAS Headache

[Elixer]

What does the win 7 box show when you do net share & net view?

 

[Mr.Entenmann]

Net Share for the Win 7 box shows all the drives on the computer, and as for Net View shows nothing, instead crashes command prompt.

 

[Elixer]

Net Share for the Win 7 box shows all the drives on the computer, and as for Net Share doesn't show nothing, instead crashes command prompt.

Net view, or net share crashes?
What url do you see in file explorer when you are looking at files on the NAS?

 

[Mr.Entenmann]

I updated post #77 as I made a error
If I understand you correctly, the only url I see is the IP address of the NAS or //crex2cloud, that is only on the Windows 7 box which has no problems seeing the folders on the NAS. Obviously not the Window8 box that I want to have access to the NAS.

 

[Elixer]

I updated post #77 as I made a error
If I understand you correctly, the only url I see is the IP address of the NAS or //crex2cloud, that is only on the Windows 7 box which has no problems seeing the folders on the NAS. Obviously not the Window8 box that I want to have access to the NAS.

You mean \\crex2cloud correct?

OK, go to (on win 8 box):
Control Panel\User Accounts and Family Safety\Credential Manager
Then hit "Windows Credential"
Then go down and click "Add a Windows credential".
Enter \\crex2cloud for network address (the exact same name it shows in net view!) and fill in username and password, and hit OK.
See if it then works.
Note, if you already see that entry listed, delete it first, then do the above.

 

[Mr.Entenmann]

Nope, that didn't work

You mean \\crex2cloud correct?

OK, go to (on win 8 box):
Control Panel\User Accounts and Family Safety\Credential Manager
Then hit "Windows Credential"
Then go down and click "Add a Windows credential".
Enter \\crex2cloud for network address (the exact same name it shows in net view!) and fill in username and password, and hit OK.
See if it then works.
Note, if you already see that entry listed, delete it first, then do the above.

 

[Elixer]

What didn't work about it?

 

[Mr.Entenmann]

I added the NAS as a Windows Credential, created a login & pass, then I tried to map a drive on the NAS as a network drive and I got the same message as seen in the first image, of post #1.

What didn't work about it?

 

[Elixer]

What does this do now?
net use L: \\CREX2CLOUD\File_Collection
dir L:
net view

 

[Mr.Entenmann]

What does this do now?
net use L: \\CREX2CLOUD\File_Collection

The system cannot find the drive specified.

 

[Elixer]

The system cannot find the drive specified.

C&P the output of all those 3 commands...(you promised)

 

[386DX]

I added the NAS as a Windows Credential, created a login & pass, then I tried to map a drive on the NAS as a network drive and I got the same message as seen in the first image, of post #1.

You can't just create a login&pass it has to be one the WD can authenticate. Do the windows credentials again (delete old one create a new one) this time use the following as the login name

CREX2CLOUD\ADMIN

for the password you *MUST* use the password you use to get into the web interface.

Without mapping any drive letters you can test out your credentials by going into windows explorer and putting the following in the address bar:

\\CREX2CLOUD

You should be able to see entire content of the NAS.

 

[Mr.Entenmann]

Elixer - I did promise.

C:\WINDOWS\system32>net view L:\\crex2cloud\File_Collection
System error 53 has occurred.

The network path was not found.

386DX - I entered in \\crex2cloud in the windows explorer address bar and got the following error;

Network Error
Windows cannot access \\crex2cloud

 

[Elixer]

CWINDOWS\system32>net view L\crex2cloud\File_Collection
System error 53 has occurred.

The network path was not found

That is wrong again...
Look again what I wrote. 3 different lines.

Also, I do hope you entered the correct username & password for the NAS, as 386DX said?

 

[Mr.Entenmann]

Three different lines ? Is this what you mean;

C:\WINDOWS\system32>net view
Server Name Remark

---------------------------------------------------------------
\\PC-one
\\CREX2CLOUD Cloud EX2 Drive
The command completed successfully.


C:\WINDOWS\system32>L:\\crex2cloud\File_Collection
The system cannot find the drive specified.

Also, I do hope you entered the correct username & password for the NAS, as 386DX said?

Yes, I posted the negative results (post #88)

 

[Elixer]

Well, assuming you did everything correctly, and typed the username & password to what the NAS expects... I can't really do anything else from this end, would need to poke around your system, and try other stuff.
However, I don't think letting strangers into your system is a smart idea, so, I can't do much more than reiterate what I have said in this thread before, make sure you are typing everything in correctly, and it should be working.

 

[Mr.Entenmann]

I have done everything correctly. Anyone have any suggestions, otherwise, I will have to move this problem elsewhere.

I don't understand, I've had half a dozen people attempt to solve this, some threw there hands in the air, others admitted to the lack of knowledge of solving this problem. I've been told, I'll need a real network guru to solve this.

Thanks for your help, Elixer, what do you think it may be ?

 

[Elixer]

The main problem is, can't see real time feedback, so, doing this in a forum format is a PITA.
What I would usually tell people is, to just reinstall windows.
That would make sure you are working from a clean state, and is far easier to debug things that way.
Now, no idea what you have installed, what programs did to modify whatever and so on.

It shouldn't be any more difficult than it was setting up a NAS on windows 7, in fact, it should be the same.

 

[386DX]

Do the credentials again this time use the IP address instead of the CREX2CLOUD for both the hosts and username. Also 100% verify that you are adding this as a windows credential and not web credentials and make sure there isn't any saved credentials using the IP of the NAS.

 

[386DX]

One other you may try is in elevated command prompt run the following commands:

sc.exe config lanmanworkstation depend= bowser/mrxsmb10/mrxsmb20/nsi
sc.exe config mrxsmb20 start= auto

This enables SMB 2.0 and 3.0 support, Win 8.1 defaults to 3.02 for security and performance reasons but I suspect your NAS might not support SMB 3.02.

 

[Mr.Entenmann]

386DX

C:\WINDOWS\system32>sc.exe config lanmanworkstation depend=browser/mrxsmb10/mrxs
md20/nsi
[SC] ChangeServiceConfig FAILED 1059:

Circular service dependency was specified.


C:\WINDOWS\system32>sc.exe config mrxsmd20 start=auto
[SC] OpenService FAILED 1060:

The specified service does not exist as an installed service.

I am guaranteed adding the credientials as a windows credential

I tried using the IP as you suggested for the host and user name. When I enter in the IP with or without \\ all it does it connect me to the NAS control panel I would have never thought this was going to be that difficult, wow.

 

[Mr.Entenmann]

Here is an idea, if someone wants to team viewer, see the problem at hand, maybe then it will help this thread progress to hopefully a solution ?

 

[Lorne]

I am following this as well as I have a co worker who is going through the same problem with his Netgear ready nas 102 and windows 8.
It hooked through a netgear gigabit switch.
Cannot access it through file management what so ever and can only get to it through IE and direct IP access.
Cannot make any links or shares to it with the win8 machine, But 3 other hardwired computers ,2 pc with win7 and a laptop with XP do everything fine.

Its hard to work with him on making it work since its his home and getting feedback is bad.

 

[Mr.Entenmann]

I'm not the only one, whew This is probably a problem many may have experienced but didn't bother to solve.

Cannot access it through file management what so ever and can only get to it through IE and direct IP access.

You can access the control panel ?

 

[386DX]

It might be your NAS doesn't support secure negotiate that is default in windows 8 and up. In powershell (run as admin if needed) run the following command:

Set-ItemProperty -Path “HKLM:\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters” RequireSecureNegotiate -Value 0 -Force

If you are still having issues can you look in event viewer and see what error you are getting when you try to access the NAS shared.