Re: Computer \\computername cannot be managed because it is not running Windows NT
- From: "Steven L Umbach" <n9rou@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 1 Aug 2006 17:14:05 -0500
That is weird as usually using the IP address works as it removes the need
to use name resolution. I can't say much more as to why it does not work on
SP2 as I have never had a need to disable NBT. You may also want to post in
the networking newsgroup to see if anyone there has seen the same behavior.
In my opinion disabling NBT does little to nothing to improve network
security. Using ipsec, if needed, would do a whole lot more to increase
network security including requring that computers authenticate with each
other before access is allowed on defined ports/protocols/IP and the ability
to encrypt and guarantee authenticity of network traffic.
Steve
"borntom" <google@xxxxxxxxxxxxxx> wrote in message
news:1154415859.757093.41590@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Using the IP does not help, the computer still identifies itself as
'Server Type: 0x0000001' and not as 'Server Type: 0x0001003'. On the
computers, which still identify themselves correct, we had no problems
without 'NetBIOS over TCP/IP'.
In addition since 'My Network Places' is broadcast based and
therefore every device can claim to be everything via broadcast
disabling 'NetBIOS over TCP/IP' and therefore loosing 'My Network
Places' is one step to more security.
Steven L Umbach schrieb:
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.
.
- Follow-Ups:
- References:
- Prev by Date: Re: Desktop icons lost on startup
- Next by Date: Re: How to change password?
- Previous by thread: Re: 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
|
