Wins Event ID 4243

Hello

I recently replaced a domain controller.
Everything is configured, but I receive errors in event viewer regarding WINS.

ID 4243
WINS Pull thread encountered an error during the process of sending a push
notification to another WINS.

WINS config seems to be configed fine.

Any ideas how to solve this?

Best Regards

Mark

Hello mark,

Have a look here:
http://support.microsoft.com/kb/321208

http://www.jsifaq.com/SF/Tips/Tip.aspx?id=1849

Best regards

Myweb
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

> Hello
>
> I recently replaced a domain controller.
> Everything is configured, but I receive errors in event viewer
> regarding WINS.
> ID 4243
> WINS Pull thread encountered an error during the process of sending a
> push
> notification to another WINS.
> WINS config seems to be configed fine.
>
> Any ideas how to solve this?
>
> Best Regards
>
> Mark
>

Thanks for replying Myweb

I have checked the article in the link you've send but was still unable to
fix this problem.
I will give you some background info on this issue.
Maybe this is related to this problem.


The new domain controller is a windows 2003 server x64 (=dc1).
This server has Global catalog enabled and is bridgehead server.
It holds the RID, PDC and Infrastructure FSMO roles.
There are 4 domain controllers in 2 sites (2 per site).
Each Dc is a win 2003 DNS and WInS server.
DC1 is however not functioning correct as dcdiag shows a problem:

Failed test advertising -- dsgetdcname returned information for dc2 when we
trying to reach dc1

Netdiag shows this error: Domain Membership test ..... Failed
The system volume has not been completely replicated to the local machine.
Machine is not working properly as a DC.

And event viewer shows this NTFRS id 13566: FRS is scanning data in the
system volume. Computer DC1 cannot become a domain controller until this
process is complete. the system volume will then be shared as SYSVOL

I have however shared Sysvol and netlogon manually.

Could they be related to the wins error?

Thanks in advance

Mark

"Myweb" wrote:

> Hello mark,
>
> Have a look here:
> http://support.microsoft.com/kb/321208
>
> http://www.jsifaq.com/SF/Tips/Tip.aspx?id=1849
>
> Best regards
>
> Myweb
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
>

Hello mark,

How are the 4 located by name? Site A and Site B and how are the NIC's configured
for DNS pointing to which one, maybe post an ipconfig /all from the 4 DC's.

Best regards

Myweb
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

> Thanks for replying Myweb
>
> I have checked the article in the link you've send but was still
> unable to
> fix this problem.
> I will give you some background info on this issue.
> Maybe this is related to this problem.
> The new domain controller is a windows 2003 server x64 (=dc1).
> This server has Global catalog enabled and is bridgehead server.
> It holds the RID, PDC and Infrastructure FSMO roles.
> There are 4 domain controllers in 2 sites (2 per site).
> Each Dc is a win 2003 DNS and WInS server.
> DC1 is however not functioning correct as dcdiag shows a problem:
> Failed test advertising -- dsgetdcname returned information for dc2
> when we trying to reach dc1
>
> Netdiag shows this error: Domain Membership test ..... Failed
> The system volume has not been completely replicated to the local
> machine.
> Machine is not working properly as a DC.
> And event viewer shows this NTFRS id 13566: FRS is scanning data in
> the system volume. Computer DC1 cannot become a domain controller
> until this process is complete. the system volume will then be shared
> as SYSVOL
>
> I have however shared Sysvol and netlogon manually.
>
> Could they be related to the wins error?
>
> Thanks in advance
>
> Mark
>
> "Myweb" wrote:
>
>> Hello mark,
>>
>> Have a look here:
>> http://support.microsoft.com/kb/321208
>> http://www.jsifaq.com/SF/Tips/Tip.aspx?id=1849
>>
>> Best regards
>>
>> Myweb
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.

Thanks again for your reply Myweb.

our domain:

DC in site A:

ANTDOM2 ANTDOM3

DC in site B:

BNTDOM1 BNTDOM2


