What's new
Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

SOLVED SCCM Client Push Fail WNetAddConnection2 failed

  • Thread starter Thread starter dprd7
  • Start date Start date
  • Replies Replies 16
  • Views Views 10K
Status
Not open for further replies.
D

dprd7

Active Member
Messages
31
Reaction score
0
Points
6
Hello Everyone. I am new to SCCM and I am running into issues pushing the client. Here is the log.

======>Begin Processing request: "2097152006", machine name: "CARDIOSCCMTEST" SMS_CLIENT_CONFIG_MANAGER 9/18/2019 9:14:18 AM 12576 (0x3120)
Execute query exec [sp_IsMPAvailable] N'HC2' SMS_CLIENT_CONFIG_MANAGER 9/18/2019 9:14:18 AM 12576 (0x3120)
---> Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 9/18/2019 9:14:18 AM 12576 (0x3120)
---> Attempting to connect to administrative share '\\CARDIOSCCMTEST.CARDIO.CHBOSTON.ORG\admin$' using account 'CARDIO\SCCM_PUSH' SMS_CLIENT_CONFIG_MANAGER 9/18/2019 9:14:18 AM 12576 (0x3120)
---> SspiEncodeStringsAsAuthIdentity succeeded! SMS_CLIENT_CONFIG_MANAGER 9/18/2019 9:14:18 AM 12576 (0x3120)
---> SspiExcludePackage succeeded! SMS_CLIENT_CONFIG_MANAGER 9/18/2019 9:14:18 AM 12576 (0x3120)
---> SspiMarshalAuthIdentity succeeded! SMS_CLIENT_CONFIG_MANAGER 9/18/2019 9:14:18 AM 12576 (0x3120)
---> NetUseAdd failed: 53: dwParamError = 0 SMS_CLIENT_CONFIG_MANAGER 9/18/2019 9:14:18 AM 12576 (0x3120)
---> NTLM fallback is enabled SMS_CLIENT_CONFIG_MANAGER 9/18/2019 9:14:18 AM 12576 (0x3120)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account CARDIO\SCCM_PUSH (00000035) SMS_CLIENT_CONFIG_MANAGER 9/18/2019 9:14:18 AM 12576 (0x3120)
---> The device CARDIOSCCMTEST.CARDIO.CHBOSTON.ORG does not exist on the network. Giving up SMS_CLIENT_CONFIG_MANAGER 9/18/2019 9:14:18 AM 12576 (0x3120)
---> Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 9/18/2019 9:14:18 AM 12576 (0x3120)
---> Attempting to connect to administrative share '\\CARDIOSCCMTEST.tch.harvard.edu\admin$' using account 'CARDIO\SCCM_PUSH' SMS_CLIENT_CONFIG_MANAGER 9/18/2019 9:14:18 AM 12576 (0x3120)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account CARDIO\SCCM_PUSH (00000035) SMS_CLIENT_CONFIG_MANAGER 9/18/2019 9:14:19 AM 12576 (0x3120)
---> The device CARDIOSCCMTEST.tch.harvard.edu does not exist on the network. Giving up SMS_CLIENT_CONFIG_MANAGER 9/18/2019 9:14:19 AM 12576 (0x3120)
---> Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 9/18/2019 9:14:19 AM 12576 (0x3120)
---> Attempting to connect to administrative share '\\CARDIOSCCMTEST\admin$' using account 'CARDIO\SCCM_PUSH' SMS_CLIENT_CONFIG_MANAGER 9/18/2019 9:14:19 AM 12576 (0x3120)
---> SspiEncodeStringsAsAuthIdentity succeeded! SMS_CLIENT_CONFIG_MANAGER 9/18/2019 9:14:19 AM 12576 (0x3120)
---> SspiExcludePackage succeeded! SMS_CLIENT_CONFIG_MANAGER 9/18/2019 9:14:19 AM 12576 (0x3120)
---> SspiMarshalAuthIdentity succeeded! SMS_CLIENT_CONFIG_MANAGER 9/18/2019 9:14:19 AM 12576 (0x3120)
---> NetUseAdd failed: 53: dwParamError = 0 SMS_CLIENT_CONFIG_MANAGER 9/18/2019 9:14:20 AM 12576 (0x3120)
---> NTLM fallback is enabled SMS_CLIENT_CONFIG_MANAGER 9/18/2019 9:14:20 AM 12576 (0x3120)
---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account CARDIO\SCCM_PUSH (00000035) SMS_CLIENT_CONFIG_MANAGER 9/18/2019 9:14:20 AM 12576 (0x3120)
---> The device CARDIOSCCMTEST does not exist on the network. Giving up SMS_CLIENT_CONFIG_MANAGER 9/18/2019 9:14:20 AM 12576 (0x3120)
---> ERROR: Unable to access target machine for request: "2097152006", machine name: "CARDIOSCCMTEST", access denied or invalid network path. SMS_CLIENT_CONFIG_MANAGER 9/18/2019 9:14:20 AM 12576 (0x3120)
STATMSG: ID=3015 SEV=W LEV=M SOURCE="SMS Server" COMP="SMS_CLIENT_CONFIG_MANAGER" SYS=HCSCCM.CARDIO.CHBOSTON.ORG SITE=HC2 PID=2572 TID=12576 GMTDATE=Wed Sep 18 13:14:20.805 2019 ISTR0="CARDIOSCCMTEST" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_CLIENT_CONFIG_MANAGER 9/18/2019 9:14:20 AM 12576 (0x3120)
Execute query exec [sp_CP_SetLastErrorCode] 2097152006, 53 SMS_CLIENT_CONFIG_MANAGER 9/18/2019 9:14:20 AM 12576 (0x3120)
Stored request "2097152006", machine name "CARDIOSCCMTEST", in queue "Retry". SMS_CLIENT_CONFIG_MANAGER 9/18/2019 9:14:20 AM 12576 (0x3120)
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097152006, 2 SMS_CLIENT_CONFIG_MANAGER 9/18/2019 9:14:20 AM 12576 (0x3120)
Execute query exec [sp_CP_SetLatest] 2097152006, N'09/18/2019 13:14:20', 1 SMS_CLIENT_CONFIG_MANAGER 9/18/2019 9:14:20 AM 12576 (0x3120)
<======End request: "2097152006", machine name: "CARDIOSCCMTEST". SMS_CLIENT_CONFIG_MANAGER 9/18/2019 9:14:20 AM 12576 (0x3120)
 
