Ask the Community
Groups
How to resolve "Cannot connect to client" errors during backups - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="summary"><strong>SUMMARY</strong></h2> <p>This article discusses how to resolve an issue where backups are failing and a reboot of the server seems to clear up the issue for a while but then then issue reoccurs.</p> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p></p> <h3 data-id="purpose">Purpose</h3> <p>Backups are failing with message cannot connect to client.</p> <h3 data-id="applies-to">Applies To</h3> <p>Windows Server 2003</p> <p>Windows Server 2008</p> <p>Windows 7</p> <p>Windows Vista</p> <p>Windows XP</p> <h3 data-id="symptoms-description">Symptoms / Description</h3> <p>Backups are failing but a reboot of the server seems to clear up the issue for a while but then then issue reoccurs.</p> <h3 data-id="cause">Cause</h3> <p>Our agent uses 2 ports for communication with the DPU appliance. Port 1743 is known as our command port and port 1745 is used for data transfer. It is possible for some other process to use 1745 and cause our backup to fail. One way to determine whether another process is using port 1745 is to run some simple network commands.</p> <p> </p> <p> netstat –ano > C:\ports.txt</p> <p> </p> <p>You can then use notepad or your favorite text editor to check the file for what processes are using what ports. The ‘-o’ flag shows what PID has the port open. Search for port 1745 and see if it is in use.</p> <p> </p> <h3 data-id="resolution-workaround-execution-process">Resolution / Workaround / Execution Process</h3> <p>You can edit the master.ini which is installed by default to C:\PCBP\master.ini. Search the file for data=1745. You can change this to data=1744. This change stops using the single port 1745 for data transfer and looks for any random open port for the data transfer.</p> <h3 data-id="third-party-sources">Third-Party Sources</h3> <p>N/A</p> <p> </p> </article> </main>