Computer \\computername cannot be managed because it is not running Windows NT

[googlegroups99]

I recently ran into an issue on a handful of machines that would
generate the following error when attempting to remotely manage them
(using compmgmt.msc):

Computer \\computername cannot be managed because it is not running
Windows NT. Would you like to manage it anyway?

I searched and searched for an answer but never came up with much.
Eventually I found a commonality between the machines. Each had the
"Windows Firewall/Internet Connection Sharing (ICS)" service set to
"Disabled", which led me to another known issue where the "Computer
Browser" service would timeout and stop
(http://support.microsoft.com/kb/889320). We have a GPO in place to
turn the Windows Firewall off, so the service technically did not need
to be disabled. I set the service to Automatic and started it, and the
Computer Browser immediately started back up as well as the
"Application Layer Gateway Service."

Believe it or not, this change has (knock on wood) completely
eliminated the original error message when attempting to manage the
machine. I mention this in hopes the same fix may work for others who
come up empty when searching for resolution for this issue. Hope it
helps.

 

[Guest]

What happens if you disable WF/ICS but try to access the computer using a
fully qualified domain name instead?

 

[googlegroups99]

We tried a variety of suggestions in related threads, all to no avail.
We attempted to connect using FQDN, IP address, disjoin/rejoin the
domain, NewSID utility, etc. This is the solution we finally landed on
that worked. So far so good.