Re: FQDN cannot be managed because it is not running Windows NT


5. The browser service is not disabled on any of the systems.
6. The DHCP Client is not disabled on any of the systems.
7. Even Logs:
JCDC01
Application
ID# 1030 Source: Userenv
ID# 1058 Source: Userenv
System
ID# 7022 source: Service Control Manager

JCDC02
Application
ID# 1005 Source: dsrestor
ID# 3013 source: Windows Search Service


Assessor07
Application
ID# 1517 Source: Userenv

Taxpc04
Application
ID# 1517 Source: Userenv
ID# 1030 Source: Userenv
ID# 1097 Source: Userenv
System
ID# 7026 Source: Service Control Manager

"Ace Fekay [MVP Direcrtory Services]" wrote:

In news:6F690930-5B29-4322-BA67-5284C7CA2F94@xxxxxxxxxxxxx,
JCCIT <JCCIT@xxxxxxxxxxxxxxxxxxxxxxxxx> requesting assistance, typed the
following:
I am running Widows Server 2003 with XP Pro clients and when I use
Active Directory to manage a computer usually everything works fine
but I have a couple PCs that I receive the fallowing error when I try
to manage them. Computer \\computername cannot be managed because
it is not running
Windows NT. Would you like to manage it anyway?
If I answer the question with a Yes a management widow will open but
the computer name in the top left has a Red X over it as if the
account was disabled. If I answer No the management widow will open
but it is for the DC that I am trying to manage the PC from.
DNS appears to resolve the machine name properly. Does anyone have
an idea what could be causing this?


1. Are all of your machines (DCs, member servers and workstaitions) only
using the internal DNS server's IP addresses in their ip configs?
2. Do you have one subnet or multiple subnets (locations)? If so, are you
using WINS?
3. Are your machines et to use an external DNS (such as an ISP, router's IP,
etc?
4. Is NetBIOS disabled?
5. Is the Browser service disabled?
6. Is the DHCP Client service disabled on any machine (DC or workstations)?
7. What event log errors exist on the workstations and DC? (Please post the
eventid# and Source names.)

Reason I ask the above quesitons is if there can be multiple reasons why
this is occuring starting with DNS misconfigs such as using an ISP's DNS
(querying an external DNS for an internal name is unlikley to return a
result), to NetBIOS and Master Browser issues, required services disabled,
and numerous others.

Other issues can cause this in conjunction with or besides DNS misconfigs,
such as a single label name domain, XP firewall tightened down too much, 3rd
party firewalls, security apps and antivirus apps, LSASRV and Userenv errors
on any of the machines (DCs and workstations), etc.

We just need to understand your config a little better to provide a more
accurate and relavent response.

Can you post an unedited ipconfig /all of a sample desktop this is happening
to as well as one of your DCs please?

Thanks,

--
Regards,
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer

For urgent issues, you may want to contact Microsoft PSS directly.
Please check http://support.microsoft.com for regional support phone
numbers.

Infinite Diversities in Infinite Combinations

.

Relevant Pages

  • Re: How to enable communication between Two different lans (subnets)/ domains 2003 server based? Ass
    ... You will also almost certainly have DNS problems running a domain behind ... server domain, with a DHCP server running on one of the 2003 boxes. ... the "inner" subnet can see the original subnet and the Internet, ... The .227 machines can see the machines on the 192.168.1.0 subnet and the ...
    (microsoft.public.windows.server.networking)
  • RE: suspicious firewall rules in WinXP firewall
    ... When that site got taken down, DNS ... suspicious firewall rules in WinXP firewall ... I can ping out of these two machines, ... World renowned security experts reveal tomorrow's threats today. ...
    (Incidents)
  • Re: Removing "permanently offline" DC...
    ... Make sure that at least one of these machines is a Global Catalog ... In the DNS console, use the DNS MMC to delete the cname ... If this was a DNS server before you brought it down, ... Event 13516 OR 13509 which indicate successful replication. ...
    (microsoft.public.windows.server.active_directory)
  • Re: ISA 2006 and Listeners Part 2!
    ... All machines use only the internal AD/DNS ... No machine should ever use any other DNS ... The AD/DNS machine will use the ISP's DNS in the ... Microsoft Internet Security & Acceleration Server: ...
    (microsoft.public.isa.configuration)
  • Re: 2 PCs not visible in net view or network browsing - Why?
    ... > it is the SAME as the Primary DNS suffix -- but this is NOT ... :yes some are public but behind firewall, so only visible to local domain.. ... Between the working machines ... > Are you using a DC for a router (multiple NICs)? ...
    (microsoft.public.win2000.networking)
Loading