[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

when trying to demote a server(and remove) using DCPROMO...

Posted on 2005-04-13
22
Medium Priority
?
1,354 Views
Last Modified: 2008-02-26
I receive the error: Failed finding a suitable domain controller for the Domain (domain listed). The specified domain does not exist or could not be contacted.

I have transferred the FISMO roles over to the new server. SYSVOL and Netlogon are shared amongst servers. Was having some trouble with the FRS, but since have made some changes to the registry and now sucessfully added the connections I needed(as shown in event viewer)
One server is Server 2000 and the other is Server 2003.

Any suggestions MUCH APPRECIATED...I am reserached out and am re-reading everything
0
Comment
Question by:UMOS
  • 11
  • 11
22 Comments
 
LVL 18

Expert Comment

by:John Gates, CISSP
ID: 13775172
Are you trying to demote the 2000 server?
0
 

Author Comment

by:UMOS
ID: 13775334
yes it is the 2000 server that I am trying to demote
0
 

Author Comment

by:UMOS
ID: 13775601
when I run nslookup on both I get
DC1-can't find server name for ip address 192.x.x.x: non existent domain
default servers not available

DC2- shows DC1 as default server
DC1 is the one I am interested in taking down
0
NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

 

Author Comment

by:UMOS
ID: 13775656
SCRATCH last comment...I switched the tcp/ip properties as suggested on another EE message and thats where the nslookup results came from. How should they be set for proper demotion. DC1 is the one I want to take offline so which should be the preferred and alternate DNS servers?
What should DC2 read as well?
0
 
LVL 18

Expert Comment

by:John Gates, CISSP
ID: 13775805
From the 2003 server disk install the support tools

Then from a cmd prompt run>

dcdiag /e /v >dcdiag.txt

Please post the output here.

-D-
0
 

Author Comment

by:UMOS
ID: 13778580
I will do that as soon as I can get back to the client site.
Thanks
0
 
LVL 18

Expert Comment

by:John Gates, CISSP
ID: 13778598
I will be here 8)

-D-
0
 

Author Comment

by:UMOS
ID: 13783823
Here is the info after I run DCdiag.

Domain Controller Diagnosis

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

Doing initial required tests
   
   Testing server: Default-First-Site-Name\W2KSERVER
      Starting test: Connectivity
         * Active Directory LDAP Services Check
         * Active Directory RPC Services Check
         ......................... W2KSERVER passed test Connectivity
   
   Testing server: Default-First-Site-Name\SERVER1
      Starting test: Connectivity
         * Active Directory LDAP Services Check
         * Active Directory RPC Services Check
         ......................... SERVER1 passed test Connectivity

Doing primary tests
   
   Testing server: Default-First-Site-Name\W2KSERVER
      Starting test: Replications
         * Replications Check
         * Replication Latency Check
         The replications latency check is not available on this DC.
         * Replication Site Latency Check
         ......................... W2KSERVER passed 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=local139,DC=com
            (Schema,Version 2)
         * Security Permissions Check for
           CN=Configuration,DC=local139,DC=com
            (Configuration,Version 2)
         * Security Permissions Check for
           DC=local139,DC=com
            (Domain,Version 2)
         ......................... W2KSERVER passed test NCSecDesc
      Starting test: NetLogons
         * Network Logons Privileges Check
         ......................... W2KSERVER passed test NetLogons
      Starting test: Advertising
         Warning: DsGetDcName returned information for \\SERVER1.local139.com, when we were trying to reach W2KSERVER.
         Server is not responding or is not considered suitable.
         The DC W2KSERVER is advertising itself as a DC and having a DS.
         The DC W2KSERVER is advertising as an LDAP server
         The DC W2KSERVER is advertising as having a writeable directory
         The DC W2KSERVER is advertising as a Key Distribution Center
         The DC W2KSERVER is advertising as a time server
         ......................... W2KSERVER failed test Advertising
      Starting test: KnowsOfRoleHolders
         Role Schema Owner = CN=NTDS Settings,CN=SERVER1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=local139,DC=com
         Role Domain Owner = CN=NTDS Settings,CN=SERVER1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=local139,DC=com
         Role PDC Owner = CN=NTDS Settings,CN=SERVER1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=local139,DC=com
         Role Rid Owner = CN=NTDS Settings,CN=SERVER1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=local139,DC=com
         Role Infrastructure Update Owner = CN=NTDS Settings,CN=SERVER1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=local139,DC=com
         ......................... W2KSERVER passed test KnowsOfRoleHolders
      Starting test: RidManager
         * Available RID Pool for the Domain is 2606 to 1073741823
         * SERVER1.local139.com is the RID Master
         * DsBind with RID Master was successful
         * rIDAllocationPool is 1106 to 1605
         * rIDNextRID: 1184
         * rIDPreviousAllocationPool is 1106 to 1605
         ......................... W2KSERVER passed test RidManager
      Starting test: MachineAccount
         * SPN found :LDAP/w2kserver.local139.com/local139.com
         * SPN found :LDAP/w2kserver.local139.com
         * SPN found :LDAP/W2KSERVER
         * SPN found :LDAP/w2kserver.local139.com/LOCAL139
         * SPN found :LDAP/004f3c8e-3ce7-47b6-b579-539d00da9aec._msdcs.local139.com
         * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/004f3c8e-3ce7-47b6-b579-539d00da9aec/local139.com
         * SPN found :HOST/w2kserver.local139.com/local139.com
         * SPN found :HOST/w2kserver.local139.com
         * SPN found :HOST/W2KSERVER
         * SPN found :HOST/w2kserver.local139.com/LOCAL139
         * SPN found :GC/w2kserver.local139.com/local139.com
         ......................... W2KSERVER 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: w32time
         * Checking Service: NETLOGON
         ......................... W2KSERVER passed test Services
      Test omitted by user request: OutboundSecureChannels
      Starting test: ObjectsReplicated
         W2KSERVER is in domain DC=local139,DC=com
         Checking for CN=W2KSERVER,OU=Domain Controllers,DC=local139,DC=com in domain DC=local139,DC=com on 2 servers
            Object is up-to-date on all servers.
         Checking for CN=NTDS Settings,CN=W2KSERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=local139,DC=com in domain CN=Configuration,DC=local139,DC=com on 2 servers
            Object is up-to-date on all servers.
         ......................... W2KSERVER passed test ObjectsReplicated
      Starting test: frssysvol
         * The File Replication Service SYSVOL ready test
         The registry lookup failed to determine the state of the SYSVOL.  The

         error returned  was 0 (The operation completed successfully.).  Check

         the FRS event log to see if the SYSVOL has successfully been shared.
         ......................... W2KSERVER passed test frssysvol
      Starting test: frsevent
         * The File Replication Service Event log test
         There are warning or error events within the last 24 hours after the

         SYSVOL has been shared.  Failing SYSVOL replication problems may cause

         Group Policy problems.
         An Warning Event occured.  EventID: 0x800034FD
            Time Generated: 04/14/2005   11:51:18
            Event String: File Replication Service is initializing the