info: ANTDOM2 replicates via rpc to antdom3
ANTDOM3 replicates via Ip to BNTDOM1
BNTDOM1 replicates via IP to ANTDOM3
BNTDOM1 replicates via RPC to BNTDOM2
BNTDOM2 replicates via RPC to BNTDOM1
ANTDOM3 replicates via RPC to ANTDOM2

Each DC's DNS has been configured to point to itself as the primary DNS
server.
For example: primary dns for BNTDOM1 is same ip as BNTDOM1

I think however that all problems are related to a single problem.
I have checked the size of my SYSVOL share on BNTDOM2 (a good DC) and compared
with BNTDOM1 (new bad dc). Both sizes are not the same, there is a
difference of 150 mb (policies folder). Is it possible SYSVOL folder (AD)
has not been completly replicated (at the time of installation - there was a
major DNS problem) and that that is causing all problems? If so, how can I
get this correctly replicated?
I do have NFTRS 13566 event ID issues (error message stated below).

Thanks in advance

Mark H

"Myweb" wrote:

> Hello mark,
>
> How are the 4 located by name? Site A and Site B and how are the NIC's configured
> for DNS pointing to which one, maybe post an ipconfig /all from the 4 DC's.
>
> Best regards
>
> Myweb
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
>
> > Thanks for replying Myweb
> >
> > I have checked the article in the link you've send but was still
> > unable to
> > fix this problem.
> > I will give you some background info on this issue.
> > Maybe this is related to this problem.
> > The new domain controller is a windows 2003 server x64 (=dc1).
> > This server has Global catalog enabled and is bridgehead server.
> > It holds the RID, PDC and Infrastructure FSMO roles.
> > There are 4 domain controllers in 2 sites (2 per site).
> > Each Dc is a win 2003 DNS and WInS server.
> > DC1 is however not functioning correct as dcdiag shows a problem:
> > Failed test advertising -- dsgetdcname returned information for dc2
> > when we trying to reach dc1
> >
> > Netdiag shows this error: Domain Membership test ..... Failed
> > The system volume has not been completely replicated to the local
> > machine.
> > Machine is not working properly as a DC.
> > And event viewer shows this NTFRS id 13566: FRS is scanning data in
> > the system volume. Computer DC1 cannot become a domain controller
> > until this process is complete. the system volume will then be shared
> > as SYSVOL
> >
> > I have however shared Sysvol and netlogon manually.
> >
> > Could they be related to the wins error?
> >
> > Thanks in advance
> >
> > Mark
> >
> > "Myweb" wrote:
> >
> >> Hello mark,
> >>
> >> Have a look here:
> >> http://support.microsoft.com/kb/321208
> >> http://www.jsifaq.com/SF/Tips/Tip.aspx?id=1849
> >>
> >> Best regards
> >>
> >> Myweb
> >> Disclaimer: This posting is provided "AS IS" with no warranties, and
> >> confers
> >> no rights.
>
>
>

Hello mark,

On the DC with the error change the primary DNS from itself to the other
DC in the same site and restart the DNS server service. Think that they not
fully replicate after promoting. You run Active directory integrated DNS?

Best regards

Myweb
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

