ICM
1 TopicICM fails on call back to local PC
Hi there. I've an odd issue with Powershell. I discovered that I cannot ICM from the domain controller to a remote workstation - and I also cannot ICM from the actual workstation PC console back to itself. This had been properly configured & working until... (Recent details: We had an SBS 2008 DC, migrated to WS2019. When I finally transferred DNS & DHCP and took the old server offline is when the ICM problem began. Before the SBS 2k8 came offline and the two DCs were still replicating AD & etc., I could ICM from the WS2019 DC with no problem.) Not sure what to make of it. On a side note, the DHCP snap-in strips the domain from the server name and replaces it with 'mshome.net' no matter how many times I delete it and add it back in - and does not allow any interaction. But the Get-DHCPServer(...) cmdlets report all the correct settings, scope, exclusions, etc. - so I've ignored this for the most part.) -------------------------------- Back to the initial question, this is an example of events pulled from WinRM / ICM where the client & destination are the same computer: Thinking perhaps User & Computer domain mismatch? Any ideas? Thanks! P.S. This might be correlated - RDP attempt from the DC to remote PC. Strange error since the DC is the computer being used, but says the DC can't be contacted for NLA.1.1KViews0likes1Comment