vCenter Server (5.5.0 Build 4180647) on Network A (192.168.1.10/32)
ESXi HOST (5.5.0 Build 1331820) on Network B (192.168.2.10/32)
vSphere Client 5.5.0 4032365 on Network A to manage vCenter Server and HOSTs
Both networks are behind separate Meraki MX Security Appliances and have a working VPN over WAN (Meraki autoVPN).
Site-to-site VPN ACL (all ports open for troubleshooting purposes).
all traffic from 192.168.1.10/32 to 192.168.2.10/32 is allowed
all traffic from 192.168.2.10/32 to 192.168.1.10/32 is allowed
- vCenter Server receives heartbeat packets from the HOST and stays connected.
- If I "open console" from vCenter Server on any of the virtual machines running on the ESXi HOST on Network B I get "Unable to connect the MKS: Could not connect to pipe \\.\pipe\vmware-authdpipe within retry period".
- If I "open console" from vSphere client directly connected to the HOST it works as expected.
I have tried refreshing the VMX/MKS SSL cache in the virtual machine as explained by this vmware kb article: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2115126
I'm also getting errors from Veeam Backup and Replication:
"Getting VM info from vSphere
Error: NFC storage connection is unavailable. Storage: [stg:datastore-25366,nfchost:host-25365,conn:FQDNvCenterServer]. Storage display name: [DATASTORENAME]. Failed to create NFC download stream. NFC path: [nfc://conn:FQDNvCenterServer,nfchost:host-25365,stg:datastore-25366@FILENAME.vmx]."
Any suggestions would be appreciated.
Regards
Ronny