system volume with data from another domain

controller. Computer W2KSERVER 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: 04/14/2005   11:53:09
            Event String: The File Replication Service is having trouble

enabling replication from SERVER1 to W2KSERVER

for c:\winnt\sysvol\domain using the DNS name

SERVER1.local139.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

SERVER1.local139.com from this computer.

 [2] FRS is not running on SERVER1.local139.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.
         ......................... W2KSERVER failed test frsevent
      Starting test: kccevent
         * The KCC Event log test
         Found no KCC errors in Directory Service Event log in the last 15 minutes.
         ......................... W2KSERVER passed test kccevent
      Starting test: systemlog
         * The System Event log test
         An Error Event occured.  EventID: 0x800009CA
            Time Generated: 04/14/2005   11:04:16
            Event String: The value named IRPstackSize in the server's

registry key LanmanServer\Parameters was not

valid, and was ignored. If you want to change the

value, change it to one that is the correct type

and is within the acceptable range, or delete the

value to use the default. This value might have

been set up by an older program that did not use

the correct boundaries.
         An Error Event occured.  EventID: 0x800009CA
            Time Generated: 04/14/2005   11:50:13
            Event String: The value named IRPstackSize in the server's

registry key LanmanServer\Parameters was not

valid, and was ignored. If you want to change the

value, change it to one that is the correct type

and is within the acceptable range, or delete the

value to use the default. This value might have

been set up by an older program that did not use

the correct boundaries.
         ......................... W2KSERVER failed test systemlog
      Test omitted by user request: VerifyReplicas
      Starting test: VerifyReferences
         The system object reference (serverReference)

         CN=W2KSERVER,OU=Domain Controllers,DC=local139,DC=com and backlink on

         CN=W2KSERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=local139,DC=com

         are correct.
         The system object reference (frsComputerReferenceBL)

         CN=W2KSERVER,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=local139,DC=com

         and backlink on CN=W2KSERVER,OU=Domain Controllers,DC=local139,DC=com

         are correct.
         The system object reference (serverReferenceBL)

         CN=W2KSERVER,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=local139,DC=com

         and backlink on

         CN=NTDS Settings,CN=W2KSERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=local139,DC=com

         are correct.
         ......................... W2KSERVER passed test VerifyReferences
      Test omitted by user request: VerifyEnterpriseReferences
   
   Testing server: Default-First-Site-Name\SERVER1
      Starting test: Replications
         * Replications Check
         [Replications Check,SERVER1] A recent replication attempt failed:
            From W2KSERVER to SERVER1
            Naming Context: CN=Schema,CN=Configuration,DC=local139,DC=com
            The replication generated an error (1722):
            The RPC server is unavailable.
            The failure occurred at 2005-04-14 11:48:14.
            The last success occurred at 2005-04-14 10:47:11.
            1 failures have occurred since the last success.
            The source W2KSERVER is responding now.
         * Replication Latency Check
            CN=Schema,CN=Configuration,DC=local139,DC=com
               Latency information for 1 entries in the vector were ignored.
                  1 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC).  
            CN=Configuration,DC=local139,DC=com
               Latency information for 1 entries in the vector were ignored.
                  1 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC).  
            DC=local139,DC=com
               Latency information for 1 entries in the vector were ignored.
                  1 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC).  
         * Replication Site Latency Check
         ......................... SERVER1 passed test Replications
      Test omitted by user request: Topology
      Test omitted by user request: CutoffServers
      Starting test: NCSecDesc
         * Security Permissions Check for
           DC=ForestDnsZones,DC=local139,DC=com
            (NDNC,Version 2)
         * Security Permissions Check for
           DC=DomainDnsZones,DC=local139,DC=com
            (NDNC,Version 2)
         * Security Permissions Check for
           CN=Schema,CN=Configuration,DC=local139,DC=com
            (Schema,Version 2)
         * Security Permissions Check for
           CN=Configuration,DC=local139,DC=com
            (Configuration,Version 2)
         * Security Permissions Check for
           DC=local139,DC=com
            (Domain,Version 2)
         ......................... SERVER1 passed test NCSecDesc
      Starting test: NetLogons
         * Network Logons Privileges Check
         ......................... SERVER1 passed test NetLogons
      Starting test: Advertising
         Fatal Error:DsGetDcName (SERVER1) call failed, error 1355
         The Locator could not find the server.
         ......................... SERVER1 failed test Advertising
      Starting test: KnowsOfRoleHolders
         Role Schema Owner = CN=NTDS Settings,CN=SERVER1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=local139,DC=com
         Role Domain Owner = CN=NTDS Settings,CN=SERVER1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=local139,DC=com
         Role PDC Owner = CN=NTDS Settings,CN=SERVER1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=local139,DC=com
         Role Rid Owner = CN=NTDS Settings,CN=SERVER1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=local139,DC=com
         Role Infrastructure Update Owner = CN=NTDS Settings,CN=SERVER1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=local139,DC=com
         ......................... SERVER1 passed test KnowsOfRoleHolders
      Starting test: RidManager
         * Available RID Pool for the Domain is 2606 to 1073741823
         * SERVER1.local139.com is the RID Master
         * DsBind with RID Master was successful
         * rIDAllocationPool is 2106 to 2605
         * rIDPreviousAllocationPool is 2106 to 2605
         * rIDNextRID: 2109
         ......................... SERVER1 passed test RidManager
      Starting test: MachineAccount
         * SPN found :LDAP/SERVER1.local139.com/local139.com
         * SPN found :LDAP/SERVER1.local139.com
         * SPN found :LDAP/SERVER1
         * SPN found :LDAP/SERVER1.local139.com/LOCAL139
         * SPN found :LDAP/dfe8f7c3-8a33-43b3-a3e3-f47b4546dfd7._msdcs.local139.com
         * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/dfe8f7c3-8a33-43b3-a3e3-f47b4546dfd7/local139.com
         * SPN found :HOST/SERVER1.local139.com/local139.com
         * SPN found :HOST/SERVER1.local139.com
         * SPN found :HOST/SERVER1
         * SPN found :HOST/SERVER1.local139.com/LOCAL139
         * SPN found :GC/SERVER1.local139.com/local139.com
         ......................... SERVER1 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: w32time
         * Checking Service: NETLOGON
         ......................... SERVER1 passed test Services
      Test omitted by user request: OutboundSecureChannels
      Starting test: ObjectsReplicated
         SERVER1 is in domain DC=local139,DC=com
         Checking for CN=SERVER1,OU=Domain Controllers,DC=local139,DC=com in domain DC=local139,DC=com on 2 servers
            Object is up-to-date on all servers.
         Checking for CN=NTDS Settings,CN=SERVER1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=local139,DC=com in domain CN=Configuration,DC=local139,DC=com on 2 servers
            Object is up-to-date on all servers.
         ......................... SERVER1 passed test ObjectsReplicated
      Starting test: frssysvol
         * The File Replication Service SYSVOL ready test
         The registry lookup failed to determine the state of the SYSVOL.  The

         error returned  was 0 (The operation completed successfully.).  Check

         the FRS event log to see if the SYSVOL has successfully been shared.
         ......................... SERVER1 passed test frssysvol
      Starting test: frsevent
         * The File Replication Service Event log test
         There are warning or error events within the last 24 hours after the

         SYSVOL has been shared.  Failing SYSVOL replication problems may cause

         Group Policy problems.
         An Warning Event occured.  EventID: 0x800034C4
            Time Generated: 04/14/2005   05:30:39
            Event String: The File Replication Service is having trouble

