Solved

DNS Problem

Posted on 2006-11-08
16
651 Views
Last Modified: 2012-06-27
We have 2 DCs. Called 'PDC' and 'BDC'. Our domain is called 'ourdomain.com'. PDC HAS AD and DNS installed. BDC has AD installed but no DNS.

Can't connect to AD on BDC.
BDC cannot find SERVER2 (network interface is correct and pointing to the DNS on PDC) when browsing the network.
BDC can ping PDC.
PDC can ping BDC.

It appears that the IP address for the BDC (192.168.0.4) is appearing as an additional Host (A) record in the DNS on PDC (192.168.0.9). Therefore there may be some conflict and the PDC thinks that it is the BDC also.

I've ran DCDIAG -V and here are the results:


    Gathering IPX configuration information.
    Querying status of the Netcard drivers... Passed
    Testing Domain membership... Passed
    Gathering NetBT configuration information.
    Testing for autoconfiguration... Passed
    Testing IP loopback ping... Passed
    Testing default gateways... Passed
    Enumerating local and remote NetBT name cache... Passed
    Testing the WINS server
        Local Area Connection
            There is no primary WINS server defined for this adapter.
            There is no secondary WINS server defined for this adapter.
    Gathering Winsock information.
    Testing DNS
          The DNS registration for pdc.ourdomain.com is correct on all DNS servers
    PASS - All the DNS entries for DC are registered on DNS server '192.168.0.9' and other DCs also have some of the names registered.
    Testing redirector and browser... Passed
    Testing DC discovery.
        Looking for a DC
    Gathering the list of Domain Controllers for domain 'ourdomain'
    Testing trust relationships... Skipped
    Testing Kerberos authentication... Failed
    Testing LDAP servers in Domain ourdomain ...
    Gathering routing information
    Gathering network statistics information.
    Gathering configuration of bindings.
    Gathering RAS connection information
    Gathering Modem information
    Gathering Netware information
    Gathering IP Security information

    Tests complete.


    Computer Name: pdc
    DNS Host Name: pdc.ourdomain.com
    DNS Domain Name: ourdomain.com
    System info : Windows 2000 Server (Build 2195)
    Processor : x86 Family 15 Model 4 Stepping 4, GenuineIntel
    Hotfixes :
        Installed?      Name
           Yes          KB329115
           Yes          KB822343
           Yes          KB823182
           Yes          KB823559
           Yes          KB824105
           Yes          KB825119
           Yes          KB826232
           Yes          KB828035
           Yes          KB828749
           Yes          KB832353
           Yes          KB832359
           Yes          KB841356
           Yes          KB842773
           Yes          KB883935
           Yes          KB885836
           Yes          KB890046
           Yes          KB893756
           Yes          KB893803v2
           Yes          KB896358
           Yes          KB896422
           Yes          KB896423
           Yes          KB896424
           Yes          KB899587
           Yes          KB899589
           Yes          KB899591
           Yes          KB900725
           Yes          KB901017
           Yes          KB901214
           Yes          KB902400
           Yes          KB904706
           Yes          KB905414
           Yes          KB905495-IE6SP1-20050805.184113
           Yes          KB905749
           Yes          KB905915-IE501SP4-20051122.191609
           Yes          KB908519
           Yes          KB908523
           Yes          KB908531
           Yes          KB910620-IE501SP4-20060112.143924
           Yes          KB911280
           Yes          KB911564
           Yes          KB911567-OE55SP2-20060317.162653
           Yes          KB911567-OE6SP1-20060316.165634
           Yes          KB912919
           Yes          KB913580
           Yes          KB914388
           Yes          KB914389
           Yes          KB917008
           Yes          KB917159
           Yes          KB917422
           Yes          KB917537
           Yes          KB917736
           Yes          KB917953
           Yes          KB918899-IE6SP1-20060725.123917
           Yes          KB920670
           Yes          KB920683
           Yes          KB920685
           Yes          KB920958
           Yes          KB921398
           Yes          KB921883
           Yes          KB922582
           Yes          KB922616
           Yes          KB923191
           Yes          KB923414
           Yes          KB924191
           Yes          KB925486-IE6SP1-20060918.120000
           Yes          Q147222
           Yes          Q828026
           No           ServicePackUninstall
           Yes          Update Rollup 1


Netcard queries test . . . . . . . : Passed

    Information of Netcard drivers:

    ---------------------------------------------------------------------------
    Description: Intel(R) PRO/1000 MT Network Connection - Packet Scheduler Miniport
    Device: \DEVICE\{98E85B6B-81CD-4DEC-82E6-07F3933C58BD}

    Media State:                     Connected

    Device State:                    Connected
    Connect Time:                    00:36:12
    Media Speed:                     1000 Gbps

    Packets Sent:                    8631
    Bytes Sent (Optional):           0

    Packets Received:                8301
    Directed Pkts Recd (Optional):   5833
    Bytes Received (Optional):       0
    Directed Bytes Recd (Optional):  0

    ---------------------------------------------------------------------------
    Description: Intel(R) PRO/1000 MT Network Connection
    Device: \DEVICE\{BC1D0A54-5B6C-4147-BB38-D7A2D5930333}

    Media State:                     Connected

    Device State:                    Connected
    Connect Time:                    00:36:14
    Media Speed:                     1000 Gbps

    Packets Sent:                    8631
    Bytes Sent (Optional):           0

    Packets Received:                8301
    Directed Pkts Recd (Optional):   5833
    Bytes Received (Optional):       0
    Directed Bytes Recd (Optional):  0

    ---------------------------------------------------------------------------
    [PASS] - At least one netcard is in the 'Connected' state.



