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

Sorry it has taken me so long to respond this time but I think you are
correct when you said that it may be a Site issue. I don’t seem to be
making much headway in resolving issue because I am spending most of my time
trying to keep users operational. The symptoms keep compounding every day.
There is a partially configured Default-First-Site but most of the objects
have not been modified since they were created. I have placed a support
call request but it will be tomorrow before they can phone support. I am
still trying to find an article to help me troubleshoot the problem or
correct my mistakes more likely.
I was also wrong about repairing the DSRM password, when I fallow the KB
322672 instructions I receive a messaging saying the password has
successfully changed but when I restart the DC the 1005 dsrestor error
appears again.
If you have any suggestion I would greatly appreciate them.


"Ace Fekay [MVP Direcrtory Services]" wrote:

In news:55CE7392-5CDA-4178-B409-CB88E876385D@xxxxxxxxxxxxx,
JCCIT <JCCIT@xxxxxxxxxxxxxxxxxxxxxxxxx> requesting assistance, typed the
following:
Thanks for responding

In regards to the JCDC02 1005 dsrestor error I reset the password as
outlined in KB 322672?


Yes, that will work.



Port 445 is not blocked on any server or PC but I had to increase the
connection time out and listen timeout
times to their maximum in Solarwinds port scanning to get the
majority to respond correctly.

Interesting. Never seen this problem that I would have needed to make such a
change.



For the workstations that are having the problem there is a DNS
record for each in the Forward Lookup table and Reverse Lookup table.
Both are also able to resolve using nslookup and pinging the computer
name. There no enabled firewall on the workstations.
Although when I do a nslookup on the domain I am receiving the
fallowing and am not sure why 10.14.73.38 is showing up it is a DHCP
server on our VOIP VLAN.

C:\>nslookup \\jacksoncountywv.local
Server: jcdc02.jacksoncountywv.local
Address: 10.35.18.211

Name: jacksoncountywv.local
Addresses: 10.35.18.210, 10.35.18.211, 10.14.73.38


It seems that 10.14.73.38 is a DC as well, and if it is, this is normal
behavior because each DC will register an LdapIpAddress that looks like:
(same as parent) A 10.14.73.38

It appear to clean this up, AD Sites must be configured. This subnet should
be in it's own Site so the machines will not query any DCs outside the site,
unless of course all DCs do not respond in it;'s own site and at which case,
will look for a DC outside the site. I assume at least one of the DCs on
this subnet is a GC.



You are correct in your assumption that the subnet is not bridged to
another VLAN.

This PC taxpc04 is working correctly this today, the only thing that
has been done to try to correct the errors were to reboot both DCs
and both workstations. Assessor06 is still having the same symptoms.

C:\>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : taxpc04
Primary Dns Suffix . . . . . . . : jacksoncountywv.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : jacksoncountywv.local
jacksoncountywv.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : jacksoncountywv.local
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
Ethernet
Physical Address. . . . . . . . . : 00-16-35-61-07-EF
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.35.18.68
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.35.18.1
DHCP Server . . . . . . . . . . . : 10.35.18.216
DNS Servers . . . . . . . . . . . : 10.35.18.210
10.35.18.211
NetBIOS over Tcpip. . . . . . . . : Disabled
Lease Obtained. . . . . . . . . . : Wednesday, September 10,
2008 8:41:2
8 PM
Lease Expires . . . . . . . . . . : Thursday, September 18,
2008 8:41:28
PM


This looks fine. It may come down to a Site issue. Are AD Sites configured?

Ace

.

Relevant Pages

  • Re: Choosing which DC to logon to
    ... For the sake of simplicity I mentioned I had 1 DC in the seperate subnet, ... two for domain logon etc. ... workstations are not allowed access to the subnet with 2 DC's.The ... Either let all clients get to the DCs freely or separate them into Sites ...
    (microsoft.public.windows.server.active_directory)
  • Re: ADS Sites and Services issue
    ... Do you have any problems with clients in other sites? ... DCs from subnet A. Clients from subnet B should in this case authenticate on ... authenticate on their local DCs. ... I put the servers in subnet A, and the workstations in subnet B. Both ...
    (microsoft.public.windows.server.active_directory)
  • Re: ADS Sites and Services issue
    ... Yes, subnet A and subnet B are both associated with the same site, and ... the DCs are located within that site as well. ... I put the servers in subnet A, and the workstations in subnet B. Both ... I query my domain name through nslookup and it only responds ...
    (microsoft.public.windows.server.active_directory)
  • Re: Which TCP/IP settings critical to join domain?
    ... the DCs are not configured with DNS. ... > the remote workstations lacked, ... > - workstations on the local subnet had no difficulty finding/joining yyy ...
    (microsoft.public.win2000.networking)
  • Re: Changing from 1 NIC to 2 NICs
    ... The workstations point to the int nic for dns and that's all the ... Here's sample output: ... i think I get the picture now on the subnet issue. ... internal nic to a 10.3.16.x configuration. ...
    (microsoft.public.windows.server.sbs)