enabling replication from

\\w2kserver.local139.com to SERVER1 for
0
 
LVL 18

Expert Comment

by:John Gates, CISSP
ID: 13784047
Ok, I think I know what is going on.  Please do a netdiag on server1 (W2003) correct?  And the W2000 server post here.  The sysvol has not replicated because of a DNS problem but I need to see the whole picture.

-D-
0
 

Author Comment

by:UMOS
ID: 13784277
Netdiag from server1
Dont have diag tool for Windows 2000, but will try to find one.
Hmm, should I remove DNS from the windows 2000 server?

 Computer Name: SERVER1
    DNS Host Name: SERVER1.local139.com
    System info : Windows 2000 Server (Build 3790)
    Processor : x86 Family 15 Model 3 Stepping 4, GenuineIntel
    List of installed hotfixes :
        KB817688
        KB817789
        KB819696
        KB823182
        KB823353
        KB823559
        KB824105
        KB824141
        KB824146
        KB824810
        KB825119
        KB825742
        KB828035
        KB828741
        KB828750
        KB832353
        KB833987
        KB834115
        KB834707
        KB835732
        KB835768
        KB837001
        KB839210
        KB839643
        KB839645
        KB840315
        KB840374
        KB840711
        KB840987
        KB841187
        KB841356
        KB841533
        KB867460
        KB867801
        KB873376
        KB873402
        KB883114
        KB885835
        KB885836
        KB887797
        Q147222
        Q819639
        Q828026


Netcard queries test . . . . . . . : Passed
    [WARNING] The net card 'RAS Async Adapter' may not be working because it has not received any packets.



Per interface results:

    Adapter : Local Area Connection

        Netcard queries test . . . : Passed

        Host Name. . . . . . . . . : SERVER1.local139.com
        IP Address . . . . . . . . : 192.10.10.13
        Subnet Mask. . . . . . . . : 255.255.255.0
        Default Gateway. . . . . . : 192.10.10.5
        Dns Servers. . . . . . . . : 192.10.10.13
                                     192.10.10.10


        AutoConfiguration results. . . . . . : Passed

        Default gateway test . . . : Passed

        NetBT name test. . . . . . : Passed

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


Global results:


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.


NetBT transports test. . . . . . . : Passed
    List of NetBt transports currently configured:
        NetBT_Tcpip_{9C5C1404-1CB2-46DF-A060-5C22EA0E8C42}
    1 NetBt transport currently configured.


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


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


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


NetBT name test. . . . . . . . . . : Passed


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


DNS test . . . . . . . . . . . . . : Passed
    PASS - All the DNS entries for DC are registered on DNS server '192.10.10.13' and other DCs also have some of the names registered.
    PASS - All the DNS entries for DC are registered on DNS server '192.10.10.10' and other DCs also have some of the names registered.


Redir and Browser test . . . . . . : Passed
    List of NetBt transports currently bound to the Redir
        NetBT_Tcpip_{9C5C1404-1CB2-46DF-A060-5C22EA0E8C42}
    The redir is bound to 1 NetBt transport.

    List of NetBt transports currently bound to the browser
        NetBT_Tcpip_{9C5C1404-1CB2-46DF-A060-5C22EA0E8C42}
    The browser is bound to 1 NetBt transport.


DC discovery test. . . . . . . . . : Failed
        [FATAL] Cannot find DC in domain 'LOCAL139'. [ERROR_NO_SUCH_DOMAIN]


DC list test . . . . . . . . . . . : Failed
        'LOCAL139': Cannot find DC to get DC list from [test skipped].


Trust relationship test. . . . . . : Skipped


Kerberos test. . . . . . . . . . . : Skipped
        'LOCAL139': 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.

 
        [WARNING] Cannot find DC in domain 'LOCAL139'. [ERROR_NO_SUCH_DOMAIN]


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
0
 
LVL 18

Expert Comment

by:John Gates, CISSP
ID: 13784421
from the windows 2000 dc can you make its primary dns your w2k3 box and try the demotion again?  It looks like you have transferred all the roles but with DNS problems I am a bit stumped on how it occurred.  Try that and let me know if you can then demote it.

-D-
0
 

Author Comment

by:UMOS
ID: 13784462
Same error
0
 
LVL 18

Expert Comment

by:John Gates, CISSP
ID: 13784514
on the w2k box when you do an nslookup for:

SERVER1.local139.com

What happens?

If it resolves properly then on the Windows 2000 server cd there are support tools just like on the W2K3 cd let's see dcdiag from the W2K Side.  A solution is close.


-D-
0
 
LVL 18

Expert Comment

by:John Gates, CISSP
ID: 13784538
Oh yeah another thing I forgot to ask.  Please do a:

netdiag /v > netdiag.txt on the W2K3 side I want to make sure that the _SRV records are visible there.


-D-  
0
 

Author Comment

by:UMOS
ID: 13784661
Doing nslookup server1.local139.com
get the following

**** Can't find server name for address 192.10.10.13: Non-existent domain
**** Default servers are not available
Server:   Unknown
address: 192.10.10.13

Name:   server1.local139.com
Address: 192.10.10.13
0
 
LVL 18

Expert Comment

by:John Gates, CISSP
ID: 13784729
Ok. Let's get the dcdiag from W2K server.
0
 

Author Comment

