Can't map network drive from win11 to a NAS

This problem has been testing me and others for weeks. I can access the NAS via its own discovery software, ping, etc.. But when I try to add a network drive in file explorer, there are just no folders available to browse. The rest of the network is OK. Disabling security software, vpn, etc. has had no impact.

What I have found is that in Advanced Sharing Settings, Network Discovery is Off. If I switch it on, I then have a ticked box 'setting up network connected devices automatically'. The trouble is as soon as I move away from the page and return to it, Network Discovery has returned to its Off Position.

I've also noticed that services such as DNS and DNSCache are just not there.

Both of those may be red herrings as I'm woriking at my competence limit.

Can anyone help. Good news is the rest of the pc is working and I have an update back-up with system image

Many thanks

How old is the NAS? If it is older you may need to enable SMB v1 to access the file structure

Tx for the reply. SMB 1 is enabled

Tx. Unfortunately it fails at Step2. I don’t have DNS Client Service showing on the console

Open the Run dialog box using the Windows key + R combination.

Input MSConfig in the Run dialog box and click on the OK button.

Switch to the Services tab and find the DNS client option from the list.

Enable the DNS client service by marking the checkbox to the left of the service.

What happens when you disable Firewall?

You cannot ping the NAS could mean NAS not configured correctly.

I had a similar problem with a Buffalo NAS, this article from PC World helped me .

Thanks all for the suggestions. Just to reaffirm the main points and a couple of extras :

- I can successfully ping the NAS.
- I've tried with and without firewalls, antivirus, VPN, etc - no success
- DNS Client and DNS Cache just aren't showing at all on the list of services so I can't enable them.
- SMB1 is enabled.
- It has alway been a Win11 pc (12 months old) and, until a few weeks ago, I could set up and access network drives from the NAS.
-The pc has auto-update on for all software

I'm wondering if the lack of DNS Client and DNS Cache services, and anything else that should be there but isn't, is the start of the problem. If so, what is the best way to overcome this.

It would help to know what type of NAS you have -- Windows, Self built with a standard Linux distro, a QNAP device etc.

If non Windows is SAMBA enabled / installed on the NAS. Often a good (but not essential) app to have running at start up.

Another thing to try is to install both on Windows and the NAS the client part of Filezilla (free)

Filezilla has identical GUI on Linux (NAS type servers usually) and Windows and is an excellent file transfer program too.



