Domain do not recognize DC

here you have the netdiag of our domain, its like the DC it is not registered at the DNS, but we have checked everything and it is.

The network is working fine, but when you click on the server at the domain it says that we are not allowed to see the network.


.....................................

    Computer Name: SERVER
    DNS Host Name: server.cosmani.local
    System info : Windows 2000 Server (Build 3790)
    Processor : x86 Family 15 Model 4 Stepping 3, GenuineIntel
    List of installed hotfixes :
        KB890046
        KB893756
        KB896358
        KB896422
        KB896424
        KB896428
        KB899587
        KB899588
        KB899589
        KB899591
        KB900725
        KB901017
        KB901214
        KB902400
        KB904706
        KB905414
        KB905915
        KB908519
        KB908531
        KB910437
        KB911562
        KB911564
        KB911565
        KB911567
        KB911927
        KB912812
        KB912919
        KB913446
        Q147222


Netcard queries test . . . . . . . : Passed
    [WARNING] The net card 'HP NC7782 Gigabit Server Adapter' may not be working.
    GetStats failed for 'Paralelo directo'. [ERROR_NOT_SUPPORTED]
    GetStats failed for 'Minipuerto WAN (PPTP)'. [ERROR_NOT_SUPPORTED]
    GetStats failed for 'Minipuerto WAN (PPPOE)'. [ERROR_NOT_SUPPORTED]
    [WARNING] The net card 'Minipuerto WAN (IP)' may not be working because it has not received any packets.
    GetStats failed for 'Minipuerto WAN (L2TP)'. [ERROR_NOT_SUPPORTED]



Per interface results:

    Adapter : Conexión de área local 2

        Netcard queries test . . . : Failed
        NetCard Status:          DISCONNECTED
            Some tests will be skipped on this interface.

        Host Name. . . . . . . . . : server
        Autoconfiguration IP Address : 169.254.43.108
        Subnet Mask. . . . . . . . : 255.255.0.0
        Default Gateway. . . . . . :
        Dns Servers. . . . . . . . :


    Adapter : Conexión de área local

        Netcard queries test . . . : Passed

        Host Name. . . . . . . . . : server.cosmani.local
        IP Address . . . . . . . . : 172.16.0.99
        Subnet Mask. . . . . . . . : 255.255.255.0
        Default Gateway. . . . . . : 172.16.0.1
        Dns Servers. . . . . . . . : 172.16.0.99


        AutoConfiguration results. . . . . . : Passed

        Default gateway test . . . : Passed

        NetBT name test. . . . . . : Passed
            No names have been found.

        WINS service test. . . . . : Skipped
            There are no WINS servers configured for this interface.


Global results:


Domain membership test . . . . . . : Passed


NetBT transports test. . . . . . . : Passed
    List of NetBt transports currently configured:
        NetBT_Tcpip_{4F045D60-0F7D-4748-A261-303F59D11451}
    1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed


IP loopback ping test. . . . . . . : Passed


Default gateway test . . . . . . . : Passed


NetBT name test. . . . . . . . . . : Passed
    [WARNING] You don't have a single interface with the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names defined.


Winsock test . . . . . . . . . . . : Passed


DNS test . . . . . . . . . . . . . : Failed
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'server.cosmani.local.'. [ERROR_TIMEOUT]
            The name 'server.cosmani.local.' may not be registered in DNS.
    [WARNING] The DNS entries for this DC are not registered correctly on DNS server '172.16.0.99'. Please wait for 30 minutes for DNS server replication.
    [FATAL] No DNS servers have the DNS records for this DC registered.


Redir and Browser test . . . . . . : Passed
    List of NetBt transports currently bound to the Redir
        NetBT_Tcpip_{4F045D60-0F7D-4748-A261-303F59D11451}
    The redir is bound to 1 NetBt transport.

    List of NetBt transports currently bound to the browser
        NetBT_Tcpip_{4F045D60-0F7D-4748-A261-303F59D11451}
    The browser is bound to 1 NetBt transport.


DC discovery test. . . . . . . . . : Passed


DC list test . . . . . . . . . . . : Failed
        Failed to enumerate DCs by using the browser. [ERROR_NO_BROWSER_SERVERS_FOUND]