by:UMOS
ID: 13784734

    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
    PASS - All the DNS entries for DC are registered on DNS server '192.10.10.13' and other DCs also have some of the names registered.
    PASS - All the DNS entries for DC are registered on DNS server '192.10.10.10' 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 'LOCAL139'
    Testing trust relationships... Skipped
    Testing Kerberos authentication... Failed
    Testing LDAP servers in Domain LOCAL139 ...
    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: SERVER1
    DNS Host Name: SERVER1.local139.com
    DNS Domain Name: local139.com
    System info : Windows 2000 Server (Build 3790)
    Processor : x86 Family 15 Model 3 Stepping 4, GenuineIntel
    Hotfixes :
        Installed?      Name
           Yes          KB817688
           Yes          KB817789
           Yes          KB819696
           Yes          KB823182
           Yes          KB823353
           Yes          KB823559
           Yes          KB824105
           Yes          KB824141
           Yes          KB824146
           Yes          KB824810
           Yes          KB825119
           Yes          KB825742
           Yes          KB828035
           Yes          KB828741
           Yes          KB828750
           Yes          KB832353
           Yes          KB833987
           Yes          KB834115
           Yes          KB834707
           Yes          KB835732
           Yes          KB835768
           Yes          KB837001
           Yes          KB839210
           Yes          KB839643
           Yes          KB839645
           Yes          KB840315
           Yes          KB840374
           Yes          KB840711
           Yes          KB840987
           Yes          KB841187
           Yes          KB841356
           Yes          KB841533
           Yes          KB867460
           Yes          KB867801
           Yes          KB873376
           Yes          KB873402
           Yes          KB883114
           Yes          KB885835
           Yes          KB885836
           Yes          KB887797
           Yes          Q147222
           Yes          Q819639
           Yes          Q828026


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

    Information of Netcard drivers:

    ---------------------------------------------------------------------------
    Description: RAS Async Adapter
    Device: \DEVICE\{9BAB0A5D-4D24-4FA5-BFD1-46392EEBF94B}

    Media State:                     Connected

    Device State:                    Connected
    Connect Time:                    3 days, 14:46:17
    Media Speed:                     28 Kbps

    Packets Sent:                    0
    Bytes Sent (Optional):           0

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

    [WARNING] The net card 'RAS Async Adapter' may not be working because it has not received any packets.
    ---------------------------------------------------------------------------
    Description: Broadcom NetXtreme 5721 Gigabit Controller
    Device: \DEVICE\{9C5C1404-1CB2-46DF-A060-5C22EA0E8C42}

    Media State:                     Connected

    Device State:                    Connected
    Connect Time:                    3 days, 14:47:53
    Media Speed:                     100 Mbps

    Packets Sent:                    1161060
    Bytes Sent (Optional):           0

    Packets Received:                1229562
    Directed Pkts Recd (Optional):   1056714
    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 . . . . . . . . : {9C5C1404-1CB2-46DF-A060-5C22EA0E8C42}

        Netcard queries test . . . : Passed

        Adapter type . . . . . . . : Ethernet
        Host Name. . . . . . . . . : SERVER1.local139.com
        Description. . . . . . . . : Broadcom NetXtreme 5721 Gigabit Controller
        Physical Address . . . . . : 00-0F-1F-F8-49-F4
        Dhcp Enabled . . . . . . . : No
        DHCP ClassID . . . . . . . :
        Autoconfiguration Enabled. : Yes
        IP Address . . . . . . . . : 192.10.10.13
        Subnet Mask. . . . . . . . : 255.255.255.0
        Default Gateway. . . . . . : 192.10.10.5
        Dns Servers. . . . . . . . : 192.10.10.13
                                     192.10.10.10

        IpConfig results . . . . . : Passed

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

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

        NetBT name test. . . . . . : Passed
            NetBT_Tcpip_{9C5C1404-1CB2-46DF-A060-5C22EA0E8C42}
            SERVER1        <00>  UNIQUE      REGISTERED
            LOCAL139       <00>  GROUP       REGISTERED
            LOCAL139       <1C>  GROUP       REGISTERED
            SERVER1        <20>  UNIQUE      REGISTERED
            LOCAL139       <1B>  UNIQUE      REGISTERED
            LOCAL139       <1E>  GROUP       REGISTERED
            SERVER1        <03>  UNIQUE      REGISTERED
            LOCAL139       <1D>  UNIQUE      REGISTERED
            ..__MSBROWSE__.<01>  GROUP       REGISTERED
            ADMINISTRATOR  <03>  UNIQUE      REGISTERED
            SERVER1        <01>  UNIQUE      REGISTERED

            NetBios Resolution : via DHCP

            Netbios Remote Cache Table
            Name           Type              HostAddress         Life [sec]
            ---------------------------------------------------------------
            RENEEB         <20>  UNIQUE      192.10.10.169         545
            CRYSTALD       <20>  UNIQUE      192.10.10.153         552
            HEALTH-9NJJC6G3<20>  UNIQUE      192.10.10.155         75


        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 . . . . . . : Yes
    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. . . . . . : LOCAL139
    Dns domain name. . . . . . . . : local139.com
    Dns forest name. . . . . . . . : local139.com
    Domain Guid. . . . . . . . . . : {829AB659-A2EE-435B-959E-0ECA64443E77}
    Domain Sid . . . . . . . . . . : S-1-5-21-73586283-1450960922-682003330
    Logon User . . . . . . . . . . : Administrator
    Logon Domain . . . . . . . . . : LOCAL139


NetBT transports test. . . . . . . : Passed
    List of NetBt transports currently configured:
        NetBT_Tcpip_{9C5C1404-1CB2-46DF-A060-5C22EA0E8C42}
    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 : 14
        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   :6
        Description: RSVP TCP Service Provider
            Provider Version   :6
            Max message size  : Stream Oriented
        Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{9C5C1404-1CB2-46DF-A060-5C22EA0E8C42}] SEQPACKET 0
            Provider Version   :2
        Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{9C5C1404-1CB2-46DF-A060-5C22EA0E8C42}] DATAGRAM 0
            Provider Version   :2
        Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{1F4863A1-5EB2-4910-B37C-C9C7C72BEC43}] SEQPACKET 1
            Provider Version   :2
        Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{1F4863A1-5EB2-4910-B37C-C9C7C72BEC43}] DATAGRAM 1
            Provider Version   :2
        Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{B3F7B406-3CAF-44C9-8449-269282D2E56F}] SEQPACKET 2
            Provider Version   :2
        Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{B3F7B406-3CAF-44C9-8449-269282D2E56F}] DATAGRAM 2
            Provider Version   :2
        Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{FF5D96F0-25CA-4B9E-A0C4-62ADD2579F65}] SEQPACKET 3
            Provider Version   :2
        Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{FF5D96F0-25CA-4B9E-A0C4-62ADD2579F65}] DATAGRAM 3
            Provider Version   :2
        Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{6830F158-8052-47BA-A82F-BB3F93C5AE4F}] SEQPACKET 4
            Provider Version   :2
        Description: MSAFD NetBIOS [\Device\NetBT_Tcpip_{6830F158-8052-47BA-A82F-BB3F93C5AE4F}] DATAGRAM 4
            Provider Version   :2

    Max UDP size : 65507 bytes


DNS test . . . . . . . . . . . . . : Passed
      Interface {9C5C1404-1CB2-46DF-A060-5C22EA0E8C42}
        DNS Domain: local139.com
        DNS Servers: 192.10.10.13 192.10.10.10
        IP Address:         Expected registration with PDN (primary DNS domain name):
          Hostname: SERVER1.local139.com.
          Authoritative zone: local139.com.
          Primary DNS server: SERVER1.local139.com 192.10.10.13
          Authoritative NS:192.10.10.10 192.10.10.13
