Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Here is my problem:

The NFS shared folder was working without any problem. All the machines of a small network could use it. But something happened few months ago(I have no idea, maybe some auto-update), and since then, I can not connect any new computer to my NFS server. The old clients can still use the drive mapped months ago, but the new ones can't map it, I get the following error:

Error code 0x80070035
The network path was not found. 

From the same machine, I can access the NFS server with SSH. What can causes this problem? What should I do?

Sorry for my bad English, Thanks for the answers!

share|improve this question

Unfortunately you don't provide enough information in your question, to this fairly generic issue.

It could be that you do not have the additional NFS client installed on your Windows systems.

It could be that you support both SMB and NFS on your file server and your working clients have a different provider order configured in their networking stack to your non-working clients (SMB vs. NFS).

You can troubleshoot this further from the command line:

- to check/mount NFS:
C:\> showmount -e server_name_or_IP
C:\> mount -o anon server:\share *

- to mount SMB:
C:\> net use * \\server\share  /user:<username> <password>

It could be that your NFS share is only exported to a select number of hosts, so some hosts can not connect, since they are not in the NFS export list.

If you are running Windows 7 clients, it could be an anonymous GUI mismatch, see:

Anyway, try that for a start and see how you go..

-- ab1


share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.