> Thanks again for your reply Myweb.
>
> our domain:
>
> DC in site A:
>
> ANTDOM2
> ANTDOM3
>
> DC in site B:
>
> BNTDOM1
> BNTDOM2
>
> info: ANTDOM2 replicates via rpc to antdom3
> ANTDOM3 replicates via Ip to BNTDOM1
> BNTDOM1 replicates via IP to ANTDOM3
> BNTDOM1 replicates via RPC to BNTDOM2
> BNTDOM2 replicates via RPC to BNTDOM1
> ANTDOM3 replicates via RPC to ANTDOM2
> Each DC's DNS has been configured to point to itself as the primary
> DNS
> server.
> For example: primary dns for BNTDOM1 is same ip as BNTDOM1
> I think however that all problems are related to a single problem.
> I have checked the size of my SYSVOL share on BNTDOM2 (a good DC) and
> compared
> with BNTDOM1 (new bad dc). Both sizes are not the same, there is a
> difference of 150 mb (policies folder). Is it possible SYSVOL folder
> (AD)
> has not been completly replicated (at the time of installation - there
> was a
> major DNS problem) and that that is causing all problems? If so, how
> can I
> get this correctly replicated?
> I do have NFTRS 13566 event ID issues (error message stated below).
> Thanks in advance
>
> Mark H
>
> "Myweb" wrote:
>
>> Hello mark,
>>
>> How are the 4 located by name? Site A and Site B and how are the
>> NIC's configured for DNS pointing to which one, maybe post an
>> ipconfig /all from the 4 DC's.
>>
>> Best regards
>>
>> Myweb
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>>> Thanks for replying Myweb
>>>
>>> I have checked the article in the link you've send but was still
>>> unable to
>>> fix this problem.
>>> I will give you some background info on this issue.
>>> Maybe this is related to this problem.
>>> The new domain controller is a windows 2003 server x64 (=dc1).
>>> This server has Global catalog enabled and is bridgehead server.
>>> It holds the RID, PDC and Infrastructure FSMO roles.
>>> There are 4 domain controllers in 2 sites (2 per site).
>>> Each Dc is a win 2003 DNS and WInS server.
>>> DC1 is however not functioning correct as dcdiag shows a problem:
>>> Failed test advertising -- dsgetdcname returned information for dc2
>>> when we trying to reach dc1
>>> Netdiag shows this error: Domain Membership test ..... Failed
>>> The system volume has not been completely replicated to the local
>>> machine.
>>> Machine is not working properly as a DC.
>>> And event viewer shows this NTFRS id 13566: FRS is scanning data in
>>> the system volume. Computer DC1 cannot become a domain controller
>>> until this process is complete. the system volume will then be
>>> shared
>>> as SYSVOL
>>> I have however shared Sysvol and netlogon manually.
>>>
>>> Could they be related to the wins error?
>>>
>>> Thanks in advance
>>>
>>> Mark
>>>
>>> "Myweb" wrote:
>>>
>>>> Hello mark,
>>>>
>>>> Have a look here:
>>>> http://support.microsoft.com/kb/321208
>>>> http://www.jsifaq.com/SF/Tips/Tip.aspx?id=1849
>>>> Best regards
>>>>
>>>> Myweb
>>>> Disclaimer: This posting is provided "AS IS" with no warranties,
>>>> and
>>>> confers
>>>> no rights.

Hello Myweb

Yes, we run active directory DNS.
The history of this DC was this:

Old BNTDOM1 was demoted with dcpromo and removed from domain.
New Server got the name BNTDOM1 and was upgraded with dcpromo.
After apparent succesfull AD server role we checked DNS server role.
We made a crucial mistake (long story) that resulted in complete loss of DNS.
We then had to recreate DNS. So DNS should be the same on all DC's.
I don't know if it is usefull now of changing primary DNS on the faulty DC,
no ?

Mark


"Myweb" wrote:

> Hello mark,
>
> On the DC with the error change the primary DNS from itself to the other
> DC in the same site and restart the DNS server service. Think that they not
> fully replicate after promoting. You run Active directory integrated DNS?
>
> Best regards
>
> Myweb
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
>
> > Thanks again for your reply Myweb.
> >
> > our domain:
> >
> > DC in site A:
> >
> > ANTDOM2
> > ANTDOM3
> >
> > DC in site B:
> >
> > BNTDOM1
> > BNTDOM2
> >
> > info: ANTDOM2 replicates via rpc to antdom3
> > ANTDOM3 replicates via Ip to BNTDOM1
> > BNTDOM1 replicates via IP to ANTDOM3
> > BNTDOM1 replicates via RPC to BNTDOM2
> > BNTDOM2 replicates via RPC to BNTDOM1
> > ANTDOM3 replicates via RPC to ANTDOM2
> > Each DC's DNS has been configured to point to itself as the primary
> > DNS
> > server.
> > For example: primary dns for BNTDOM1 is same ip as BNTDOM1
> > I think however that all problems are related to a single problem.
> > I have checked the size of my SYSVOL share on BNTDOM2 (a good DC) and
> > compared
> > with BNTDOM1 (new bad dc). Both sizes are not the same, there is a
> > difference of 150 mb (policies folder). Is it possible SYSVOL folder
> > (AD)
> > has not been completly replicated (at the time of installation - there
> > was a
> > major DNS problem) and that that is causing all problems? If so, how
> > can I
> > get this correctly replicated?
> > I do have NFTRS 13566 event ID issues (error message stated below).
> > Thanks in advance
> >
> > Mark H
> >
> > "Myweb" wrote:
> >
> >> Hello mark,
> >>
> >> How are the 4 located by name? Site A and Site B and how are the
> >> NIC's configured for DNS pointing to which one, maybe post an
> >> ipconfig /all from the 4 DC's.
> >>
> >> Best regards
> >>
> >> Myweb
> >> Disclaimer: This posting is provided "AS IS" with no warranties, and
> >> confers
> >> no rights.
> >>> Thanks for replying Myweb
> >>>
> >>> I have checked the article in the link you've send but was still
> >>> unable to
> >>> fix this problem.
> >>> I will give you some background info on this issue.
> >>> Maybe this is related to this problem.
> >>> The new domain controller is a windows 2003 server x64 (=dc1).
> >>> This server has Global catalog enabled and is bridgehead server.
> >>> It holds the RID, PDC and Infrastructure FSMO roles.
> >>> There are 4 domain controllers in 2 sites (2 per site).
> >>> Each Dc is a win 2003 DNS and WInS server.
> >>> DC1 is however not functioning correct as dcdiag shows a problem:
> >>> Failed test advertising -- dsgetdcname returned information for dc2
> >>> when we trying to reach dc1
> >>> Netdiag shows this error: Domain Membership test ..... Failed
> >>> The system volume has not been completely replicated to the local
> >>> machine.
> >>> Machine is not working properly as a DC.
> >>> And event viewer shows this NTFRS id 13566: FRS is scanning data in
> >>> the system volume. Computer DC1 cannot become a domain controller
> >>> until this process is complete. the system volume will then be
> >>> shared
> >>> as SYSVOL
> >>> I have however shared Sysvol and netlogon manually.
> >>>
> >>> Could they be related to the wins error?
> >>>
> >>> Thanks in advance
> >>>
> >>> Mark
> >>>
> >>> "Myweb" wrote:
> >>>
> >>>> Hello mark,
> >>>>
> >>>> Have a look here:
> >>>> http://support.microsoft.com/kb/321208
> >>>> http://www.jsifaq.com/SF/Tips/Tip.aspx?id=1849
> >>>> Best regards
> >>>>
> >>>> Myweb
> >>>> Disclaimer: This posting is provided "AS IS" with no warranties,
> >>>> and
> >>>> confers
> >>>> no rights.
>
>
>

Hello mark,

Please post the complete dcdiag and netdiag result here. Since you have had
so big problems before, lets have a look on it for all people here.

Best regards

Myweb
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