Check the DNS registration for DCs entries on DNS server '192.10.10.13'
The Record is different on DNS server '192.10.10.13'.
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.10.10.13', no need to re-register.

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

The record on DNS server 192.10.10.13 is:
DNS NAME = local139.com
DNS DATA =
            A  192.10.10.13
            A  192.10.10.10
+------------------------------------------------------+

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

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

The record on DNS server 192.10.10.13 is:
DNS NAME = _ldap._tcp.local139.com
DNS DATA =
            SRV 0 100 389 w2kserver.local139.com
            SRV 0 100 389 server1.local139.com
+------------------------------------------------------+

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

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

The record on DNS server 192.10.10.13 is:
DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.local139.com
DNS DATA =
            SRV 0 100 389 w2kserver.local139.com
            SRV 0 100 389 server1.local139.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.829ab659-a2ee-435b-959e-0eca64443e77.domains._msdcs.local139.com.
DNS DATA =
            SRV 0 100 389 SERVER1.local139.com.

The record on DNS server 192.10.10.13 is:
DNS NAME = _ldap._tcp.829ab659-a2ee-435b-959e-0eca64443e77.domains._msdcs.local139.com
DNS DATA =
            SRV 0 100 389 server1.local139.com
            SRV 0 100 389 w2kserver.local139.com
+------------------------------------------------------+

The Record is correct on DNS server '192.10.10.13'.

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

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

The record on DNS server 192.10.10.13 is:
DNS NAME = _kerberos._tcp.dc._msdcs.local139.com
DNS DATA =
            SRV 0 100 88 w2kserver.local139.com
            SRV 0 100 88 server1.local139.com
+------------------------------------------------------+

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

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

The record on DNS server 192.10.10.13 is:
DNS NAME = _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.local139.com
DNS DATA =
            SRV 0 100 88 w2kserver.local139.com
            SRV 0 100 88 server1.local139.com
+------------------------------------------------------+

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

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

The record on DNS server 192.10.10.13 is:
DNS NAME = _ldap._tcp.dc._msdcs.local139.com
DNS DATA =
            SRV 0 100 389 server1.local139.com
            SRV 0 100 389 w2kserver.local139.com
+------------------------------------------------------+

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

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

The record on DNS server 192.10.10.13 is:
DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.local139.com
DNS DATA =
            SRV 0 100 389 w2kserver.local139.com
            SRV 0 100 389 server1.local139.com
+------------------------------------------------------+

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

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

The record on DNS server 192.10.10.13 is:
DNS NAME = _kerberos._tcp.local139.com
DNS DATA =
            SRV 0 100 88 server1.local139.com
            SRV 0 100 88 w2kserver.local139.com
+------------------------------------------------------+

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

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

The record on DNS server 192.10.10.13 is:
DNS NAME = _kerberos._tcp.Default-First-Site-Name._sites.local139.com
DNS DATA =
            SRV 0 100 88 server1.local139.com
            SRV 0 100 88 w2kserver.local139.com
+------------------------------------------------------+

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

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

The record on DNS server 192.10.10.13 is:
DNS NAME = _kerberos._udp.local139.com
DNS DATA =
            SRV 0 100 88 server1.local139.com
            SRV 0 100 88 w2kserver.local139.com
+------------------------------------------------------+

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

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

The record on DNS server 192.10.10.13 is:
DNS NAME = _kpasswd._tcp.local139.com
DNS DATA =
            SRV 0 100 464 server1.local139.com
            SRV 0 100 464 w2kserver.local139.com
+------------------------------------------------------+

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

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

The record on DNS server 192.10.10.13 is:
DNS NAME = _kpasswd._udp.local139.com
DNS DATA =
            SRV 0 100 464 server1.local139.com
            SRV 0 100 464 w2kserver.local139.com
+------------------------------------------------------+

The Record is correct on DNS server '192.10.10.13'.

The Record is correct on DNS server '192.10.10.13'.

The Record is correct on DNS server '192.10.10.13'.

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = gc._msdcs.local139.com.
DNS DATA =
            A  192.10.10.13

The record on DNS server 192.10.10.13 is:
DNS NAME = gc._msdcs.local139.com
DNS DATA =
            A  192.10.10.13
            A  192.10.10.19
+------------------------------------------------------+

The Record is correct on DNS server '192.10.10.13'.

The Record is correct on DNS server '192.10.10.13'.

The Record is correct on DNS server '192.10.10.13'.

The Record is correct on DNS server '192.10.10.13'.

The Record is correct on DNS server '192.10.10.13'.

The Record is correct on DNS server '192.10.10.13'.

The Record is correct on DNS server '192.10.10.13'.

The Record is correct on DNS server '192.10.10.13'.

    PASS - All the DNS entries for DC are registered on DNS server '192.10.10.13' and other DCs also have some of the names registered.
Check the DNS registration for DCs entries on DNS server '192.10.10.10'
The Record is different on DNS server '192.10.10.10'.
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.10.10.10', no need to re-register.

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

The record on DNS server 192.10.10.10 is:
DNS NAME = local139.com
DNS DATA =
            A  192.10.10.13
            A  192.10.10.10
+------------------------------------------------------+

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

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

The record on DNS server 192.10.10.10 is:
DNS NAME = _ldap._tcp.local139.com
DNS DATA =
            SRV 0 100 389 server1.local139.com
            SRV 0 100 389 w2kserver.local139.com
+------------------------------------------------------+

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

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

The record on DNS server 192.10.10.10 is:
DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.local139.com
DNS DATA =
            SRV 0 100 389 server1.local139.com
            SRV 0 100 389 w2kserver.local139.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.829ab659-a2ee-435b-959e-0eca64443e77.domains._msdcs.local139.com.
DNS DATA =
            SRV 0 100 389 SERVER1.local139.com.

The record on DNS server 192.10.10.10 is:
DNS NAME = _ldap._tcp.829ab659-a2ee-435b-959e-0eca64443e77.domains._msdcs.local139.com
DNS DATA =
            SRV 0 100 389 server1.local139.com
            SRV 0 100 389 w2kserver.local139.com
+------------------------------------------------------+

The Record is correct on DNS server '192.10.10.10'.

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

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

The record on DNS server 192.10.10.10 is:
DNS NAME = _kerberos._tcp.dc._msdcs.local139.com
DNS DATA =
            SRV 0 100 88 server1.local139.com
            SRV 0 100 88 w2kserver.local139.com
+------------------------------------------------------+

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

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

The record on DNS server 192.10.10.10 is:
DNS NAME = _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.local139.com
DNS DATA =
            SRV 0 100 88 server1.local139.com
            SRV 0 100 88 w2kserver.local139.com
+------------------------------------------------------+

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

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

The record on DNS server 192.10.10.10 is:
DNS NAME = _ldap._tcp.dc._msdcs.local139.com
DNS DATA =
            SRV 0 100 389 server1.local139.com
            SRV 0 100 389 w2kserver.local139.com
+------------------------------------------------------+

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

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