Per interface results:

    Adapter : Local Area Connection
        Adapter ID . . . . . . . . : {BC1D0A54-5B6C-4147-BB38-D7A2D5930333}

        Netcard queries test . . . : Passed

        Adapter type . . . . . . . : Ethernet
        Host Name. . . . . . . . . : pdc
        Description. . . . . . . . : Intel(R) PRO/1000 MT Network Connection (Microsoft's Packet Scheduler)
        Physical Address . . . . . : 00-15-F2-0B-3A-26
        Dhcp Enabled . . . . . . . : No
        DHCP ClassID . . . . . . . :
        Autoconfiguration Enabled. : Yes
        IP Address . . . . . . . . : 192.168.0.9
        Subnet Mask. . . . . . . . : 255.255.255.0
        Default Gateway. . . . . . : 192.168.0.1
        Dns Servers. . . . . . . . : 192.168.0.9

        IpConfig results . . . . . : Passed

        AutoConfiguration results. . . . . . : Passed
            AutoConfiguration is not in use.

        Default gateway test . . . : Passed
            Pinging gateway 192.168.0.1 - reachable
            At least one gateway reachable for this adapter.

        NetBT name test. . . . . . : Passed
            NetBT_Tcpip_{BC1D0A54-5B6C-4147-BB38-D7A2D5930333}
            pdc        <00>  UNIQUE      REGISTERED
            ourdomain  <00>  GROUP       REGISTERED
            ourdomain  <1C>  GROUP       REGISTERED
            pdc        <20>  UNIQUE      REGISTERED
            ourdomain  <1B>  UNIQUE      REGISTERED
            ourdomain  <1E>  GROUP       REGISTERED
            pdc        <03>  UNIQUE      REGISTERED
            ourdomain  <1D>  UNIQUE      REGISTERED
            ..__MSBROWSE__.<01>  GROUP       REGISTERED
            INet~Services  <1C>  GROUP       REGISTERED
            IS~pdc.....<00>  UNIQUE      REGISTERED
            ADMINISTRATOR  <03>  UNIQUE      REGISTERED

            NetBios Resolution : Enabled

            Netbios Remote Cache Table
            Name           Type              HostAddress         Life [sec]
            ---------------------------------------------------------------
            ourdomain  <1C>  GROUP       192.168.0.4           402


        WINS service test. . . . . : Skipped
            There is no primary WINS server defined for this adapter.
            There is no secondary WINS server defined for this adapter.
            There are no WINS servers configured for this interface.
        IPX test : IPX is not installed on this machine.


Global results:


IP General configuration
    LMHOSTS Enabled. . . . . . . . : Yes
    DNS for WINS resolution. . . . : Enabled
    Node Type. . . . . . . . . . . : Hybrid
    NBT Scope ID . . . . . . . . . :
    Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled . . . . . . : No
    DNS resolution for NETBIOS . . : No



Domain membership test . . . . . . : Failed
    [WARNING] Ths system volume has not been completely replicated to the local machine. This machine is not working properly as a DC.
    Machine is a . . . . . . . . . : Primary Domain Controller Emulator
    Netbios Domain name. . . . . . : ourdomain
    Dns domain name. . . . . . . . : ourdomain.com
    Dns forest name. . . . . . . . : ourdomain.com
    Domain Guid. . . . . . . . . . : {FB2ECE95-7ACB-4600-92C7-088A05F98148}
    Domain Sid . . . . . . . . . . : S-1-5-21-1498383394-3377977846-3067083130
    Logon User . . . . . . . . . . : administrator
    Logon Domain . . . . . . . . . : ourdomain


NetBT transports test. . . . . . . : Passed
    List of NetBt transports currently configured:
        NetBT_Tcpip_{BC1D0A54-5B6C-4147-BB38-D7A2D5930333}
    1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed
    PASS - you have at least one non-autoconfigured IP address


IP loopback ping test. . . . . . . : Passed
    PASS - pinging IP loopback address was successful.
    Your IP stack is most probably OK.


Default gateway test . . . . . . . : Passed
    PASS - you have at least one reachable gateway.


NetBT name test. . . . . . . . . . : Passed
   No NetBT scope defined

   PASS - The NetBT is properly configured.
     There is at least one interface where the <00> 'WorkStation Service',
     <03> 'Messenger Service', <20> 'WINS' names are defined and they are
     not in conflict.


Winsock test . . . . . . . . . . . : Passed
    The number of protocols which have been reported : 17
        Description: MSAFD Tcpip [TCP/IP]
            Provider Version   :2
            Max message size  : Stream Oriented
        Description: MSAFD Tcpip [UDP/IP]
            Provider Version   :2
        Description: RSVP UDP Service Provider
            Provider Version   :4
        Description: RSVP TCP Service Provider
            Provider Version   :4
            Max message size  : Stream Oriented
        Description: MSAFD AppleTalk [ADSP]
            Provider Version   :2
        Description: MSAFD AppleTalk [ADSP] [Pseudo Stream]
            Provider Version   :2
            Max message size  : Stream Oriented
        Description: MSAFD AppleTalk [PAP]
            Provider Version   :2
        Description: MSAFD AppleTalk [RTMP]
            Provider Version   :2
            Max message size  : Stream Oriented
        Description: MSAFD AppleTalk [ZIP]
            Provider Version   :2
            Max message size  : Stream Oriented
        Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{BC1D0A54-5B6C-4147-BB38-D7A2D5930333}] SEQPACKET 0
            Provider Version   :2
        Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{BC1D0A54-5B6C-4147-BB38-D7A2D5930333}] DATAGRAM 0
            Provider Version   :2
        Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{EE7F9783-7BA0-41E6-913C-1669CFDF7F11}] SEQPACKET 3
            Provider Version   :2
        Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{EE7F9783-7BA0-41E6-913C-1669CFDF7F11}] DATAGRAM 3
            Provider Version   :2
        Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{04DC68E8-AD60-40EB-B81F-CDB2A07065E1}] SEQPACKET 1
            Provider Version   :2
        Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{04DC68E8-AD60-40EB-B81F-CDB2A07065E1}] DATAGRAM 1
            Provider Version   :2
        Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{B4168FB2-8DA7-4D2C-9411-88BD4CB0205B}] SEQPACKET 2
            Provider Version   :2
        Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{B4168FB2-8DA7-4D2C-9411-88BD4CB0205B}] DATAGRAM 2
            Provider Version   :2

    Max UDP size : 65507 bytes


DNS test . . . . . . . . . . . . . : Passed
      Interface {BC1D0A54-5B6C-4147-BB38-D7A2D5930333}
        DNS Domain:
        DNS Servers: 192.168.0.9
        IP Address: 192.168.0.9
        Expected registration with PDN (primary DNS domain name):
          Hostname: pdc.ourdomain.com.
          Authoritative zone: ourdomain.com.
          Primary DNS server: pdc.ourdomain.com 192.168.0.9
          Authoritative NS:192.168.0.9
      Verify DNS registration:
        Name: pdc.ourdomain.com
        Expected IP: 192.168.0.9
          Server 192.168.0.9: NO_ERROR
    The DNS registration for pdc.ourdomain.com is correct on all DNS servers
Check the DNS registration for DCs entries on DNS server '192.168.0.9'
The Record is different on DNS server '192.168.0.9'.
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 '192.168.0.9', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = ourdomain.com.
DNS DATA =
            A  192.168.0.9

The record on DNS server 192.168.0.9 is:
DNS NAME = ourdomain.com
DNS DATA =
            A  192.168.0.9
            A  192.168.0.4
+------------------------------------------------------+

The Record is different on DNS server '192.168.0.9'.
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 '192.168.0.9', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.ourdomain.com.
DNS DATA =
            SRV 0 100 389 pdc.ourdomain.com.

The record on DNS server 192.168.0.9 is:
DNS NAME = _ldap._tcp.ourdomain.com
DNS DATA =
            SRV 0 100 389 bdc.ourdomain.com
            SRV 0 100 389 pdc.ourdomain.com
+------------------------------------------------------+

The Record is different on DNS server '192.168.0.9'.
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 '192.168.0.9', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.ourdomain.com.
DNS DATA =
            SRV 0 100 389 pdc.ourdomain.com.

The record on DNS server 192.168.0.9 is:
DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.ourdomain.com
DNS DATA =
            SRV 0 100 389 bdc.ourdomain.com
            SRV 0 100 389 pdc.ourdomain.com
+------------------------------------------------------+

The Record is different on DNS server '192.168.0.9'.
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 '192.168.0.9', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.fb2ece95-7acb-4600-92c7-088a05f98148.domains._msdcs.ourdomain.com.
DNS DATA =
            SRV 0 100 389 pdc.ourdomain.com.

The record on DNS server 192.168.0.9 is:
DNS NAME = _ldap._tcp.fb2ece95-7acb-4600-92c7-088a05f98148.domains._msdcs.ourdomain.com
DNS DATA =
            SRV 0 100 389 bdc.ourdomain.com
            SRV 0 100 389 pdc.ourdomain.com
+------------------------------------------------------+

The Record is correct on DNS server '192.168.0.9'.

The Record is different on DNS server '192.168.0.9'.
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 '192.168.0.9', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.dc._msdcs.ourdomain.com.
DNS DATA =
            SRV 0 100 88 pdc.ourdomain.com.

The record on DNS server 192.168.0.9 is:
DNS NAME = _kerberos._tcp.dc._msdcs.ourdomain.com
DNS DATA =
            SRV 0 100 88 bdc.ourdomain.com
            SRV 0 100 88 pdc.ourdomain.com
            SRV 0 100 88 server.ourdomain.com
+------------------------------------------------------+

The Record is different on DNS server '192.168.0.9'.
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 '192.168.0.9', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.ourdomain.com.
DNS DATA =
            SRV 0 100 88 pdc.ourdomain.com.

The record on DNS server 192.168.0.9 is:
DNS NAME = _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.ourdomain.com
DNS DATA =
            SRV 0 100 88 pdc.ourdomain.com
            SRV 0 100 88 bdc.ourdomain.com
+------------------------------------------------------+

The Record is different on DNS server '192.168.0.9'.
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 '192.168.0.9', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.dc._msdcs.ourdomain.com.
DNS DATA =
            SRV 0 100 389 pdc.ourdomain.com.

The record on DNS server 192.168.0.9 is:
DNS NAME = _ldap._tcp.dc._msdcs.ourdomain.com
DNS DATA =
            SRV 0 100 389 pdc.ourdomain.com
            SRV 0 100 389 server.ourdomain.com
            SRV 0 100 389 bdc.ourdomain.com
+------------------------------------------------------+

The Record is different on DNS server '192.168.0.9'.
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 '192.168.0.9', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.ourdomain.com.
DNS DATA =
            SRV 0 100 389 pdc.ourdomain.com.

The record on DNS server 192.168.0.9 is:
DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.ourdomain.com
DNS DATA =
            SRV 0 100 389 bdc.ourdomain.com
            SRV 0 100 389 pdc.ourdomain.com
+------------------------------------------------------+

The Record is different on DNS server '192.168.0.9'.
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 '192.168.0.9', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.ourdomain.com.
DNS DATA =
            SRV 0 100 88 pdc.ourdomain.com.

The record on DNS server 192.168.0.9 is:
DNS NAME = _kerberos._tcp.ourdomain.com
DNS DATA =
            SRV 0 100 88 bdc.ourdomain.com
            SRV 0 100 88 pdc.ourdomain.com
+------------------------------------------------------+

The Record is different on DNS server '192.168.0.9'.
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 '192.168.0.9', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.Default-First-Site-Name._sites.ourdomain.com.
DNS DATA =
            SRV 0 100 88 pdc.ourdomain.com.

