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!

PENDING failed to authenticate as the client push account

  • Thread starter Thread starter czql5v
  • Start date Start date
  • Replies Replies 9
  • Views Views 2K

czql5v

Member
Messages
6
Reaction score
0
Points
1
We are having a problem with SCCM Client machines on one particular subnet with failed to connect to admin$, failed to authenticate the machine account, failed to authenticate as the client push account. We don't seem to be having this problem on any other subnets. For example we have a subnet group where we have 5 different subnets present (these do not authenticate - and error) we have another group with two different subnets (these are error free) and we are able to map drives without any issues on these two subnets.

We have checked the firewalls and all GPO's and there is nothing that would filter out any of these subnets. I did notice in SCCM roles that the subnets that are working had the Distribution Point Role installed where the subnets there were not working did not. Could this be the problem we are encountering?

Can anyone let me know if they have experienced similar issues and how they have managed to resolve. If you require any further information please let me know.

This is becoming a big issue within management.

Kind Regards.
 
Taking a single line out of context, is not helpful. What is the exit code of the install? Since this effect some clients and not others, this could be a boundaries issue, as such are you only using ip ranges for boundaries?
 
Taking a single line out of context, is not helpful. What is the exit code of the install? Since this effect some clients and not others, this could be a boundaries issue, as such are you only using ip ranges for boundaries?
Hi Garth,

Thanks for the reply its appreciated.

"Taking a single line out of context, is not helpful." Not sure what you mean ?
The IP boundaries are setup using IP Ranges for example 10.0.0.0/24 etc, etc.

What I did notice is that for the boundaries subnets that are erroring the DP role is not installed, but the MP role is. The DP role and MP is installed on the other boundary subnet which is working.

I am not sure what the difference is between the DP and MP role and whether that would make a difference?

Regards.
 
Review the boundaries and make sure the clients that are part of the subnet are covered. Review the boundary group and make sure a valid DP is assigned for this subnet.
 
Review the boundaries and make sure the clients that are part of the subnet are covered. Review the boundary group and make sure a valid DP is assigned for this subnet.
Hi Prajwal Desai,

Thanks for the reply.

Yes - I did check the boundaries and they all stack up. I.E. the clients are all covered on the subnets.

This is the error message we are getting.
1712848516968.png
I can confirm that the user 5859724 is a local admin member of the above machine.

Thanks for any information you could provide to help me resolve this particular problem.

Regards.
 
Can you try this: From the ConfigMgr server, test if the user 5859724 can access the admin$ share on the remote client computer. Let us know if that works.
 
Review the boundaries and make sure the clients that are part of the subnet are covered. Review the boundary group and make sure a valid DP is assigned for this subnet.
Review the boundaries and make sure the clients that are part of the subnet are covered. Review the boundary group and make sure a valid DP is assigned for this subnet.
Hi Prajwal Desai,

I have just checked the boundary groups and noticed that the DP role is not installed on the subnets that are failing. Could this be the problem?
 
Hi Prajwal Desai,

I have just checked the boundary groups and noticed that the DP role is not installed on the subnets that are failing. Could this be the problem?
Hi Prajwal,

Any ideas what this might be. As mentioned the DP role is not installed on the boundary groups that the subnet is part of. Could \ how would this be the problem.

Regards.
 
Can you try this: From the ConfigMgr server, test if the user 5859724 can access the admin$ share on the remote client computer. Let us know if that works.
Hi Prajwal,

I have noticed the logs and this user is unable to access the admin$ share from configmgr server.
 
Back
Top