Tuesday 17 March 2015

SCCM 2012 R2 - Client Push Error - WNetAddConnection2 failed (logon32_logon_new_credentials) using account

Symptoms:

Assuming your SCCM server and clients aren't all in the same subnet/VLAN, you may ecounter the following error message in the ccm.log;

WNetAddConnection2 failed (logon32_logon_new_credentials) using account --- (00000035)

ERROR: Unable to access target machine for request"xxxxxx", machine name "xxxxx", access denied or invalid network path.


The ccm.log can be found in %SCCM Install Directory%\Logs\ccm.log

Cause:

Either the account used for the client push doesn't have the requisite permissions or the communication between the SCCM server and the target machine is being blocked.

Fixes:

Check the network side of things. Ports required to be open in order to push out the SCCM Client:

  • Server Message Block (SMB) between the site server and client computer (TCP 445)
  • RPC endpoint mapper between the site server and the client computer (UDP 135; TCP 135)
  • RPC dynamic ports between the site server and the client computer (TCP Dynamic)
  • Hypertext Transfer Protocol (HTTP) from the client computer to a management point when the connection is over HTTP (TCP 80)
  • Secure Hypertext Transfer Protocol (HTTPS) from the client computer to a management point when the connection is over HTTPS (443)

Check the account you added in Client Push. Is the password right? In 2012, use the 'verify option to confirm whether or not the account can access the admin$ share on the target machine:



No comments:

Post a Comment