Sort by date Sort by votes
WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account CARDIO\SCCM_PUSH (00000035) SMS_CLIENT_CONFIG_MANAGER 9/18/2019 9:14:20 AM 12576 (0x3120)
Click to expand...

In the client, check if the "CARDIO\SCCM_PUSH" user is member of local administrators group.
 
Upvote 0 Downvote
Thank you for the quick response. The CARDIO\SCCM_PUSH account is in the administrator group within a group we have called Set Local Admins
 
Upvote 0 Downvote
From the site server, try to access to the "\\CARDIOSCCMTEST.tch.harvard.edu\admin$" share.

If you have Windows firewall on the client machine, try to disable it and check again. The same if you have an Antivirus.

Check also if the ccmsetup folder is created on the client machine (C:\Windows\ccmsetup).
 
Upvote 0 Downvote
So I added the SCCM_PUSH account to the local administrator account without being in a group. I seem to be getting less errors.

I can connect to the admin share from the site server.

We the have ports open for SCCM but I will try no firewall. I will also disable Symantec.

Any idea what this error is?

---> Unable to connect to remote machine "CARDIOSCCMTEST.tch.harvard.edu" using Kerberos with alternate account, error - 0x800706ba. SMS_CLIENT_CONFIG_MANAGER 9/18/2019 10:04:39 AM 12392 (0x3068)

And this one

---> Unable to connect to WMI (root\ccm) on remote machine "CARDIOSCCMTEST.tch.harvard.edu", error = 0x8004100e. SMS_CLIENT_CONFIG_MANAGER 9/18/2019 10:04:39 AM 12392 (0x3068)
 
Upvote 0 Downvote
Upvote 0 Downvote
So when I disabled the Firewall and Symantec the WMI error is gone but still receiving this one

---> Unable to connect to remote machine "CARDIOSCCMTEST.tch.harvard.edu" using Kerberos with alternate account, error - 0x800706ba.

Also when I sent the original log is there a way to have SCCM hit \\CARDIOSCCMTEST\admin$ first instead of going to\\CARDIOSCCMTEST.CARDIO.CHBOSTON.ORG\admin$ and \\CARDIOSCCMTEST.TCH.HARVARD.EDU\admin$
 
Upvote 0 Downvote
Thanks for the info. Anything on Kerberos with that error?

Is there anyway to change the default?
 
Upvote 0 Downvote
Ensure that the Push Installation Account are correctly configured (login, password), if you can give us screenshots, It's will be easy for us to help you.
 
Upvote 0 Downvote
Will do and thanks for all the help. Is there anyway to force the short name for client push or SCCM will always try the FQDN first?
 
Upvote 0 Downvote
Why you are asking this? If you ping with the client FQDN from the Site Server, Is it worked?
Ensure that the DNS suffixes are also configured in the TCP/IP settings on the Site Server and the client.
 
Upvote 0 Downvote
That is one of our issues since we are on a sub domain and not in control of our DNS. We can only ping and connect to CARDIOSCCMTEST and CARDIOSCCMTEST.TCH.HARVARD.EDU. We can not connect using CARDIOSCCMTEST.CARDIO.CHBOSTON.ORG which is always the first one SCCM wants to use since that is our Domain. They will not do DNS records of our client machines so I was hoping to see if there was a way to have \\CARDIOSCCMTEST\Admin$ be first since in our old SCCM 2012 Windows 2008 R2 a previous co worker of mine was able to have that be first but I don't know if that was just by design back then or he did something special to force it.

We do have DNS suffixes configured in the TCP/IP Settings which are and in the following order.

CARDIO.CHBOSTON.ORG
TCH.HARVARD.EDU
CHBOSTON.ORG

Thanks again for all the help.
 
Upvote 0 Downvote
So basically. File & Print Sharing and WMI

Port 80 is open by default correct. No need to setup a rule for that.
 
Upvote 0 Downvote
You can check the ports with Telnet command.

If you have any antivirus, try to close it and check again.
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

  • PENDING PXE Boot Issue - Not Receiving IP
  • PENDING MECM cannot access to WSUS WID
  • PENDING How to handle duplicate "x86/x64 unknown computer" listings within same site code
  • PENDING Intune Expedite Update policy missing KB5077744 OOB update
  • PENDING KB5077744 update deployment via SCCM

    • Forum statistics

    Threads
    7,165
    Messages
    27,971
    Members
    18,271
    Latest member
    prashantrm

    Latest posts

    Trending content
    Back
    Top