Then if you know the IP address of the server (which you must since you can ping it) try and reach the files on it FROM Windows using the filezilla GUI ( sftp://NAS IP address, your user account on the NAS, password, then choose quick connect.

If no files are shown then NAS set up is incorrect. Note though check that NAS and Windows machine have same workgroup name i.e belong to the same work group otherwise you will have problems.

From the NAS can you Ping the windows machine. From the console also you can get the currently assigned IP address of the NAS by typing ip -c a or ifconfig depending on the actual OS on the NAS. Presumably you have some type of command console on the NAS that you can access. Ensure also the SSH service is enabled on the NAS. With Linux type OS'es I don't like "Auto update" as things can change and settings get altered.

(On Windows -- ensure the OPENSSH client is enabled and started-- that's usually by default but check in services - and t's often good to install from the "add optional features" in Windows the openSSH server and start it too).

cheers
jimbo

RobFJ said:

DNS Client and DNS Cache just aren't showing at all on the list of services so I can't enable them......

I'm wondering if the lack of DNS Client and DNS Cache services, and anything else that should be there but isn't, is the start of the problem. If so, what is the best way to overcome this.

Click to expand...

DNS Client shouldn't be missing in Services.
What happens if you open an admin command prompt and type net start dnscache ?

Bree said:

DNS Client shouldn't be missing in Services.
What happens if you open an admin command prompt and type net start dnscache ?

Click to expand...

I just get the message 'The Service Name is invalid"

jimbo45 said:

It would help to know what type of NAS you have -- Windows, Self built with a standard Linux distro, a QNAP device etc.

I

Click to expand...

Tx for the reply

The NAS is a QNAP, TS509.

QNAP has remotely tested it and are satisfied that it is working as it should and is configured correctly.

I'll try the other suggestions - if my tech ability and understanding lets me :)

RobFJ said:

Tx for the reply

The NAS is a QNAP, TS509.

QNAP has remotely tested it and are satisfied that it is working as it should and is configured correctly.

I'll try the other suggestions - if my tech ability and understanding lets me :)

Click to expand...

Hi there

@RobFJ

provided you can get a keyboard / monitor connected try working through this document. The OS seems quite a basic Linux type thing with some proprietary stuff but things like SAMBA, FTP etc are all available and "installable". My only remark is that it seems seems quite an expensive bit of kit for what it does but that's another issue.


Cheers
jimbo

RobFJ said:

I just get the message 'The Service Name is invalid"

Click to expand...

Your system may have become corrupted. Try running the command dism /online /cleanup-image /RestoreHealth in an admin command prompt, followed by the command sfc /ScanNow

Bree said:

Your system may have become corrupted. Try running the command dism /online /cleanup-image /RestoreHealth in an admin command prompt, followed by the command sfc /ScanNow

Repair Windows Image Component Store in Windows 11 Tutorial

This tutorial will show you how to repair Windows image component store corruption in Windows 11. If a Windows image becomes unserviceable, you can use the DISM (Deployment Imaging and Servicing Management) tool or Repair-WindowsImage cmdlet to update the files and correct the problem. For...

www.elevenforum.com

Use System File Checker (SFC) to Repair System Files in Windows 11 Tutorial

This tutorial will show you how to run the System File Checker (SFC) tool to repair missing, corrupted, and modified system files in Windows 10 and Windows 11. System File Checker (SFC) is a tool built into Windows that will check for system file corruption. The SFC /SCANNOW command scans and...

www.elevenforum.com

Click to expand...

Hi there
There's usually several ways of fixing things -- however since the NAS "Seems" 99.9% OK I'd test it at that end first -- if it can ping the windows machine and the user can log on to the NAS then that IMO is the time to start looking at the windows end. Until one of the ends is 100% working changing anything at the other end is just going to be a lottery.

For most people Windows is surprisingly hard to get corrupted -- in spite of what people say especially if you are using reasonably stable releases !!!! I'd be surprised if Windows was that corrupted, however it's an easy thing to run that command.

In the end an old restore of windows or a brand new clean install might be the only solution. I assume there's no problem with the router, ISP network connections (dynamic IP addresses, changing to 100% Ipv6 etc etc).

Cheers
jimbo

jimbo45 said:

There's usually several ways of fixing things -- however since the NAS "Seems" 99.9% OK I'd test it at that end first -- if it can ping the windows machine and the user can log on to the NAS then that IMO is the time to start looking at the windows end. Until one of the ends is 100% working changing anything at the other end is just going to be a lottery.

Click to expand...

The OP reports that they have no DNS Cache service listed in Services. This should not happen.

Bree said:

What happens if you open an admin command prompt and type net start dnscache ?

Click to expand...

RobFJ said:

I just get the message 'The Service Name is invalid"

Click to expand...

This should not happen either. It does look like the problem is at the PC end, not the NAS.

Bree said:

The OP has no DNS Cache service listed in Services. This should not happen.



This should not happen either. It does look like the problem is at the PC end, not the NAS.

Click to expand...

probably true -- It's just I prefer to ensure at least one end is `100% working before messing around with the other end. !!

Cheers
jimbo

Bree said:

Your system may have become corrupted. Try running the command dism /online /cleanup-image /RestoreHealth in an admin command prompt, followed by the command sfc /ScanNow

Click to expand...

Tx for the suggestion. Running the first command resulted in a 'successfully repaired' result (but no indication of what was done) and the second identified 3 corrupt but potentially unimportant drivers like modem. Unfortunately I've still got the problem.

I'll try pinging my pc from the NAS to rule that issue out (or in) but I can't seem to find a way to do it. Can someone help.

Many thanks

RobFJ said:

Tx for the suggestion. Running the first command resulted in a 'successfully repaired' result (but no indication of what was done) and the second identified 3 corrupt but potentially unimportant drivers like modem. Unfortunately I've still got the problem.

I'll try pinging my pc from the NAS to rule that issue out (or in) but I can't seem to find a way to do it. Can someone help.

Many thanks

Click to expand...

Hi there
1) Get the IP address of your Windows machine (from Windows) == type ipconfig. If no address then a problem right there-- modem / windows drivers hosed up.

2) If OK then logon to your NAS - use a keyboard and monitor rather than the tiny screen on the NAS itself

3) On the console simply type ping {windows machine ip address) e.g ping 192.168.2.125 or whatever it is.

you should get some sort of return back from ping. If Windows returns a response from ping then you've got a Windows or modem problem and can ignore NAS as it won't be the problem.

(ensure on the Windows machine you have enabled "Allow remote connections to this computer" and uncheck the box "only allow etc etc".) While testing don't let extra securityget in the way -- you can always adjust that later.

cheers

jimbo