> Hello Myweb
>
> Yes, we run active directory DNS.
> The history of this DC was this:
> Old BNTDOM1 was demoted with dcpromo and removed from domain.
> New Server got the name BNTDOM1 and was upgraded with dcpromo.
> After apparent succesfull AD server role we checked DNS server role.
> We made a crucial mistake (long story) that resulted in complete loss
> of DNS.
> We then had to recreate DNS. So DNS should be the same on all DC's.
> I don't know if it is usefull now of changing primary DNS on the
> faulty DC,
> no ?
> Mark
>
> "Myweb" wrote:
>
>> Hello mark,
>>
>> On the DC with the error change the primary DNS from itself to the
>> other DC in the same site and restart the DNS server service. Think
>> that they not fully replicate after promoting. You run Active
>> directory integrated DNS?
>>
>> Best regards
>>
>> Myweb
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>>> Thanks again for your reply Myweb.
>>>
>>> our domain:
>>>
>>> DC in site A:
>>>
>>> ANTDOM2
>>> ANTDOM3
>>> DC in site B:
>>>
>>> BNTDOM1
>>> BNTDOM2
>>> info: ANTDOM2 replicates via rpc to antdom3
>>> ANTDOM3 replicates via Ip to BNTDOM1
>>> BNTDOM1 replicates via IP to ANTDOM3
>>> BNTDOM1 replicates via RPC to BNTDOM2
>>> BNTDOM2 replicates via RPC to BNTDOM1
>>> ANTDOM3 replicates via RPC to ANTDOM2
>>> Each DC's DNS has been configured to point to itself as the primary
>>> DNS
>>> server.
>>> For example: primary dns for BNTDOM1 is same ip as BNTDOM1
>>> I think however that all problems are related to a single problem.
>>> I have checked the size of my SYSVOL share on BNTDOM2 (a good DC)
>>> and
>>> compared
>>> with BNTDOM1 (new bad dc). Both sizes are not the same, there is a
>>> difference of 150 mb (policies folder). Is it possible SYSVOL
>>> folder
>>> (AD)
>>> has not been completly replicated (at the time of installation -
>>> there
>>> was a
>>> major DNS problem) and that that is causing all problems? If so,
>>> how
>>> can I
>>> get this correctly replicated?
>>> I do have NFTRS 13566 event ID issues (error message stated below).
>>> Thanks in advance
>>> Mark H
>>>
>>> "Myweb" wrote:
>>>
>>>> Hello mark,
>>>>
>>>> How are the 4 located by name? Site A and Site B and how are the
>>>> NIC's configured for DNS pointing to which one, maybe post an
>>>> ipconfig /all from the 4 DC's.
>>>>
>>>> Best regards
>>>>
>>>> Myweb
>>>> Disclaimer: This posting is provided "AS IS" with no warranties,
>>>> and
>>>> confers
>>>> no rights.
>>>>> Thanks for replying Myweb
>>>>>
>>>>> I have checked the article in the link you've send but was still
>>>>> unable to
>>>>> fix this problem.
>>>>> I will give you some background info on this issue.
>>>>> Maybe this is related to this problem.
>>>>> The new domain controller is a windows 2003 server x64 (=dc1).
>>>>> This server has Global catalog enabled and is bridgehead server.
>>>>> It holds the RID, PDC and Infrastructure FSMO roles.
>>>>> There are 4 domain controllers in 2 sites (2 per site).
>>>>> Each Dc is a win 2003 DNS and WInS server.
>>>>> DC1 is however not functioning correct as dcdiag shows a problem:
>>>>> Failed test advertising -- dsgetdcname returned information for
>>>>> dc2
>>>>> when we trying to reach dc1
>>>>> Netdiag shows this error: Domain Membership test ..... Failed
>>>>> The system volume has not been completely replicated to the local
>>>>> machine.
>>>>> Machine is not working properly as a DC.
>>>>> And event viewer shows this NTFRS id 13566: FRS is scanning data
>>>>> in
>>>>> the system volume. Computer DC1 cannot become a domain controller
>>>>> until this process is complete. the system volume will then be
>>>>> shared
>>>>> as SYSVOL
>>>>> I have however shared Sysvol and netlogon manually.
>>>>> Could they be related to the wins error?
>>>>>
>>>>> Thanks in advance
>>>>>
>>>>> Mark
>>>>>
>>>>> "Myweb" wrote:
>>>>>
>>>>>> Hello mark,
>>>>>>
>>>>>> Have a look here:
>>>>>> http://support.microsoft.com/kb/321208
>>>>>> http://www.jsifaq.com/SF/Tips/Tip.aspx?id=1849
>>>>>> Best regards
>>>>>> Myweb
>>>>>> Disclaimer: This posting is provided "AS IS" with no warranties,
>>>>>> and
>>>>>> confers
>>>>>> no rights.

Hello myweb:

here is extract from dcdiag:

omain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Diegem007\BNTDOM1
Starting test: Connectivity
......................... BNTDOM1 passed test Connectivity

Doing primary tests

