Network drive issue
Author
Discussion

red_slr

Original Poster:

20,845 posts

219 months

Thursday 4th March 2021
quotequote all
I have been using the same network drive for about 10 years, never had an issue.
About 6 months ago it started failing to connect to the drive.
It was fine on other computers so pretty sure its not the drive but my PC thats the issue.

After a few weeks of faffing about I figured out a way to get it to connect reliably - once connected its fine till I reboot the PC.

This is what I have to do.

Open explorer
Remove the mapped drive.
Close explorer
Open another explorer
Open a different shared drive
Go back to "my pc"
Click map network drive
Put in the address of the network drive
Fails to find the drive
Press diagnose the problem
Whilst its running press cancel
Then press connect again and it connects straight away.
Works fine the rest of the day or till reboot.

Anyone got any ideas? Its doing my head in each morning having to do this process!!

Cheers!


Comacchio

1,544 posts

211 months

Thursday 4th March 2021
quotequote all
Open notepad and type the below, changing x for the drive letter of your choice.

Net use x: /delete
Net use x: \\enter\yourlocationhere /persistent:yes

Save to a convenient location and change the file extension to .bat

Double click on the new file - it should delete the mapped drive then remap it.

red_slr

Original Poster:

20,845 posts

219 months

Thursday 4th March 2021
quotequote all
Cheers will try that at lunch time and report back!

dapprman

2,786 posts

297 months

Thursday 4th March 2021
quotequote all
Is it a Netgear ReadyNas?
I set my old one up at my parents and had similar issues - when I went to log on to the NAS I found i couldn't and further research showed that the last version of SSL for that model was so out of date it was now considered a security risk and so was being rejected by all modern network software. This meant I could not SSH on to it and the cookies required for mounting persistence were failing - hence why I could mount with no problems but as the connection times out the remote drive would no longer be accessible.

red_slr

Original Poster:

20,845 posts

219 months

Thursday 4th March 2021
quotequote all
Comacchio said:
Open notepad and type the below, changing x for the drive letter of your choice.

Net use x: /delete
Net use x: \\enter\yourlocationhere /persistent:yes

Save to a convenient location and change the file extension to .bat

Double click on the new file - it should delete the mapped drive then remap it.
Edit..
Sorry I was wrong it did work!

Thanks very much <sends virtual beer!>

Edited by red_slr on Thursday 4th March 14:55

red_slr

Original Poster:

20,845 posts

219 months

Friday 5th March 2021
quotequote all
Spoke too soon that didn't work frown

I dont get it my other network drives are fine?

thebraketester

15,817 posts

168 months

Friday 5th March 2021
quotequote all
What drive is it?

red_slr

Original Poster:

20,845 posts

219 months

Friday 5th March 2021
quotequote all
Freecom 500gb network drive.

Its old, but its working fine for everyone else?


r-kid

850 posts

217 months

Friday 5th March 2021
quotequote all
Similar to what dapprman said, its likely a setting issue.

Likely your NAS is based on SMB1, which was disabled by default in a recent Windows 10 update. Check if SMB1 is disabled on your pc, enabling it again should enable you to reach the NAS again.

https://docs.microsoft.com/en-us/windows-server/st...

Open Control Panel in your PC/Notebook.
Click on Programs.
Click on Turn Windows features on or off link.
Expand the SMB 1.0/CIFS File Sharing Support option.
Check the SMB 1.0/CIFS Client option.
Click the OK button.

red_slr

Original Poster:

20,845 posts

219 months

Friday 5th March 2021
quotequote all
Thanks

I have

Automatic removal (ticked)
Client (ticked)
Server (unticked)


red_slr

Original Poster:

20,845 posts

219 months

Tuesday 9th March 2021
quotequote all
Anyone got any more ideas? Still scratching my head on this one

LordGrover

34,185 posts

242 months

Tuesday 9th March 2021
quotequote all
I think it's likely the samba issue above. No longer secure enough so has been blocked by Windows.
Replace with new.

red_slr

Original Poster:

20,845 posts

219 months

Tuesday 9th March 2021
quotequote all
But it does map though, so I can still access it - just have to faff every morning with it?
Is that still likely to be the same thing?

QuartzDad

2,995 posts

152 months

Tuesday 9th March 2021
quotequote all
Anything helpful in event viewer?

dapprman

2,786 posts

297 months

Tuesday 9th March 2021
quotequote all
red_slr said:
But it does map though, so I can still access it - just have to faff every morning with it?
Is that still likely to be the same thing?
It's the certificate that's the issue so mapping will work, reconnecting with out removing and re-adding it will fail.

red_slr

Original Poster:

20,845 posts

219 months

Tuesday 9th March 2021
quotequote all
dapprman said:
red_slr said:
But it does map though, so I can still access it - just have to faff every morning with it?
Is that still likely to be the same thing?
It's the certificate that's the issue so mapping will work, reconnecting with out removing and re-adding it will fail.
Ah ok cheers I get it now

red_slr

Original Poster:

20,845 posts

219 months

Tuesday 9th March 2021
quotequote all
QuartzDad said:
Anything helpful in event viewer?
Bit beyond my paygrade but will have a look tomorrow on boot up.

Whoozit

3,882 posts

299 months

Tuesday 9th March 2021
quotequote all
I had this issue with an old Netgear NAS. Some machines connected fine, others (brand new and old) didn't. What fixed it was clearing the cached credentials

https://www.top-password.com/blog/clear-saved-cred...