Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Patch Manager > Patch Manager - Knowledgebase Articles > No connection could be made because the target machine actively refused it

No connection could be made because the target machine actively refused it

Overview

When you add a WSUS server to Patch Manager, the following error displays:

Could not connect to server:

Exception occurred at 

No connection could be made because the target machine actively refused it 

Environment

Patch Manager 2.1 and earlier

Cause 

The WSUS server is not responding on the appropriate port. As a result, Patch Manager cannot connect to the WSUS server.

Resolution

Verify that:

  1. The WSUS server is installed and configured properly.
  2. The WSUS listening port is correct. 
  3. Patch Manager is able to resolve the WSUS server and the port included in the Connection Wizard is correct. 
  4. The WSUS server has no errors in the Windows Event and Application logs and is functioning correctly.

 

Last modified

Tags

Classifications

Public