The record on DNS server 192.168.0.9 is:
DNS NAME = _kerberos._tcp.Default-First-Site-Name._sites.ourdomain.com
DNS DATA =
            SRV 0 100 88 bdc.ourdomain.com
            SRV 0 100 88 pdc.ourdomain.com
+------------------------------------------------------+

The Record is different on DNS server '192.168.0.9'.
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 '192.168.0.9', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._udp.ourdomain.com.
DNS DATA =
            SRV 0 100 88 pdc.ourdomain.com.

The record on DNS server 192.168.0.9 is:
DNS NAME = _kerberos._udp.ourdomain.com
DNS DATA =
            SRV 0 100 88 bdc.ourdomain.com
            SRV 0 100 88 pdc.ourdomain.com
+------------------------------------------------------+

The Record is different on DNS server '192.168.0.9'.
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 '192.168.0.9', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kpasswd._tcp.ourdomain.com.
DNS DATA =
            SRV 0 100 464 pdc.ourdomain.com.

The record on DNS server 192.168.0.9 is:
DNS NAME = _kpasswd._tcp.ourdomain.com
DNS DATA =
            SRV 0 100 464 pdc.ourdomain.com
            SRV 0 100 464 bdc.ourdomain.com
+------------------------------------------------------+

The Record is different on DNS server '192.168.0.9'.
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 '192.168.0.9', no need to re-register.

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kpasswd._udp.ourdomain.com.
DNS DATA =
            SRV 0 100 464 pdc.ourdomain.com.

The record on DNS server 192.168.0.9 is:
DNS NAME = _kpasswd._udp.ourdomain.com
DNS DATA =
            SRV 0 100 464 pdc.ourdomain.com
            SRV 0 100 464 bdc.ourdomain.com
+------------------------------------------------------+

The Record is correct on DNS server '192.168.0.9'.

The Record is correct on DNS server '192.168.0.9'.

The Record is correct on DNS server '192.168.0.9'.

The Record is correct on DNS server '192.168.0.9'.

The Record is correct on DNS server '192.168.0.9'.

The Record is correct on DNS server '192.168.0.9'.

    PASS - All the DNS entries for DC are registered on DNS server '192.168.0.9' and other DCs also have some of the names registered.


Redir and Browser test . . . . . . : Passed
    List of transports currently bound to the Redir
        NetbiosSmb
        NetBT_Tcpip_{BC1D0A54-5B6C-4147-BB38-D7A2D5930333}
    The redir is bound to 1 NetBt transport.

    List of transports currently bound to the browser
        NetBT_Tcpip_{BC1D0A54-5B6C-4147-BB38-D7A2D5930333}
    The browser is bound to 1 NetBt transport.
    Mailslot test for ourdomain* passed.


DC discovery test. . . . . . . . . : Failed

    Find DC in domain 'ourdomain':
        [FATAL] Cannot find DC in domain 'ourdomain'. [ERROR_NO_SUCH_DOMAIN]


DC list test . . . . . . . . . . . : Failed
        'ourdomain': Cannot find DC to get DC list from [test skipped].
    List of DCs in Domain 'ourdomain':


Trust relationship test. . . . . . : Skipped


Kerberos test. . . . . . . . . . . : Skipped
        'ourdomain': Cannot find DC to get DC list from [test skipped].


LDAP test. . . . . . . . . . . . . : Failed
    Cannot find DC to run LDAP tests on. The error occurred was: The specified domain either does not exist or could not be contacted.

 

    Find DC in domain 'ourdomain':
        [WARNING] Cannot find DC in domain 'ourdomain'. [ERROR_NO_SUCH_DOMAIN]


Routing table test . . . . . . . . : Passed
Active Routes :
Network Destination        Netmask           Gateway         Interface  Metric
         0.0.0.0           0.0.0.0       192.168.0.1       192.168.0.9       1
       127.0.0.0         255.0.0.0         127.0.0.1         127.0.0.1       1
       127.0.0.1   255.255.255.255         127.0.0.1         127.0.0.1       1
     192.168.0.0     255.255.255.0       192.168.0.9       192.168.0.9       1
     192.168.0.9   255.255.255.255         127.0.0.1         127.0.0.1       1
       224.0.0.0         240.0.0.0       192.168.0.9       192.168.0.9       1
 255.255.255.255   255.255.255.255       192.168.0.9       192.168.0.9       1
No persistent route entries.


