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

After disabling 'NetBIOS over TCP/IP' via DHCP some of our computers
can not be managed remotely. So far, it seems only to affect computer
running Windows XP SP2. The strange thing is that this happens not all
of the time, sometimes after a reboot everything as OK and vice versa.

When attempting to connect to one of the computers in question using
computer management (from any server or workstation) one receives this
message:
Computer \\computername cannot be managed because it is not running
Windows NT. Would you like to manage it anyway?

Some other remote administration tools do not work at all.

After using Wireshark it turned out the computer does identify itself
via Server Message Block (SMB) NetServerGetInfo as
'Server Type: 0x0000001' and not as 'Server Type: 0x0001003'.

That means that the computer identifies itself incorrectly only as
'Workstation' and not as 'Workstation', 'Server' and 'NT Workstation'.

The identification as 'Server' and 'NT Workstation' should be carried
out if 'File and Printer Sharing for Microsoft Networks' is installed
and activated on the network interface card, according to
http://support.microsoft.com/kb/262597/en-us and our observations.
Sadly reinstalling 'File and Printer Sharing for Microsoft Networks'
does only fixes the problem till the next reboot. Reinstalling the
'Client Microsoft for Networks' doesn't fix the problem longer than the
next reboot. Re-enabling 'NetBIOS over TCP/IP' via DHCP does fix the
problem, but want to have 'NetBIOS over TCP/IP' disabled.

The were some posts mentioning the same problem:
http://groups.google.com/groups?hl=en&q=%22Computer+*+cannot+be+managed+because+it+is+not+running+Windows+NT%22&Submit3=Search

We think it could be an error in Windows XP SP2.

Is there anyone with an idea how this problem can be fixed? Any help
would be appreciated.

.

Relevant Pages

  • WIn 98 browsing to Windows 2000 Server
    ... Netbios over TCP/IP is enabled on the server...any other ... >Which network protocols do you have on your network? ... >>I am having trouble browsing to a Windows 2000 Server ...
    (microsoft.public.security)
  • Re: Disabled NetBIOS, Now Clients Cant Browse
    ... With Windows 2000, Windows XP and Windows Server 2003 you don't need NetBIOS ... over TCP/IP to connect to shared resources. ...
    (microsoft.public.win2000.networking)
  • Re: NetBios over TCP/IP
    ... I just posted that the default will still show NetBIOS ... Windows Networking MVP ... I have enable NetBIOS over TCP/IP but ipconfig /all shows NetBIOS over ... installing a second network protocol ...
    (microsoft.public.windowsxp.network_web)
  • Re: Vant see pcs in domain
    ... so why don't you spend you time studying to get somewhere. ... Windows Internet Name Service provides a dynamic replicated ... as a NetBIOS name server and register and resolve names for WINS-enabled ... client computers on your network as described in the NetBIOS over TCP/IP ...
    (microsoft.public.cert.exam.mcse)
  • Wintel Engineers - Singapore Permanent Position
    ... Windows 2000 & Windows NT.Required 3 years of experience in System ... Proofed excellent analytical and problem management skills, ... Enterprise server and Handheld support.- Min. of 1 year experience ... Server hands on experience- In-depth Windows Server & Exchange ...
    (microsoft.public.win2000.cmdprompt.admin)