Re: Computer \\computername cannot be managed because it is not running Windows NT
- From: "Lanwench [MVP - Exchange]" <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 31 Jul 2006 13:35:38 -0400
My reply is at the bottom of your message.
In news:1154355477.343577.29080@xxxxxxxxxxxxxxxxxxxxxxxxxxx,
borntom <google@xxxxxxxxxxxxxx> typed:
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.
I have no idea, but a) I always enable NetBIOS over TCP/IP as it just seems
to work better and b) if you run WINS there's little downside to it. What's
the reason you disabled it in the first place, if you don't mind my asking?
A lot of stuff still relies on it, sad to say.
.
- References:
- Prev by Date: Re: Windows Restore
- Next by Date: Re: How to change password?
- Previous by thread: Computer \\computername cannot be managed because it is not running Windows NT
- Next by thread: Re: Computer \\computername cannot be managed because it is not running Windows NT
- Index(es):
Relevant Pages
|
