Windows explorer & server on network

mushtafa

mushtafa

mushtafa

Soldato
Joined
17 May 2013
Posts
2,973
Location
West Sussex, UK
I have a server running unraid with multiple shares setup.

Since a new install of Windows 10, it's not behaving correctly. It seems 50/50 if it's going to work or not.
When it does work, I have the server listed under Network in Windows Explorer and can navigate the shares. I also have two network drives mapped which work as they should.

When it doesn't work the server isn't shown in Windows Explorer. The mapped drives do not work. I get error 'Windows cannot access \\xxxxxx' '0x80070035'

If I use the run command and type the IP\share it works.

I've switched on SMB 1.0/CIFS File Sharing Support.

I've added the credentials of the share into Windows.

Any ideas please? I'm pretty sure it's an issue with the PC rather than the server
 
Rebooted the PC to check a BIOS setting to find it's now working properly again. I'm now sure it's a Windows problem
 
I certainly wouldn’t be enabling SMB1 on anything that’s for sure. unraid supports smb2.

Make sure you have the latest windows 10 20H2 update and remove SMB1.

Make sure you are accessing the shares via IP and not by domain names where possible so it cuts out the extra layer.

Has the unraid network card got a static ip ?

Can you ping the server up address after it drops the connection?

Have you set up usernames and passwords for the shares and have you got it remembered on the connection via the map drives?

you can write a script to test mapping of shared drives with also a disconnection script and just have this as a startup script in the start menu. Might be a bit more persistent then.

Can you show us a bit more about your network settings /configs?
 
1. I've now disabled SMB1 again.
2. Just checked and found the Windows update.
3. When right clicking the mapped drives and looking at 'Target' is shows name rather than IP. I'll see if I can change it.
4. Yes, unraid has a static IP
5. I didn't try a ping, I'll do that when it fails next.
6. I have a user and password set for the shares. I've added these details into the credentials of Windows.
7. I'll do some research regarding a script.
8. What network info do you need? The server is connected to my R8000p via ethernet and using a static IP. The PC is also connected to the same wireless router, also using a static IP.
 
1. You will need to enable “min SMB 2” share on the unraid server.

2. Great! Update all your machines.

3. It could be failing to resolve domain name (dns).

7. It’s just “net use Z: \\ipaddress\share” to map it and if you create the username and password the same as the PC you won’t need to add authentication details to the script. Yo disconnect the drive it’s just “net use Z: /delete”. These go into a text file and just save it as connect.bat and disconnect.bat (multiple shares) just add each share to a line in the file. Run them manually to see if they work before adding it to startup/shutdown stuff. Unless you want to map them manually anyway.

8. you have mentioned enough I bet it’s down to dns failing to resolve the server name.
 
Thanks for the info. At the moment the mapped drives are showing and working, but I'm unable to navigate through the rest of the server in the network part of explorer. I assume this has disappeared since disabling SMB1? Will I have to map all the individual shares?
 
mushtafa said:
Thanks for the info. At the moment the mapped drives are showing and working, but I'm unable to navigate through the rest of the server in the network part of explorer. I assume this has disappeared since disabling SMB1? Will I have to map all the individual shares?
Click to expand...

It’s probably down to disabling SMB1. You need to make sure on the unraid server SMB2 is enabled.

http://kmwoley.com/blog/tag/unraid/page/2/
 
You must log in or register to reply here.
Back
Top Bottom