Netstat information test . . . . . : Passed


    Interface Statistics

                                    Received             Sent
    Unicast Packets                  3322393          1882496
    Non-unicast packets                 5626             3152
    Discards                               0                0
    Errors                                 0                0
    Unknown protocols                      0           457224

    Interface index         =  1
    Description             =  Internal loopback interface for 127.0.0 network
    Type                    =  24
    MTU                     =  32768
    Speed                   =  10000000
    Physical Address        =  00-00-00-00-00-00
    Administrative Status   =  1
    Operational Status      =  1
    Last Changed            =  0
    Output Queue Length     =  0


    Interface index         =  16777219
    Description             =  Intel(R) PRO/1000 MT Network Connection (Microsoft's Packet Scheduler)
    Type                    =  6
    MTU                     =  1500
    Speed                   =  1000000000
    Physical Address        =  00-15-F2-0B-3A-26
    Administrative Status   =  1
    Operational Status      =  1
    Last Changed            =  844753543
    Output Queue Length     =  0



    Active Connections

  Proto Local Address         Foreign Address                           State
    TCP   pdc:echo          pdc.ourdomain.com:34900           LISTENING
    TCP   pdc:discard       pdc.ourdomain.com:18462           LISTENING
    TCP   pdc:daytime       pdc.ourdomain.com:43253           LISTENING
    TCP   pdc:qotd          pdc.ourdomain.com:35020           LISTENING
    TCP   pdc:chargen       pdc.ourdomain.com:18654           LISTENING
    TCP   pdc:smtp          pdc.ourdomain.com:18558           LISTENING
    TCP   pdc:nameserver    pdc.ourdomain.com:59477           LISTENING
    TCP   pdc:domain        pdc.ourdomain.com:10245           LISTENING
    TCP   pdc:http          pdc.ourdomain.com:18462           LISTENING
    TCP   pdc:kerberos      pdc.ourdomain.com:34857           LISTENING
    TCP   pdc:epmap         pdc.ourdomain.com:26805           LISTENING
    TCP   pdc:imap          pdc.ourdomain.com:18614           LISTENING
    TCP   pdc:ldap          pdc.ourdomain.com:43140           LISTENING
    TCP   pdc:https         pdc.ourdomain.com:26874           LISTENING
    TCP   pdc:microsoft-ds  pdc.ourdomain.com:26678           LISTENING
    TCP   pdc:kpasswd       pdc.ourdomain.com:2296            LISTENING
    TCP   pdc:593           pdc.ourdomain.com:10490           LISTENING
    TCP   pdc:ldaps         pdc.ourdomain.com:26797           LISTENING
    TCP   pdc:691           pdc.ourdomain.com:2188            LISTENING
    TCP   pdc:993           pdc.ourdomain.com:18574           LISTENING
    TCP   pdc:1026          pdc.ourdomain.com:18466           LISTENING
    TCP   pdc:1029          pdc.ourdomain.com:2087            LISTENING
    TCP   pdc:1053          pdc.ourdomain.com:59449           LISTENING
    TCP   pdc:1060          pdc.ourdomain.com:2105            LISTENING
    TCP   pdc:1067          pdc.ourdomain.com:59515           LISTENING
    TCP   pdc:1069          pdc.ourdomain.com:51226           LISTENING
    TCP   pdc:1076          pdc.ourdomain.com:59528           LISTENING
    TCP   pdc:1077          pdc.ourdomain.com:10338           LISTENING
    TCP   pdc:1210          pdc.ourdomain.com:59403           LISTENING
    TCP   pdc:1211          pdc.ourdomain.com:2288            LISTENING
    TCP   pdc:pptp          pdc.ourdomain.com:59435           LISTENING
    TCP   pdc:2064          pdc.ourdomain.com:26762           LISTENING
    TCP   pdc:3268          pdc.ourdomain.com:43090           LISTENING
    TCP   pdc:3269          pdc.ourdomain.com:43129           LISTENING
    TCP   pdc:3389          pdc.ourdomain.com:59558           LISTENING
    TCP   pdc:4005          pdc.ourdomain.com:2293            LISTENING
    TCP   pdc:8025          pdc.ourdomain.com:43058           LISTENING
    TCP   pdc:12174         pdc.ourdomain.com:18681           LISTENING
    TCP   pdc:38292         pdc.ourdomain.com:34853           LISTENING
    TCP   pdc:ldap          pdc.ourdomain.com:1066            ESTABLISHED
    TCP   pdc:ldap          pdc.ourdomain.com:1073            ESTABLISHED
    TCP   pdc:ldap          pdc.ourdomain.com:1075            ESTABLISHED
    TCP   pdc:ldap          pdc.ourdomain.com:1078            ESTABLISHED
    TCP   pdc:ldap          pdc.ourdomain.com:2792            ESTABLISHED
    TCP   pdc:microsoft-ds  pdc.ourdomain.com:2936            ESTABLISHED
    TCP   pdc:1066          pdc.ourdomain.com:ldap            ESTABLISHED
    TCP   pdc:1070          pdc.ourdomain.com:51405           LISTENING
    TCP   pdc:1073          pdc.ourdomain.com:ldap            ESTABLISHED
    TCP   pdc:1075          pdc.ourdomain.com:ldap            ESTABLISHED
    TCP   pdc:1078          pdc.ourdomain.com:ldap            ESTABLISHED
    TCP   pdc:ms-sql-s      pdc.ourdomain.com:51400           LISTENING
    TCP   pdc:1628          pdc.ourdomain.com:2048            LISTENING
    TCP   pdc:1643          pdc.ourdomain.com:51203           LISTENING
    TCP   pdc:1644          pdc.ourdomain.com:18530           LISTENING
    TCP   pdc:2792          pdc.ourdomain.com:ldap            ESTABLISHED
    TCP   pdc:2936          pdc.ourdomain.com:microsoft-ds    ESTABLISHED
    TCP   pdc:smtp          19.Red-81-32-139.dynamicIP.rima-tde.net:1709  LAST_ACK
    TCP   pdc:smtp          19.Red-81-32-139.dynamicIP.rima-tde.net:3252  CLOSE_WAIT
    TCP   pdc:smtp          88.242.20.51:1227                         LAST_ACK
    TCP   pdc:netbios-ssn   pdc.ourdomain.com:10328           LISTENING
    TCP   pdc:netbios-ssn   bdc.ourdomain.com:2203               ESTABLISHED
    TCP   pdc:netbios-ssn   adrian2.ourdomain.com:1843            ESTABLISHED
    TCP   pdc:ldap          pdc.ourdomain.com:1258            ESTABLISHED
    TCP   pdc:ldap          pdc.ourdomain.com:1259            ESTABLISHED
    TCP   pdc:ldap          pdc.ourdomain.com:1314            ESTABLISHED
    TCP   pdc:ldap          pdc.ourdomain.com:1315            ESTABLISHED
    TCP   pdc:ldap          pdc.ourdomain.com:1446            ESTABLISHED
    TCP   pdc:ldap          pdc.ourdomain.com:2066            ESTABLISHED
    TCP   pdc:ldap          pdc.ourdomain.com:3134            ESTABLISHED
    TCP   pdc:ldap          pdc.ourdomain.com:3254            ESTABLISHED
    TCP   pdc:ldap          pdc.ourdomain.com:3372            TIME_WAIT
    TCP   pdc:ldap          pdc.ourdomain.com:3373            TIME_WAIT
    TCP   pdc:ldap          pdc.ourdomain.com:3448            TIME_WAIT
    TCP   pdc:ldap          pdc.ourdomain.com:3449            TIME_WAIT
    TCP   pdc:microsoft-ds  pdc.ourdomain.com:3248            ESTABLISHED
    TCP   pdc:microsoft-ds  thermal.ourdomain.com:2206            ESTABLISHED
    TCP   pdc:691           pdc.ourdomain.com:1268            ESTABLISHED
    TCP   pdc:1026          pdc.ourdomain.com:2068            ESTABLISHED
    TCP   pdc:1026          sales003.ourdomain.com:1161           ESTABLISHED
    TCP   pdc:1026          sales003.ourdomain.com:1173           ESTABLISHED
    TCP   pdc:1026          sales003.ourdomain.com:1174           ESTABLISHED
    TCP   pdc:1026          sales002.ourdomain.com:1081           ESTABLISHED
    TCP   pdc:1026          sales002.ourdomain.com:1095           ESTABLISHED
    TCP   pdc:1026          sales002.ourdomain.com:1096           ESTABLISHED
    TCP   pdc:1257          pdc.ourdomain.com:3268            ESTABLISHED
    TCP   pdc:1258          pdc.ourdomain.com:ldap            ESTABLISHED
    TCP   pdc:1259          pdc.ourdomain.com:ldap            ESTABLISHED
    TCP   pdc:1268          pdc.ourdomain.com:691             ESTABLISHED
    TCP   pdc:1314          pdc.ourdomain.com:ldap            ESTABLISHED
    TCP   pdc:1315          pdc.ourdomain.com:ldap            ESTABLISHED
    TCP   pdc:1399          pdc.ourdomain.com:3268            ESTABLISHED
    TCP   pdc:ms-sql-s      pdc.ourdomain.com:43220           LISTENING
    TCP   pdc:1446          pdc.ourdomain.com:ldap            ESTABLISHED
    TCP   pdc:1499          pdc.ourdomain.com:3268            ESTABLISHED
    TCP   pdc:1675          pdc.ourdomain.com:ldap            CLOSE_WAIT
    TCP   pdc:1829          pdc.ourdomain.com:3268            ESTABLISHED
    TCP   pdc:2066          pdc.ourdomain.com:ldap            ESTABLISHED
    TCP   pdc:2068          pdc.ourdomain.com:1026            ESTABLISHED
    TCP   pdc:3134          pdc.ourdomain.com:ldap            ESTABLISHED
    TCP   pdc:3248          pdc.ourdomain.com:microsoft-ds    ESTABLISHED
    TCP   pdc:3254          pdc.ourdomain.com:ldap            ESTABLISHED
    TCP   pdc:3268          pdc.ourdomain.com:1257            ESTABLISHED
    TCP   pdc:3268          pdc.ourdomain.com:1399            ESTABLISHED
    TCP   pdc:3268          pdc.ourdomain.com:1499            ESTABLISHED
    TCP   pdc:3268          pdc.ourdomain.com:1829            ESTABLISHED
    TCP   pdc:3358          pdc.ourdomain.com:epmap           TIME_WAIT
    TCP   pdc:3367          pdc.ourdomain.com:epmap           TIME_WAIT
    TCP   pdc:3370          pdc.ourdomain.com:epmap           TIME_WAIT
    TCP   pdc:3375          pdc.ourdomain.com:epmap           TIME_WAIT
    TCP   pdc:3378          pdc.ourdomain.com:epmap           TIME_WAIT
    TCP   pdc:3381          pdc.ourdomain.com:epmap           TIME_WAIT
    TCP   pdc:3418          pdc.ourdomain.com:epmap           TIME_WAIT
    TCP   pdc:3421          pdc.ourdomain.com:epmap           TIME_WAIT
    TCP   pdc:3426          bdc.ourdomain.com:epmap              TIME_WAIT
    TCP   pdc:3427          bdc.ourdomain.com:2299               TIME_WAIT
    TCP   pdc:3428          pdc.ourdomain.com:epmap           TIME_WAIT
    TCP   pdc:3432          pdc.ourdomain.com:smtp            TIME_WAIT
    TCP   pdc:3434          pdc.ourdomain.com:epmap           TIME_WAIT
    TCP   pdc:3441          pdc.ourdomain.com:epmap           TIME_WAIT
    TCP   pdc:3446          pdc.ourdomain.com:epmap           TIME_WAIT
    TCP   pdc:3453          pdc.ourdomain.com:epmap           TIME_WAIT
    UDP  pdc:echo          *:*                                    
    UDP  pdc:discard       *:*                                    
    UDP  pdc:daytime       *:*                                    
    UDP  pdc:qotd          *:*                                    
    UDP  pdc:chargen       *:*                                    
    UDP  pdc:nameserver    *:*                                    
    UDP  pdc:bootpc        *:*                                    
    UDP  pdc:epmap         *:*                                    
    UDP  pdc:snmp          *:*                                    
    UDP  pdc:microsoft-ds  *:*                                    
    UDP  pdc:1028          *:*                                    
    UDP  pdc:1038          *:*                                    
    UDP  pdc:1051          *:*                                    
    UDP  pdc:1054          *:*                                    
    UDP  pdc:1064          *:*                                    
    UDP  pdc:1065          *:*                                    
    UDP  pdc:1072          *:*                                    
    UDP  pdc:1082          *:*                                    
    UDP  pdc:1130          *:*                                    
    UDP  pdc:1246          *:*                                    
    UDP  pdc:1256          *:*                                    
    UDP  pdc:1267          *:*                                    
    UDP  pdc:1271          *:*                                    
    UDP  pdc:1289          *:*                                    
    UDP  pdc:ms-sql-m      *:*                                    
    UDP  pdc:1569          *:*                                    
    UDP  pdc:1645          *:*                                    
    UDP  pdc:1646          *:*                                    
    UDP  pdc:1674          *:*                                    
    UDP  pdc:l2tp          *:*                                    
    UDP  pdc:radius        *:*                                    
    UDP  pdc:radacct       *:*                                    
    UDP  pdc:2065          *:*                                    
    UDP  pdc:2085          *:*                                    
    UDP  pdc:2967          *:*                                    
    UDP  pdc:3414          *:*                                    
    UDP  pdc:3456          *:*                                    
    UDP  pdc:3457          *:*                                    
    UDP  pdc:38037         *:*                                    
    UDP  pdc:38293         *:*                                    
    UDP  pdc:domain        *:*                                    
    UDP  pdc:1044          *:*                                    
    UDP  pdc:1045          *:*                                    
    UDP  pdc:1063          *:*                                    
    UDP  pdc:1068          *:*                                    
    UDP  pdc:2196          *:*                                    
    UDP  pdc:2493          *:*                                    
    UDP  pdc:domain        *:*                                    
    UDP  pdc:bootps        *:*                                    
    UDP  pdc:bootpc        *:*                                    
    UDP  pdc:kerberos      *:*                                    
    UDP  pdc:ntp           *:*                                    
    UDP  pdc:netbios-ns    *:*                                    
    UDP  pdc:netbios-dgm   *:*                                    
    UDP  pdc:389           *:*                                    
    UDP  pdc:kpasswd       *:*                                    
    UDP  pdc:isakmp        *:*                                    
    UDP  pdc:2535          *:*                                    
    UDP  pdc:4500          *:*                                    


    IP  Statistics

    Packets Received              =   40,304
    Received Header Errors        =   0
    Received Address Errors       =   5
    Datagrams Forwarded           =   0
    Unknown Protocols Received    =   0
    Received Packets Discarded    =   0
    Received Packets Delivered    =   40,304
    Output Requests               =   39,332
    Routing Discards              =   0
    Discarded Output Packets      =   0
    Output Packet No Route        =   0
    Reassembly  Required          =   0
    Reassembly Successful         =   0
    Reassembly Failures           =   0
    Datagrams successfully fragmented  =   0
    Datagrams failing fragmentation    =   0
    Fragments Created                  =   0
    Forwarding                        =    1
    Default TTL                       =    128
    Reassembly  timeout               =    60


    TCP Statistics

    Active Opens               =    994
    Passive Opens              =    977
    Failed Connection Attempts =    20
    Reset Connections          =    91
    Current Connections        =    54
    Received Segments          =    27,634
    Segment Sent               =    27,211
    Segment Retransmitted      =    104
    Retransmission Timeout Algorithm  =   vanj
    Minimum Retransmission Timeout  = 300
    Maximum Retransmission Timeout  = 60,000
    Maximum Number of Connections   = -1


    UDP Statistics

    Datagrams Received    =   9,985
    No Ports              =   1,455
    Receive Errors        =   0
    Datagrams Sent        =   9,359


    ICMP Statistics

                              Received           Sent
    Messages                     2,643          2,643
    Errors                           0              0
    Destination  Unreachable        92             92
    Time    Exceeded                 0              0
    Parameter Problems               0              0
    Source Quenchs                   0              0
    Redirects                        0              0
    Echos                        1,275          1,275
    Echo Replies                 1,276          1,276
    Timestamps                       0              0
    Timestamp Replies                0              0
    Address Masks                    0              0
    Address Mask Replies             0              0


Bindings test. . . . . . . . . . . : Passed
    Component Name : NDIS Usermode I/O Protocol
    Bind Name: Ndisuio
    Binding Paths:
        Owner of the binding path : NDIS Usermode I/O Protocol
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndis5
            Upper Component: NDIS Usermode I/O Protocol
            Lower Component: Intel(R) PRO/1000 MT Network Connection

        Owner of the binding path : NDIS Usermode I/O Protocol
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndis5
            Upper Component: NDIS Usermode I/O Protocol
            Lower Component: NVIDIA nForce Networking Controller


    Component Name : Network Monitor Driver
    Bind Name: NM
    Binding Paths:
        Owner of the binding path : Network Monitor Driver
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndis5
            Upper Component: Network Monitor Driver
            Lower Component: Intel(R) PRO/1000 MT Network Connection

        Owner of the binding path : Network Monitor Driver
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndis5
            Upper Component: Network Monitor Driver
            Lower Component: NVIDIA nForce Networking Controller

        Owner of the binding path : Network Monitor Driver
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndiswanbh
            Upper Component: Network Monitor Driver
            Lower Component: WAN Miniport (Network Monitor)


    Component Name : Point to Point Tunneling Protocol
    Bind Name: mspptp
    Binding Paths:

    Component Name : Layer 2 Tunneling Protocol
    Bind Name: msl2tp
    Binding Paths:

    Component Name : Remote Access NDIS WAN Driver
    Bind Name: NdisWan
    Binding Paths:
        Owner of the binding path : Remote Access NDIS WAN Driver
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndiscowan
            Upper Component: Remote Access NDIS WAN Driver
            Lower Component: Direct Parallel

        Owner of the binding path : Remote Access NDIS WAN Driver
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndiswan
            Upper Component: Remote Access NDIS WAN Driver
            Lower Component: WAN Miniport (PPTP)

        Owner of the binding path : Remote Access NDIS WAN Driver
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndiscowan
            Upper Component: Remote Access NDIS WAN Driver
            Lower Component: WAN Miniport (L2TP)

        Owner of the binding path : Remote Access NDIS WAN Driver
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndiswanasync
            Upper Component: Remote Access NDIS WAN Driver
            Lower Component: RAS Async Adapter


    Component Name : Message-oriented TCP/IP Protocol (SMB session)
    Bind Name: NetbiosSmb
    Binding Paths:

    Component Name : WINS Client(TCP/IP) Protocol
    Bind Name: NetBT
    Binding Paths:
        Owner of the binding path : WINS Client(TCP/IP) Protocol
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndis5
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: Intel(R) PRO/1000 MT Network Connection

        Owner of the binding path : WINS Client(TCP/IP) Protocol
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndis5
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: NVIDIA nForce Networking Controller

        Owner of the binding path : WINS Client(TCP/IP) Protocol
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndiswanip
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: WAN Miniport (IP)


    Component Name : Internet Protocol (TCP/IP)
    Bind Name: Tcpip
    Binding Paths:
        Owner of the binding path : Internet Protocol (TCP/IP)
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndis5
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: Intel(R) PRO/1000 MT Network Connection

        Owner of the binding path : Internet Protocol (TCP/IP)
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndis5
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: NVIDIA nForce Networking Controller

        Owner of the binding path : Internet Protocol (TCP/IP)
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndiswanip
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: WAN Miniport (IP)


    Component Name : Client for Microsoft Networks
    Bind Name: LanmanWorkstation
    Binding Paths:
        Owner of the binding path : Client for Microsoft Networks
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios_smb
            Upper Component: Client for Microsoft Networks
            Lower Component: Message-oriented TCP/IP Protocol (SMB session)

        Owner of the binding path : Client for Microsoft Networks
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios
            Upper Component: Client for Microsoft Networks
            Lower Component: WINS Client(TCP/IP) Protocol
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndis5
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: Intel(R) PRO/1000 MT Network Connection

        Owner of the binding path : Client for Microsoft Networks
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios
            Upper Component: Client for Microsoft Networks
            Lower Component: WINS Client(TCP/IP) Protocol
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndis5
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: NVIDIA nForce Networking Controller

        Owner of the binding path : Client for Microsoft Networks
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios
            Upper Component: Client for Microsoft Networks
            Lower Component: WINS Client(TCP/IP) Protocol
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndiswanip
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: WAN Miniport (IP)


    Component Name : QoS Packet Scheduler
    Bind Name: PSched
    Binding Paths:
        Owner of the binding path : QoS Packet Scheduler
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndis5
            Upper Component: QoS Packet Scheduler
            Lower Component: NVIDIA nForce Networking Controller

        Owner of the binding path : QoS Packet Scheduler
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndis5
            Upper Component: QoS Packet Scheduler
            Lower Component: Intel(R) PRO/1000 MT Network Connection

        Owner of the binding path : QoS Packet Scheduler
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndiswanbh
            Upper Component: QoS Packet Scheduler
            Lower Component: WAN Miniport (Network Monitor)

        Owner of the binding path : QoS Packet Scheduler
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndiswanip
            Upper Component: QoS Packet Scheduler
            Lower Component: WAN Miniport (IP)


    Component Name : Wireless Configuration
    Bind Name: wzcsvc
    Binding Paths:

    Component Name : DHCP Server
    Bind Name: DHCPServer
    Binding Paths:

    Component Name : Steelhead
    Bind Name: RemoteAccess
    Binding Paths:

    Component Name : Dial-Up Server
    Bind Name: msrassrv
    Binding Paths:

    Component Name : Remote Access Connection Manager
    Bind Name: RasMan
    Binding Paths:

    Component Name : Dial-Up Client
    Bind Name: msrascli
    Binding Paths:

    Component Name : File and Printer Sharing for Microsoft Networks
    Bind Name: LanmanServer
    Binding Paths:
        Owner of the binding path : File and Printer Sharing for Microsoft Networks
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios_smb
            Upper Component: File and Printer Sharing for Microsoft Networks
            Lower Component: Message-oriented TCP/IP Protocol (SMB session)

        Owner of the binding path : File and Printer Sharing for Microsoft Networks
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios
            Upper Component: File and Printer Sharing for Microsoft Networks
            Lower Component: WINS Client(TCP/IP) Protocol
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndis5
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: Intel(R) PRO/1000 MT Network Connection

        Owner of the binding path : File and Printer Sharing for Microsoft Networks
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios
            Upper Component: File and Printer Sharing for Microsoft Networks
            Lower Component: WINS Client(TCP/IP) Protocol
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndis5
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: NVIDIA nForce Networking Controller

        Owner of the binding path : File and Printer Sharing for Microsoft Networks
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios
            Upper Component: File and Printer Sharing for Microsoft Networks
            Lower Component: WINS Client(TCP/IP) Protocol
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndiswanip
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: WAN Miniport (IP)


    Component Name : NetBIOS Interface
    Bind Name: NetBIOS
    Binding Paths:
        Owner of the binding path : NetBIOS Interface
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios
            Upper Component: NetBIOS Interface
            Lower Component: WINS Client(TCP/IP) Protocol
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndis5
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: Intel(R) PRO/1000 MT Network Connection

        Owner of the binding path : NetBIOS Interface
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios
            Upper Component: NetBIOS Interface
            Lower Component: WINS Client(TCP/IP) Protocol
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndis5
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: NVIDIA nForce Networking Controller

        Owner of the binding path : NetBIOS Interface
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: netbios
            Upper Component: NetBIOS Interface
            Lower Component: WINS Client(TCP/IP) Protocol
        -Interface Name: tdi
            Upper Component: WINS Client(TCP/IP) Protocol
            Lower Component: Internet Protocol (TCP/IP)
        -Interface Name: ndiswanip
            Upper Component: Internet Protocol (TCP/IP)
            Lower Component: WAN Miniport (IP)


    Component Name : QoS RSVP
    Bind Name: RSVP
    Binding Paths:

    Component Name : Generic Packet Classifier
    Bind Name: Gpc
    Binding Paths:

    Component Name : Intel(R) PRO/1000 MT Network Connection
    Bind Name: {BC1D0A54-5B6C-4147-BB38-D7A2D5930333}
    Binding Paths:

    Component Name : NVIDIA nForce Networking Controller
    Bind Name: {EE7F9783-7BA0-41E6-913C-1669CFDF7F11}
    Binding Paths:

    Component Name : WAN Miniport (Network Monitor)
    Bind Name: NdisWanBh
    Binding Paths:

    Component Name : WAN Miniport (IP)
    Bind Name: NdisWanIp
    Binding Paths:

    Component Name : Direct Parallel
    Bind Name: {65B4CA87-57F0-4CDE-8841-864D67052843}
    Binding Paths:

    Component Name : WAN Miniport (PPTP)
    Bind Name: {630FB7C3-E80E-4881-AEB7-D2B1306A21BF}
    Binding Paths:

    Component Name : WAN Miniport (L2TP)
    Bind Name: {8948E183-04EE-4664-AA73-55736EC8F83D}
    Binding Paths:

    Component Name : RAS Async Adapter
    Bind Name: {6D4DC246-6CA1-4569-85EA-FCC3475C1A95}
    Binding Paths:



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


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Passed
    IPSec policy service is active, but no policy is assigned.

    IPSec Statistics

     Oakley Main Modes             : 0
     Oakley Quick Modes            : 0
     Active Associations           : 0
     Soft Associations             : 0
     Authenticated Bytes Sent      : 0
     Authenticated Bytes Received  : 0
     Confidential Bytes Sent       : 0
     Confidential Bytes Received   : 0
     Offloaded Bytes Sent          : 0
     Offloaded Bytes Received      : 0
     ReKeys                        : 0

     Authentication Failures       : 0
     Negotiation Failures          : 0
     Packets not decrypted         : 0
     Packets not authenticated     : 0
     Invalid Cookies Rcvd          : 0
     Acquire fail                  : 0
     Receive fail                  : 0
     Send fail                     : 0
     GetSpiFail                    : 0
     KeyAddFail                    : 0
     KeyUpdateFail                 : 0

     Active Acquire                : 1
     Active Rcv                    : 0
     Active Send                   : 0
     Total Acquire                 : 0
     TotalGetSpi                   : 0
     TotalKeyAdd                   : 0
     TotalKeyUpdate                : 0
     Inactive Associations         : 0
     Dead Associations             : 0
     Pending Keys                  : 0
     Key Flushes                   : 0
     Key Additions                 : 0
     Key Deletes                   : 0

    Phase 1 offers count is 4
     OFFER #1:
     PFS : No, Encryption : 3DES, Hash : SHA1, Group : Medium (2)
     Quickmodes per MainMode : 0, Lifetime Seconds : 28800
     OFFER #2:
     PFS : No, Encryption : 3DES, Hash : MD5, Group : Medium (2)
     Quickmodes per MainMode : 0, Lifetime Seconds : 28800
     OFFER #3:
     PFS : No, Encryption : DES, Hash : SHA1, Group : Low (1)
     Quickmodes per MainMode : 0, Lifetime Seconds : 28800
     OFFER #4:
     PFS : No, Encryption : DES, Hash : MD5, Group : Low (1)
     Quickmodes per MainMode : 0, Lifetime Seconds : 28800

    Current Phase 1 SAs:
    No SAs.


    Current Phase 2 SAs:
    No SAs.




Lee.
0
Comment
Question by:LeeGolding
  • 8
  • 7
16 Comments
 
LVL 70

Expert Comment

by:Chris Dent
ID: 17896772

Just seen you had two questions.

Can you run DCDiag from BDC please? All the above is from PDC.

These parts of your log are more concerning than the DNS Registration information you have:

DC discovery test. . . . . . . . . : Failed

    Find DC in domain 'ourdomain':
        [FATAL] Cannot find DC in domain 'ourdomain'. [ERROR_NO_SUCH_DOMAIN]


DC list test . . . . . . . . . . . : Failed
        'ourdomain': Cannot find DC to get DC list from [test skipped].
    List of DCs in Domain 'ourdomain':

LDAP test. . . . . . . . . . . . . : Failed
    Cannot find DC to run LDAP tests on. The error occurred was: The specified domain either does not exist or could not be contacted.

You haven't renamed the domain after installation at all have you?

Chris
0
 

Author Comment

by:LeeGolding
ID: 17896938
I haven't renamed the domain.

We have had some spyware and various server crashes and I think DNS/AD has corrupted or thereabouts. But, I've had some experience and the DNS server looks ok at first glance so to speak.

I'll get a listout of DCDIAG for the BDC shortly.

Thanks,

Lee.
0
 

Author Comment

by:LeeGolding
ID: 17897160
DCDIAG -v on BDC (the second domain controller):


------------------------------------------------
DC Diagnosis

Performing initial setup:
   * Verifing that the local machine BDC, is a DC.
   * Connecting to directory service on server BDC.
   * Collecting site info.
   * Identifying all servers.
   * Found 2 DC(s). Testing 1 of them.
   Done gathering initial info.

Doing initial non skippeable tests

   Testing server: Default-First-Site-Name\BDC
      Starting test: Connectivity
         * Active Directory LDAP Services Check
         * Active Directory RPC Services Check
         ......................... BDC passed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\BDC
      Starting test: Replications
         * Replications Check
         [Replications Check,BDC] Inbound replication is disabled.
         To correct, run "repadmin /options BDC -DISABLE_INBOUND_REPL"
         [Replications Check,BDC] Outbound replication is disabled.
         To correct, run "repadmin /options BDC -DISABLE_OUTBOUND_REPL"
         ......................... BDC failed test Replications
      Test omitted by user request: Topology
      Test omitted by user request: CutoffServers
      Starting test: NCSecDesc
         * Security Permissions Check for
           CN=Schema,CN=Configuration,DC=ourdomain,DC=com
         * Security Permissions Check for
           CN=Configuration,DC=ourdomain,DC=com
         * Security Permissions Check for
           DC=ourdomain,DC=com
         ......................... BDC passed test NCSecDesc
      Starting test: NetLogons
         * Network Logons Privileges Check
         ......................... BDC passed test NetLogons
      Starting test: Advertising
         Fatal Error:DsGetDcName (BDC) call failed, error 1355
         The Locator could not find the server.
         ......................... BDC failed test Advertising
      Starting test: KnowsOfRoleHolders
         Role Schema Owner = CN=NTDS
Settings,CN=PDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ourdomain,DC=com
         [PDC] DsBind() failed with error -2146893022,
         The target principal name is incorrect..
         Warning: PDC is the Schema Owner, but is not responding to DS
RPC Bind.
         [PDC] LDAP bind failed with error 31,
         A device attached to the system is not functioning..
         Warning: PDC is the Schema Owner, but is not responding to LDAP
Bind.
         Role Domain Owner = CN=NTDS
Settings,CN=PDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ourdomain,DC=com
         Warning: PDC is the Domain Owner, but is not responding to DS
RPC Bind.
         Warning: PDC is the Domain Owner, but is not responding to LDAP
Bind.
         Role PDC Owner = CN=NTDS
Settings,CN=PDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ourdomain,DC=com
         Warning: PDC is the PDC Owner, but is not responding to DS RPC
Bind.
         Warning: PDC is the PDC Owner, but is not responding to LDAP
Bind.
         Role Rid Owner = CN=NTDS
Settings,CN=PDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ourdomain,DC=com
         Warning: PDC is the Rid Owner, but is not responding to DS RPC
Bind.
         Warning: PDC is the Rid Owner, but is not responding to LDAP
Bind.
         Role Infrastructure Update Owner = CN=NTDS
Settings,CN=PDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ourdomain,DC=com
         Warning: PDC is the Infrastructure Update Owner, but is not
responding to DS RPC Bind.
         Warning: PDC is the Infrastructure Update Owner, but is not
responding to LDAP Bind.
         ......................... BDC failed test KnowsOfRoleHolders
      Starting test: RidManager
         * Available RID Pool for the Domain is 6602 to 1073741823
         * PDC.ourdomain.com is the RID Master
         [BDC] DsBindWithCred() failed with error -2146893022. The target
principal name is incorrect.
         ......................... BDC failed test RidManager
      Starting test: MachineAccount
         * SPN found :LDAP/BDC.ourdomain.com/ourdomain.com
         * SPN found :LDAP/BDC.ourdomain.com
         * SPN found :LDAP/BDC
         * SPN found :LDAP/BDC.ourdomain.com/OURDOMAIN
         * SPN found
:LDAP/8379fd6a-2382-4e58-bc5f-8cf6e5d7d111._msdcs.ourdomain.com
         * SPN found
:E3514235-4B06-11D1-AB04-00C04FC2DCD2/8379fd6a-2382-4e58-bc5f-8cf6e5d7d111/ourdomain.com
         * SPN found :HOST/BDC.ourdomain.com/ourdomain.com
         * SPN found :HOST/BDC.ourdomain.com
         * SPN found :HOST/BDC
         * SPN found :HOST/BDC.ourdomain.com/OURDOMAIN
         * SPN found :GC/BDC.ourdomain.com/ourdomain.com
         ......................... BDC passed test MachineAccount
      Starting test: Services
         * Checking Service: Dnscache
         * Checking Service: NtFrs
         * Checking Service: IsmServ
         * Checking Service: kdc
         * Checking Service: SamSs
         * Checking Service: LanmanServer
         * Checking Service: LanmanWorkstation
         * Checking Service: RpcSs
         * Checking Service: RPCLOCATOR
         * Checking Service: w32time
         * Checking Service: TrkWks
         * Checking Service: TrkSvr
         * Checking Service: NETLOGON
            NETLOGON Service is paused on [BDC]
         * Checking Service: Dnscache
         * Checking Service: NtFrs
            SMTPSVC Service is stopped on [BDC]
         ......................... BDC failed test Services
      Test omitted by user request: OutboundSecureChannels
      Starting test: ObjectsReplicated
         BDC is in domain DC=ourdomain,DC=com
         Checking for CN=BDC,OU=Domain Controllers,DC=ourdomain,DC=com
in domain DC=ourdomain,DC=com on 1 servers
            Object is up-to-date on all servers.
         Checking for CN=NTDS
Settings,CN=BDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=ourdomain,DC=com
in domain CN=Configuration,DC=ourdomain,DC=com on 1 servers
            Object is up-to-date on all servers.
         ......................... BDC passed test ObjectsReplicated
      Starting test: frssysvol
         * The File Replication Service Event log test
         Error: No record of File Replication System, SYSVOL started.
         The Active Directory may be prevented from starting.
         There are errors after the SYSVOL has been shared.
         The SYSVOL can prevent the AD from starting.
         An Warning Event occured.  EventID: 0x800034FD
            Time Generated: 11/08/2006   09:21:06
            Event String: File Replication Service is initializing the
system volume with data from another domain
controller. Computer BDC cannot become a domain
controller until this process is complete. The
system volume will then be shared as SYSVOL.

To check for the SYSVOL share, at the command
prompt, type:
net share

When File Replication Service completes the
initialization process, the SYSVOL share will
appear.

The initialization of the system volume can take
some time. The time is dependent on the amount of
data in the system volume, the availability of
other domain controllers, and the replication
interval between domain controllers.
         An Warning Event occured.  EventID: 0x800034C4
            Time Generated: 11/08/2006   09:23:08
            Event String: The File Replication Service is having trouble
enabling replication from PDC to BDC for
c:\winnt\sysvol\domain using the DNS name
PDC.ourdomain.com. FRS will keep
retrying.
Following are some of the reasons you would see
this warning.

[1] FRS can not correctly resolve the DNS name
PDC.ourdomain.com from this computer.
[2] FRS is not running on
PDC.ourdomain.com.
[3] The topology information in the Active
Directory for this replica has not yet replicated
to all the Domain Controllers.

This event log message will appear once per
connection, After the problem is fixed you will
see another event log message indicating that the
connection has been established.
         ......................... BDC passed test frssysvol
      Starting test: kccevent
         * The KCC Event log test
         An Warning Event occured.  EventID: 0x80000679
            Time Generated: 11/08/2006   10:25:50
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0xC00005BA
            Time Generated: 11/08/2006   10:25:50
            (Event String could not be retrieved)
         An Warning Event occured.  EventID: 0x80000581
            Time Generated: 11/08/2006   10:25:50
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0xC000055D
            Time Generated: 11/08/2006   10:25:50
            (Event String could not be retrieved)
         ......................... BDC failed test kccevent
      Starting test: systemlog
         * The System Event log test
         An Error Event occured.  EventID: 0x0000410A
            Time Generated: 11/08/2006   09:28:11
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0x0000410A
            Time Generated: 11/08/2006   09:30:11
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0xC0001F60
            Time Generated: 11/08/2006   09:59:00
            Event String: The browser service has failed to retrieve the
backup list too many times on transport
\Device\NetBT_Tcpip_{0585E132-983A-4F60-8162-F025304ECB72}.
The backup browser is stopping.
         An Error Event occured.  EventID: 0x0000410A
            Time Generated: 11/08/2006   10:01:11
            (Event String could not be retrieved)
         ......................... BDC failed test systemlog

   Running enterprise tests on : ourdomain.com
      Starting test: Intersite
         Skipping site Default-First-Site-Name, this site is outside the
scope
         provided by the command line arguments provided.
         ......................... ourdomain.com passed test Intersite
      Starting test: FsmoCheck
         Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355
         A Global Catalog Server could not be located - All GC's are down.
         PDC Name: \\PDC.ourdomain.com
         Locator Flags: 0xe00001fd
         Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
         A Time Server could not be located.
         The server holding the PDC role is down.
         Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error
1355
         A Good Time Server could not be located.
         Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1355
         A KDC could not be located - All the KDCs are down.
         ......................... ourdomain.com failed test FsmoCheck

0
 
LVL 70

Accepted Solution

by:
Chris Dent earned 500 total points
ID: 17899919

Well at least it hasn't gone only half-way wrong... Please make sure you have full system state backups of both DCs at this point in case anything needs to be undone.

You may want to try:

repadmin /options BDC -DISABLE_INBOUND_REPL
repadmin /options BDC -DISABLE_OUTBOUND_REPL

Taken from the Diagnostics above. However, it's perhaps unlikely to play along. It's possible that, if the above doesn't fix it, you may be able to get it working if the secure channel between the DC and the domain is rebuilt. If you follow this article for that one:

http://support.microsoft.com/kb/288167

If all else fails then you can try removing the BDC DC from the network completely using this article:

http://support.microsoft.com/kb/216498

Then start again entirely with that one.

Chris
0
 

Author Comment

by:LeeGolding
ID: 17905263
I've done the repadmin and restarted both servers. I now get the following on the BDC server.

--------------------------------------------------------------------------
Default-First-Site-Name\BDC
DSA Options : (none)
objectGuid  : 8379fd6a-2382-4e58-bc5f-8cf6e5d7d111
invocationID: cae28b79-4d91-4bd6-9b28-3e1952c1aab5

==== INBOUND NEIGHBORS ======================================

CN=Schema,CN=Configuration,DC=ourdomain,DC=com
    Default-First-Site-Name\PDC via RPC
        objectGuid: 5145552f-2fa9-4a58-8b8e-58cd9ced39a5
        Last attempt @ 2006-11-09 10:29.31 failed, result 1908:
            Could not find the domain controller for this domain.
        Last success @ 2006-08-12 08:49.11.
        2050 consecutive failure(s).

CN=Configuration,DC=ourdomain,DC=com
    Default-First-Site-Name\PDC via RPC
        objectGuid: 5145552f-2fa9-4a58-8b8e-58cd9ced39a5
        Last attempt @ 2006-11-09 10:29.31 failed, result 1908:
            Could not find the domain controller for this domain.
        Last success @ 2006-08-12 09:34.25.
        9676 consecutive failure(s).

DC=ourdomain,DC=com
    Default-First-Site-Name\PDC via RPC
        objectGuid: 5145552f-2fa9-4a58-8b8e-58cd9ced39a5
        Last attempt @ 2006-11-09 10:34.57 failed, result 1908:
            Could not find the domain controller for this domain.
        Last success @ 2006-08-12 09:34.11.
        13533 consecutive failure(s).

==== OUTBOUND NEIGHBORS FOR CHANGE NOTIFICATIONS ============

CN=Schema,CN=Configuration,DC=ourdomain,DC=com
    Default-First-Site-Name\PDC via RPC
        objectGuid: 5145552f-2fa9-4a58-8b8e-58cd9ced39a5

CN=Configuration,DC=ourdomain,DC=com
    Default-First-Site-Name\PDC via RPC
        objectGuid: 5145552f-2fa9-4a58-8b8e-58cd9ced39a5

DC=ourdomain,DC=com
    Default-First-Site-Name\PDC via RPC
        objectGuid: 5145552f-2fa9-4a58-8b8e-58cd9ced39a5
------------------------------------



And the following on server PDC:

-------------------------------------
Default-First-Site-Name\pdc
DSA Options : IS_GC
objectGuid  : 5145552f-2fa9-4a58-8b8e-58cd9ced39a5
invocationID: dcca8c3f-5a10-4d42-9b79-3c86414c5a75

==== INBOUND NEIGHBORS ======================================

CN=Schema,CN=Configuration,DC=ourdomain,DC=com
    Default-First-Site-Name\bdc via RPC
        objectGuid: 8379fd6a-2382-4e58-bc5f-8cf6e5d7d111
        Last attempt @ 2006-11-09 10:34.45 was successful.

CN=Configuration,DC=ourdomain,DC=com
    Default-First-Site-Name\bdc via RPC
        objectGuid: 8379fd6a-2382-4e58-bc5f-8cf6e5d7d111
        Last attempt @ 2006-11-09 10:34.45 was successful.

DC=ourdomain,DC=com
    Default-First-Site-Name\bdc via RPC
        objectGuid: 8379fd6a-2382-4e58-bc5f-8cf6e5d7d111
        Last attempt @ 2006-11-09 10:34.45 was successful.

==== OUTBOUND NEIGHBORS FOR CHANGE NOTIFICATIONS ============

CN=Schema,CN=Configuration,DC=ourdomain,DC=com
    Default-First-Site-Name\bdc via RPC
        objectGuid: 8379fd6a-2382-4e58-bc5f-8cf6e5d7d111

CN=Configuration,DC=ourdomain,DC=com
    Default-First-Site-Name\bdc via RPC
        objectGuid: 8379fd6a-2382-4e58-bc5f-8cf6e5d7d111

DC=ourdomain,DC=com
    Default-First-Site-Name\bdc via RPC
        objectGuid: 8379fd6a-2382-4e58-bc5f-8cf6e5d7d111
---------------------------------------------------------------------
0
 
LVL 38

Expert Comment

by:Shift-3
ID: 17905907
This may be a shot in the dark, but it's possible there is a problem with PDC's SRV records.  Try running dcdiag /fix on it.
0
 
LVL 70

Expert Comment

by:Chris Dent
ID: 17908013

I would expect the PDC to complain a lot more about it, but it definately can't hurt anything so it's well worth doing.

Chris
0
 
LVL 70

Expert Comment

by:Chris Dent
ID: 17908078

Hmm... We have more of a problem here.

> Last success @ 2006-08-12 08:49.11

It's been well over 60 days since BDC replicated with PDC. BDC has almost certainly been tombstoned and doesn't stand much of a chance at all of recovery. There is a caveat to this: if you did the original DC Promo on a Windows 2003 SP1 machine (first DC) then the Tombstone value is 180 Days not 60, in which case it's not dead yet.

You can refer to these articles for a little more information on this:

http://support.microsoft.com/kb/216993
http://support.microsoft.com/kb/870695

You may need to remove the BDC and promote a new server in it's place if you want to maintain 2 DCs. I'll see if I can find a bit more of a definate "what to do" for a tombstoned DC; never personally seen one. The article I posted earlier should allow you to remove it:

http://support.microsoft.com/kb/216498

Alongside 870695 above.

Chris
0
How to improve team productivity

Quip adds documents, spreadsheets, and tasklists to your Slack experience
- Elevate ideas to Quip docs
- Share Quip docs in Slack
- Get notified of changes to your docs
- Available on iOS/Android/Desktop/Web
- Online/Offline

 

Author Comment

by:LeeGolding
ID: 17910390
Looks like a problem with SYSVOL.

Enabled replication on the server BDC with your:

repadmin /options BDC -DISABLE_INBOUND_REPL
repadmin /options BDC -DISABLE_OUTBOUND_REPL

DCDIAG /fix

Used netdom to reset the server BDC account in the domain, from a command prompt.

Did a D4 authorative restore as per a MS knowledge base article and restarted FRS and everything over the next couple of hours started working again. Including replication, SYSVOLs became mounted, all communication and domain back to normal and all clients can connect.

I've Netman66 to thank for other bits of help.

Thanks Chris :-)

