SOLVED Unable to connect to remote machine using kerberos with alternate account

[MrCheques]

Hello everyone,

SCCM noob here. I am attempting to push the client to a device that has been discovered in my AD by SCCM. However when I right click the device and click "Install Client", my CCM logfile throws the error message posted in the title (unable to connect to remote machine using kerberos with alternate account).

I have scowered the internet looking for solutions. Posted the error message in Google and clicked on just about every link that comes up. Most of the advice is that its a "firewall problem", however I have disabled the firewall and I'm still getting the issue (Home lab, so dont freak out Sec Admins!).

After a day of fighting with this (yesterday), I come to you all this morning in hopes that someone may have had a similar experience and knows the fix.

Thank you for any and all advice!

Edit: For additional info

- I have added my SCCM_Push account as a local admin to the client using GPO (I verified that it worked)

-I have added WMI and File and Print sharing firewall rules to the firewall using GPO and also verified that those are also in place. (But again, I have tried turning firewall off completely on both client and server, and the issue persists. I don't think its a firewall issue)

 

[Garth]

I would no use the push option to install the client, instead use computers star up script. https://askgarth.com/blog/configmgr-client-health-start-up-script/

 

[Garth]

Can you map a drive using the push account from the site server?

 

[MrCheques]

Issue resolved. The problem was DNS. Somehow it was told an incorrect IP address at some point. No idea when or where as I don't ever remember entering in information for DNS, but I changed my servers IP address to whatever it was calling for and that cleared the issue.