Testing server: Diegem007\BNTDOM1
Starting test: Replications
......................... BNTDOM1 passed test Replications
Starting test: NCSecDesc
......................... BNTDOM1 passed test NCSecDesc
Starting test: NetLogons
......................... BNTDOM1 passed test NetLogons
Starting test: Advertising
Warning: DsGetDcName returned information for \\bntdom2.med.be,
when we were trying to reach BNTDOM1.
Server is not responding or is not considered suitable.
......................... BNTDOM1 failed test Advertising
Starting test: KnowsOfRoleHolders
......................... BNTDOM1 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... BNTDOM1 passed test RidManager
Starting test: MachineAccount
......................... BNTDOM1 passed test MachineAccount
Starting test: Services
......................... BNTDOM1 passed test Services
Starting test: ObjectsReplicated
......................... BNTDOM1 passed test ObjectsReplicated
Starting test: frssysvol
......................... BNTDOM1 passed test frssysvol
Starting test: frsevent
......................... BNTDOM1 passed test frsevent
Starting test: kccevent
......................... BNTDOM1 passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0xC0011093
Time Generated: 03/30/2007 14:05:37
Event String: WINS Pull thread encountered an error during the

An Error Event occured. EventID: 0xC0011093
Time Generated: 03/30/2007 14:13:05
Event String: WINS Pull thread encountered an error during the

An Error Event occured. EventID: 0xC0011093
Time Generated: 03/30/2007 14:33:15
Event String: WINS Pull thread encountered an error during the

An Error Event occured. EventID: 0xC0011093
Time Generated: 03/30/2007 14:38:46
Event String: WINS Pull thread encountered an error during the

An Error Event occured. EventID: 0xC0011093
Time Generated: 03/30/2007 14:43:52
Event String: WINS Pull thread encountered an error during the

An Error Event occured. EventID: 0xC00110D3
Time Generated: 03/30/2007 14:48:09
Event String: The WINS replicator Pull thread encountered an

......................... BNTDOM1 failed test systemlog
Starting test: VerifyReferences
......................... BNTDOM1 passed test VerifyReferences

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

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

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

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

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

Running enterprise tests on : med.be
Starting test: Intersite
......................... med.be passed test Intersite
Starting test: FsmoCheck
......................... med.be passed test FsmoCheck


and netdiag:


Computer Name: BNTDOM1
DNS Host Name: bntdom1.med.be
System info : Microsoft Windows Server 2003 (Build 3790)
Processor : EM64T Family 6 Model 15 Stepping 6, GenuineIntel
List of installed hotfixes :
KB931836
Q147222


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



Per interface results:

Adapter : Team 1

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : bntdom1
IP Address . . . . . . . . : 10.2.70.51
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 10.2.70.1
Primary WINS Server. . . . : 10.2.70.51
Secondary WINS Server. . . : 10.2.70.55
Dns Servers. . . . . . . . : 10.2.70.51
10.2.70.55
10.2.38.51
10.2.38.55


AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Passed

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

WINS service test. . . . . : Passed


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_{7460DA9A-07C4-4F34-92E8-3D0D17DB8215}
1 NetBt transport currently configured.


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


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


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


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


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


DNS test . . . . . . . . . . . . . : Passed
PASS - All the DNS entries for DC are registered on DNS server
'10.2.70.51' and other DCs also have some of the names registered.
PASS - All the DNS entries for DC are registered on DNS server
'10.2.70.55' and other DCs also have some of the names registered.
PASS - All the DNS entries for DC are registered on DNS server
'10.2.38.51' and other DCs also have some of the names registered.
PASS - All the DNS entries for DC are registered on DNS server
'10.2.38.55' 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_{7460DA9A-07C4-4F34-92E8-3D0D17DB8215}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{7460DA9A-07C4-4F34-92E8-3D0D17DB8215}
The browser is bound to 1 NetBt transport.


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


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


Trust relationship test. . . . . . : Skipped


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


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


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


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


Modem diagnostics test . . . . . . : Passed

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

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


The command completed successfully


>