Computers cannot enter the domain share. Security threat. How to fix?

Question

Domain Name System

Previously:
The Internet cable went to the server (windows server 2003), from the second network card the cable went to the hub. Everything worked.
One person corrected this situation
Now: The Internet cable goes to the router (192.168.1.1) and the router distributes IP (192.168.1.2 - 192.168.1.250), the server (windows server 2003) is connected to the network, it received a new IP 192.168.1.10, on it the domain controller is raised, all computers on the network have changed the subnet.
After these actions, the person who changed the network called n actions.
The problem is that computers have stopped entering each other's ball. Require Authorization. They come in by IP.

Microsoft Windows [Версия 5.2.3790]
(С) Корпорация Майкрософт, 1985-2003.

C:\Documents and Settings\Администратор.MAIN.000>netdiag

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

    Computer Name: MAIN
    DNS Host Name: main.ind.domain
    System info : Microsoft Windows Server 2003 R2 (Build 3790)
    Processor : x86 Family 6 Model 58 Stepping 9, GenuineIntel
    List of installed hotfixes :
        KB2570791
        Q147222


Netcard queries test . . . . . . . : Passed
    GetStats failed for '╧Ё ьющ ярЁрыыхы№э√щ яюЁЄ'. [ERROR_NOT_SUPPORTED]
    [WARNING] The net card '╠шэшяюЁЄ WAN (PPTP)' may not be working because it h
as not received any packets.
    [WARNING] The net card '╠шэшяюЁЄ WAN (PPPoE)' may not be working because it
has not received any packets.
    [WARNING] The net card '╠шэшяюЁЄ WAN (IP)' may not be working because it has
 not received any packets.
    GetStats failed for '╠шэшяюЁЄ WAN (L2TP)'. [ERROR_NOT_SUPPORTED]
    [WARNING] The net card '╠шэшяюЁЄ WAN (IP) - Kaspersky Anti-Virus NDIS Minipo
rt' may not be working because it has not received any packets.



Per interface results:

    Adapter : local

        Netcard queries test . . . : Passed

        Host Name. . . . . . . . . : main.IND
        IP Address . . . . . . . . : 192.168.1.10
        Subnet Mask. . . . . . . . : 255.255.255.0
        Default Gateway. . . . . . : 192.168.1.1
        Primary WINS Server. . . . : 192.168.1.1
        Dns Servers. . . . . . . . : 192.168.1.1


        AutoConfiguration results. . . . . . : Passed

        Default gateway test . . . : Passed

        NetBT name test. . . . . . : Passed
        [WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenge
r Service', <20> 'WINS' names is missing.

        WINS service test. . . . . : Failed
            The test failed.  We were unable to query the WINS servers.


Global results:


Domain membership test . . . . . . : Passed


NetBT transports test. . . . . . . : Passed
    List of NetBt transports currently configured:
        NetBT_Tcpip_{D7954B69-53EA-4C96-8FB5-7142272ADE1A}
    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 Servi
ce', <03> 'Messenger Service', <20> 'WINS' names defined.


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


DNS test . . . . . . . . . . . . . : Failed
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'main.ind.domain.'. [RCODE_SERVER_FAILURE]
            The name 'main.ind.domain.' may not be registered in DNS.
    [WARNING] The DNS entries for this DC are not registered correctly on DNS se
rver '192.168.1.1'. 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_{D7954B69-53EA-4C96-8FB5-7142272ADE1A}
    The redir is bound to 1 NetBt transport.

    List of NetBt transports currently bound to the browser
        NetBT_Tcpip_{D7954B69-53EA-4C96-8FB5-7142272ADE1A}
    The browser is bound to 1 NetBt transport.


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


DC list test . . . . . . . . . . . : Passed


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

C:\Documents and Settings\Администратор.MAIN.000>

dcdiag

Microsoft Windows [Версия 5.2.3790]
(С) Корпорация Майкрософт, 1985-2003.

C:\Documents and Settings\Администратор.MAIN.000>dcdiag

Domain Controller Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site-Name\MAIN
      Starting test: Connectivity
         The host f1d40bd1-cd40-472a-b9ba-c17ee6078e6b._msdcs.ind.domain coul
d not be resolved to an
         IP address.  Check the DNS server, DHCP, server name, etc
         Although the Guid DNS name
         (f1d40bd1-cd40-472a-b9ba-c17ee6078e6b._msdcs.ind.domain) couldn't
         be resolved, the server name (main.ind.domain) resolved to the IP
         address (192.168.1.10) and was pingable.  Check that the IP address is
         registered correctly with the DNS server.
         ......................... MAIN failed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\MAIN
      Skipping all tests, because server MAIN is
      not responding to directory service requests

   Running partition tests on : ForestDnsZones
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom

   Running partition tests on : DomainDnsZones
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom

   Running partition tests on : Schema
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom

   Running partition tests on : Configuration
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom

   Running partition tests on : ind
      Starting test: CrossRefValidation
         ......................... ind passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... ind passed test CheckSDRefDom

   Running enterprise tests on : ind.domain
      Starting test: Intersite
         ......................... ind.domain passed test Intersite
      Starting test: FsmoCheck
         ......................... ind.domain passed test FsmoCheck

C:\Documents and Settings\Администратор.MAIN.000>

In the settings of client machines, the gateway and DNS are 192.168.1.1

Answer 1

Why do clients have a gateway address in dns, and not a domain controller?

Answer 2

The WINS and DNS server you have specified is the gateway, not the winserver, netdiag polls the network and the gateway, takes information from the gateway and gives it to you. Try to manually fill in DNS and WINS on the router with the address of the winserver.