Official comment

This is typically part of the Communication setup and testing - see reference to online document : https://dbvisit.atlassian.net/wiki/display/DS8QSG/Dbvisit+Standby+Networking+-+Dbvnet#DbvisitStandbyNetworking-Dbvnet-7.TroubleshootingDbvnet
1. Ensure the hostnames of the two Windows servers and their IP addresses are present in the hosts file on both servers - c:\Windows\System32\Drivers\etc\hosts.
2. You may have to adjust the "metric" for the specific network interface to make sure ipv4 gets higher priority.
Example see attached - 3 steps to get to the metric.
Adjust the automatic setting to something like 20, then retry - restart of dbvnet will be required
You can do this on your test system standby server first - the metric change might require a windows restart to take affect.
See attached screen print
3. Once you have carried out the steps run the netstat command on both primary and standby servers.
C:\Users\Administrator> netstat -ano|findstr 7890
With expected output as :
TCP 0.0.0.0:7890 0.0.0.0:0 LISTENING 2396 TCP 172.16.1.92:7890 172.16.1.91:61319 ESTABLISHED 2396
Check the status of the ports on Primary Server
================================================
C:\Program Files\Dbvisit\Standby>netstat -ano|findstr 7890
C:\Program Files\Dbvisit\Standby>netstat -ano|findstr 7891
Check the status of the ports on Standby Server
================================================
C:\Program Files\Dbvisit\Standby>netstat -ano|findstr 7890
C:\Program Files\Dbvisit\Standby>netstat -ano|findstr 7891
4. Finally run the System Readiness test :
C:\Program Files\Dbvisit\Standby>dbvctl.exe -f system_readiness