Solved Any advice welcome (1 Viewer)

DickyP

Active member
Local time
Today, 19:38
Joined
Apr 2, 2024
Messages
398
Any advice (polite and anatomically possible) about a weird problem. On one of PCs my mapping to my NAS has suddenly failed and I can't re-map it, whereas the other PCs (One Win 10 and one Win 11) no problems. I can still see the NAS on the other PC using a UNC path.

Given I normally use UNC paths in code the problem is survivable but annoying.

The NAS is a 4tb WD Cloud about 6 years old. Firmware is up to date

Any thoughts.
 
Don't have a lot of experience with NAS but I bought one for a charity client last year and didn't have any problems when it was installed on my computer. I hope you are not trying to share an Access db using the cloud feature.
 
It's attached directly my network as are all the PCs via ethernet connection. No cloud usage.
 
Is it mapped as the same device letter on all the PC's? Maybe if you uninstall the device from the network and start again? Just grasping at straws here.
 
Try shutting down EVERYTHING on the network and letting it come back up as though from a long-duration power failure. Wait at least 10 seconds, maybe 20 for snort & giggles before the restart, and see if everything comes back up.

You also noted that this was a hard-wired connection. Reseat the cables.

The CMD prompt (in admin mode) has access to the NET command and the NETSTAT command that you can use to find if any interface is throwing out errors at a higher rate than other interfaces. These days it is rare to have a network I/F fail on you, but maybe try to do the manual remap - which you say fails - and then check the system & device event logs to look for events logged at the time of the failure.
 
Had the same issue, turned out that the PC in question was running a VPN (wireguard). As soon as I disabled it, everything worked as before
 
Thanks - I'll have a look but as they are all mine and as I never installed a VPN I don't hold out much hope.
 
Thanks every for your help.

Of course the question now is why should something that's worked for 4 years in its current form suddenly stop working?
 
If it stopped working on a Wednesday, I'd vote for "Microsoft Tuesday Night patches" as the primary suspect.
 

Users who are viewing this thread

Back
Top Bottom