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



I have recently come across this error message when attempting to use
computer management to remotely manage my workstations. These are all
machines with fresh installs of Windows XP Professional SP2. I've disabled
windows firewall on all the machines, and have tried unjoining and
rejoining them to the domain. However, every time I try to manage them
remotely I receive this error message. If I answer "Yes" to the window it
allows me to manage it. However, applications that I use to remotely
manage windows services on multiple workstations fail to work on these
machines. Anyone have this problem and know how to fix it?
.



Relevant Pages

  • Re: Server 2003 slow network connectivity
    ... All the workstations are Windows XP. ... Are there any messages in the Event logs that might indicate where the ... the error message on the dcdiag is just a report of a failure from the ...
    (microsoft.public.windows.server.networking)
  • Re: BAT file to retrieve Registry Setting
    ... workstations are the infamous Windows 95 with a few Windows 98s. ... I am not sure if these machines have reg.exe on them. ... I plan to setup a BAT file accessible on the network for each person to run ...
    (microsoft.public.win2000.cmdprompt.admin)
  • Re: VB6 - Vista
    ... working relatively fast, nobody replaces it. ... So we have machines with different operating systems. ... You can still buy machines with windows 2000 from Dell, ...
    (microsoft.public.vb.general.discussion)
  • Re: "Delayed Write Failed"
    ... "Delayed Write Failed" Error Message When You Write a File to a Server ... "Delayed Write Failed" Error Message When You Manage Files in Windows XP ... | machines with XP Service Pack 1 applied. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Change local administrator password for all PCs in the domain
    ... > I have about 200 workstations in my Windows 2000 domain. ... you could setup a custom script or Group Policy (in ... no workgroup machines. ...
    (microsoft.public.windows.server.scripting)

Loading