Lee.
0
 
LVL 70

Expert Comment

by:Chris Dent
ID: 17910407

Good stuff :) Glad I could help out a little.

Chris
0
 

Author Comment

by:LeeGolding
ID: 17910410
One more thing, how can I find out why it hadn't replicated since 2006-08-12 08:49.11?

Ta,

Lee.
0
 
LVL 70

Expert Comment

by:Chris Dent
ID: 17910430

I would expect it to be in the Event log, although you may find the reason is really vague. It could be anything from mis-configured DNS to a more serious problem with the DCs account on the domain.

Chris
0
 

Author Comment

by:LeeGolding
ID: 17910474
What command line commands can I use to ensure that replication is running perfectly now?

Lee.
0
 
LVL 70

Expert Comment

by:Chris Dent
ID: 17910493

You can use:

repadmin /showreps

That will show the current status of replication from the current DC.

Chris
0
 

Author Comment

by:LeeGolding
ID: 17912923
Cool.

Thanks for all the help Chris.

Lee.
0
 
LVL 70

Expert Comment

by:Chris Dent
ID: 17913043

Pleasure.

Chris
0

Featured Post

What Should I Do With This Threat Intelligence?

Are you wondering if you actually need threat intelligence? The answer is yes. We explain the basics for creating useful threat intelligence.

Join & Write a Comment

This may not be a text book method to resolve VSS backup issues but it seemed to have worked on few of the Windows 2003 servers we had issues while performing a Volume Shadow Copy backup. If you have issues while performing a shadow copy backup usin…
Setting up a Microsoft WSUS update system is free relatively speaking if you have hard disk space and processor capacity.   However, WSUS can be a blessing and a curse. For example, there is nothing worse than approving updates and they just have…
Internet Business Fax to Email Made Easy - With eFax Corporate (http://www.enterprise.efax.com), you'll receive a dedicated online fax number, which is used the same way as a typical analog fax number. You'll receive secure faxes in your email, fr…
This video discusses moving either the default database or any database to a new volume.

759 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now