The record on DNS server 192.10.10.10 is:
DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.local139.com
DNS DATA =
            SRV 0 100 389 server1.local139.com
            SRV 0 100 389 w2kserver.local139.com
+------------------------------------------------------+

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

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

The record on DNS server 192.10.10.10 is:
DNS NAME = _kerberos._tcp.local139.com
DNS DATA =
            SRV 0 100 88 server1.local139.com
            SRV 0 100 88 w2kserver.local139.com
+------------------------------------------------------+

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

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

The record on DNS server 192.10.10.10 is:
DNS NAME = _kerberos._tcp.Default-First-Site-Name._sites.local139.com
DNS DATA =
            SRV 0 100 88 server1.local139.com
            SRV 0 100 88 w2kserver.local139.com
+------------------------------------------------------+

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

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

The record on DNS server 192.10.10.10 is:
DNS NAME = _kerberos._udp.local139.com
DNS DATA =
            SRV 0 100 88 server1.local139.com
            SRV 0 100 88 w2kserver.local139.com
+------------------------------------------------------+

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

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

The record on DNS server 192.10.10.10 is:
DNS NAME = _kpasswd._tcp.local139.com
DNS DATA =
            SRV 0 100 464 server1.local139.com
            SRV 0 100 464 w2kserver.local139.com
+------------------------------------------------------+

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

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

The record on DNS server 192.10.10.10 is:
DNS NAME = _kpasswd._udp.local139.com
DNS DATA =
            SRV 0 100 464 server1.local139.com
            SRV 0 100 464 w2kserver.local139.com
+------------------------------------------------------+

The Record is correct on DNS server '192.10.10.10'.

The Record is correct on DNS server '192.10.10.10'.

The Record is correct on DNS server '192.10.10.10'.

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = gc._msdcs.local139.com.
DNS DATA =
            A  192.10.10.13

The record on DNS server 192.10.10.10 is:
DNS NAME = gc._msdcs.local139.com
DNS DATA =
            A  192.10.10.13
            A  192.10.10.19
+------------------------------------------------------+

The Record is correct on DNS server '192.10.10.10'.

The Record is correct on DNS server '192.10.10.10'.

The Record is correct on DNS server '192.10.10.10'.

The Record is correct on DNS server '192.10.10.10'.

The Record is correct on DNS server '192.10.10.10'.

The Record is correct on DNS server '192.10.10.10'.

The Record is correct on DNS server '192.10.10.10'.

The Record is correct on DNS server '192.10.10.10'.

    PASS - All the DNS entries for DC are registered on DNS server '192.10.10.10' 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_{9C5C1404-1CB2-46DF-A060-5C22EA0E8C42}
    The redir is bound to 1 NetBt transport.

    List of transports currently bound to the browser
        NetBT_Tcpip_{9C5C1404-1CB2-46DF-A060-5C22EA0E8C42}
    The browser is bound to 1 NetBt transport.
    Mailslot test for LOCAL139* passed.


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

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


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


Trust relationship test. . . . . . : Skipped