Trust relationship test. . . . . . : Skipped


Kerberos test. . . . . . . . . . . : Passed


LDAP test. . . . . . . . . . . . . : Passed


Bindings test. . . . . . . . . . . : Passed


WAN configuration test . . . . . . : Skipped
    No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

    Note: run "netsh ipsec dynamic show /?" for more detailed information


The command completed successfully
zaldivar05Asked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
Rob WilliamsConnect With a Mentor Commented:
The earlier errors may be mis-leading. It may not be "its like the DC it is not registered at the DNS", but rather a duplicate/conflicting entry.
A 169.254.x.x address means that a network card is set to obtain and IP automatically and is not finding a DHCP server. That in itself is not a problem, but it appears that this IP and the server name have registered themselves in DNS, and I'm willing to bet they are at the top of the binding order.
-If you have 2 network adapters I would disable the one not in use (right click on it and choose disable). If not, the entry must have been made at a time when it could not connect.
-Make sure the server is assigned a static IP, I assume it is the 172.16.0.108
-Open the DNS management console and under the forward and reverse DNS zones delete any entries relating to the 168.254.x.x IP . There should be matching ones in forward and reverse zones.
-Go to control panel | network settings | (on the menu bar) advanced | advanced settings | adapters and bindings | move the adapter (if 2) with the 172.x.x.x address to the top of the list
0
 
MasPreguntasCommented:
Perhaps is some sort of permissions problem. When it says you are not allowed to see the network that makes  me think its something with permissions. How are you clicking on the server, from what PC, what user account and can you logon to the DC? Have you tried connecting to it via "\\servername" or "\\ip address of server"?
0
 
zaldivar05Author Commented:
there is no problem when you log on a workstation. You can see the network fine, you can click on the server and see the share folders, you can loggin in to the network, you can connect with \\servername and \\ip.address of server. You can see al the computers at the network

The only problem is the server itself. when you click on the domain it says you dont have the rights to see the domain.

It should be something with the DNS as the netdiag say it

DNS test . . . . . . . . . . . . . : Failed
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'server.cosmani.local.'. [ERROR_TIMEOUT]
            The name 'server.cosmani.local.' may not be registered in DNS.
    [WARNING] The DNS entries for this DC are not registered correctly on DNS server '172.16.0.99'. Please wait for 30 minutes for DNS server replication.
    [FATAL] No DNS servers have the DNS records for this DC registered.
0
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 
jpdaveyCommented:
In your DNS zone for that domain do you have the _msdcs, _sites, etc. folders?

Do you have a Event Log entry saying something about SYSVOL being fixed or created or something like that and to wait until it's done before it allows the server to be a domain controller?

Do you have a System State backup of that server from before this started happening?

Is this the only DC in your domain? If not, you might be able to fix it by removing AD (if it lets you) then adding it again.

Just some thoughts.

JP
0
 
zaldivar05Author Commented:
I have a DNS warning

Error Id 5782

There are not DNS configured for local system.


This is the only DC, but we had before another DC. This was the secondary server that we promoted when we took the other server out.

This started happening since we took the old server out so we do not have system state backup.


This is how the dnsmgmt tree looks like

direct zone

    - _msdcs.cosmani.local
            - dc
                  - sites
                  - _tcp
            - domains
                  - 93a4a47a.....
            - gc
                  - _sites
                  - _tcp
             - pdc
                 - _tcp

     - cosmani.local
             - _sites
                   - nombre-predeterminado
             - _tcp
             - _udp
             - DomainDnsZones  
                    - _sites
                    - _tcp
             - ForestDnsZones
                    - _sites
                    - _tcp

           
    - cosmani.local



0
 
Rob WilliamsCommented:
You can get a "Cannot find a primary authoritative DNS server for the name" error if the server's DNS is pointing to an ISP rather than itself, even if it is secondary DNS. Just to be sure, verify all is configured correctly with the checklist below. Once done I would recommend running  netdiag  /fix

