Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Error message when you try to mount an NFS export on a Windows Server 2003 R2-based NFS client computer from a Tru64 UNIX-based NFS server: "Network Path Not Found"


View products that this article applies to.

Symptoms

Consider the following scenario. You install Windows Services for UNIX on a Microsoft Windows Server 2003 R2-based computer on which "Client for NFS" is running. Additionally, you have a Tru64 UNIX-based NFS server. In this scenario, when you try to mount a network file system (NFS) export on the NFS client computer from the NFS server, you receive the following error message:

Network Path Not Found.

↑ Back to the top


Cause

This problem occurs because of an error in the Domain Name System (DNS) reverse lookup.

↑ Back to the top


Resolution

Create pointer (PTR) records for the NFS client computers on the DNS server.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More information

In this scenario, the NFS client computer can enumerate the NFS export. However, the NFS client computer cannot mount the NFS export. If you capture a network trace when the problem occurs, the trace includes the following information:
"V3 MNT Reply"
Reply State: denied (1)
Reject State: AUTH_ERROR (1)
Some NFS servers require valid PTR records as part of the security mechanism.

↑ Back to the top


Keywords: kberrmsg, kbtshoot, kbprb, KB926095

↑ Back to the top

Article Info
Article ID : 926095
Revision : 3
Created on : 10/23/2006
Published on : 10/23/2006
Exists online : False
Views : 339