Kerberos test. . . . . . . . . . . : Skipped
        'LOCAL139': 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 'LOCAL139':
        [WARNING] Cannot find DC in domain 'LOCAL139'. [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.10.10.5      192.10.10.13      20
       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.10.10.0     255.255.255.0      192.10.10.13      192.10.10.13      20
    192.10.10.13   255.255.255.255         127.0.0.1         127.0.0.1      20
   192.10.10.255   255.255.255.255      192.10.10.13      192.10.10.13      20
       224.0.0.0         240.0.0.0      192.10.10.13      192.10.10.13      20
 255.255.255.255   255.255.255.255      192.10.10.13      192.10.10.13       1
No persistent route entries.


Netstat information test . . . . . : Passed


    Interface Statistics

                                    Received             Sent
    Unicast Packets                466620642        783335121
    Non-unicast packets                74010             8324
    Discards                               0                0
    Errors                                 0                0
    Unknown protocols                 107101           458284

    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         =  65539
    Description             =  Broadcom NetXtreme 5721 Gigabit Controller
    Type                    =  6
    MTU                     =  1500
    Speed                   =  100000000
    Physical Address        =  00-0F-1F-F8-49-F4
    Administrative Status   =  1
    Operational Status      =  1
    Last Changed            =  161282780
    Output Queue Length     =  0



    Active Connections

  Proto Local Address         Foreign Address                           State
    TCP   SERVER1:nameserver    SERVER1.local139.com:22645                LISTENING
    TCP   SERVER1:domain        SERVER1.local139.com:57431                LISTENING
    TCP   SERVER1:kerberos      SERVER1.local139.com:6195                 LISTENING
    TCP   SERVER1:epmap         SERVER1.local139.com:49381                LISTENING
    TCP   SERVER1:ldap          SERVER1.local139.com:4110                 LISTENING
    TCP   SERVER1:microsoft-ds  SERVER1.local139.com:45057                LISTENING
    TCP   SERVER1:kpasswd       SERVER1.local139.com:20611                LISTENING
    TCP   SERVER1:593           SERVER1.local139.com:30830                LISTENING
    TCP   SERVER1:ldaps         SERVER1.local139.com:37005                LISTENING
    TCP   SERVER1:1025          SERVER1.local139.com:36915                LISTENING
    TCP   SERVER1:1026          SERVER1.local139.com:12348                LISTENING
    TCP   SERVER1:1028          SERVER1.local139.com:43262                LISTENING
    TCP   SERVER1:1311          SERVER1.local139.com:43182                LISTENING
    TCP   SERVER1:pptp          SERVER1.local139.com:10364                LISTENING
    TCP   SERVER1:2160          SERVER1.local139.com:59562                LISTENING
    TCP   SERVER1:2161          SERVER1.local139.com:14387                LISTENING
    TCP   SERVER1:2260          SERVER1.local139.com:14373                LISTENING
    TCP   SERVER1:3005          SERVER1.local139.com:6309                 LISTENING
    TCP   SERVER1:3007          SERVER1.local139.com:28762                LISTENING
    TCP   SERVER1:3019          SERVER1.local139.com:55302                LISTENING
    TCP   SERVER1:3024          SERVER1.local139.com:69                   LISTENING
    TCP   SERVER1:3052          SERVER1.local139.com:12427                LISTENING
    TCP   SERVER1:3185          SERVER1.local139.com:59639                LISTENING
    TCP   SERVER1:3268          SERVER1.local139.com:43042                LISTENING
    TCP   SERVER1:3269          SERVER1.local139.com:43166                LISTENING
    TCP   SERVER1:3338          SERVER1.local139.com:2288                 LISTENING
    TCP   SERVER1:3389          SERVER1.local139.com:4115                 LISTENING
    TCP   SERVER1:6101          SERVER1.local139.com:4135                 LISTENING
    TCP   SERVER1:6106          SERVER1.local139.com:43145                LISTENING
    TCP   SERVER1:8000          SERVER1.local139.com:2237                 LISTENING
    TCP   SERVER1:8081          SERVER1.local139.com:57581                LISTENING
    TCP   SERVER1:10000         SERVER1.local139.com:2169                 LISTENING
    TCP   SERVER1:ldap          SERVER1.local139.com:1052                 ESTABLISHED
    TCP   SERVER1:ldap          SERVER1.local139.com:1055                 ESTABLISHED
    TCP   SERVER1:ldap          SERVER1.local139.com:1056                 ESTABLISHED
    TCP   SERVER1:ldap          SERVER1.local139.com:3183                 ESTABLISHED
    TCP   SERVER1:1052          SERVER1.local139.com:ldap                 ESTABLISHED
    TCP   SERVER1:1055          SERVER1.local139.com:ldap                 ESTABLISHED
    TCP   SERVER1:1056          SERVER1.local139.com:ldap                 ESTABLISHED
    TCP   SERVER1:3039          SERVER1.local139.com:8408                 LISTENING
    TCP   SERVER1:3183          SERVER1.local139.com:ldap                 ESTABLISHED
    TCP   SERVER1:nameserver    W2KSERVER:3381                            ESTABLISHED
    TCP   SERVER1:netbios-ssn   SERVER1.local139.com:30758                LISTENING
    TCP   SERVER1:netbios-ssn   RENEEB:1394                               ESTABLISHED
    TCP   SERVER1:ldap          SERVER1.local139.com:3670                 ESTABLISHED
    TCP   SERVER1:microsoft-ds  JEAN-OZKKR0:1153                          ESTABLISHED
    TCP   SERVER1:microsoft-ds  192.10.10.167:1132                        ESTABLISHED
    TCP   SERVER1:microsoft-ds  192.10.10.168:3246                        ESTABLISHED
    TCP   SERVER1:1025          W2KSERVER:1061                            ESTABLISHED
    TCP   SERVER1:1025          SERVER1.local139.com:3011                 ESTABLISHED
    TCP   SERVER1:1172          SERVER1.local139.com:2161                 ESTABLISHED
    TCP   SERVER1:2161          SERVER1.local139.com:1172                 ESTABLISHED
    TCP   SERVER1:3002          W2KSERVER:ldap                            CLOSE_WAIT
    TCP   SERVER1:3007          W2KSERVER:1162                            ESTABLISHED
    TCP   SERVER1:3011          SERVER1.local139.com:1025                 ESTABLISHED
    TCP   SERVER1:3022          SERVER1.local139.com:ldap                 CLOSE_WAIT
    TCP   SERVER1:3157          W2KSERVER:ldap                            CLOSE_WAIT
    TCP   SERVER1:3179          SERVER1.local139.com:ldap                 CLOSE_WAIT
    TCP   SERVER1:3532          W2KSERVER:1026                            ESTABLISHED
    TCP   SERVER1:3544          SERVER1.local139.com:epmap                TIME_WAIT
    TCP   SERVER1:3545          SERVER1.local139.com:1025                 TIME_WAIT
    TCP   SERVER1:3546          SERVER1.local139.com:1025                 TIME_WAIT
    TCP   SERVER1:3548          W2KSERVER:epmap                           TIME_WAIT
    TCP   SERVER1:3549          W2KSERVER:epmap                           TIME_WAIT
    TCP   SERVER1:3550          W2KSERVER:1117                            TIME_WAIT
    TCP   SERVER1:3551          W2KSERVER:1117                            TIME_WAIT
    TCP   SERVER1:3552          W2KSERVER:1026                            TIME_WAIT
    TCP   SERVER1:3566          RENEEB:netbios-ssn                        TIME_WAIT
    TCP   SERVER1:3568          192.10.10.24:9100                         TIME_WAIT
    TCP   SERVER1:3577          CRYSTALD:microsoft-ds                     TIME_WAIT
    TCP   SERVER1:3579          RNP80B13C:9100                            TIME_WAIT
    TCP   SERVER1:3581          W2KSERVER:1026                            ESTABLISHED
    TCP   SERVER1:3644          JEAN-OZKKR0:microsoft-ds                  ESTABLISHED
    TCP   SERVER1:3646          192.10.10.26:9100                         TIME_WAIT
    TCP   SERVER1:3652          RENEEB:microsoft-ds                       ESTABLISHED
    TCP   SERVER1:3654          192.10.10.24:9100                         TIME_WAIT
    TCP   SERVER1:3670          SERVER1.local139.com:ldap                 ESTABLISHED
    UDP  SERVER1:nameserver    *:*                                    
    UDP  SERVER1:microsoft-ds  *:*                                    
    UDP  SERVER1:isakmp        *:*                                    
    UDP  SERVER1:1030          *:*                                    
    UDP  SERVER1:1051          *:*                                    
    UDP  SERVER1:1057          *:*                                    
    UDP  SERVER1:1171          *:*                                    
    UDP  SERVER1:ms-sql-m      *:*                                    
    UDP  SERVER1:2148          *:*                                    
    UDP  SERVER1:2160          *:*                                    
    UDP  SERVER1:2161          *:*                                    
    UDP  SERVER1:3001          *:*                                    
    UDP  SERVER1:3003          *:*                                    
    UDP  SERVER1:3008          *:*                                    
    UDP  SERVER1:3036          *:*                                    
    UDP  SERVER1:3052          *:*                                    
    UDP  SERVER1:3077          *:*                                    
    UDP  SERVER1:3156          *:*                                    
    UDP  SERVER1:3178          *:*                                    
    UDP  SERVER1:3181          *:*                                    
    UDP  SERVER1:3182          *:*                                    
    UDP  SERVER1:3361          *:*                                    
    UDP  SERVER1:4500          *:*                                    
    UDP  SERVER1:4942          *:*                                    
    UDP  SERVER1:7846          *:*                                    
    UDP  SERVER1:8081          *:*                                    
    UDP  SERVER1:8082          *:*                                    
    UDP  SERVER1:domain        *:*                                    
    UDP  SERVER1:ntp           *:*                                    
    UDP  SERVER1:3050          *:*                                    
    UDP  SERVER1:3051          *:*                                    
    UDP  SERVER1:3180          *:*                                    
    UDP  SERVER1:3801          *:*                                    
    UDP  SERVER1:domain        *:*                                    
    UDP  SERVER1:bootps        *:*                                    
    UDP  SERVER1:bootpc        *:*                                    
    UDP  SERVER1:kerberos      *:*                                    
    UDP  SERVER1:ntp           *:*                                    
    UDP  SERVER1:netbios-ns    *:*                                    
    UDP  SERVER1:netbios-dgm   *:*                                    
    UDP  SERVER1:389           *:*                                    
    UDP  SERVER1:kpasswd       *:*                                    
    UDP  SERVER1:2535          *:*                                    


    IP  Statistics

    Packets Received              =   2,804,446
    Received Header Errors        =   0
    Received Address Errors       =   0
    Datagrams Forwarded           =   0
    Unknown Protocols Received    =   0
    Received Packets Discarded    =   0
    Received Packets Delivered    =   2,804,445
    Output Requests               =   2,892,993
    Routing Discards              =   0
    Discarded Output Packets      =   0
    Output Packet No Route        =   0
    Reassembly  Required          =   2
    Reassembly Successful         =   1
    Reassembly Failures           =   0
    Datagrams successfully fragmented  =   1
    Datagrams failing fragmentation    =   0
    Fragments Created                  =   2
    Forwarding                        =    1
    Default TTL                       =    128
    Reassembly  timeout               =    60


    TCP Statistics

    Active Opens               =    15,852
    Passive Opens              =    7,366
    Failed Connection Attempts =    1,958
    Reset Connections          =    1,392
    Current Connections        =    30
    Received Segments          =    2,684,891
    Segment Sent               =    2,586,114
    Segment Retransmitted      =    202,977
    Retransmission Timeout Algorithm  =   vanj
    Minimum Retransmission Timeout  = 300
    Maximum Retransmission Timeout  = 120,000
    Maximum Number of Connections   = -1


    UDP Statistics

    Datagrams Received    =   96,807
    No Ports              =   9,771
    Receive Errors        =   0
    Datagrams Sent        =   77,660


    ICMP Statistics

                              Received           Sent
    Messages                    25,929         25,929
    Errors                           0              0
    Destination  Unreachable        21             21
    Time    Exceeded                 0              0
    Parameter Problems               0              0
    Source Quenchs                   0              0
    Redirects                        0              0
    Echos                       12,881         12,881
    Echo Replies                12,994         12,994
    Timestamps                       0              0
    Timestamp Replies                0              0
    Address Masks                    0              0
    Address Mask Replies             0              0


Bindings test. . . . . . . . . . . : Passed
    Component Name : Broadcom Advanced Server Program Driver
    Bind Name: Blfp
    Binding Paths:
        Owner of the binding path : Broadcom Advanced Server Program Driver
        Binding Enabled: No
    Interfaces of the binding path:
        -Interface Name: ndis5
            Upper Component: Broadcom Advanced Server Program Driver
            Lower Component: Broadcom NetXtreme 5721 Gigabit Controller


    Component Name : Point to Point Protocol Over Ethernet
    Bind Name: RasPppoe
    Binding Paths:
        Owner of the binding path : Point to Point Protocol Over Ethernet
        Binding Enabled: Yes
    Interfaces of the binding path:
        -Interface Name: ndis5
            Upper Component: Point to Point Protocol Over Ethernet
            Lower Component: Broadcom NetXtreme 5721 Gigabit Controller


    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: ndiswanasync
            Upper Component: Remote Access NDIS WAN Driver
            Lower Component: RAS Async Adapter

        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 (PPPOE)

        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)


    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: Broadcom NetXtreme 5721 Gigabit Controller


    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: Broadcom NetXtreme 5721 Gigabit 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: Broadcom NetXtreme 5721 Gigabit 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: Broadcom NetXtreme 5721 Gigabit 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 : WebClient
    Bind Name: WebClient
    Binding Paths:

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

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

    Component Name : Network Load Balancing
    Bind Name: Wlbs
    Binding Paths:
        Owner of the binding path : Network Load Balancing
        Binding Enabled: No
    Interfaces of the binding path:
        -Interface Name: ndis5
            Upper Component: Network Load Balancing
            Lower Component: Broadcom NetXtreme 5721 Gigabit Controller


    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: Broadcom NetXtreme 5721 Gigabit 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 : Generic Packet Classifier
    Bind Name: Gpc
    Binding Paths:

    Component Name : Application Layer Gateway
    Bind Name: ALG
    Binding Paths:

    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: Broadcom NetXtreme 5721 Gigabit 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 : Broadcom NetXtreme 5721 Gigabit Controller
    Bind Name: {9C5C1404-1CB2-46DF-A060-5C22EA0E8C42}
    Binding Paths:

    Component Name : RAS Async Adapter
    Bind Name: {9BAB0A5D-4D24-4FA5-BFD1-46392EEBF94B}
    Binding Paths:

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

    Component Name : Direct Parallel
    Bind Name: {C2617B0A-1096-44B2-AC9A-FC38AA316AA3}
    Binding Paths:

    Component Name : WAN Miniport (PPPOE)
    Bind Name: {27E6368F-C279-4870-AB32-8C50797A514B}
    Binding Paths:

    Component Name : WAN Miniport (PPTP)
    Bind Name: {F0A866C1-1FAF-4C4F-96D4-D73BDEC06195}
    Binding Paths:

    Component Name : WAN Miniport (L2TP)
    Bind Name: {B5282BE2-5661-43FA-B765-8D0F2CA0E934}
    Binding Paths:



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