------------------------------
Assuming you have completed the server installation, installed Active Directory, and joined the workstations to the Domain, make sure DNS is configured as follows, assuming a single network adapter:
-The server's NIC should be configured with a static IP, the Internet router as the gateway, and only the server itself as the DNS server. Do not use an ISP DNS server here
-Each workstation should be configured using DHCP (obtain and IP address and DNS automatically) or if configured with static addresses; a static IP in the same subnet as the server, same subnet mask as the server, the gateway pointing to your Internet router, and the DNS server pointing ONLY to the server/domain controller. Again do not put an ISP's DNS server here
-In the DNS management console under Administrative tools, right click on the server name and choose properties. On the Forwarders tab add your ISP's DNS servers
-If the workstations are using DHCP, open the DHCP management console on the server under Administrative tools and click on the server name to expand it, click on the scope to expand it, right click on scope options and choose configure options. On the general tab add the Internet router's IP in #003 router, the server's IP in #006 DNS Servers, and the domain name and suffix under #015 such as mydomain.local
-If  DHCP is enabled on the router, rather than the server, it should really be disabled on the router and configured on the server. Enabling DHCP on the server allows for dynamic updates to DNS
-The DHCP client service should be running on servers and workstations even where you are not using DHCP assignments. The DHCP client service controls the dynamic DNS updates

If you have been having DNS problems, on the workstations that have been having problems you should clear the DNS cache by entering at a command line
  ipconfig  /flushdns
and then
  ipconfig  /registerdns


0
 
micromarchCommented:
start and stop the netlogon service if your srv records are blank.
0
 
micromarchCommented:
make sure there are no records left in dns of the old retired server you braught down. are your zone active directory integrated?
0
 
jpdaveyCommented:
Oh, yeah, like RobWill said, make sure your AD server is ONLY pointing at itself for DNS in it's NIC's IP settings.
0
 
micromarchCommented:
lol
0
 
zaldivar05Author Commented:
all the points robwill wrote were ok at the server.

I run ipconfig /flushdns and ipconfig /registerdns and then netdiag /fix

now the netdiag looks as follws, it gives the same warning but now the test passed, and then netBT test that was ok before now fails.

NetBT name test. . . . . . : Failed
            \Device\NetBT_Tcpip_{82284442-F133-4DA3-B0B1-05446F22EE9A}
        [FATAL] At least one of your NetBT names is not registered properly.
                You have a potential name conflict.
                Please check that the machine name is unique.
        [WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names is missing.

NetBT name test. . . . . . . . . . : Failed
    [WARNING] You don't have a single interface with the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names defined.

DNS test . . . . . . . . . . . . . : Passed
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'server.cosmani.local.'. [ERROR_TIMEOUT]
            The name 'server.cosmani.local.' may not be registered in DNS.
    PASS - All the DNS entries for DC are registered on DNS server '172.16.0.99' and other DCs also have some of the names registered.


0
 
Rob WilliamsCommented:
One thought, check that the LAN or private network adapter is the first in the binding order, I assume "Conexión de área local" IP 172.16.0.99. To do so go to Control panel | network connections | (on the menu bar) advanced | Advanced settings | Binding order | if the above adapter is not at the top of the list try moving it there.
Then again try:
ipconfig  /flushdns
ipconfig  /registerdns
netdiag /fix
0
 
zaldivar05Author Commented:
the network adapter was not the first in the binding order, I moved in first possition, rune ipconfig and netdiag /fix but still the same errors at the netdiag log.

Now one thing is fixed, when I go into my local area network I can browse all the clients although it took a while thinking before It could browse them.

0
 
Rob WilliamsCommented:
1) My next recommendation would be to verify the following services are running on the server in the services management console. They should be set to automatic and started; computer browser, workstation and server services.

2) Then run on the domain controller dcdiag which is available from the Windows resource kit or from:
  http://www3.ns.sympatico.ca/malagash/Downloads/Net/dcdiag.exe

3) Run netdiag again but in the verbose mode:
  netdiag  /debug
0
 
zaldivar05Author Commented:
all those services are up. netdiag /debug did not solve it. I have the same errors

also I paste the errors I got with the dcdiag

all the test passed but this one.

   Starting test: systemlog
         An Error Event occured.  EventID: 0xC0002725
            Time Generated: 05/16/2006   20:43:00
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0xC0002725
            Time Generated: 05/16/2006   20:43:00
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0xC0002725
            Time Generated: 05/16/2006   20:43:00
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 05/16/2006   21:05:19
            (Event String could not be retrieved)
         ......................... SERVER failed test systemlog
