This was an oddball issue. 1 Host/VA out of 3 getting these errors - The referenced VA is the TARGET va. Job fails at 6%. Resolution is working, VA is DHCP, Source Host was even rebooted. Nameservers correct in resolve.conf. Not resolved by Previous KB's. Not resolved by Net use /d.
These are the messages in the logs.
An existing connection was forcibly closed by the remote host AND/OR
No connection could be made because the target machine actively refused it.
,
It always comes back to DNS. The best thing to do is manually configure Network info and not rely on DHCP. If you still get the error, try choosing a different IP address.
This particular case was resolved after he disabled the 120 address forced a reassignment.
He had some suspicion that something was wrong with the address .120, but we will never know what. I think it was duplicated in DNS, or there was some firewall rule or script blocker rule attached to that address. Forward and reverse lookup worked.
