Let’s talk about the problem and discuss how it can be PREVENTED! First, Client-A isn’t even turned on…but we get a response. Some of you may already realize this is what happens when we send a Kerberos ticket intended for one computer to another computer, but let’s quickly walk through this process.Ugh, now we’ve got two different names associated with the same IP address in DNS. I mentioned this issue manifesting itself as a problem installing the SCCM client, but in reality we can demonstrate this with a much simpler example; accessing a shared folder. Realize this works just fine if the IP address is used instead of the FQDN. Because NTLM authentication will be used instead of Kerberos authentication.
Got a DHCP address from the server Now my issue is as follow.
When i ping the new laptop (PC1) i am directed to the original ip of the first laptop ( IP 10.0.0.33) When I looked at my new laptop I saw that the IP is 10.0.0.26 and DHCP shows the same in the lease list I can ping the IP 10.0.0.26 but when trying to resolve the name(PC1), it still points to the old original laptop's IP of 10.0.0.33 When I opened my DNS, i saw that PC1's record is listed and the IP still points to 10.0.0.33 Can I delete the record in the DNS server's dns list (PC1) and run ipconfig /registerdns on the new laptop to have the new dns record be registered on the server?
Recently, and on three separate occasions, I worked with SCCM administrators having issues deploying the SCCM client.
Specifically, they were seeing the error “Failed to get token for current process (5)” in
We discovered the problem was related to DNS and DHCP rather than SCCM.