When I try to open my my router-attached network drive, I get this error:
It was working just fine before, but I think I caused the problem. I was trying to fix something else, and followed the advice in this video:
But then after I discovered the network drive error, I then went back to the video and tried to undo what he said to do. But I can't open the network drive anymore. Does anyone know what to do to fix this issue? Thank you
If you did not backup your registry changes, and do not have a system backup image , try system restore to a point earlier than when you made the changes..
A bit of advice if you care to take it...always CYA when working in the registry or running scripts. Likewise, NEVER make such changes unless you know for sure they come from a reputable source....like @Brink tutorial section. Not only does he give fixes, he also gives a method to undo the changes if necessary.
While there are some knowledgeable youtube videos, be cautious because the so-called experts are a dime a dozen. You can not trust them all.
I use system images for my insurance. I've screwed up before or I was given bad advise so it's saved my bacon more than once. If I work in the registry, I always export any change I make so I can undo it.
I did actually image the hard drive after I got all my programs installed using clonezilla and redo rescue. So I do have that option to go back. It just seems like such an error would be fixable without having to resort to that?
Yes, I will not follow anymore questionable YouTube videos from Indian guys..
Go to File Explorer, click the arrow at the far left of the Address Bar and select Network from the drop-down. It’ll open network devices window and should prompt you to turn on File Sharing (yellow bar at the top, right below the address bar). Turn it on.
Good news, I was able to fix the issue! In addition to not being able to access the network drive, when I clicked on a computer on the network, it gave me the same error, but this time a specific error code, 1208. So I started googling for that error code. Somehow a thread on reddit came up (it didn't even mention the error code so I don't know why it came up) but someone in the thread said this:
Try in an admin powershell or wt (this will disable security features)
So I executed all three commands, rebooted, and voila, everything is working again. I don't know what caused the issue in the first place; it doesn't seem like the stuff mentioned in that video would have caused it, but it's working now.
