Error Message

If vmware debugging is enabled in SGMON the following should be observed in the log generated.

---------------------------------------------------------------------------------------------------------------------------------------------------------

[fsys\shared] - VDDK-Warn: [NFC ERROR] NfcNewAuthdConnectionEx: Failed to connect to peer. Error: Connection terminated by server
[fsys\shared] - VDDK-Log: NBD_ClientOpen: Couldn't connect to esx.server.local:902 Connection terminated by server
[fsys\shared] - VDDK-Log: DISKLIB-DSCPTR: : "vpxa-nfc://[DataStoreX] VM-Name/vmdkname.vmdk@ esx.server.local:902" : Failed to open NBD extent.
[fsys\shared] - VDDK-Log: DISKLIB-LINK : "vpxa-nfc://[DataStoreX] VM-Name/vmdkname.vmdk@ esx.server.local:902" : failed to open (NBD_ERR_NETWORK_CONNECT).
[fsys\shared] - VDDK-Log: DISKLIB-CHAIN : "vpxa-nfc://[DataStoreX] VM-Name/vmdkname.vmdk@ esx.server.local:902" : failed to open (NBD_ERR_NETWORK_CONNECT).
[fsys\shared] - VDDK-Log: DISKLIB-LIB : Failed to open 'vpxa-nfc://[DataStoreX] VM-Name/vmdkname.vmdk@ esx.server.local:902' with flags 0x1e NBD_ERR_NETWORK_CONNECT (2338).

VM_VCBPROXY_FS::OpenObj() Could not open the disk '[DataStoreX] VM-Name/vmdkname.vmdk' DiskCompatibility: 'dependent' DiskMode 'persistent' Error Text: 'You do not have access rights to this file' Error: '13'
 LP_ENV::MsgError: error 0xe0009585 processing object VM-Name/vmdkname.vmdk

-------------------------------------------------------------------------------------------------------------------------------------

UMI Code: V-79-57344-38277

There is no connection to the ESX server in question.  to test connectivity to port the ESX server on port 902 telnet to this port form the command line interface (telnet esx-server  902) as detailed in vmware article (https://kb.vmware.com/s/article/1003487). 

Please note that this article references sites not owned or maintained by Veritas and, as such, Veritas is not responsible for the content portrayed on such sites, including any revisions to or deletions of content or third-party software on which this article relies. User is responsible for conducting all necessary due diligence prior to following the instructions described in this article.

The following output should be listed, provided the connection to the ESX completed successfully.

C:\>telnet server 902
Connecting...

220 VMware Authentication Daemon Version 1.10: SSL Required,ServerDaemonProtocol:SOAP, MKSDisplayProtocol:VNC

The connection can also be checked using the "netstat -na | "902" command from the command line interface.  The state that points to a successful connection is "ESTABLISHED". any other state indicates the connection did not take place.

Communication issues with the ESX server needs to be fixed either by checking the firewalls on the Media server, ESX servers or network infrastructure.