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

You could try using the computers IP address as a workaround. Otherwise you
will probably have to keep using netbios over tcp/ip. Is there a specific
reason why you feel the need to disable netbios over tcp/ip??

Steve


"borntom" <google@xxxxxxxxxxxxxx> wrote in message
news:1154355477.343577.29080@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
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

  • Re: How set server for home network?
    ... I changed the TCP/IP configuration on Win2k computer to Enable NetBIOS over ... (Win2k can access win98) ... You should only be running TCP/IP. ... You can create different users on the server and it can ...
    (microsoft.public.win2000.networking)
  • Re: TCP/IP Win2K
    ... TCP/IP ... You need to enable NetBIOS over TCP/IP because ALL Windows versions, ... For TCP/IP naming you either need DNS, running any server that supports it, ... TCP/IP is working on a computer, from its console: ping localhost. ...
    (microsoft.public.win2000.networking)
  • Re: My Network Places
    ... Contact the administrator of this server to find out if you have ... Make sure all computers in the workgroup are configured to use NetBIOS ... Click Internet Protocol (TCP/IP) and click Properties. ... click Use NetBIOS setting from the DHCP server. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Hung NetBIOS connections?
    ... NetBIOS over TCP/IP without a name server is legacy (even with a name server ... Local networking is all using NetBIOS ... > The problem I'm seeing now is, sometimes NetBIOS connections seem to ...
    (microsoft.public.win2000.networking)
  • Re: Computer \computername cannot be managed because it is not running Windows NT
    ... disabling 'NetBIOS over TCP/IP' and therefore loosing 'My Network ... Sadly reinstalling 'File and Printer Sharing for Microsoft Networks' ...
    (microsoft.public.windowsxp.security_admin)