0
 
Rob WilliamsCommented:
netdiag /debug, won't repair anything it just has a lengthier output which might better explain the errors.

As for your other results from dcdiag could you post a little more detail of the error sections, I am afraid the above is not enough for me to try to help diagnose. Also looks like it was writing errors to the System log in the event viewer. Perhaps open the event viewer and look for the event ID #'s (should be 2 to 4 digit #'1) and the Source name, of any related errors.
0
 
zaldivar05Author Commented:
ok, this is what I get with netdiag /debug

NetBT name test. . . . . . : Failed
            NetBT_Tcpip_{82284442-F133-4DA3-B0B1-05446F22EE9A}
            SERVER         <00>  UNIQUE      CONFLICT
            COSMANI        <00>  GROUP       REGISTERED
            COSMANI        <1C>  GROUP       REGISTERED
            SERVER         <20>  UNIQUE      CONFLICT
            COSMANI        <1B>  UNIQUE      REGISTERED
            COSMANI        <1E>  GROUP       REGISTERED
            COSMANI        <1D>  UNIQUE      REGISTERED
            ..__MSBROWSE__.<01>  GROUP       REGISTERED
        [FATAL] At least one of your NetBT names is not registered properly.
                You have a potential name conflict.
                Please check that the machine name is unique.
        [WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names is missing.


********** * ********** * ********** * ********** * ********** *
* CHECK NAME cosmani.local. on DNS server 172.16.0.99
********** * ********** * ********** * ********** * ********** *

The Record is different on DNS server '172.16.0.99'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '172.16.0.99', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = cosmani.local.
DNS DATA =
            A  169.254.43.108

The record on DNS server 172.16.0.99 is:
DNS NAME = cosmani.local
DNS DATA =
            A  172.16.0.99
            A  169.254.43.108
+------------------------------------------------------+


********** * ********** * ********** * ********** * ********** *
* CHECK NAME gc._msdcs.cosmani.local. on DNS server 172.16.0.99
********** * ********** * ********** * ********** * ********** *

The Record is different on DNS server '172.16.0.99'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '172.16.0.99', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = gc._msdcs.cosmani.local.
DNS DATA =
            A  169.254.43.108

The record on DNS server 172.16.0.99 is:
DNS NAME = gc._msdcs.cosmani.local
DNS DATA =
            A  172.16.0.99
            A  169.254.43.108
+------------------------------------------------------+


********** * ********** * ********** * ********** * ********** *
* CHECK NAME DomainDnsZones.cosmani.local. on DNS server 172.16.0.99
********** * ********** * ********** * ********** * ********** *

The Record is different on DNS server '172.16.0.99'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '172.16.0.99', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = DomainDnsZones.cosmani.local.
DNS DATA =
            A  169.254.43.108

The record on DNS server 172.16.0.99 is:
DNS NAME = DomainDnsZones.cosmani.local
DNS DATA =
            A  172.16.0.99
            A  169.254.43.108
+------------------------------------------------------+


********** * ********** * ********** * ********** * ********** *
* CHECK NAME ForestDnsZones.cosmani.local. on DNS server 172.16.0.99
********** * ********** * ********** * ********** * ********** *

The Record is different on DNS server '172.16.0.99'.
DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain.
Your DC entry is one of them on DNS server '172.16.0.99', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = ForestDnsZones.cosmani.local.
DNS DATA =
            A  169.254.43.108

The record on DNS server 172.16.0.99 is:
DNS NAME = ForestDnsZones.cosmani.local
DNS DATA =
            A  172.16.0.99
            A  169.254.43.108
+------------------------------------------------------+

DC list test . . . . . . . . . . . : Failed
        Failed to enumerate DCs by using the browser. [ERROR_NO_BROWSER_SERVERS_FOUND]
    List of DCs in Domain 'COSMANI':
        server.cosmani.local

0
 
zaldivar05Author Commented:
We join both network cards with a server application to balance weight and now there is no errors at netdiag. It should have been a netlan conflict between the two nics or something like that.

0
 
Rob WilliamsCommented:
Excellent, glad to hear it is resolved.
Thanks,
--Rob
0
All Courses

From novice to tech pro — start learning today.