Modem diagnostics test . . . . . . : Passed

    Name . . . . . . . . . . . . . : Conexant D850 56K V.9x DFVc Modem
        DeviceID . . . . . . . . . : 0
        Port . . . . . . . . . . . : COM3
        Negotiated Speed . . . . . : 0
        Compression. . . . . . . . : Off
        Error control. . . . . . . : Off
        Forced error control . . . : Off
        Cellular . . . . . . . . . : Off
        Flowcontrol hard . . . . . : Off
        Flowcontrol soft . . . . . : Off
        CCITT override . . . . . . : Off
        Speed adjust . . . . . . . : Off
        Tone dial. . . . . . . . . : Off
        Blind dial . . . . . . . . : Off
        V23 override . . . . . . . : Off

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

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


The command completed successfully
0
 
LVL 18

Expert Comment

by:John Gates, CISSP
ID: 13784814
Follow the instructions here after making a system state backup of the 2000 server:

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


0
 

Author Comment

by:UMOS
ID: 13784846
Thanks for all your help will try, and will let you know of the outcome.
0
 
LVL 18

Accepted Solution

by:
John Gates, CISSP earned 2000 total points
ID: 13784863
K before hand I would also suggest shutting the W2K server down and make sure that the domain operates correctly before the /forceremoval switch


-D-
0
 

Author Comment

by:UMOS
ID: 13795411
Found out another company has taken over the domain...must've lapsed and contact was not notified (we have just gotten this client in the past year and half or so)
gave points for all your help....
Thanks

any suggestions for a peaceful way to set up another domain, with little down time to client????
0
 
LVL 18

Expert Comment

by:John Gates, CISSP
ID: 13795431
You can rename the domain if you are in server 2003 forest functional level ;-)

-D-
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

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…
ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
This Micro Tutorial will teach you how to add a cinematic look to any film or video out there. There are very few simple steps that you will follow to do so. This will be demonstrated using Adobe Premiere Pro CS6.
With just a little bit of  SQL and VBA, many doors open to cool things like synchronize a list box to display data relevant to other information on a form.  If you have never written code or looked at an SQL statement before, no problem! ...  give i…

834 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