Follow the above steps to troubleshoot connection issues.

• Ensure that installation instructions are followed, including firewall exception rules. The ReadMe.htm is attached to this document and can also be found where SSR Monitor is installed at C:\Program Files (x86)\veritas\veritas System Recovery Monitor\Docs\ReadMe.htm.
• Add an exception to the system firewall for C:\Program Files\veritas\veritas System Recovery\Console\VProconsole
• Ensure that the Veritas System Recovery service (VProSvc.exe) is operational.
• The user account used to connect to the SSR client has the necessary administrator rights.
• Attempt to connect using the IP address of the machine. If IP address connects while NetBIOS and hostname don't, rule out DNS issues.
• Run Windows Update on each machine and ensure all important updates are applied. (Certain operating systems require depencancies that were built into Microsoft Updates.)
• SSR and SSR Monitor 2013 should be installed on the same computer, as SSR Monitor facilitates ‘1-to-1 mgmt’ feature using local SSR console.
• Add the DCOM port (Default is TCP port 135) and Veritas System Recovery service (Vprosvc.exe) to the firewall exceptions list.
• Veritas System Recovery Service must be running and functional on the SSR Monitor computer.
• Turn off UAC (User Access Control) on the client computer (https://windows.microsoft.com/en-us/windows-vista/Turn-User-Account-Control-on-or-off). This is necessary when using a 'standard' user in workgroup environment, or a domain user with restrictive permissions in domain environment. UAC's security mechanism does not allow SSR Monitor to connect to the SSR agent on the client computers.
• Ensure that the Simple File sharing option is disabled on Microsoft Windows XP (All Editions) and Microsoft Windows Server 2003 (All Editions)
• One SSR Monitor session per machine. If multiple users are logged into the machine (including remote connections), only one can use SSR Monitor.