Error " The Target principal name is incorrect"

Pcnetnet · Jun 4, 2008

Hi All,
I have big problem , becuase i miss take change the DC system day to
2002 , then the DC over 60 days, We have replcate error on DC to DC2
Error " The Target principal name is incorrect"

how to fix it ?? i don't reinstall the DC , becuase the DC is GC , Thanks,

DC and DC2 : Windows 2003 Std R2 SP2

Meinolf Weber · Jun 4, 2008

Hello pcnetnet,

Please post the complete error message here. i assume it is from the event
viewer? Then press the 2 papaer button in the right corner and just paste
it to the posting. Also give some more details about what you have done.
If i understand you correct, you changed the system time to 2002 and leave
it so over 60 days? Or do you mean the tombstone lifetime which is 60 days?
But this is NOT the case in your system. For 2003 R2 with SP2 installed the
tombstone lifetime is 180 days.

To determine the tombstone lifetime for the forest:

1. On the Start menu, click Run, type adsiedit.msc, and then click OK.

2. In the console tree, double-click Configuration [DomainControllerName],
CN=Configuration,DC=[ForestRootDomain], CN=Services, and CN=Windows NT.

3. Right-click CN=Directory Service, and then click Properties.

4. In the Attribute column, click tombstoneLifetime.

5. Note the value in the Value column. If the value is <not set>, the default
value is in effect.

Also see here:
http://support.microsoft.com/kb/924890

Additional run dcdiag /v to check for errors and post the complete output
here.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

Pcnetnet · Jun 5, 2008

Hi All,
Yes , because the Site A DC Server change the time to year 2002 (is my
mistake ), now the site A server and site B DC cannot replication ,
on Site A
open AD site and Services replcate to Site B DC
Replicate Now ---- is ok ,
but when i connect to Site B
open AD site and Services replacte to Site A DC
"The Follwing error occurred during the attempt to synhronize naming context
abc.com from domain controller DC_A to domain controller DC_B:
The naming context is in the process of being removed or is not replicated
from the specified server.
This operation will not continue "
For The Event Log
Site B

Event Type: Error
Event Source: Kerberos
Event Category: None
Event ID: 4
Date: 6/5/2008
Time: 9:35:10 AM
User: N/A
Computer: DC_B
Description:
The kerberos client received a KRB_AP_ERR_MODIFIED error from the server
host/smlad.sml.com. The target name used was
LDAP/6ad1947f-b693-4166-85fc-d2097457fec6._msdcs.abc.com. This indicates
that the password used to encrypt the kerberos service ticket is different
than that on the target server. Commonly, this is due to identically named
machine accounts in the target realm (ABC.COM), and the client realm.
Please contact your system administrator.

On Site A

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: 6/5/2008
Time: 9:39:04 AM
User: N/A
Computer: DC_A
Description:
This computer was not able to set up a secure session with a domain
controller in domain DC_C due to the following:
There are currently no logon servers available to service the logon request.
This may lead to authentication problems. Make sure that this computer is
connected to the network. If the problem persists, please contact your
domain administrator.

ADDITIONAL INFO
If this computer is a domain controller for the specified domain, it sets up
the secure session to the primary domain controller emulator in the
specified domain. Otherwise, this computer sets up the secure session to any
domain controller in the specified domain.

i think the Site A DC can be replicate to other site (B,C,D,E) . but other
site cannot replicate to Site A ,
how can i do , i want setup another DC on Site A , but i don't know if the
new DC connect to DC_A dcpromo to DC_A2 have problem ? HELP

Meinolf Weber said:
Hello pcnetnet,

Please post the complete error message here. i assume it is from the event
viewer? Then press the 2 papaer button in the right corner and just paste
it to the posting. Also give some more details about what you have done.
If i understand you correct, you changed the system time to 2002 and leave
it so over 60 days? Or do you mean the tombstone lifetime which is 60
days? But this is NOT the case in your system. For 2003 R2 with SP2
installed the tombstone lifetime is 180 days.

To determine the tombstone lifetime for the forest:

1. On the Start menu, click Run, type adsiedit.msc, and then click OK.

2. In the console tree, double-click Configuration
[DomainControllerName], CN=Configuration,DC=[ForestRootDomain],
CN=Services, and CN=Windows NT.

3. Right-click CN=Directory Service, and then click Properties.

4. In the Attribute column, click tombstoneLifetime.

5. Note the value in the Value column. If the value is <not set>, the
default value is in effect.

Also see here:
http://support.microsoft.com/kb/924890

Additional run dcdiag /v to check for errors and post the complete output
here.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

Hi All,
I have big problem , becuase i miss take change the DC system day
to
2002 , then the DC over 60 days, We have replcate error on DC to DC2
Error " The Target principal name is incorrect"

how to fix it ?? i don't reinstall the DC , becuase the DC is GC ,
Thanks,

DC and DC2 : Windows 2003 Std R2 SP2

Click to expand...

Meinolf Weber · Jun 5, 2008

Hello pcnetnet,

Please see also my questions. Additional run netidag /v and repadmin /showreps
and post the output also here.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

Hi All,
Yes , because the Site A DC Server change the time to year 2002
(is my
mistake ), now the site A server and site B DC cannot replication ,
on Site A
open AD site and Services replcate to Site B DC
Replicate Now ---- is ok ,
but when i connect to Site B
open AD site and Services replacte to Site A DC
"The Follwing error occurred during the attempt to synhronize naming
context
abc.com from domain controller DC_A to domain controller DC_B:
The naming context is in the process of being removed or is not
replicated
from the specified server.
This operation will not continue "
For The Event Log
Site B
Event Type: Error
Event Source: Kerberos
Event Category: None
Event ID: 4
Date: 6/5/2008
Time: 9:35:10 AM
User: N/A
Computer: DC_B
Description:
The kerberos client received a KRB_AP_ERR_MODIFIED error from the
server
host/smlad.sml.com. The target name used was
LDAP/6ad1947f-b693-4166-85fc-d2097457fec6._msdcs.abc.com. This
indicates
that the password used to encrypt the kerberos service ticket is
different
than that on the target server. Commonly, this is due to identically
named
machine accounts in the target realm (ABC.COM), and the client realm.
Please contact your system administrator.
On Site A

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: 6/5/2008
Time: 9:39:04 AM
User: N/A
Computer: DC_A
Description:
This computer was not able to set up a secure session with a domain
controller in domain DC_C due to the following:
There are currently no logon servers available to service the logon
request.
This may lead to authentication problems. Make sure that this computer
is
connected to the network. If the problem persists, please contact your
domain administrator.
ADDITIONAL INFO
If this computer is a domain controller for the specified domain, it
sets up
the secure session to the primary domain controller emulator in the
specified domain. Otherwise, this computer sets up the secure session
to any
domain controller in the specified domain.
i think the Site A DC can be replicate to other site (B,C,D,E) . but
other
site cannot replicate to Site A ,
how can i do , i want setup another DC on Site A , but i don't know if
the
new DC connect to DC_A dcpromo to DC_A2 have problem ? HELP

Hello pcnetnet,

Please post the complete error message here. i assume it is from the
event viewer? Then press the 2 papaer button in the right corner and
just paste it to the posting. Also give some more details about what
you have done. If i understand you correct, you changed the system
time to 2002 and leave it so over 60 days? Or do you mean the
tombstone lifetime which is 60 days? But this is NOT the case in your
system. For 2003 R2 with SP2 installed the tombstone lifetime is 180
days.

To determine the tombstone lifetime for the forest:

1. On the Start menu, click Run, type adsiedit.msc, and then click
OK.

2. In the console tree, double-click Configuration
[DomainControllerName], CN=Configuration,DC=[ForestRootDomain],
CN=Services, and CN=Windows NT.

3. Right-click CN=Directory Service, and then click Properties.

4. In the Attribute column, click tombstoneLifetime.

5. Note the value in the Value column. If the value is <not set>,
the default value is in effect.

Also see here:
http://support.microsoft.com/kb/924890
Additional run dcdiag /v to check for errors and post the complete
output here.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

Hi All,
I have big problem , becuase i miss take change the DC system day
to
2002 , then the DC over 60 days, We have replcate error on DC to DC2
Error " The Target principal name is incorrect"
how to fix it ?? i don't reinstall the DC , becuase the DC is GC ,
Thanks,

DC and DC2 : Windows 2003 Std R2 SP2

Click to expand...

Click to expand...

Meinolf Weber · Jun 5, 2008

Hello pcnetnet,

For event id 4:
http://technet2.microsoft.com/Windo...2e32-4282-bce7-3209d1ea8bf11033.mspx?mfr=true

For event id 5719:
http://support.microsoft.com/kb/938449

http://www.eventid.net/display.asp?eventid=5719&eventno=104&source=NETLOGON&phase=1

http://www.chicagotech.net/troubleshooting/rpcfailed1.htm

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

Ruchi Manuja · Jun 5, 2008

Hello

if we are getting replication error then please run the following command
and post the output.

repadmin /showreps >test.txt
dcdiag /v >dc.txt

these two outputs will show us the exact issue you are facing regarding
replication.

Thanks

Pcnetnet · Jun 5, 2008

Hi
This is netidag /v and repadmin /showreps report file , many many
Thanks

ftp://smltmp

[email protected]/MS/AD.zip

Meinolf Weber said:
Hello pcnetnet,

Please see also my questions. Additional run netidag /v and repadmin
/showreps and post the output also here.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

Hi All,
Yes , because the Site A DC Server change the time to year 2002
(is my
mistake ), now the site A server and site B DC cannot replication ,
on Site A
open AD site and Services replcate to Site B DC
Replicate Now ---- is ok ,
but when i connect to Site B
open AD site and Services replacte to Site A DC
"The Follwing error occurred during the attempt to synhronize naming
context
abc.com from domain controller DC_A to domain controller DC_B:
The naming context is in the process of being removed or is not
replicated
from the specified server.
This operation will not continue "
For The Event Log
Site B
Event Type: Error
Event Source: Kerberos
Event Category: None
Event ID: 4
Date: 6/5/2008
Time: 9:35:10 AM
User: N/A
Computer: DC_B
Description:
The kerberos client received a KRB_AP_ERR_MODIFIED error from the
server
host/smlad.sml.com. The target name used was
LDAP/6ad1947f-b693-4166-85fc-d2097457fec6._msdcs.abc.com. This
indicates
that the password used to encrypt the kerberos service ticket is
different
than that on the target server. Commonly, this is due to identically
named
machine accounts in the target realm (ABC.COM), and the client realm.
Please contact your system administrator.
On Site A

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: 6/5/2008
Time: 9:39:04 AM
User: N/A
Computer: DC_A
Description:
This computer was not able to set up a secure session with a domain
controller in domain DC_C due to the following:
There are currently no logon servers available to service the logon
request.
This may lead to authentication problems. Make sure that this computer
is
connected to the network. If the problem persists, please contact your
domain administrator.
ADDITIONAL INFO
If this computer is a domain controller for the specified domain, it
sets up
the secure session to the primary domain controller emulator in the
specified domain. Otherwise, this computer sets up the secure session
to any
domain controller in the specified domain.
i think the Site A DC can be replicate to other site (B,C,D,E) . but
other
site cannot replicate to Site A ,
how can i do , i want setup another DC on Site A , but i don't know if
the
new DC connect to DC_A dcpromo to DC_A2 have problem ? HELP

Hello pcnetnet,

Please post the complete error message here. i assume it is from the
event viewer? Then press the 2 papaer button in the right corner and
just paste it to the posting. Also give some more details about what
you have done. If i understand you correct, you changed the system
time to 2002 and leave it so over 60 days? Or do you mean the
tombstone lifetime which is 60 days? But this is NOT the case in your
system. For 2003 R2 with SP2 installed the tombstone lifetime is 180
days.

To determine the tombstone lifetime for the forest:

1. On the Start menu, click Run, type adsiedit.msc, and then click
OK.

2. In the console tree, double-click Configuration
[DomainControllerName], CN=Configuration,DC=[ForestRootDomain],
CN=Services, and CN=Windows NT.

3. Right-click CN=Directory Service, and then click Properties.

4. In the Attribute column, click tombstoneLifetime.

5. Note the value in the Value column. If the value is <not set>,
the default value is in effect.

Also see here:
http://support.microsoft.com/kb/924890
Additional run dcdiag /v to check for errors and post the complete
output here.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
Hi All,
I have big problem , becuase i miss take change the DC system day
to
2002 , then the DC over 60 days, We have replcate error on DC to DC2
Error " The Target principal name is incorrect"
how to fix it ?? i don't reinstall the DC , becuase the DC is GC ,
Thanks,

DC and DC2 : Windows 2003 Std R2 SP2

Click to expand...

Click to expand...

Meinolf Weber · Jun 5, 2008

Hello pcnetnet,

Sorry, but i do not open any attachments. So please copy the output to one
posting for each machine or choose the netdiag without /v. Maybe it will
be enough for starting the search.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

Hi
This is netidag /v and repadmin /showreps report file , many
many
Thanks
ftp://smltmp[email protected]/MS/AD.zip

Hello pcnetnet,

Please see also my questions. Additional run netidag /v and repadmin
/showreps and post the output also here.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

Hi All,
Yes , because the Site A DC Server change the time to year 2002
(is my
mistake ), now the site A server and site B DC cannot replication ,
on Site A
open AD site and Services replcate to Site B DC
Replicate Now ---- is ok ,
but when i connect to Site B
open AD site and Services replacte to Site A DC
"The Follwing error occurred during the attempt to synhronize naming
context
abc.com from domain controller DC_A to domain controller DC_B:
The naming context is in the process of being removed or is not
replicated
from the specified server.
This operation will not continue "
For The Event Log
Site B
Event Type: Error
Event Source: Kerberos
Event Category: None
Event ID: 4
Date: 6/5/2008
Time: 9:35:10 AM
User: N/A
Computer: DC_B
Description:
The kerberos client received a KRB_AP_ERR_MODIFIED error from the
server
host/smlad.sml.com. The target name used was
LDAP/6ad1947f-b693-4166-85fc-d2097457fec6._msdcs.abc.com. This
indicates
that the password used to encrypt the kerberos service ticket is
different
than that on the target server. Commonly, this is due to identically
named
machine accounts in the target realm (ABC.COM), and the client
realm.
Please contact your system administrator.
On Site A
Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: 6/5/2008
Time: 9:39:04 AM
User: N/A
Computer: DC_A
Description:
This computer was not able to set up a secure session with a domain
controller in domain DC_C due to the following:
There are currently no logon servers available to service the logon
request.
This may lead to authentication problems. Make sure that this
computer
is
connected to the network. If the problem persists, please contact
your
domain administrator.
ADDITIONAL INFO
If this computer is a domain controller for the specified domain, it
sets up
the secure session to the primary domain controller emulator in the
specified domain. Otherwise, this computer sets up the secure
session
to any
domain controller in the specified domain.
i think the Site A DC can be replicate to other site (B,C,D,E) .
but
other
site cannot replicate to Site A ,
how can i do , i want setup another DC on Site A , but i don't know
if
the
new DC connect to DC_A dcpromo to DC_A2 have problem ? HELP
Hello pcnetnet,

Please post the complete error message here. i assume it is from
the event viewer? Then press the 2 papaer button in the right
corner and just paste it to the posting. Also give some more
details about what you have done. If i understand you correct, you
changed the system time to 2002 and leave it so over 60 days? Or do
you mean the tombstone lifetime which is 60 days? But this is NOT
the case in your system. For 2003 R2 with SP2 installed the
tombstone lifetime is 180 days.

To determine the tombstone lifetime for the forest:

1. On the Start menu, click Run, type adsiedit.msc, and then click
OK.

2. In the console tree, double-click Configuration
[DomainControllerName], CN=Configuration,DC=[ForestRootDomain],
CN=Services, and CN=Windows NT.

3. Right-click CN=Directory Service, and then click Properties.

4. In the Attribute column, click tombstoneLifetime.

5. Note the value in the Value column. If the value is <not set>,
the default value is in effect.

Also see here:
http://support.microsoft.com/kb/924890
Additional run dcdiag /v to check for errors and post the complete
output here.
Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties,
and
confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
Hi All,
I have big problem , becuase i miss take change the DC system day
to
2002 , then the DC over 60 days, We have replcate error on DC to
DC2
Error " The Target principal name is incorrect"
how to fix it ?? i don't reinstall the DC , becuase the DC is GC ,
Thanks,
DC and DC2 : Windows 2003 Std R2 SP2

Click to expand...

Click to expand...

pcnetnet · Jun 5, 2008

Hi All,
I zip the output file on here -->
ftp://smltmp

[email protected]/MS/AD.zip
file netdiag_b.txt --- > for site B netdiag /v
repadmin_b.txt ---> for Site B repadmin /showreps
netdiag_a.txt ----> for site A netdiag /v
repadmin_a.txt ----> for site A repadmin /showreps

becasue the file size is too large cannot post on newsgroup , Thanks All, i
need help , Thanks

pcnetnet · Jun 5, 2008

Hi All,
More Detail for my case ,
On siteA (HK) DC have 2 server dc1 and dc2
On SiteB (CN) DC habe 1 server dc_b1
before i have mistake change the server time to year 2002 on dc1 , then the
server dc1 cannot replacte to dc2 and dc_b1 ,if i create new user account
DC2 , DC1 no this account , because the AD role (PDC role, globe cataory
,,,) setup on DC1. on now , i need down the DC2 server , because the DC2 is
working , user cannot logon to domain if user connect to DC2 logon , how to
reset ? change to normal or i need setup new server into this domain ? but
my new server is connect to DC1 or DC2 promto to new DC ? Help , Very very
very Thanks All ~~~~~~~~

pcnetnet · Jun 8, 2008

hi all ,
help

pcnetnet said:
Hi All,
More Detail for my case ,
On siteA (HK) DC have 2 server dc1 and dc2
On SiteB (CN) DC habe 1 server dc_b1
before i have mistake change the server time to year 2002 on dc1 , then
the server dc1 cannot replacte to dc2 and dc_b1 ,if i create new user
account DC2 , DC1 no this account , because the AD role (PDC role, globe
cataory ,,,) setup on DC1. on now , i need down the DC2 server , because
the DC2 is working , user cannot logon to domain if user connect to DC2
logon , how to reset ? change to normal or i need setup new server into
this domain ? but my new server is connect to DC1 or DC2 promto to new DC
? Help , Very very very Thanks All ~~~~~~~~

Ace Fekay [MVP] · Jun 9, 2008

In

pcnetnet said:
hi all ,
help

The diagnostic results are beneficial to help you. I realize trying to post
all of them together in one post is too large. The results are only text
based, so all you have to do is copy/paste the results for each run in a
separate post. If it takes 3 or 4 posts, no problem. You can add to the
subject and prefix it with the current subject, such as, "netdiag - Re:
Error " The Target principal name is incorrect." Others normally post text
based results in this fashion. Keep in mind, many in the groups will not
download and open posted files or URL references to files. It's just a
security concern. I hope you understand.

Btw, I didn't see a results in your list for a dcdiag, as Meinolf asked. Did
you run one? If not, please run a "dcdiag /v" and post that along with the
others.

Thanks!

--
Regards,
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Infinite Diversities in Infinite Combinations

pcnetnet · Jun 9, 2008

For Site A netdiag #1

Gathering IPX configuration information.
Querying status of the Netcard drivers... Passed
Testing IpConfig - pinging the Primary WINS server... 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 2
Sending name query to primary WINS server 192.168.0.78 - Passed
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
'127.0.0.1' and other DCs also have some of the names registered.
Testing redirector and browser... Passed
Testing DC discovery.
Looking for a DC
Looking for a PDC emulator
Looking for an Active Directory DC
Gathering the list of Domain Controllers for domain 'SML'
Testing trust relationships... Skipped
Testing Kerberos authentication... Passed
Testing LDAP servers in Domain SML ...
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: SMLAD
DNS Host Name: SMLAD.sml.com
DNS Domain Name: sml.com
System info : Microsoft Windows Server 2003 R2 (Build 3790)
Processor : x86 Family 6 Model 8 Stepping 3, GenuineIntel
Hotfixes :
Installed? Name
Yes KB909520
Yes KB921503
Yes KB925398_WMP64
Yes KB925902
Yes KB926122
Yes KB927891
Yes KB928090-IE7
Yes KB929123
Yes KB929969
Yes KB930178
Yes KB931768-IE7
Yes KB931784
Yes KB931836
Yes KB932168
Yes KB933360
Yes KB933566-IE7
Yes KB933729
Yes KB933854
Yes KB935839
Yes KB935840
Yes KB935966
Yes KB936021
Yes KB936357
Yes KB936782
Yes KB937143-IE7
Yes KB938127-IE7
Yes KB939653-IE7
Yes KB941202
Yes KB941568
Yes KB941569
Yes KB941644
Yes KB941672
Yes KB941693
Yes KB942615-IE7
Yes KB942763
Yes KB942830
Yes KB942831
Yes KB943055
Yes KB943460
Yes KB943484
Yes KB943485
Yes KB944533-IE7
Yes KB944653
Yes KB945553
Yes KB946026
Yes KB947864-IE7
Yes KB948496
Yes KB948590
Yes KB948881
Yes Q147222
No ServicePackUninstall

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

Information of Netcard drivers:

---------------------------------------------------------------------------
Description: 3Com 3C996 10/100/1000 Server NIC
Device: \DEVICE\{7BA3D71A-43A4-4A81-B318-94D0445BE672}

Media State: Connected

Device State: Connected
Connect Time: 46 days, 03:39:16
Media Speed: 100 Mbps

Packets Sent: 69046309
Bytes Sent (Optional): 0

Packets Received: 102444906
Directed Pkts Recd (Optional): 77468584
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 2
Adapter ID . . . . . . . . : {7BA3D71A-43A4-4A81-B318-94D0445BE672}

Netcard queries test . . . : Passed

Adapter type . . . . . . . : Ethernet
Host Name. . . . . . . . . : SMLAD
Description. . . . . . . . : 3Com 3C996 10/100/1000 Server NIC
Physical Address . . . . . : 00-04-76-2F-E2-96
Dhcp Enabled . . . . . . . : No
DHCP ClassID . . . . . . . :
Autoconfiguration Enabled. : Yes
IP Address . . . . . . . . : 192.168.0.55
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 192.168.0.253
Primary WINS Server. . . . : 192.168.0.78
Dns Servers. . . . . . . . : 127.0.0.1

IpConfig results . . . . . : Passed
Pinging the Primary WINS server 192.168.0.78 - reachable

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

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

NetBT name test. . . . . . : Passed
NetBT_Tcpip_{7BA3D71A-43A4-4A81-B318-94D0445BE672}
SMLAD <00> UNIQUE REGISTERED
SML <00> GROUP REGISTERED
SML <1C> GROUP REGISTERED
SMLAD <20> UNIQUE REGISTERED
SML <1E> GROUP REGISTERED
SML <1D> UNIQUE REGISTERED
..__MSBROWSE__.<01> GROUP REGISTERED
SML <1B> UNIQUE REGISTERED
[WARNING] At least one of the <00> 'WorkStation Service', <03>
'Messenger Service', <20> 'WINS' names is missing.

NetBios Resolution : via DHCP

Netbios Remote Cache Table
Name Type HostAddress Life [sec]
---------------------------------------------------------------
PHIL_HUNGXP <20> UNIQUE 192.168.5.68 12
AMANDA_CHOW <20> UNIQUE 192.168.5.186 10
ANDREW_CHAN <20> UNIQUE 192.168.5.155 5
STEPHEN_TSUI <20> UNIQUE 192.168.5.146 15
CHIWAIXP <20> UNIQUE 192.168.0.168 317
SML-SMLS-IMAC <00> UNIQUE 192.168.7.62 5
SMLDC2 <20> UNIQUE 192.168.9.10 400
SMLWPS <20> UNIQUE 192.168.0.38 390
SMLAOS1 <20> UNIQUE 192.168.0.30 390
SML <20> UNIQUE 192.168.16.2 315
SMLSQLW <20> UNIQUE 192.168.0.220 310
SMLAOS5 <20> UNIQUE 192.168.0.34 310
SMLDC <20> UNIQUE 192.168.6.11 310
SMLVN-DC01 <20> UNIQUE 192.168.19.10 310
SMLUS-DC.SML.CO<4D> UNIQUE 192.168.36.250 250
SML <1C> GROUP 192.168.0.55 192
SMLUS-DC <20> UNIQUE 192.168.36.250 147
DEMO11 <20> UNIQUE 192.168.5.145 12
DEMO5 <20> UNIQUE 192.168.5.170 2
DYSCAN4 <20> UNIQUE 192.168.5.86 10
DYTEST <20> UNIQUE 192.168.0.134 505
DYSUN <20> UNIQUE 192.168.0.78 310
DYDC <20> UNIQUE 192.168.0.52 310
ERIC_HFLAM <20> UNIQUE 192.168.5.165 15
ERIKA_FOKXP <20> UNIQUE 192.168.5.111 12
ERIC_LEUNGXP <20> UNIQUE 192.168.6.48 522
UKTEMP <20> UNIQUE 192.168.0.36 310
FTP <20> UNIQUE 192.168.0.90 317
VERA_CHANXP <20> UNIQUE 192.168.5.105 12
VM_FTP <20> UNIQUE 192.168.5.117 540
WPSSQL <20> UNIQUE 192.168.0.39 310
HENRY_LAU <20> UNIQUE 192.168.5.103 15
YANNI_YEUNG <20> UNIQUE 192.168.5.157 2
KEN_LEEXP <20> UNIQUE 192.168.6.127 395
LEWIS_LAU <20> UNIQUE 192.168.5.116 7
LOUIS_KWAN <20> UNIQUE 192.168.6.94 395
ORDERING2 <20> UNIQUE 192.168.5.108 12

WINS service test. . . . . : Passed
Sending name query to primary WINS server 192.168.0.78 - Passed
There is no secondary WINS server defined for this adapter.
The test was successful. At least one WINS server was found.
IPX test : IPX is not installed on this machine.

Global results:

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

Domain membership test . . . . . . : Passed
Machine is a . . . . . . . . . : Primary Domain Controller Emulator
Netbios Domain name. . . . . . : SML
Dns domain name. . . . . . . . : sml.com
Dns forest name. . . . . . . . : sml.com
Domain Guid. . . . . . . . . . : {BAC13477-EC37-4340-941F-7A21AE77D0CB}
Domain Sid . . . . . . . . . . : S-1-5-21-2444645589-256595936-971879393
Logon User . . . . . . . . . . : chiwai
Logon Domain . . . . . . . . . : SML

NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{7BA3D71A-43A4-4A81-B318-94D0445BE672}
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
[WARNING] You don't have a single interface with the <00> 'WorkStation
Service', <03> 'Messenger Service', <20> 'WINS' names defined.

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_{7BA3D71A-43A4-4A81-B318-94D0445BE672}] SEQPACKET 1
Provider Version :2
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{7BA3D71A-43A4-4A81-B318-94D0445BE672}] DATAGRAM 1
Provider Version :2
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{54257D51-038A-4C8B-AFB5-054CEFED027B}] SEQPACKET 0
Provider Version :2
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{54257D51-038A-4C8B-AFB5-054CEFED027B}] DATAGRAM 0
Provider Version :2
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{7ADE4086-0590-4446-8A30-3BA8F214F296}] SEQPACKET 2
Provider Version :2
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{7ADE4086-0590-4446-8A30-3BA8F214F296}] DATAGRAM 2
Provider Version :2
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{033E750A-1C2A-4671-8663-4ADAAC47EF76}] SEQPACKET 3
Provider Version :2
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{033E750A-1C2A-4671-8663-4ADAAC47EF76}] DATAGRAM 3
Provider Version :2
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{456187EB-C973-4902-8B1D-A3D3F6D694D9}] SEQPACKET 4
Provider Version :2
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{456187EB-C973-4902-8B1D-A3D3F6D694D9}] DATAGRAM 4
Provider Version :2

Max UDP size : 65507 bytes

DNS test . . . . . . . . . . . . . : Passed
Interface {7BA3D71A-43A4-4A81-B318-94D0445BE672}
DNS Domain:
DNS Servers: 127.0.0.1
IP Address: Expected registration with PDN (primary DNS
domain name):
Hostname: SMLAD.sml.com.
Authoritative zone: sml.com.
Primary DNS server: SMLAD.sml.com 192.168.0.55
Authoritative NS:192.168.8.70 192.168.0.55 192.168.100.20
192.168.36.250 192.168.0.58
Check the DNS registration for DCs entries on DNS server '127.0.0.1'
The Record is different on DNS server '127.0.0.1'.
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 '127.0.0.1', no need to
re-register.

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

The record on DNS server 127.0.0.1 is:
DNS NAME = sml.com
DNS DATA =
A 192.168.8.70
A 192.168.100.20
A 192.168.36.250
A 192.168.0.55
A 192.168.0.58
+------------------------------------------------------+

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

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

The record on DNS server 127.0.0.1 is:
DNS NAME = _ldap._tcp.sml.com
DNS DATA =
SRV 0 100 389 smlus-dc.sml.com
SRV 0 100 389 dyapp3.sml.com
SRV 0 100 389 smlad2.sml.com
SRV 0 100 389 dgdc.sml.com
SRV 0 100 389 smlad.sml.com
+------------------------------------------------------+

The Record is correct on DNS server '127.0.0.1'.

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME =
_ldap._tcp.bac13477-ec37-4340-941f-7a21ae77d0cb.domains._msdcs.sml.com.
DNS DATA =
SRV 0 100 389 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME =
_ldap._tcp.bac13477-ec37-4340-941f-7a21ae77d0cb.domains._msdcs.sml.com
DNS DATA =
SRV 0 100 389 smlus-dc.sml.com
SRV 0 100 389 dgdc.sml.com
SRV 0 100 389 smlad2.sml.com
SRV 0 100 389 dyapp3.sml.com
SRV 0 100 389 smlad.sml.com
+------------------------------------------------------+

The Record is correct on DNS server '127.0.0.1'.

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

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

The record on DNS server 127.0.0.1 is:
DNS NAME = _kerberos._tcp.dc._msdcs.sml.com
DNS DATA =
SRV 0 100 88 smlad.sml.com
SRV 0 100 88 smlus-dc.sml.com
SRV 0 100 88 dyapp3.sml.com
SRV 0 100 88 smlad2.sml.com
SRV 0 100 88 dgdc.sml.com
+------------------------------------------------------+

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

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

The record on DNS server 127.0.0.1 is:
DNS NAME = _ldap._tcp.dc._msdcs.sml.com
DNS DATA =
SRV 0 100 389 dgdc.sml.com
SRV 0 100 389 smlad2.sml.com
SRV 0 100 389 smlus-dc.sml.com
SRV 0 100 389 dyapp3.sml.com
SRV 0 100 389 smlad.sml.com
+------------------------------------------------------+

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

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

The record on DNS server 127.0.0.1 is:
DNS NAME = _kerberos._tcp.sml.com
DNS DATA =
SRV 0 100 88 smlad.sml.com
SRV 0 100 88 dyapp3.sml.com
SRV 0 100 88 smlus-dc.sml.com
SRV 0 100 88 dgdc.sml.com
SRV 0 100 88 smlad2.sml.com
+------------------------------------------------------+

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

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

The record on DNS server 127.0.0.1 is:
DNS NAME = _kerberos._udp.sml.com
DNS DATA =
SRV 0 100 88 smlad.sml.com
SRV 0 100 88 dyapp3.sml.com
SRV 0 100 88 smlus-dc.sml.com
SRV 0 100 88 dgdc.sml.com
SRV 0 100 88 smlad2.sml.com
+------------------------------------------------------+

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

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

The record on DNS server 127.0.0.1 is:
DNS NAME = _kpasswd._tcp.sml.com
DNS DATA =
SRV 0 100 464 smlad.sml.com
SRV 0 100 464 dyapp3.sml.com
SRV 0 100 464 smlus-dc.sml.com
SRV 0 100 464 dgdc.sml.com
SRV 0 100 464 smlad2.sml.com
+------------------------------------------------------+

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

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

The record on DNS server 127.0.0.1 is:
DNS NAME = _kpasswd._udp.sml.com
DNS DATA =
SRV 0 100 464 smlad.sml.com
SRV 0 100 464 dyapp3.sml.com
SRV 0 100 464 smlus-dc.sml.com
SRV 0 100 464 dgdc.sml.com
SRV 0 100 464 smlad2.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = DomainDnsZones.sml.com.
DNS DATA =
A 192.168.0.55

The record on DNS server 127.0.0.1 is:
DNS NAME = DomainDnsZones.sml.com
DNS DATA =
A 192.168.0.55
A 192.168.8.70
A 192.168.100.20
A 192.168.0.58
A 192.168.36.250
+------------------------------------------------------+

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

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

The record on DNS server 127.0.0.1 is:
DNS NAME = _ldap._tcp.DomainDnsZones.sml.com
DNS DATA =
SRV 0 100 389 smlad.sml.com
SRV 0 100 389 dyapp3.sml.com
SRV 0 100 389 smlad2.sml.com
SRV 0 100 389 dgdc.sml.com
SRV 0 100 389 smlus-dc.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = ForestDnsZones.sml.com.
DNS DATA =
A 192.168.0.55

The record on DNS server 127.0.0.1 is:
DNS NAME = ForestDnsZones.sml.com
DNS DATA =
A 192.168.11.2
A 192.168.16.2
A 5.73.235.93
A 192.168.20.10
A 192.168.19.10
A 192.168.8.70
A 192.168.36.250
A 192.168.34.10
A 192.168.100.20
A 192.168.0.58
A 192.168.0.55
+------------------------------------------------------+

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

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

The record on DNS server 127.0.0.1 is:
DNS NAME = _ldap._tcp.ForestDnsZones.sml.com
DNS DATA =
SRV 0 100 389 smlthai.thai.sml.com
SRV 0 100 389 smlad.sml.com
SRV 0 100 389 sml.korea.sml.com
SRV 0 100 389 dyapp3.sml.com
SRV 0 100 389 smlvn-dc01.vietnam.sml.com
SRV 0 100 389 smlus-dc.sml.com
SRV 0 100 389 smlad2.sml.com
SRV 0 100 389 smlvn-dc02.vietnam.sml.com
SRV 0 100 389 dgdc.sml.com
SRV 0 100 389 mn-fs01.rpdi.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.gc._msdcs.sml.com.
DNS DATA =
SRV 0 100 3268 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME = _ldap._tcp.gc._msdcs.sml.com
DNS DATA =
SRV 0 100 3268 smlvn-dc01.vietnam.sml.com
SRV 0 100 3268 smlad.sml.com
SRV 0 100 3268 smlthai.thai.sml.com
SRV 0 100 3268 mn-fs01.rpdi.sml.com
SRV 0 100 3268 sml.korea.sml.com
+------------------------------------------------------+

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

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

The record on DNS server 127.0.0.1 is:
DNS NAME = gc._msdcs.sml.com
DNS DATA =
A 192.168.11.2
A 192.168.34.10
A 192.168.16.2
A 5.73.235.93
A 192.168.19.10
A 192.168.0.55
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _gc._tcp.sml.com.
DNS DATA =
SRV 0 100 3268 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME = _gc._tcp.sml.com
DNS DATA =
SRV 0 100 3268 smlthai.thai.sml.com
SRV 0 100 3268 mn-fs01.rpdi.sml.com
SRV 0 100 3268 sml.korea.sml.com
SRV 0 100 3268 smlvn-dc01.vietnam.sml.com
SRV 0 100 3268 smlad.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.HongKong._sites.sml.com.
DNS DATA =
SRV 0 100 389 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME = _ldap._tcp.HongKong._sites.sml.com
DNS DATA =
SRV 0 100 389 smlad2.sml.com
SRV 0 100 389 smlad.sml.com
+------------------------------------------------------+

The Record is correct on DNS server '127.0.0.1'.

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.HongKong._sites.dc._msdcs.sml.com.
DNS DATA =
SRV 0 100 88 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME = _kerberos._tcp.HongKong._sites.dc._msdcs.sml.com
DNS DATA =
SRV 0 100 88 smlad.sml.com
SRV 0 100 88 smlad2.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.HongKong._sites.dc._msdcs.sml.com.
DNS DATA =
SRV 0 100 389 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME = _ldap._tcp.HongKong._sites.dc._msdcs.sml.com
DNS DATA =
SRV 0 100 389 smlad2.sml.com
SRV 0 100 389 smlad.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.HongKong._sites.sml.com.
DNS DATA =
SRV 0 100 88 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME = _kerberos._tcp.HongKong._sites.sml.com
DNS DATA =
SRV 0 100 88 smlad.sml.com
SRV 0 100 88 smlad2.sml.com
+------------------------------------------------------+

The Record is correct on DNS server '127.0.0.1'.

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.HongKong._sites.ForestDnsZones.sml.com.
DNS DATA =
SRV 0 100 389 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME = _ldap._tcp.HongKong._sites.ForestDnsZones.sml.com
DNS DATA =
SRV 0 100 389 smlad.sml.com
SRV 0 100 389 smlad2.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.HongKong._sites.DomainDnsZones.sml.com.
DNS DATA =
SRV 0 100 389 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME = _ldap._tcp.HongKong._sites.DomainDnsZones.sml.com
DNS DATA =
SRV 0 100 389 smlad.sml.com
SRV 0 100 389 smlad2.sml.com
+------------------------------------------------------+

pcnetnet · Jun 9, 2008

For Site A netdiag #2

The Record is correct on DNS server '127.0.0.1'.

The Record is correct on DNS server '127.0.0.1'.

The Record is correct on DNS server '127.0.0.1'.

The Record is correct on DNS server '127.0.0.1'.

The Record is correct on DNS server '127.0.0.1'.

The Record is correct on DNS server '127.0.0.1'.

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

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

The record on DNS server 127.0.0.1 is:
DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.ForestDnsZones.sml.com
DNS DATA =
SRV 0 100 389 smlad.sml.com
SRV 0 100 389 smlad2.sml.com
SRV 0 100 389 dyapp3.sml.com
+------------------------------------------------------+

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

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

The record on DNS server 127.0.0.1 is:
DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.DomainDnsZones.sml.com
DNS DATA =
SRV 0 100 389 smlad2.sml.com
SRV 0 100 389 smlad.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Korea._sites.DomainDnsZones.sml.com.
DNS DATA =
SRV 0 100 389 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME = _ldap._tcp.Korea._sites.DomainDnsZones.sml.com
DNS DATA =
SRV 0 100 389 smlad2.sml.com
SRV 0 100 389 smlad.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.RPDI._sites.DomainDnsZones.sml.com.
DNS DATA =
SRV 0 100 389 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME = _ldap._tcp.RPDI._sites.DomainDnsZones.sml.com
DNS DATA =
SRV 0 100 389 smlad2.sml.com
SRV 0 100 389 smlad.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Thailand._sites.DomainDnsZones.sml.com.
DNS DATA =
SRV 0 100 389 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME = _ldap._tcp.Thailand._sites.DomainDnsZones.sml.com
DNS DATA =
SRV 0 100 389 smlad2.sml.com
SRV 0 100 389 smlad.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Vietnam._sites.DomainDnsZones.sml.com.
DNS DATA =
SRV 0 100 389 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME = _ldap._tcp.Vietnam._sites.DomainDnsZones.sml.com
DNS DATA =
SRV 0 100 389 smlad2.sml.com
SRV 0 100 389 smlad.sml.com
+------------------------------------------------------+

The Record is correct on DNS server '127.0.0.1'.

The Record is correct on DNS server '127.0.0.1'.

The Record is correct on DNS server '127.0.0.1'.

The Record is correct on DNS server '127.0.0.1'.

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.UK._sites.ForestDnsZones.sml.com.
DNS DATA =
SRV 0 100 389 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME = _ldap._tcp.UK._sites.ForestDnsZones.sml.com
DNS DATA =
SRV 0 100 389 smlad.sml.com
SRV 0 100 389 smlad2.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.UK._sites.DomainDnsZones.sml.com.
DNS DATA =
SRV 0 100 389 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME = _ldap._tcp.UK._sites.DomainDnsZones.sml.com
DNS DATA =
SRV 0 100 389 smlad.sml.com
SRV 0 100 389 smlad2.sml.com
+------------------------------------------------------+

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

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

The record on DNS server 127.0.0.1 is:
DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.sml.com
DNS DATA =
SRV 0 100 389 dyapp3.sml.com
SRV 0 100 389 smlad.sml.com
SRV 0 100 389 smlad2.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Korea._sites.sml.com.
DNS DATA =
SRV 0 100 389 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME = _ldap._tcp.Korea._sites.sml.com
DNS DATA =
SRV 0 100 389 dyapp3.sml.com
SRV 0 100 389 smlad.sml.com
SRV 0 100 389 smlad2.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.RPDI._sites.sml.com.
DNS DATA =
SRV 0 100 389 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME = _ldap._tcp.RPDI._sites.sml.com
DNS DATA =
SRV 0 100 389 dyapp3.sml.com
SRV 0 100 389 smlad.sml.com
SRV 0 100 389 smlad2.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Thailand._sites.sml.com.
DNS DATA =
SRV 0 100 389 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME = _ldap._tcp.Thailand._sites.sml.com
DNS DATA =
SRV 0 100 389 dyapp3.sml.com
SRV 0 100 389 smlad.sml.com
SRV 0 100 389 smlad2.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.UK._sites.sml.com.
DNS DATA =
SRV 0 100 389 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME = _ldap._tcp.UK._sites.sml.com
DNS DATA =
SRV 0 100 389 dyapp3.sml.com
SRV 0 100 389 smlad.sml.com
SRV 0 100 389 smlad2.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Vietnam._sites.sml.com.
DNS DATA =
SRV 0 100 389 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME = _ldap._tcp.Vietnam._sites.sml.com
DNS DATA =
SRV 0 100 389 dyapp3.sml.com
SRV 0 100 389 smlad.sml.com
SRV 0 100 389 smlad2.sml.com
+------------------------------------------------------+

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

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

The record on DNS server 127.0.0.1 is:
DNS NAME = _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.sml.com
DNS DATA =
SRV 0 100 88 smlad.sml.com
SRV 0 100 88 smlad2.sml.com
SRV 0 100 88 dyapp3.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.Korea._sites.dc._msdcs.sml.com.
DNS DATA =
SRV 0 100 88 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME = _kerberos._tcp.Korea._sites.dc._msdcs.sml.com
DNS DATA =
SRV 0 100 88 dyapp3.sml.com
SRV 0 100 88 smlad.sml.com
SRV 0 100 88 smlad2.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.RPDI._sites.dc._msdcs.sml.com.
DNS DATA =
SRV 0 100 88 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME = _kerberos._tcp.RPDI._sites.dc._msdcs.sml.com
DNS DATA =
SRV 0 100 88 dyapp3.sml.com
SRV 0 100 88 smlad.sml.com
SRV 0 100 88 smlad2.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.Thailand._sites.dc._msdcs.sml.com.
DNS DATA =
SRV 0 100 88 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME = _kerberos._tcp.Thailand._sites.dc._msdcs.sml.com
DNS DATA =
SRV 0 100 88 dyapp3.sml.com
SRV 0 100 88 smlad.sml.com
SRV 0 100 88 smlad2.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.UK._sites.dc._msdcs.sml.com.
DNS DATA =
SRV 0 100 88 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME = _kerberos._tcp.UK._sites.dc._msdcs.sml.com
DNS DATA =
SRV 0 100 88 dyapp3.sml.com
SRV 0 100 88 smlad.sml.com
SRV 0 100 88 smlad2.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.Vietnam._sites.dc._msdcs.sml.com.
DNS DATA =
SRV 0 100 88 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME = _kerberos._tcp.Vietnam._sites.dc._msdcs.sml.com
DNS DATA =
SRV 0 100 88 dyapp3.sml.com
SRV 0 100 88 smlad.sml.com
SRV 0 100 88 smlad2.sml.com
+------------------------------------------------------+

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

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

The record on DNS server 127.0.0.1 is:
DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.sml.com
DNS DATA =
SRV 0 100 389 dyapp3.sml.com
SRV 0 100 389 smlad.sml.com
SRV 0 100 389 smlad2.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Korea._sites.dc._msdcs.sml.com.
DNS DATA =
SRV 0 100 389 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME = _ldap._tcp.Korea._sites.dc._msdcs.sml.com
DNS DATA =
SRV 0 100 389 dyapp3.sml.com
SRV 0 100 389 smlad.sml.com
SRV 0 100 389 smlad2.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.RPDI._sites.dc._msdcs.sml.com.
DNS DATA =
SRV 0 100 389 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME = _ldap._tcp.RPDI._sites.dc._msdcs.sml.com
DNS DATA =
SRV 0 100 389 dyapp3.sml.com
SRV 0 100 389 smlad.sml.com
SRV 0 100 389 smlad2.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Thailand._sites.dc._msdcs.sml.com.
DNS DATA =
SRV 0 100 389 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME = _ldap._tcp.Thailand._sites.dc._msdcs.sml.com
DNS DATA =
SRV 0 100 389 dyapp3.sml.com
SRV 0 100 389 smlad.sml.com
SRV 0 100 389 smlad2.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.UK._sites.dc._msdcs.sml.com.
DNS DATA =
SRV 0 100 389 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME = _ldap._tcp.UK._sites.dc._msdcs.sml.com
DNS DATA =
SRV 0 100 389 dyapp3.sml.com
SRV 0 100 389 smlad.sml.com
SRV 0 100 389 smlad2.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _ldap._tcp.Vietnam._sites.dc._msdcs.sml.com.
DNS DATA =
SRV 0 100 389 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME = _ldap._tcp.Vietnam._sites.dc._msdcs.sml.com
DNS DATA =
SRV 0 100 389 dyapp3.sml.com
SRV 0 100 389 smlad.sml.com
SRV 0 100 389 smlad2.sml.com
+------------------------------------------------------+

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

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

The record on DNS server 127.0.0.1 is:
DNS NAME = _kerberos._tcp.Default-First-Site-Name._sites.sml.com
DNS DATA =
SRV 0 100 88 dyapp3.sml.com
SRV 0 100 88 smlad.sml.com
SRV 0 100 88 smlad2.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.Korea._sites.sml.com.
DNS DATA =
SRV 0 100 88 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME = _kerberos._tcp.Korea._sites.sml.com
DNS DATA =
SRV 0 100 88 dyapp3.sml.com
SRV 0 100 88 smlad.sml.com
SRV 0 100 88 smlad2.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.RPDI._sites.sml.com.
DNS DATA =
SRV 0 100 88 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME = _kerberos._tcp.RPDI._sites.sml.com
DNS DATA =
SRV 0 100 88 dyapp3.sml.com
SRV 0 100 88 smlad.sml.com
SRV 0 100 88 smlad2.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.Thailand._sites.sml.com.
DNS DATA =
SRV 0 100 88 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME = _kerberos._tcp.Thailand._sites.sml.com
DNS DATA =
SRV 0 100 88 dyapp3.sml.com
SRV 0 100 88 smlad.sml.com
SRV 0 100 88 smlad2.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.UK._sites.sml.com.
DNS DATA =
SRV 0 100 88 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME = _kerberos._tcp.UK._sites.sml.com
DNS DATA =
SRV 0 100 88 dyapp3.sml.com
SRV 0 100 88 smlad.sml.com
SRV 0 100 88 smlad2.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = _kerberos._tcp.Vietnam._sites.sml.com.
DNS DATA =
SRV 0 100 88 SMLAD.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME = _kerberos._tcp.Vietnam._sites.sml.com
DNS DATA =
SRV 0 100 88 dyapp3.sml.com
SRV 0 100 88 smlad.sml.com
SRV 0 100 88 smlad2.sml.com
+------------------------------------------------------+

PASS - All the DNS entries for DC are registered on DNS server
'127.0.0.1' 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_{7BA3D71A-43A4-4A81-B318-94D0445BE672}
The redir is bound to 1 NetBt transport.

List of transports currently bound to the browser
NetBT_Tcpip_{7BA3D71A-43A4-4A81-B318-94D0445BE672}
The browser is bound to 1 NetBt transport.
Mailslot test for SML* passed.

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

Find DC in domain 'SML':
Found this DC in domain 'SML':
DC. . . . . . . . . . . : \\SMLAD.sml.com
Address . . . . . . . . : \\192.168.0.55
Domain Guid . . . . . . : {BAC13477-EC37-4340-941F-7A21AE77D0CB}
Domain Name . . . . . . : sml.com
Forest Name . . . . . . : sml.com
DC Site Name. . . . . . : HongKong
Our Site Name . . . . . : HongKong
Flags . . . . . . . . . : PDC emulator GC DS KDC TIMESERV GTIMESERV
WRITABLE DNS_DC DNS_DOMAIN DNS_FOREST CLOSE_SITE 0x8

Find PDC emulator in domain 'SML':
Found this PDC emulator in domain 'SML':
DC. . . . . . . . . . . : \\SMLAD.sml.com
Address . . . . . . . . : \\192.168.0.55
Domain Guid . . . . . . : {BAC13477-EC37-4340-941F-7A21AE77D0CB}
Domain Name . . . . . . : sml.com
Forest Name . . . . . . : sml.com
DC Site Name. . . . . . : HongKong
Our Site Name . . . . . : HongKong
Flags . . . . . . . . . : PDC emulator GC DS KDC TIMESERV GTIMESERV
WRITABLE DNS_DC DNS_DOMAIN DNS_FOREST CLOSE_SITE 0x8

Find Active Directory DC in domain 'SML':
Found this Active Directory DC in domain 'SML':
DC. . . . . . . . . . . : \\SMLAD.sml.com
Address . . . . . . . . : \\192.168.0.55
Domain Guid . . . . . . : {BAC13477-EC37-4340-941F-7A21AE77D0CB}
Domain Name . . . . . . : sml.com
Forest Name . . . . . . : sml.com
DC Site Name. . . . . . : HongKong
Our Site Name . . . . . : HongKong
Flags . . . . . . . . . : PDC emulator GC DS KDC TIMESERV GTIMESERV
WRITABLE DNS_DC DNS_DOMAIN DNS_FOREST CLOSE_SITE 0x8

DC list test . . . . . . . . . . . : Passed
List of DCs in Domain 'SML':
SMLAD.sml.com
dyapp3.sml.com (this DC is down)
smlad2.sml.com (this DC is down)
[WARNING] Cannot ping 'smlad2.sml.com' (it may be down).

SMLUS-DC.sml.com
dgdc.sml.com (this DC is down)

Trust relationship test. . . . . . : Skipped

Kerberos test. . . . . . . . . . . : Passed
Cached Tickets:

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

Do un-authenticated LDAP call to 'SMLAD.sml.com'.
Found 1 entries:
Attr: currentTime
Val: 17 20080605091601.0Z
Attr: subschemaSubentry
Val: 53 CN=Aggregate,CN=Schema,CN=Configuration,DC=sml,DC=com
Attr: dsServiceName
Val: 88 CN=NTDS
Settings,CN=SMLAD,CN=Servers,CN=HongKong,CN=Sites,CN=Configuration,DC=sml,DC=com
Attr: namingContexts
Val: 13 DC=sml,DC=com
Val: 30 CN=Configuration,DC=sml,DC=com
Val: 40 CN=Schema,CN=Configuration,DC=sml,DC=com
Val: 31 DC=DomainDnsZones,DC=sml,DC=com
Val: 31 DC=ForestDnsZones,DC=sml,DC=com
Attr: defaultNamingContext
Val: 13 DC=sml,DC=com
Attr: schemaNamingContext
Val: 40 CN=Schema,CN=Configuration,DC=sml,DC=com
Attr: configurationNamingContext
Val: 30 CN=Configuration,DC=sml,DC=com
Attr: rootDomainNamingContext
Val: 13 DC=sml,DC=com
Attr: supportedControl
Val: 22 1.2.840.113556.1.4.319
Val: 22 1.2.840.113556.1.4.801
Val: 22 1.2.840.113556.1.4.473
Val: 22 1.2.840.113556.1.4.528
Val: 22 1.2.840.113556.1.4.417
Val: 22 1.2.840.113556.1.4.619
Val: 22 1.2.840.113556.1.4.841
Val: 22 1.2.840.113556.1.4.529
Val: 22 1.2.840.113556.1.4.805
Val: 22 1.2.840.113556.1.4.521
Val: 22 1.2.840.113556.1.4.970
Val: 23 1.2.840.113556.1.4.1338
Val: 22 1.2.840.113556.1.4.474
Val: 23 1.2.840.113556.1.4.1339
Val: 23 1.2.840.113556.1.4.1340
Val: 23 1.2.840.113556.1.4.1413
Val: 23 2.16.840.1.113730.3.4.9
Val: 24 2.16.840.1.113730.3.4.10
Val: 23 1.2.840.113556.1.4.1504
Val: 23 1.2.840.113556.1.4.1852
Val: 22 1.2.840.113556.1.4.802
Val: 23 1.2.840.113556.1.4.1907
Val: 23 1.2.840.113556.1.4.1948
Attr: supportedLDAPVersion
Val: 1 3
Val: 1 2
Attr: supportedLDAPPolicies
Val: 14 MaxPoolThreads
Val: 15 MaxDatagramRecv
Val: 16 MaxReceiveBuffer
Val: 15 InitRecvTimeout
Val: 14 MaxConnections
Val: 15 MaxConnIdleTime
Val: 11 MaxPageSize
Val: 16 MaxQueryDuration
Val: 16 MaxTempTableSize
Val: 16 MaxResultSetSize
Val: 22 MaxNotificationPerConn
Val: 11 MaxValRange
Attr: highestCommittedUSN
Val: 7 5617381
Attr: supportedSASLMechanisms
Val: 6 GSSAPI
Val: 10 GSS-SPNEGO
Val: 8 EXTERNAL
Val: 10 DIGEST-MD5
Attr: dnsHostName
Val: 13 SMLAD.sml.com
Attr: ldapServiceName
Val: 22 sml.com:[email protected]
Attr: serverName
Val: 71
CN=SMLAD,CN=Servers,CN=HongKong,CN=Sites,CN=Configuration,DC=sml,DC=com
Attr: supportedCapabilities
Val: 22 1.2.840.113556.1.4.800
Val: 23 1.2.840.113556.1.4.1670
Val: 23 1.2.840.113556.1.4.1791
Attr: isSynchronized
Val: 4 TRUE
Attr: isGlobalCatalogReady
Val: 4 TRUE
Attr: domainFunctionality
Val: 1 2
Attr: forestFunctionality
Val: 1 2
Attr: domainControllerFunctionality
Val: 1 2

Do NTLM authenticated LDAP call to 'SMLAD.sml.com'.
Found 1 entries:
Attr: currentTime
Val: 17 20080605091601.0Z
Attr: subschemaSubentry
Val: 53 CN=Aggregate,CN=Schema,CN=Configuration,DC=sml,DC=com
Attr: dsServiceName
Val: 88 CN=NTDS
Settings,CN=SMLAD,CN=Servers,CN=HongKong,CN=Sites,CN=Configuration,DC=sml,DC=com
Attr: namingContexts
Val: 13 DC=sml,DC=com
Val: 30 CN=Configuration,DC=sml,DC=com
Val: 40 CN=Schema,CN=Configuration,DC=sml,DC=com
Val: 31 DC=DomainDnsZones,DC=sml,DC=com
Val: 31 DC=ForestDnsZones,DC=sml,DC=com
Attr: defaultNamingContext
Val: 13 DC=sml,DC=com
Attr: schemaNamingContext
Val: 40 CN=Schema,CN=Configuration,DC=sml,DC=com
Attr: configurationNamingContext
Val: 30 CN=Configuration,DC=sml,DC=com
Attr: rootDomainNamingContext
Val: 13 DC=sml,DC=com
Attr: supportedControl
Val: 22 1.2.840.113556.1.4.319
Val: 22 1.2.840.113556.1.4.801
Val: 22 1.2.840.113556.1.4.473
Val: 22 1.2.840.113556.1.4.528
Val: 22 1.2.840.113556.1.4.417
Val: 22 1.2.840.113556.1.4.619
Val: 22 1.2.840.113556.1.4.841
Val: 22 1.2.840.113556.1.4.529
Val: 22 1.2.840.113556.1.4.805
Val: 22 1.2.840.113556.1.4.521
Val: 22 1.2.840.113556.1.4.970
Val: 23 1.2.840.113556.1.4.1338
Val: 22 1.2.840.113556.1.4.474
Val: 23 1.2.840.113556.1.4.1339
Val: 23 1.2.840.113556.1.4.1340
Val: 23 1.2.840.113556.1.4.1413
Val: 23 2.16.840.1.113730.3.4.9
Val: 24 2.16.840.1.113730.3.4.10
Val: 23 1.2.840.113556.1.4.1504
Val: 23 1.2.840.113556.1.4.1852
Val: 22 1.2.840.113556.1.4.802
Val: 23 1.2.840.113556.1.4.1907
Val: 23 1.2.840.113556.1.4.1948
Attr: supportedLDAPVersion
Val: 1 3
Val: 1 2
Attr: supportedLDAPPolicies
Val: 14 MaxPoolThreads
Val: 15 MaxDatagramRecv
Val: 16 MaxReceiveBuffer
Val: 15 InitRecvTimeout
Val: 14 MaxConnections
Val: 15 MaxConnIdleTime
Val: 11 MaxPageSize
Val: 16 MaxQueryDuration
Val: 16 MaxTempTableSize
Val: 16 MaxResultSetSize
Val: 22 MaxNotificationPerConn
Val: 11 MaxValRange
Attr: highestCommittedUSN
Val: 7 5617381
Attr: supportedSASLMechanisms
Val: 6 GSSAPI
Val: 10 GSS-SPNEGO
Val: 8 EXTERNAL
Val: 10 DIGEST-MD5
Attr: dnsHostName
Val: 13 SMLAD.sml.com
Attr: ldapServiceName
Val: 22 sml.com:[email protected]
Attr: serverName
Val: 71
CN=SMLAD,CN=Servers,CN=HongKong,CN=Sites,CN=Configuration,DC=sml,DC=com
Attr: supportedCapabilities
Val: 22 1.2.840.113556.1.4.800
Val: 23 1.2.840.113556.1.4.1670
Val: 23 1.2.840.113556.1.4.1791
Attr: isSynchronized
Val: 4 TRUE
Attr: isGlobalCatalogReady
Val: 4 TRUE
Attr: domainFunctionality
Val: 1 2
Attr: forestFunctionality
Val: 1 2
Attr: domainControllerFunctionality
Val: 1 2

Do Negotiate authenticated LDAP call to 'SMLAD.sml.com'.
Found 1 entries:
Attr: currentTime
Val: 17 20080605091601.0Z
Attr: subschemaSubentry
Val: 53 CN=Aggregate,CN=Schema,CN=Configuration,DC=sml,DC=com
Attr: dsServiceName
Val: 88 CN=NTDS
Settings,CN=SMLAD,CN=Servers,CN=HongKong,CN=Sites,CN=Configuration,DC=sml,DC=com
Attr: namingContexts
Val: 13 DC=sml,DC=com
Val: 30 CN=Configuration,DC=sml,DC=com
Val: 40 CN=Schema,CN=Configuration,DC=sml,DC=com
Val: 31 DC=DomainDnsZones,DC=sml,DC=com
Val: 31 DC=ForestDnsZones,DC=sml,DC=com
Attr: defaultNamingContext
Val: 13 DC=sml,DC=com
Attr: schemaNamingContext
Val: 40 CN=Schema,CN=Configuration,DC=sml,DC=com
Attr: configurationNamingContext
Val: 30 CN=Configuration,DC=sml,DC=com
Attr: rootDomainNamingContext
Val: 13 DC=sml,DC=com
Attr: supportedControl
Val: 22 1.2.840.113556.1.4.319
Val: 22 1.2.840.113556.1.4.801
Val: 22 1.2.840.113556.1.4.473
Val: 22 1.2.840.113556.1.4.528
Val: 22 1.2.840.113556.1.4.417
Val: 22 1.2.840.113556.1.4.619
Val: 22 1.2.840.113556.1.4.841
Val: 22 1.2.840.113556.1.4.529
Val: 22 1.2.840.113556.1.4.805
Val: 22 1.2.840.113556.1.4.521
Val: 22 1.2.840.113556.1.4.970
Val: 23 1.2.840.113556.1.4.1338
Val: 22 1.2.840.113556.1.4.474
Val: 23 1.2.840.113556.1.4.1339
Val: 23 1.2.840.113556.1.4.1340
Val: 23 1.2.840.113556.1.4.1413
Val: 23 2.16.840.1.113730.3.4.9
Val: 24 2.16.840.1.113730.3.4.10
Val: 23 1.2.840.113556.1.4.1504
Val: 23 1.2.840.113556.1.4.1852
Val: 22 1.2.840.113556.1.4.802
Val: 23 1.2.840.113556.1.4.1907
Val: 23 1.2.840.113556.1.4.1948
Attr: supportedLDAPVersion
Val: 1 3
Val: 1 2
Attr: supportedLDAPPolicies
Val: 14 MaxPoolThreads
Val: 15 MaxDatagramRecv
Val: 16 MaxReceiveBuffer
Val: 15 InitRecvTimeout
Val: 14 MaxConnections
Val: 15 MaxConnIdleTime
Val: 11 MaxPageSize
Val: 16 MaxQueryDuration
Val: 16 MaxTempTableSize
Val: 16 MaxResultSetSize
Val: 22 MaxNotificationPerConn
Val: 11 MaxValRange
Attr: highestCommittedUSN
Val: 7 5617381
Attr: supportedSASLMechanisms
Val: 6 GSSAPI
Val: 10 GSS-SPNEGO
Val: 8 EXTERNAL
Val: 10 DIGEST-MD5
Attr: dnsHostName
Val: 13 SMLAD.sml.com
Attr: ldapServiceName
Val: 22 sml.com:[email protected]
Attr: serverName
Val: 71
CN=SMLAD,CN=Servers,CN=HongKong,CN=Sites,CN=Configuration,DC=sml,DC=com
Attr: supportedCapabilities
Val: 22 1.2.840.113556.1.4.800
Val: 23 1.2.840.113556.1.4.1670
Val: 23 1.2.840.113556.1.4.1791
Attr: isSynchronized
Val: 4 TRUE
Attr: isGlobalCatalogReady
Val: 4 TRUE
Attr: domainFunctionality
Val: 1 2
Attr: forestFunctionality
Val: 1 2
Attr: domainControllerFunctionality
Val: 1 2

Registered Service Principal Names:
MSSQLSvc/SMLAD.sml.com
NtFrs-88f5d2bd-b646-11d2-a6d3-00c04fc9b232/SMLAD.sml.com
ldap/SMLAD.sml.com/ForestDnsZones.sml.com
ldap/SMLAD.sml.com/DomainDnsZones.sml.com
GC/SMLAD.sml.com/sml.com
HOST/SMLAD.sml.com/SML
HOST/SMLAD
HOST/SMLAD.sml.com
HOST/SMLAD.sml.com/sml.com
E3514235-4B06-11D1-AB04-00C04FC2DCD2/6ad1947f-b693-4166-85fc-d2097457fec6/sml.com
ldap/6ad1947f-b693-4166-85fc-d2097457fec6._msdcs.sml.com
ldap/SMLAD.sml.com/SML
ldap/SMLAD
ldap/SMLAD.sml.com
ldap/SMLAD.sml.com/sml.com
DNS/SMLAD.sml.com
Since 'dyapp3.sml.com' is down, it cannot be tested.

pcnetnet · Jun 9, 2008

For Site A netdiag #3

Registered Service Principal Names:
MSSQLSvc/SMLAD.sml.com
NtFrs-88f5d2bd-b646-11d2-a6d3-00c04fc9b232/SMLAD.sml.com
ldap/SMLAD.sml.com/ForestDnsZones.sml.com
ldap/SMLAD.sml.com/DomainDnsZones.sml.com
GC/SMLAD.sml.com/sml.com
HOST/SMLAD.sml.com/SML
HOST/SMLAD
HOST/SMLAD.sml.com
HOST/SMLAD.sml.com/sml.com
E3514235-4B06-11D1-AB04-00C04FC2DCD2/6ad1947f-b693-4166-85fc-d2097457fec6/sml.com
ldap/6ad1947f-b693-4166-85fc-d2097457fec6._msdcs.sml.com
ldap/SMLAD.sml.com/SML
ldap/SMLAD
ldap/SMLAD.sml.com
ldap/SMLAD.sml.com/sml.com
DNS/SMLAD.sml.com
Since 'smlad2.sml.com' is down, it cannot be tested.
[WARNING] Failed to query SPN registration on DC 'smlad2.sml.com'.

Do un-authenticated LDAP call to 'SMLUS-DC.sml.com'.
Found 1 entries:
Attr: currentTime
Val: 17 20080605091622.0Z
Attr: subschemaSubentry
Val: 53 CN=Aggregate,CN=Schema,CN=Configuration,DC=sml,DC=com
Attr: dsServiceName
Val: 85 CN=NTDS
Settings,CN=SMLUS-DC,CN=Servers,CN=US,CN=Sites,CN=Configuration,DC=sml,DC=com
Attr: namingContexts
Val: 13 DC=sml,DC=com
Val: 30 CN=Configuration,DC=sml,DC=com
Val: 40 CN=Schema,CN=Configuration,DC=sml,DC=com
Val: 31 DC=DomainDnsZones,DC=sml,DC=com
Val: 31 DC=ForestDnsZones,DC=sml,DC=com
Attr: defaultNamingContext
Val: 13 DC=sml,DC=com
Attr: schemaNamingContext
Val: 40 CN=Schema,CN=Configuration,DC=sml,DC=com
Attr: configurationNamingContext
Val: 30 CN=Configuration,DC=sml,DC=com
Attr: rootDomainNamingContext
Val: 13 DC=sml,DC=com
Attr: supportedControl
Val: 22 1.2.840.113556.1.4.319
Val: 22 1.2.840.113556.1.4.801
Val: 22 1.2.840.113556.1.4.473
Val: 22 1.2.840.113556.1.4.528
Val: 22 1.2.840.113556.1.4.417
Val: 22 1.2.840.113556.1.4.619
Val: 22 1.2.840.113556.1.4.841
Val: 22 1.2.840.113556.1.4.529
Val: 22 1.2.840.113556.1.4.805
Val: 22 1.2.840.113556.1.4.521
Val: 22 1.2.840.113556.1.4.970
Val: 23 1.2.840.113556.1.4.1338
Val: 22 1.2.840.113556.1.4.474
Val: 23 1.2.840.113556.1.4.1339
Val: 23 1.2.840.113556.1.4.1340
Val: 23 1.2.840.113556.1.4.1413
Val: 23 2.16.840.1.113730.3.4.9
Val: 24 2.16.840.1.113730.3.4.10
Val: 23 1.2.840.113556.1.4.1504
Val: 23 1.2.840.113556.1.4.1852
Val: 22 1.2.840.113556.1.4.802
Val: 23 1.2.840.113556.1.4.1907
Val: 23 1.2.840.113556.1.4.1948
Attr: supportedLDAPVersion
Val: 1 3
Val: 1 2
Attr: supportedLDAPPolicies
Val: 14 MaxPoolThreads
Val: 15 MaxDatagramRecv
Val: 16 MaxReceiveBuffer
Val: 15 InitRecvTimeout
Val: 14 MaxConnections
Val: 15 MaxConnIdleTime
Val: 11 MaxPageSize
Val: 16 MaxQueryDuration
Val: 16 MaxTempTableSize
Val: 16 MaxResultSetSize
Val: 22 MaxNotificationPerConn
Val: 11 MaxValRange
Attr: highestCommittedUSN
Val: 5 52048
Attr: supportedSASLMechanisms
Val: 6 GSSAPI
Val: 10 GSS-SPNEGO
Val: 8 EXTERNAL
Val: 10 DIGEST-MD5
Attr: dnsHostName
Val: 16 SMLUS-DC.sml.com
Attr: ldapServiceName
Val: 25 sml.com:[email protected]
Attr: serverName
Val: 68
CN=SMLUS-DC,CN=Servers,CN=US,CN=Sites,CN=Configuration,DC=sml,DC=com
Attr: supportedCapabilities
Val: 22 1.2.840.113556.1.4.800
Val: 23 1.2.840.113556.1.4.1670
Val: 23 1.2.840.113556.1.4.1791
Attr: isSynchronized
Val: 4 TRUE
Attr: isGlobalCatalogReady
Val: 5 FALSE
Attr: domainFunctionality
Val: 1 2
Attr: forestFunctionality
Val: 1 2
Attr: domainControllerFunctionality
Val: 1 2

Do NTLM authenticated LDAP call to 'SMLUS-DC.sml.com'.
Found 1 entries:
Attr: currentTime
Val: 17 20080605091630.0Z
Attr: subschemaSubentry
Val: 53 CN=Aggregate,CN=Schema,CN=Configuration,DC=sml,DC=com
Attr: dsServiceName
Val: 85 CN=NTDS
Settings,CN=SMLUS-DC,CN=Servers,CN=US,CN=Sites,CN=Configuration,DC=sml,DC=com
Attr: namingContexts
Val: 13 DC=sml,DC=com
Val: 30 CN=Configuration,DC=sml,DC=com
Val: 40 CN=Schema,CN=Configuration,DC=sml,DC=com
Val: 31 DC=DomainDnsZones,DC=sml,DC=com
Val: 31 DC=ForestDnsZones,DC=sml,DC=com
Attr: defaultNamingContext
Val: 13 DC=sml,DC=com
Attr: schemaNamingContext
Val: 40 CN=Schema,CN=Configuration,DC=sml,DC=com
Attr: configurationNamingContext
Val: 30 CN=Configuration,DC=sml,DC=com
Attr: rootDomainNamingContext
Val: 13 DC=sml,DC=com
Attr: supportedControl
Val: 22 1.2.840.113556.1.4.319
Val: 22 1.2.840.113556.1.4.801
Val: 22 1.2.840.113556.1.4.473
Val: 22 1.2.840.113556.1.4.528
Val: 22 1.2.840.113556.1.4.417
Val: 22 1.2.840.113556.1.4.619
Val: 22 1.2.840.113556.1.4.841
Val: 22 1.2.840.113556.1.4.529
Val: 22 1.2.840.113556.1.4.805
Val: 22 1.2.840.113556.1.4.521
Val: 22 1.2.840.113556.1.4.970
Val: 23 1.2.840.113556.1.4.1338
Val: 22 1.2.840.113556.1.4.474
Val: 23 1.2.840.113556.1.4.1339
Val: 23 1.2.840.113556.1.4.1340
Val: 23 1.2.840.113556.1.4.1413
Val: 23 2.16.840.1.113730.3.4.9
Val: 24 2.16.840.1.113730.3.4.10
Val: 23 1.2.840.113556.1.4.1504
Val: 23 1.2.840.113556.1.4.1852
Val: 22 1.2.840.113556.1.4.802
Val: 23 1.2.840.113556.1.4.1907
Val: 23 1.2.840.113556.1.4.1948
Attr: supportedLDAPVersion
Val: 1 3
Val: 1 2
Attr: supportedLDAPPolicies
Val: 14 MaxPoolThreads
Val: 15 MaxDatagramRecv
Val: 16 MaxReceiveBuffer
Val: 15 InitRecvTimeout
Val: 14 MaxConnections
Val: 15 MaxConnIdleTime
Val: 11 MaxPageSize
Val: 16 MaxQueryDuration
Val: 16 MaxTempTableSize
Val: 16 MaxResultSetSize
Val: 22 MaxNotificationPerConn
Val: 11 MaxValRange
Attr: highestCommittedUSN
Val: 5 52048
Attr: supportedSASLMechanisms
Val: 6 GSSAPI
Val: 10 GSS-SPNEGO
Val: 8 EXTERNAL
Val: 10 DIGEST-MD5
Attr: dnsHostName
Val: 16 SMLUS-DC.sml.com
Attr: ldapServiceName
Val: 25 sml.com:[email protected]
Attr: serverName
Val: 68
CN=SMLUS-DC,CN=Servers,CN=US,CN=Sites,CN=Configuration,DC=sml,DC=com
Attr: supportedCapabilities
Val: 22 1.2.840.113556.1.4.800
Val: 23 1.2.840.113556.1.4.1670
Val: 23 1.2.840.113556.1.4.1791
Attr: isSynchronized
Val: 4 TRUE
Attr: isGlobalCatalogReady
Val: 5 FALSE
Attr: domainFunctionality
Val: 1 2
Attr: forestFunctionality
Val: 1 2
Attr: domainControllerFunctionality
Val: 1 2

Do Negotiate authenticated LDAP call to 'SMLUS-DC.sml.com'.
Found 1 entries:
Attr: currentTime
Val: 17 20080605091632.0Z
Attr: subschemaSubentry
Val: 53 CN=Aggregate,CN=Schema,CN=Configuration,DC=sml,DC=com
Attr: dsServiceName
Val: 85 CN=NTDS
Settings,CN=SMLUS-DC,CN=Servers,CN=US,CN=Sites,CN=Configuration,DC=sml,DC=com
Attr: namingContexts
Val: 13 DC=sml,DC=com
Val: 30 CN=Configuration,DC=sml,DC=com
Val: 40 CN=Schema,CN=Configuration,DC=sml,DC=com
Val: 31 DC=DomainDnsZones,DC=sml,DC=com
Val: 31 DC=ForestDnsZones,DC=sml,DC=com
Attr: defaultNamingContext
Val: 13 DC=sml,DC=com
Attr: schemaNamingContext
Val: 40 CN=Schema,CN=Configuration,DC=sml,DC=com
Attr: configurationNamingContext
Val: 30 CN=Configuration,DC=sml,DC=com
Attr: rootDomainNamingContext
Val: 13 DC=sml,DC=com
Attr: supportedControl
Val: 22 1.2.840.113556.1.4.319
Val: 22 1.2.840.113556.1.4.801
Val: 22 1.2.840.113556.1.4.473
Val: 22 1.2.840.113556.1.4.528
Val: 22 1.2.840.113556.1.4.417
Val: 22 1.2.840.113556.1.4.619
Val: 22 1.2.840.113556.1.4.841
Val: 22 1.2.840.113556.1.4.529
Val: 22 1.2.840.113556.1.4.805
Val: 22 1.2.840.113556.1.4.521
Val: 22 1.2.840.113556.1.4.970
Val: 23 1.2.840.113556.1.4.1338
Val: 22 1.2.840.113556.1.4.474
Val: 23 1.2.840.113556.1.4.1339
Val: 23 1.2.840.113556.1.4.1340
Val: 23 1.2.840.113556.1.4.1413
Val: 23 2.16.840.1.113730.3.4.9
Val: 24 2.16.840.1.113730.3.4.10
Val: 23 1.2.840.113556.1.4.1504
Val: 23 1.2.840.113556.1.4.1852
Val: 22 1.2.840.113556.1.4.802
Val: 23 1.2.840.113556.1.4.1907
Val: 23 1.2.840.113556.1.4.1948
Attr: supportedLDAPVersion
Val: 1 3
Val: 1 2
Attr: supportedLDAPPolicies
Val: 14 MaxPoolThreads
Val: 15 MaxDatagramRecv
Val: 16 MaxReceiveBuffer
Val: 15 InitRecvTimeout
Val: 14 MaxConnections
Val: 15 MaxConnIdleTime
Val: 11 MaxPageSize
Val: 16 MaxQueryDuration
Val: 16 MaxTempTableSize
Val: 16 MaxResultSetSize
Val: 22 MaxNotificationPerConn
Val: 11 MaxValRange
Attr: highestCommittedUSN
Val: 5 52048
Attr: supportedSASLMechanisms
Val: 6 GSSAPI
Val: 10 GSS-SPNEGO
Val: 8 EXTERNAL
Val: 10 DIGEST-MD5
Attr: dnsHostName
Val: 16 SMLUS-DC.sml.com
Attr: ldapServiceName
Val: 25 sml.com:[email protected]
Attr: serverName
Val: 68
CN=SMLUS-DC,CN=Servers,CN=US,CN=Sites,CN=Configuration,DC=sml,DC=com
Attr: supportedCapabilities
Val: 22 1.2.840.113556.1.4.800
Val: 23 1.2.840.113556.1.4.1670
Val: 23 1.2.840.113556.1.4.1791
Attr: isSynchronized
Val: 4 TRUE
Attr: isGlobalCatalogReady
Val: 5 FALSE
Attr: domainFunctionality
Val: 1 2
Attr: forestFunctionality
Val: 1 2
Attr: domainControllerFunctionality
Val: 1 2

Registered Service Principal Names:
MSSQLSvc/SMLAD.sml.com
NtFrs-88f5d2bd-b646-11d2-a6d3-00c04fc9b232/SMLAD.sml.com
ldap/SMLAD.sml.com/ForestDnsZones.sml.com
ldap/SMLAD.sml.com/DomainDnsZones.sml.com
GC/SMLAD.sml.com/sml.com
HOST/SMLAD.sml.com/SML
HOST/SMLAD
HOST/SMLAD.sml.com
HOST/SMLAD.sml.com/sml.com
E3514235-4B06-11D1-AB04-00C04FC2DCD2/6ad1947f-b693-4166-85fc-d2097457fec6/sml.com
ldap/6ad1947f-b693-4166-85fc-d2097457fec6._msdcs.sml.com
ldap/SMLAD.sml.com/SML
ldap/SMLAD
ldap/SMLAD.sml.com
ldap/SMLAD.sml.com/sml.com
DNS/SMLAD.sml.com
Since 'dgdc.sml.com' is down, it cannot be tested.

Registered Service Principal Names:
MSSQLSvc/SMLAD.sml.com
NtFrs-88f5d2bd-b646-11d2-a6d3-00c04fc9b232/SMLAD.sml.com
ldap/SMLAD.sml.com/ForestDnsZones.sml.com
ldap/SMLAD.sml.com/DomainDnsZones.sml.com
GC/SMLAD.sml.com/sml.com
HOST/SMLAD.sml.com/SML
HOST/SMLAD
HOST/SMLAD.sml.com
HOST/SMLAD.sml.com/sml.com
E3514235-4B06-11D1-AB04-00C04FC2DCD2/6ad1947f-b693-4166-85fc-d2097457fec6/sml.com
ldap/6ad1947f-b693-4166-85fc-d2097457fec6._msdcs.sml.com
ldap/SMLAD.sml.com/SML
ldap/SMLAD
ldap/SMLAD.sml.com
ldap/SMLAD.sml.com/sml.com
DNS/SMLAD.sml.com

Routing table test . . . . . . . . : Passed
Active Routes :
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 192.168.0.253 192.168.0.55
20
61.135.150.76 255.255.255.255 192.168.0.1 192.168.0.55
1
61.135.179.169 255.255.255.255 192.168.0.1 192.168.0.55
1
61.135.208.88 255.255.255.255 192.168.0.1 192.168.0.55
1
61.152.82.18 255.255.255.255 192.168.0.1 192.168.0.55
1
121.0.17.58 255.255.255.255 192.168.0.1 192.168.0.55
1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
192.55.83.30 255.255.255.255 192.168.0.1 192.168.0.55
1
192.168.0.0 255.255.255.0 192.168.0.55 192.168.0.55
20
192.168.0.55 255.255.255.255 127.0.0.1 127.0.0.1
20
192.168.0.255 255.255.255.255 192.168.0.55 192.168.0.55
20
192.168.2.6 255.255.255.255 192.168.0.3 192.168.0.55
1
192.168.11.0 255.255.255.0 192.168.0.1 192.168.0.55
1
192.168.16.2 255.255.255.255 192.168.0.1 192.168.0.55
1
192.168.19.10 255.255.255.255 192.168.0.1 192.168.0.55
1
192.168.34.10 255.255.255.255 192.168.0.1 192.168.0.55
1
192.168.36.250 255.255.255.255 192.168.0.3 192.168.0.55
1
192.168.88.219 255.255.255.255 192.168.0.1 192.168.0.55
1
192.168.139.1 255.255.255.255 192.168.0.1 192.168.0.55
1
192.168.220.1 255.255.255.255 192.168.0.1 192.168.0.55
1
202.12.28.140 255.255.255.255 192.168.0.1 192.168.0.55
1
202.67.240.221 255.255.255.255 192.168.0.1 192.168.0.55
1
202.72.171.112 255.255.255.255 192.168.0.1 192.168.0.55
1
202.101.42.29 255.255.255.255 192.168.0.1 192.168.0.55
1
202.166.85.9 255.255.255.255 192.168.0.1 192.168.0.55
1
220.181.26.169 255.255.255.255 192.168.0.1 192.168.0.55
1
220.181.28.3 255.255.255.255 192.168.0.1 192.168.0.55
1
224.0.0.0 240.0.0.0 192.168.0.55 192.168.0.55
20
255.255.255.255 255.255.255.255 192.168.0.55 192.168.0.55
1

Persistent Route Entries:
192.168.11.0 255.255.255.0 192.168.0.1 0
1

Netstat information test . . . . . : Passed

Interface Statistics

Received Sent
Unicast Packets 944057669 849824857
Non-unicast packets 17558594 569203
Discards 0 0
Errors 0 0
Unknown protocols 7987803 458284

Interface index = 1
Description = MS TCP Loopback interface
Type = 24
MTU = 1520
Speed = 10000000
Physical Address = 00-00-00-00-00-00
Administrative Status = 1
Operational Status = 1
Last Changed = 1119102541
Output Queue Length = 0

Interface index = 65539
Description = 3Com 3C996 10/100/1000 Server NIC
Type = 6
MTU = 1500
Speed = 100000000
Physical Address = 00-04-76-2F-E2-96
Administrative Status = 1
Operational Status = 1
Last Changed = 1119102553
Output Queue Length = 0

Active Connections

Proto Local Address Foreign Address
State
TCP SMLAD:domain SMLAD.sml.com:49282
LISTENING
TCP SMLAD:http SMLAD.sml.com:20482
LISTENING
TCP SMLAD:kerberos SMLAD.sml.com:47154
LISTENING
TCP SMLAD:epmap SMLAD.sml.com:22741
LISTENING
TCP SMLAD:ldap SMLAD.sml.com:epmap
LISTENING
TCP SMLAD:https SMLAD.sml.com:47116
LISTENING
TCP SMLAD:microsoft-ds SMLAD.sml.com:28691
LISTENING
TCP SMLAD:kpasswd SMLAD.sml.com:39038
LISTENING
TCP SMLAD:http-rpc-epmap SMLAD.sml.com:49158
LISTENING
TCP SMLAD:ldaps SMLAD.sml.com:39118
LISTENING
TCP SMLAD:1025 SMLAD.sml.com:221
LISTENING
TCP SMLAD:1028 SMLAD.sml.com:10476
LISTENING
TCP SMLAD:1060 SMLAD.sml.com:39155
LISTENING
TCP SMLAD:1063 SMLAD.sml.com:38999
LISTENING
TCP SMLAD:1070 SMLAD.sml.com:6350
LISTENING
TCP SMLAD:1071 SMLAD.sml.com:39150
LISTENING
TCP SMLAD:1311 SMLAD.sml.com:4220
LISTENING
TCP SMLAD:1888 SMLAD.sml.com:38958
LISTENING
TCP SMLAD:msft-gc SMLAD.sml.com:4264
LISTENING
TCP SMLAD:msft-gc-ssl SMLAD.sml.com:47258
LISTENING
TCP SMLAD:ms-wbt-server SMLAD.sml.com:24811
LISTENING
TCP SMLAD:4581 SMLAD.sml.com:53394
LISTENING
TCP SMLAD:5800 SMLAD.sml.com:2176
LISTENING
TCP SMLAD:5900 SMLAD.sml.com:6292
LISTENING
TCP SMLAD:8000 SMLAD.sml.com:18658
LISTENING
TCP SMLAD:ldap SMLAD.sml.com:1038
ESTABLISHED
TCP SMLAD:ldap SMLAD.sml.com:1039
ESTABLISHED
TCP SMLAD:ldap SMLAD.sml.com:1041
ESTABLISHED
TCP SMLAD:ldap SMLAD.sml.com:3943
ESTABLISHED
TCP SMLAD:1038 SMLAD.sml.com:ldap
ESTABLISHED
TCP SMLAD:1039 SMLAD.sml.com:ldap
ESTABLISHED
TCP SMLAD:1041 SMLAD.sml.com:ldap
ESTABLISHED
TCP SMLAD:1088 SMLAD.sml.com:53287
LISTENING
TCP SMLAD:2491 SMLAD.sml.com:30845
LISTENING
TCP SMLAD:3064 SMLAD.sml.com:ldap
CLOSE_WAIT
TCP SMLAD:3475 SMLAD.sml.com:ldap
CLOSE_WAIT
TCP SMLAD:3943 SMLAD.sml.com:ldap
ESTABLISHED
TCP SMLAD:epmap dyapp2.sml.com:3398
ESTABLISHED
TCP SMLAD:epmap uksql.sml.com:2972
ESTABLISHED
TCP SMLAD:epmap uksql.sml.com:3000
ESTABLISHED
TCP SMLAD:epmap 192.168.6.44:1827
ESTABLISHED
TCP SMLAD:epmap dhkcmanwu.sml.com:1858
ESTABLISHED
TCP SMLAD:epmap nina_lee.sml_dy:2278
ESTABLISHED
TCP SMLAD:netbios-ssn SMLAD.sml.com:26665
LISTENING
TCP SMLAD:netbios-ssn dyapp5.sml.com:2266
ESTABLISHED
TCP SMLAD:netbios-ssn ft-ltxp-10.fastabs.local:1785
ESTABLISHED
TCP SMLAD:ldap SMLAD.sml.com:1622
FIN_WAIT_2
TCP SMLAD:ldap SMLAD.sml.com:2465
TIME_WAIT
TCP SMLAD:ldap SMLAD.sml.com:2466
TIME_WAIT
TCP SMLAD:ldap SMLAD.sml.com:2467
TIME_WAIT
TCP SMLAD:ldap SMLAD.sml.com:2485
TIME_WAIT
TCP SMLAD:ldap SMLAD.sml.com:2538
TIME_WAIT
TCP SMLAD:ldap SMLAD.sml.com:2539
TIME_WAIT
TCP SMLAD:ldap SMLAD.sml.com:2540
ESTABLISHED
TCP SMLAD:ldap SMLAD.sml.com:4007
ESTABLISHED
TCP SMLAD:ldap dyapp2.sml.com:3401
TIME_WAIT
TCP SMLAD:ldap dyapp6.sml.com:1210
TIME_WAIT
TCP SMLAD:ldap CHIWAIXP:3493
TIME_WAIT
TCP SMLAD:ldap DHKCZOECHAN:4696
TIME_WAIT
TCP SMLAD:ldap 192.168.6.143:2810
ESTABLISHED
TCP SMLAD:ldap 192.168.6.143:2815
ESTABLISHED
TCP SMLAD:ldap sherman_law.sml.com:1957
TIME_WAIT
TCP SMLAD:microsoft-ds DYDC:1082
ESTABLISHED
TCP SMLAD:microsoft-ds dyapp2.sml.com:3413
ESTABLISHED
TCP SMLAD:microsoft-ds DYSUN:3745
ESTABLISHED
TCP SMLAD:microsoft-ds DYSUN:4812
ESTABLISHED
TCP SMLAD:microsoft-ds ISSP2:1633
ESTABLISHED
TCP SMLAD:microsoft-ds SMLSQLW:3915
ESTABLISHED
TCP SMLAD:microsoft-ds chung_lee.sml.com:4783
ESTABLISHED
TCP SMLAD:microsoft-ds demo11.sml.com:4294
ESTABLISHED
TCP SMLAD:microsoft-ds SMLDC:1676
ESTABLISHED
TCP SMLAD:microsoft-ds 192.168.6.143:2816
ESTABLISHED
TCP SMLAD:1025 SMLAOS5:1554
ESTABLISHED
TCP SMLAD:1025 UKTEMP:3252
ESTABLISHED
TCP SMLAD:1025 WPSSQL:1095
ESTABLISHED
TCP SMLAD:1025 DYDC:1757
ESTABLISHED
TCP SMLAD:1025 smlacc.sml.com:1452
ESTABLISHED
TCP SMLAD:1025 SMLAD.sml.com:1470
ESTABLISHED
TCP SMLAD:1025 SMLAD.sml.com:3654
ESTABLISHED
TCP SMLAD:1025 dyapp2.sml.com:1162
ESTABLISHED
TCP SMLAD:1025 dyapp2.sml.com:3236
ESTABLISHED
TCP SMLAD:1025 dyapp2.sml.com:3399
ESTABLISHED
TCP SMLAD:1025 dyapp6.sml.com:1144
ESTABLISHED
TCP SMLAD:1025 DYSUN:4978
ESTABLISHED
TCP SMLAD:1025 dyhelp.sml.com:2257
ESTABLISHED
TCP SMLAD:1025 dyhelp.sml.com:3843
ESTABLISHED
TCP SMLAD:1025 uksql.sml.com:2202
ESTABLISHED
TCP SMLAD:1025 uksql.sml.com:2946
ESTABLISHED
TCP SMLAD:1025 uksql.sml.com:2973
ESTABLISHED
TCP SMLAD:1025 testapp1.sml.com:4105
ESTABLISHED
TCP SMLAD:1025 testapp2.sml.com:1835
ESTABLISHED
TCP SMLAD:1025 smlsql1.sml.com:1280
ESTABLISHED
TCP SMLAD:1025 smlsql2.sml.com:1158
ESTABLISHED
TCP SMLAD:1025 SMLSQLW:1969
ESTABLISHED
TCP SMLAD:1025 smlbackup2.sml.com:2038
ESTABLISHED
TCP SMLAD:1025 192.168.6.44:1828
ESTABLISHED
TCP SMLAD:1025 dhkcmanwu.sml.com:1859
ESTABLISHED
TCP SMLAD:1025 nina_lee.sml_dy:2279
ESTABLISHED
TCP SMLAD:1025 SMLDC2:3165
ESTABLISHED
TCP SMLAD:1025 SML:1072
ESTABLISHED
TCP SMLAD:1025 SML:1117
ESTABLISHED
TCP SMLAD:1025 SML:4874
ESTABLISHED
TCP SMLAD:1025 SML:4916
ESTABLISHED
TCP SMLAD:1025 SML:4975
ESTABLISHED
TCP SMLAD:1025 SMLVN-DC01:1086
ESTABLISHED
TCP SMLAD:1025 SMLVN-DC01:1180
ESTABLISHED
TCP SMLAD:1025 SMLVN-DC01:1646
ESTABLISHED
TCP SMLAD:1025 SMLVN-DC01:1703
ESTABLISHED
TCP SMLAD:1025 SMLVN-DC01:1704
ESTABLISHED
TCP SMLAD:1025 SMLVN-DC01:2098
ESTABLISHED
TCP SMLAD:1025 SMLVN-DC01:2149
ESTABLISHED
TCP SMLAD:1025 SMLVN-DC01:2150
ESTABLISHED
TCP SMLAD:1025 SMLVN-DC01:2617
ESTABLISHED
TCP SMLAD:1025 SMLVN-DC01:2669
ESTABLISHED
TCP SMLAD:1025 SMLVN-DC01:2676
ESTABLISHED
TCP SMLAD:1025 SMLVN-DC01:3039
ESTABLISHED
TCP SMLAD:1025 SMLVN-DC01:3100
ESTABLISHED
TCP SMLAD:1025 SMLVN-DC01:3101
ESTABLISHED
TCP SMLAD:1025 SMLVN-DC01:4118
ESTABLISHED
TCP SMLAD:1025 SMLVN-DC01:4172
ESTABLISHED
TCP SMLAD:1025 SMLVN-DC01:4173
ESTABLISHED
TCP SMLAD:1025 SMLVN-DC01:4605
ESTABLISHED
TCP SMLAD:1025 SMLVN-DC01:4651
ESTABLISHED
TCP SMLAD:1025 dgdc.sml.com:1364
ESTABLISHED
TCP SMLAD:1470 SMLAD.sml.com:1025
ESTABLISHED
TCP SMLAD:1530 FTP:netbios-ssn
ESTABLISHED
TCP SMLAD:1622 SMLAD.sml.com:ldap
CLOSE_WAIT
TCP SMLAD:2203 SMLAD.sml.com:msft-gc
CLOSE_WAIT
TCP SMLAD:2205 SMLAD.sml.com:ldap
CLOSE_WAIT
TCP SMLAD:2307 dytest.sml.com:microsoft-ds
ESTABLISHED
TCP SMLAD:2325 DYDC:1026
ESTABLISHED
TCP SMLAD:2456 SMLAD.sml.com:1025
TIME_WAIT
TCP SMLAD:2465 SMLAD.sml.com:ldap
TIME_WAIT
TCP SMLAD:2468 SMLAD.sml.com:microsoft-ds
TIME_WAIT
TCP SMLAD:2502 DYSUN:epmap
ESTABLISHED
TCP SMLAD:2503 DYSUN:1153
ESTABLISHED
TCP SMLAD:2518 DYDC:epmap
TIME_WAIT
TCP SMLAD:2519 DYDC:1026
ESTABLISHED
TCP SMLAD:2531 SMLAD.sml.com:netbios-ssn
TIME_WAIT
TCP SMLAD:2538 SMLAD.sml.com:ldap
TIME_WAIT
TCP SMLAD:2539 SMLAD.sml.com:ldap
TIME_WAIT
TCP SMLAD:2540 SMLAD.sml.com:ldap
ESTABLISHED
TCP SMLAD:2541 SMLAD.sml.com:ldap
TIME_WAIT
TCP SMLAD:2542 SMLAD.sml.com:epmap
TIME_WAIT
TCP SMLAD:2543 SMLAD.sml.com:1025
TIME_WAIT
TCP SMLAD:2544 dyapp3.sml.com:ldap
TIME_WAIT
TCP SMLAD:2545 SMLAD.sml.com:epmap
TIME_WAIT
TCP SMLAD:2546 SMLAD.sml.com:1025
TIME_WAIT
TCP SMLAD:2558 SMLUS-DC:ldap
TIME_WAIT
TCP SMLAD:2559 SMLUS-DC:ldap
TIME_WAIT
TCP SMLAD:2565 SMLUS-DC:ldap
ESTABLISHED
TCP SMLAD:2566 SMLUS-DC:ldap
FIN_WAIT_1
TCP SMLAD:2568 SMLAD.sml.com:epmap
TIME_WAIT
TCP SMLAD:2569 SMLAD.sml.com:1025
TIME_WAIT
TCP SMLAD:2570 dgdc.sml.com:ldap
TIME_WAIT
TCP SMLAD:2571 SMLAD.sml.com:epmap
TIME_WAIT
TCP SMLAD:2572 SMLAD.sml.com:1025
TIME_WAIT
TCP SMLAD:3004 SMLAD.sml.com:ldap
CLOSE_WAIT
TCP SMLAD:msft-gc 192.168.112.7:2842
TIME_WAIT
TCP SMLAD:ms-wbt-server CHIWAIXP:3471
ESTABLISHED
TCP SMLAD:ms-wbt-server demo11.sml.com:2677
ESTABLISHED
TCP SMLAD:3560 SMLAD.sml.com:ldap
CLOSE_WAIT
TCP SMLAD:3563 SMLAD.sml.com:ldap
CLOSE_WAIT
TCP SMLAD:3565 SMLAD.sml.com:ldap
CLOSE_WAIT
TCP SMLAD:3654 SMLAD.sml.com:1025
ESTABLISHED
TCP SMLAD:3967 DYDC:microsoft-ds
ESTABLISHED
TCP SMLAD:4007 SMLAD.sml.com:ldap
ESTABLISHED
TCP SMLAD:4076 SMLAD.sml.com:ldap
CLOSE_WAIT
TCP SMLAD:5900 demo11.sml.com:2296
ESTABLISHED
UDP SMLAD:snmp *:*
UDP SMLAD:microsoft-ds *:*
UDP SMLAD:isakmp *:*
UDP SMLAD:1029 *:*
UDP SMLAD:1030 *:*
UDP SMLAD:1031 *:*
UDP SMLAD:1032 *:*
UDP SMLAD:1047 *:*
UDP SMLAD:1077 *:*
UDP SMLAD:1317 *:*
UDP SMLAD:1645 *:*
UDP SMLAD:1646 *:*
UDP SMLAD:radius *:*
UDP SMLAD:radacct *:*
UDP SMLAD:1882 *:*
UDP SMLAD:2967 *:*
UDP SMLAD:3254 *:*
UDP SMLAD:ipsec-msft *:*
UDP SMLAD:4571 *:*
UDP SMLAD:domain *:*
UDP SMLAD:ntp *:*
UDP SMLAD:1036 *:*
UDP SMLAD:1042 *:*
UDP SMLAD:1043 *:*
UDP SMLAD:1049 *:*
UDP SMLAD:1061 *:*
UDP SMLAD:1072 *:*
UDP SMLAD:1075 *:*
UDP SMLAD:1092 *:*
UDP SMLAD:1360 *:*
UDP SMLAD:1375 *:*
UDP SMLAD:1523 *:*
UDP SMLAD:1570 *:*
UDP SMLAD:1613 *:*
UDP SMLAD:1881 *:*
UDP SMLAD:1883 *:*
UDP SMLAD:1953 *:*
UDP SMLAD:2188 *:*
UDP SMLAD:2537 *:*
UDP SMLAD:2571 *:*
UDP SMLAD:3003 *:*
UDP SMLAD:3559 *:*
UDP SMLAD:domain *:*
UDP SMLAD:bootps *:*
UDP SMLAD:bootpc *:*
UDP SMLAD:kerberos *:*
UDP SMLAD:ntp *:*
UDP SMLAD:netbios-ns *:*
UDP SMLAD:netbios-dgm *:*
UDP SMLAD:389 *:*
UDP SMLAD:kpasswd *:*
UDP SMLAD:2535 *:*

IP Statistics

Packets Received = 101,288,299
Received Header Errors = 0
Received Address Errors = 109
Datagrams Forwarded = 0
Unknown Protocols Received = 0
Received Packets Discarded = 795
Received Packets Delivered = 101,278,730
Output Requests = 83,300,039
Routing Discards = 0
Discarded Output Packets = 0
Output Packet No Route = 0
Reassembly Required = 17,316
Reassembly Successful = 8,651
Reassembly Failures = 14
Datagrams successfully fragmented = 2,995
Datagrams failing fragmentation = 0
Fragments Created = 5,990
Forwarding = 2
Default TTL = 128
Reassembly timeout = 60

TCP Statistics

Active Opens = 325,689
Passive Opens = 2,480,127
Failed Connection Attempts = 55,000
Reset Connections = 255,275
Current Connections = 111
Received Segments = 64,527,479
Segment Sent = 59,782,021
Segment Retransmitted = 328,684
Retransmission Timeout Algorithm = vanj
Minimum Retransmission Timeout = 300
Maximum Retransmission Timeout = 120,000
Maximum Number of Connections = -1

UDP Statistics

Datagrams Received = 33,680,182
No Ports = 3,545,139
Receive Errors = 7
Datagrams Sent = 21,427,153

ICMP Statistics

Received Sent
Messages 1,926,606 1,926,606
Errors 0 0
Destination Unreachable 1,022,577 1,022,577
Time Exceeded 1,881 1,881
Parameter Problems 0 0
Source Quenchs 7 7
Redirects 59,481 59,481
Echos 670,377 670,377
Echo Replies 172,283 172,283
Timestamps 0 0
Timestamp Replies 0 0
Address Masks 0 0
Address Mask Replies 0 0

Bindings test. . . . . . . . . . . : Passed
Component Name : NDIS Usermode I/O Protocol
Bind Name: Ndisuio
Binding Paths:
Owner of the binding path : NDIS Usermode I/O Protocol
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: NDIS Usermode I/O Protocol
Lower Component: 3Com 3C996 10/100/1000 Server NIC

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: 3Com EtherLink Server 10/100 PCI (3C980C-TXM)

Owner of the binding path : NDIS Usermode I/O Protocol
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: NDIS Usermode I/O Protocol
Lower Component: Intel(R) PRO/100 Network Connection

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: 3Com 3C996 10/100/1000 Server NIC

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: 3Com EtherLink Server 10/100 PCI (3C980C-TXM)

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: Intel(R) PRO/100 Network Connection

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

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

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

Owner of the binding path : Remote Access NDIS WAN Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswan
Upper Component: Remote Access NDIS WAN Driver
Lower Component: WAN Miniport (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)

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

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

Component Name : WINS Client(TCP/IP) Protocol
Bind Name: NetBT
Binding Paths:
Owner of the binding path : WINS Client(TCP/IP) Protocol
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: 3Com 3C996 10/100/1000 Server NIC

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: 3Com EtherLink Server 10/100 PCI (3C980C-TXM)

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

Owner of the binding path : WINS Client(TCP/IP) Protocol
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: 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: 3Com 3C996 10/100/1000 Server NIC

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: 3Com EtherLink Server 10/100 PCI (3C980C-TXM)

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

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: 3Com 3C996 10/100/1000 Server NIC

Owner of the binding path : Client for Microsoft Networks
Binding Enabled: No
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: 3Com EtherLink Server 10/100 PCI (3C980C-TXM)

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

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

pcnetnet · Jun 9, 2008

For Site A netdiag #4

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: 3Com 3C996 10/100/1000 Server NIC

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: 3Com EtherLink Server 10/100 PCI (3C980C-TXM)

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: Intel(R) PRO/100 Network Connection

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: 3Com 3C996 10/100/1000 Server NIC

Owner of the binding path : File and Printer Sharing for Microsoft
Networks
Binding Enabled: No
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: 3Com EtherLink Server 10/100 PCI (3C980C-TXM)

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

Owner of the binding path : File and Printer Sharing for Microsoft
Networks
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: netbios
Upper Component: File and Printer Sharing for Microsoft Networks
Lower Component: WINS Client(TCP/IP) Protocol
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: 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: 3Com 3C996 10/100/1000 Server NIC

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: 3Com EtherLink Server 10/100 PCI (3C980C-TXM)

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

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

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

Component Name : Direct Parallel
Bind Name: {F11442E6-F1A9-4278-A8F8-8969FD2A42EA}
Binding Paths:

Component Name : WAN Miniport (PPPOE)
Bind Name: {39AAD227-D9AC-45B5-9328-A4BF90B9902F}
Binding Paths:

Component Name : WAN Miniport (PPTP)
Bind Name: {5122F1C9-F518-4C23-AE3B-B3E32F7CA00B}
Binding Paths:

Component Name : WAN Miniport (L2TP)
Bind Name: {8FE3E3C0-4E9A-4229-A06B-C0C45C7EED55}
Binding Paths:

Component Name : RAS Async Adapter
Bind Name: {B8C1010D-9AE5-454E-AAE7-F689CE32FD25}
Binding Paths:

Component Name : Intel(R) PRO/100 Network Connection
Bind Name: {7ADE4086-0590-4446-8A30-3BA8F214F296}
Binding Paths:

Component Name : 3Com 3C996 10/100/1000 Server NIC
Bind Name: {7BA3D71A-43A4-4A81-B318-94D0445BE672}
Binding Paths:

Component Name : 3Com EtherLink Server 10/100 PCI (3C980C-TXM)
Bind Name: {54257D51-038A-4C8B-AFB5-054CEFED027B}
Binding Paths:

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

pcnetnet · Jun 9, 2008

For Site A repladmin output

HongKong\SMLAD
DC Options: IS_GC
Site Options: (none)
DC object GUID: 6ad1947f-b693-4166-85fc-d2097457fec6
DC invocationID: 6ad1947f-b693-4166-85fc-d2097457fec6

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

DC=sml,DC=com
DR_Site\DYAPP3 via RPC
DC object GUID: 1a6d2c04-fe41-4950-a501-856db04507c0
Last attempt @ 2008-06-05 14:51:04 was successful.
HongKong\SMLAD2 via RPC
DC object GUID: 798e9d55-ed60-4054-ab63-357fd4201d0d
Last attempt @ 2008-06-05 16:51:25 failed, result 1722 (0x6ba):
The RPC server is unavailable.
29 consecutive failure(s).
Last success @ 2008-06-04 12:07:52.

CN=Configuration,DC=sml,DC=com
Thailand\SMLTHAI via RPC
DC object GUID: fb481c80-3e8a-46e3-ac78-43ed173fa761
Last attempt @ 2008-06-05 14:52:09 was successful.
Vietnam\SMLVN-DC02 via RPC
DC object GUID: 3d057050-a338-40a5-9a2d-3f95953022ab
Last attempt @ 2008-06-05 14:52:10 was successful.
RPDI\MN-FS01 via RPC
DC object GUID: 2b1f1e86-a93a-41a1-b08c-a54a9c550659
Last attempt @ 2008-06-05 14:52:13 was successful.
Vietnam\SMLVN-DC01 via RPC
DC object GUID: e67f6898-595c-447f-b747-93eafb48c741
Last attempt @ 2008-06-05 14:52:14 was successful.
Korea\SML via RPC
DC object GUID: d496eae0-78e1-4fd8-8fc8-64265fb7099c
Last attempt @ 2008-06-05 14:52:16 was successful.
DR_Site\DYAPP3 via RPC
DC object GUID: 1a6d2c04-fe41-4950-a501-856db04507c0
Last attempt @ 2008-06-05 14:52:16 was successful.
HongKong\SMLAD2 via RPC
DC object GUID: 798e9d55-ed60-4054-ab63-357fd4201d0d
Last attempt @ 2008-06-05 16:51:46 failed, result 1722 (0x6ba):
The RPC server is unavailable.
29 consecutive failure(s).
Last success @ 2008-06-04 12:07:02.

CN=Schema,CN=Configuration,DC=sml,DC=com
Thailand\SMLTHAI via RPC
DC object GUID: fb481c80-3e8a-46e3-ac78-43ed173fa761
Last attempt @ 2008-06-05 14:52:16 was successful.
Vietnam\SMLVN-DC02 via RPC
DC object GUID: 3d057050-a338-40a5-9a2d-3f95953022ab
Last attempt @ 2008-06-05 14:52:17 was successful.
RPDI\MN-FS01 via RPC
DC object GUID: 2b1f1e86-a93a-41a1-b08c-a54a9c550659
Last attempt @ 2008-06-05 14:52:17 was successful.
Vietnam\SMLVN-DC01 via RPC
DC object GUID: e67f6898-595c-447f-b747-93eafb48c741
Last attempt @ 2008-06-05 14:52:19 was successful.
Korea\SML via RPC
DC object GUID: d496eae0-78e1-4fd8-8fc8-64265fb7099c
Last attempt @ 2008-06-05 14:52:19 was successful.
DR_Site\DYAPP3 via RPC
DC object GUID: 1a6d2c04-fe41-4950-a501-856db04507c0
Last attempt @ 2008-06-05 14:52:19 was successful.
HongKong\SMLAD2 via RPC
DC object GUID: 798e9d55-ed60-4054-ab63-357fd4201d0d
Last attempt @ 2008-06-05 16:52:07 failed, result 1722 (0x6ba):
The RPC server is unavailable.
29 consecutive failure(s).
Last success @ 2008-06-04 12:07:02.

DC=DomainDnsZones,DC=sml,DC=com
DR_Site\DYAPP3 via RPC
DC object GUID: 1a6d2c04-fe41-4950-a501-856db04507c0
Last attempt @ 2008-06-05 14:52:19 was successful.
HongKong\SMLAD2 via RPC
DC object GUID: 798e9d55-ed60-4054-ab63-357fd4201d0d
Last attempt @ 2008-06-05 16:51:25 failed, result 1256 (0x4e8):
The remote system is not available. For information about
network troubleshooting, see Windows Help.
29 consecutive failure(s).
Last success @ 2008-06-04 12:07:02.

DC=ForestDnsZones,DC=sml,DC=com
Vietnam\SMLVN-DC02 via RPC
DC object GUID: 3d057050-a338-40a5-9a2d-3f95953022ab
Last attempt @ 2008-06-05 14:52:19 was successful.
Thailand\SMLTHAI via RPC
DC object GUID: fb481c80-3e8a-46e3-ac78-43ed173fa761
Last attempt @ 2008-06-05 14:54:14 was successful.
RPDI\MN-FS01 via RPC
DC object GUID: 2b1f1e86-a93a-41a1-b08c-a54a9c550659
Last attempt @ 2008-06-05 14:54:17 was successful.
Vietnam\SMLVN-DC01 via RPC
DC object GUID: e67f6898-595c-447f-b747-93eafb48c741
Last attempt @ 2008-06-05 14:54:21 was successful.
Korea\SML via RPC
DC object GUID: d496eae0-78e1-4fd8-8fc8-64265fb7099c
Last attempt @ 2008-06-05 14:54:23 was successful.
DR_Site\DYAPP3 via RPC
DC object GUID: 1a6d2c04-fe41-4950-a501-856db04507c0
Last attempt @ 2008-06-05 14:54:23 was successful.
HongKong\SMLAD2 via RPC
DC object GUID: 798e9d55-ed60-4054-ab63-357fd4201d0d
Last attempt @ 2008-06-05 16:51:25 failed, result 1256 (0x4e8):
The remote system is not available. For information about
network troubleshooting, see Windows Help.
29 consecutive failure(s).
Last success @ 2008-06-04 12:07:02.

DC=thai,DC=sml,DC=com
Thailand\SMLTHAI via RPC
DC object GUID: fb481c80-3e8a-46e3-ac78-43ed173fa761
Last attempt @ 2008-06-05 14:54:24 was successful.
RPDI\MN-FS01 via RPC
DC object GUID: 2b1f1e86-a93a-41a1-b08c-a54a9c550659
Last attempt @ 2008-06-05 14:54:24 was successful.
Vietnam\SMLVN-DC01 via RPC
DC object GUID: e67f6898-595c-447f-b747-93eafb48c741
Last attempt @ 2008-06-05 14:54:24 was successful.
Korea\SML via RPC
DC object GUID: d496eae0-78e1-4fd8-8fc8-64265fb7099c
Last attempt @ 2008-06-05 14:54:25 was successful.

DC=korea,DC=sml,DC=com
Thailand\SMLTHAI via RPC
DC object GUID: fb481c80-3e8a-46e3-ac78-43ed173fa761
Last attempt @ 2008-06-05 14:54:25 was successful.
RPDI\MN-FS01 via RPC
DC object GUID: 2b1f1e86-a93a-41a1-b08c-a54a9c550659
Last attempt @ 2008-06-05 14:54:25 was successful.
Vietnam\SMLVN-DC01 via RPC
DC object GUID: e67f6898-595c-447f-b747-93eafb48c741
Last attempt @ 2008-06-05 14:54:25 was successful.
Korea\SML via RPC
DC object GUID: d496eae0-78e1-4fd8-8fc8-64265fb7099c
Last attempt @ 2008-06-05 14:54:26 was successful.

DC=rpdi,DC=sml,DC=com
Thailand\SMLTHAI via RPC
DC object GUID: fb481c80-3e8a-46e3-ac78-43ed173fa761
Last attempt @ 2008-06-05 14:54:26 was successful.
RPDI\MN-FS01 via RPC
DC object GUID: 2b1f1e86-a93a-41a1-b08c-a54a9c550659
Last attempt @ 2008-06-05 14:54:26 was successful.
Vietnam\SMLVN-DC01 via RPC
DC object GUID: e67f6898-595c-447f-b747-93eafb48c741
Last attempt @ 2008-06-05 14:54:27 was successful.
Korea\SML via RPC
DC object GUID: d496eae0-78e1-4fd8-8fc8-64265fb7099c
Last attempt @ 2008-06-05 14:54:27 was successful.

DC=vietnam,DC=sml,DC=com
Vietnam\SMLVN-DC02 via RPC
DC object GUID: 3d057050-a338-40a5-9a2d-3f95953022ab
Last attempt @ 2008-06-05 14:54:31 was successful.
Thailand\SMLTHAI via RPC
DC object GUID: fb481c80-3e8a-46e3-ac78-43ed173fa761
Last attempt @ 2008-06-05 14:54:31 was successful.
RPDI\MN-FS01 via RPC
DC object GUID: 2b1f1e86-a93a-41a1-b08c-a54a9c550659
Last attempt @ 2008-06-05 14:54:31 was successful.
Vietnam\SMLVN-DC01 via RPC
DC object GUID: e67f6898-595c-447f-b747-93eafb48c741
Last attempt @ 2008-06-05 14:54:32 was successful.
Korea\SML via RPC
DC object GUID: d496eae0-78e1-4fd8-8fc8-64265fb7099c
Last attempt @ 2008-06-05 14:54:32 was successful.

DC=china-dg,DC=sml,DC=com
Thailand\SMLTHAI via RPC
DC object GUID: fb481c80-3e8a-46e3-ac78-43ed173fa761
Last attempt @ 2008-06-05 14:54:32 was successful.
RPDI\MN-FS01 via RPC
DC object GUID: 2b1f1e86-a93a-41a1-b08c-a54a9c550659
Last attempt @ 2008-06-05 14:54:32 was successful.
Vietnam\SMLVN-DC01 via RPC
DC object GUID: e67f6898-595c-447f-b747-93eafb48c741
Last attempt @ 2008-06-05 14:54:33 was successful.
Korea\SML via RPC
DC object GUID: d496eae0-78e1-4fd8-8fc8-64265fb7099c
Last attempt @ 2008-06-05 14:54:33 was successful.

Source: HongKong\SMLAD2
******* 29 CONSECUTIVE FAILURES since 2008-06-04 12:07:52
Last error: 1256 (0x4e8):
The remote system is not available. For information about
network troubleshooting, see Windows Help.

pcnetnet · Jun 9, 2008

For Site B netdiag #1

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
'127.0.0.1' and other DCs also have some of the names registered.
Testing redirector and browser... Passed
Testing DC discovery.
Looking for a DC
Looking for a PDC emulator
Looking for an Active Directory DC
Gathering the list of Domain Controllers for domain 'SML'
Testing trust relationships... Passed
Testing Kerberos authentication... Passed
Testing LDAP servers in Domain SML ...
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: DYAPP3
DNS Host Name: dyapp3.sml.com
DNS Domain Name: sml.com
System info : Microsoft Windows Server 2003 R2 (Build 3790)
Processor : x86 Family 15 Model 2 Stepping 9, GenuineIntel
Hotfixes :
Installed? Name
Yes KB921503
Yes KB924667-v2
Yes KB925398_WMP64
Yes KB925902
Yes KB926122
Yes KB927891
Yes KB929123
Yes KB930178
Yes KB931784
Yes KB932168
Yes KB933360
Yes KB933729
Yes KB933854
Yes KB935839
Yes KB935840
Yes KB935966
Yes KB936021
Yes KB936357
Yes KB936782
Yes KB938127
Yes KB938127-IE7
Yes KB939653
Yes KB939653-IE7
Yes KB941202
Yes KB941568
Yes KB941569
Yes KB941644
Yes KB941672
Yes KB941693
Yes KB942615-IE7
Yes KB942763
Yes KB943055
Yes KB943460
Yes KB943484
Yes KB943485
Yes KB944533-IE7
Yes KB944653
Yes KB945553
Yes KB946026
Yes KB947864-IE7
Yes KB948496
Yes KB948590
Yes KB948881
Yes Q147222
No ServicePackUninstall

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

Information of Netcard drivers:

---------------------------------------------------------------------------
Description: Broadcom NetXtreme Gigabit Ethernet
Device: \DEVICE\{885EF630-203E-4055-B650-65AF69E8CF3E}

Media State: Connected

Device State: Connected
Connect Time: 56 days, 07:07:47
Media Speed: 1 Gbps

Packets Sent: 5014818
Bytes Sent (Optional): 0

Packets Received: 8418510
Directed Pkts Recd (Optional): 6133994
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 . . . . . . . . : {885EF630-203E-4055-B650-65AF69E8CF3E}

Netcard queries test . . . : Passed

Adapter type . . . . . . . : Ethernet
Host Name. . . . . . . . . : dyapp3
Description. . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address . . . . . : 00-0F-1F-67-EC-42
Dhcp Enabled . . . . . . . : No
DHCP ClassID . . . . . . . :
Autoconfiguration Enabled. : Yes
IP Address . . . . . . . . : 192.168.8.70
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 192.168.8.4
Dns Servers. . . . . . . . : 127.0.0.1

IpConfig results . . . . . : Passed

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

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

NetBT name test. . . . . . : Passed
NetBT_Tcpip_{885EF630-203E-4055-B650-65AF69E8CF3E}
DYAPP3 <00> UNIQUE REGISTERED
SML <00> GROUP REGISTERED
SML <1C> GROUP REGISTERED
DYAPP3 <20> UNIQUE REGISTERED
SML <1E> GROUP REGISTERED
SML <1D> UNIQUE REGISTERED
..__MSBROWSE__.<01> GROUP REGISTERED
[WARNING] At least one of the <00> 'WorkStation Service', <03>
'Messenger Service', <20> 'WINS' names is missing.

NetBios Resolution : via DHCP

Netbios Remote Cache Table
Name Type HostAddress Life [sec]
---------------------------------------------------------------
192.168.0.134 <20> UNIQUE 192.168.0.134 562

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. . . . . . . . . . . : Broadcast
NBT Scope ID . . . . . . . . . :
Routing Enabled. . . . . . . . : No
WINS Proxy Enabled . . . . . . : No
DNS resolution for NETBIOS . . : No

Domain membership test . . . . . . : Passed
Machine is a . . . . . . . . . : Domain Controller
Netbios Domain name. . . . . . : SML
Dns domain name. . . . . . . . : sml.com
Dns forest name. . . . . . . . : sml.com
Domain Guid. . . . . . . . . . : {BAC13477-EC37-4340-941F-7A21AE77D0CB}
Domain Sid . . . . . . . . . . : S-1-5-21-2444645589-256595936-971879393
Logon User . . . . . . . . . . : administrator
Logon Domain . . . . . . . . . : SML

NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{885EF630-203E-4055-B650-65AF69E8CF3E}
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
[WARNING] You don't have a single interface with the <00> 'WorkStation
Service', <03> 'Messenger Service', <20> 'WINS' names defined.

Winsock test . . . . . . . . . . . : Passed
The number of protocols which have been reported : 12
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_{885EF630-203E-4055-B650-65AF69E8CF3E}] SEQPACKET 0
Provider Version :2
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{885EF630-203E-4055-B650-65AF69E8CF3E}] DATAGRAM 0
Provider Version :2
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{14920296-4028-43BD-91DA-F8E82F50A10B}] SEQPACKET 1
Provider Version :2
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{14920296-4028-43BD-91DA-F8E82F50A10B}] DATAGRAM 1
Provider Version :2
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{9B479EE7-3079-4A03-B171-752B6762BCAA}] SEQPACKET 2
Provider Version :2
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{9B479EE7-3079-4A03-B171-752B6762BCAA}] DATAGRAM 2
Provider Version :2
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{829F7413-3232-4F43-94E1-B885D40272E8}] SEQPACKET 3
Provider Version :2
Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{829F7413-3232-4F43-94E1-B885D40272E8}] DATAGRAM 3
Provider Version :2

Max UDP size : 65507 bytes

DNS test . . . . . . . . . . . . . : Passed
Interface {885EF630-203E-4055-B650-65AF69E8CF3E}
DNS Domain:
DNS Servers: 127.0.0.1
IP Address: Expected registration with PDN (primary DNS
domain name):
Hostname: dyapp3.sml.com.
Authoritative zone: sml.com.
Primary DNS server: dyapp3.sml.com 192.168.8.70
Authoritative NS:192.168.100.20 192.168.0.58 192.168.8.70
192.168.0.55 192.168.36.250
Check the DNS registration for DCs entries on DNS server '127.0.0.1'
The Record is different on DNS server '127.0.0.1'.
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 '127.0.0.1', no need to
re-register.

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

The record on DNS server 127.0.0.1 is:
DNS NAME = sml.com
DNS DATA =
A 192.168.0.58
A 192.168.8.70
A 192.168.100.20
A 192.168.36.250
A 192.168.0.55
+------------------------------------------------------+

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

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

The record on DNS server 127.0.0.1 is:
DNS NAME = _ldap._tcp.sml.com
DNS DATA =
SRV 0 100 389 dgdc.sml.com
SRV 0 100 389 smlad.sml.com
SRV 0 100 389 smlus-dc.sml.com
SRV 0 100 389 dyapp3.sml.com
SRV 0 100 389 smlad2.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME =
_ldap._tcp.bac13477-ec37-4340-941f-7a21ae77d0cb.domains._msdcs.sml.com.
DNS DATA =
SRV 0 100 389 dyapp3.sml.com.

The record on DNS server 127.0.0.1 is:
DNS NAME =
_ldap._tcp.bac13477-ec37-4340-941f-7a21ae77d0cb.domains._msdcs.sml.com
DNS DATA =
SRV 0 100 389 dgdc.sml.com
SRV 0 100 389 smlad2.sml.com
SRV 0 100 389 dyapp3.sml.com
SRV 0 100 389 smlad.sml.com
SRV 0 100 389 smlus-dc.sml.com
+------------------------------------------------------+

The Record is correct on DNS server '127.0.0.1'.

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

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

The record on DNS server 127.0.0.1 is:
DNS NAME = _kerberos._tcp.dc._msdcs.sml.com
DNS DATA =
SRV 0 100 88 dgdc.sml.com
SRV 0 100 88 smlad.sml.com
SRV 0 100 88 smlus-dc.sml.com
SRV 0 100 88 dyapp3.sml.com
SRV 0 100 88 smlad2.sml.com
+------------------------------------------------------+

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

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

The record on DNS server 127.0.0.1 is:
DNS NAME = _ldap._tcp.dc._msdcs.sml.com
DNS DATA =
SRV 0 100 389 dyapp3.sml.com
SRV 0 100 389 smlad.sml.com
SRV 0 100 389 dgdc.sml.com
SRV 0 100 389 smlad2.sml.com
SRV 0 100 389 smlus-dc.sml.com
+------------------------------------------------------+

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

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

The record on DNS server 127.0.0.1 is:
DNS NAME = _kerberos._tcp.sml.com
DNS DATA =
SRV 0 100 88 dgdc.sml.com
SRV 0 100 88 smlad2.sml.com
SRV 0 100 88 smlad.sml.com
SRV 0 100 88 dyapp3.sml.com
SRV 0 100 88 smlus-dc.sml.com
+------------------------------------------------------+

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

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

The record on DNS server 127.0.0.1 is:
DNS NAME = _kerberos._udp.sml.com
DNS DATA =
SRV 0 100 88 dgdc.sml.com
SRV 0 100 88 smlad2.sml.com
SRV 0 100 88 smlad.sml.com
SRV 0 100 88 dyapp3.sml.com
SRV 0 100 88 smlus-dc.sml.com
+------------------------------------------------------+

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

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

The record on DNS server 127.0.0.1 is:
DNS NAME = _kpasswd._tcp.sml.com
DNS DATA =
SRV 0 100 464 dgdc.sml.com
SRV 0 100 464 smlad2.sml.com
SRV 0 100 464 smlad.sml.com
SRV 0 100 464 dyapp3.sml.com
SRV 0 100 464 smlus-dc.sml.com
+------------------------------------------------------+

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

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

The record on DNS server 127.0.0.1 is:
DNS NAME = _kpasswd._udp.sml.com
DNS DATA =
SRV 0 100 464 dgdc.sml.com
SRV 0 100 464 smlad2.sml.com
SRV 0 100 464 smlad.sml.com
SRV 0 100 464 dyapp3.sml.com
SRV 0 100 464 smlus-dc.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = ForestDnsZones.sml.com.
DNS DATA =
A 192.168.8.70

The record on DNS server 127.0.0.1 is:
DNS NAME = ForestDnsZones.sml.com
DNS DATA =
A 192.168.100.20
A 192.168.0.55
A 192.168.11.2
A 192.168.16.2
A 5.73.235.93
A 192.168.20.10
A 192.168.19.10
A 192.168.8.70
A 192.168.36.250
A 192.168.0.58
A 192.168.34.10
+------------------------------------------------------+

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

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

The record on DNS server 127.0.0.1 is:
DNS NAME = _ldap._tcp.ForestDnsZones.sml.com
DNS DATA =
SRV 0 100 389 dgdc.sml.com
SRV 0 100 389 mn-fs01.rpdi.sml.com
SRV 0 100 389 smlthai.thai.sml.com
SRV 0 100 389 smlad.sml.com
SRV 0 100 389 sml.korea.sml.com
SRV 0 100 389 dyapp3.sml.com
SRV 0 100 389 smlvn-dc01.vietnam.sml.com
SRV 0 100 389 smlus-dc.sml.com
SRV 0 100 389 smlad2.sml.com
SRV 0 100 389 smlvn-dc02.vietnam.sml.com
+------------------------------------------------------+

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

+------------------------------------------------------+
The record on your DC is:
DNS NAME = DomainDnsZones.sml.com.
DNS DATA =
A 192.168.8.70

The record on DNS server 127.0.0.1 is:
DNS NAME = DomainDnsZones.sml.com
DNS DATA =
A 192.168.100.20
A 192.168.0.58
A 192.168.36.250
A 192.168.0.55
A 192.168.8.70
+------------------------------------------------------+

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

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

The record on DNS server 127.0.0.1 is:
DNS NAME = _ldap._tcp.DomainDnsZones.sml.com
DNS DATA =
SRV 0 100 389 dgdc.sml.com
SRV 0 100 389 smlus-dc.sml.com
SRV 0 100 389 smlad.sml.com
SRV 0 100 389 dyapp3.sml.com
SRV 0 100 389 smlad2.sml.com
+------------------------------------------------------+

The Record is correct on DNS server '127.0.0.1'.

The Record is correct on DNS server '127.0.0.1'.

The Record is correct on DNS server '127.0.0.1'.

The Record is correct on DNS server '127.0.0.1'.

The Record is correct on DNS server '127.0.0.1'.

The Record is correct on DNS server '127.0.0.1'.

PASS - All the DNS entries for DC are registered on DNS server
'127.0.0.1' 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_{885EF630-203E-4055-B650-65AF69E8CF3E}
The redir is bound to 1 NetBt transport.

List of transports currently bound to the browser
NetBT_Tcpip_{885EF630-203E-4055-B650-65AF69E8CF3E}
The browser is bound to 1 NetBt transport.
Mailslot test for SML* passed.

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

Find DC in domain 'SML':
Found this DC in domain 'SML':
DC. . . . . . . . . . . : \\dyapp3.sml.com
Address . . . . . . . . : \\192.168.8.70
Domain Guid . . . . . . : {BAC13477-EC37-4340-941F-7A21AE77D0CB}
Domain Name . . . . . . : sml.com
Forest Name . . . . . . : sml.com
DC Site Name. . . . . . : DR_Site
Our Site Name . . . . . : DR_Site
Flags . . . . . . . . . : DS KDC TIMESERV WRITABLE DNS_DC DNS_DOMAIN
DNS_FOREST CLOSE_SITE 0x8

Find PDC emulator in domain 'SML':
Found this PDC emulator in domain 'SML':
DC. . . . . . . . . . . : \\SMLAD.sml.com
Address . . . . . . . . : \\192.168.0.55
Domain Guid . . . . . . : {BAC13477-EC37-4340-941F-7A21AE77D0CB}
Domain Name . . . . . . : sml.com
Forest Name . . . . . . : sml.com
DC Site Name. . . . . . : HongKong
Our Site Name . . . . . : DR_Site
Flags . . . . . . . . . : PDC emulator GC DS KDC TIMESERV GTIMESERV
WRITABLE DNS_DC DNS_DOMAIN DNS_FOREST 0x8

Find Active Directory DC in domain 'SML':
Found this Active Directory DC in domain 'SML':
DC. . . . . . . . . . . : \\dyapp3.sml.com
Address . . . . . . . . : \\192.168.8.70
Domain Guid . . . . . . : {BAC13477-EC37-4340-941F-7A21AE77D0CB}
Domain Name . . . . . . : sml.com
Forest Name . . . . . . : sml.com
DC Site Name. . . . . . : DR_Site
Our Site Name . . . . . : DR_Site
Flags . . . . . . . . . : DS KDC TIMESERV WRITABLE DNS_DC DNS_DOMAIN
DNS_FOREST CLOSE_SITE 0x8

DC list test . . . . . . . . . . . : Passed
List of DCs in Domain 'SML':
dyapp3.sml.com
SMLAD.sml.com (this DC is down)
smlad2.sml.com (this DC is down)
[WARNING] Cannot ping 'smlad2.sml.com' (it may be down).

SMLUS-DC.sml.com
dgdc.sml.com

Trust relationship test. . . . . . : Passed
Test to ensure DomainSid of domain 'SML' is correct.
Secure channel for domain 'SML' is to '\\SMLAD.sml.com'.
Secure channel for domain 'SML' was successfully set to PDC emulator
'\\SMLAD.sml.com'.

Kerberos test. . . . . . . . . . . : Passed
Cached Tickets:

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

Do un-authenticated LDAP call to 'dyapp3.sml.com'.
Found 1 entries:
Attr: currentTime
Val: 17 20080605094036.0Z
Attr: subschemaSubentry
Val: 53 CN=Aggregate,CN=Schema,CN=Configuration,DC=sml,DC=com
Attr: dsServiceName
Val: 88 CN=NTDS
Settings,CN=DYAPP3,CN=Servers,CN=DR_Site,CN=Sites,CN=Configuration,DC=sml,DC=com
Attr: namingContexts
Val: 13 DC=sml,DC=com
Val: 30 CN=Configuration,DC=sml,DC=com
Val: 40 CN=Schema,CN=Configuration,DC=sml,DC=com
Val: 31 DC=DomainDnsZones,DC=sml,DC=com
Val: 31 DC=ForestDnsZones,DC=sml,DC=com
Attr: defaultNamingContext
Val: 13 DC=sml,DC=com
Attr: schemaNamingContext
Val: 40 CN=Schema,CN=Configuration,DC=sml,DC=com
Attr: configurationNamingContext
Val: 30 CN=Configuration,DC=sml,DC=com
Attr: rootDomainNamingContext
Val: 13 DC=sml,DC=com
Attr: supportedControl
Val: 22 1.2.840.113556.1.4.319
Val: 22 1.2.840.113556.1.4.801
Val: 22 1.2.840.113556.1.4.473
Val: 22 1.2.840.113556.1.4.528
Val: 22 1.2.840.113556.1.4.417
Val: 22 1.2.840.113556.1.4.619
Val: 22 1.2.840.113556.1.4.841
Val: 22 1.2.840.113556.1.4.529
Val: 22 1.2.840.113556.1.4.805
Val: 22 1.2.840.113556.1.4.521
Val: 22 1.2.840.113556.1.4.970
Val: 23 1.2.840.113556.1.4.1338
Val: 22 1.2.840.113556.1.4.474
Val: 23 1.2.840.113556.1.4.1339
Val: 23 1.2.840.113556.1.4.1340
Val: 23 1.2.840.113556.1.4.1413
Val: 23 2.16.840.1.113730.3.4.9
Val: 24 2.16.840.1.113730.3.4.10
Val: 23 1.2.840.113556.1.4.1504
Val: 23 1.2.840.113556.1.4.1852
Val: 22 1.2.840.113556.1.4.802
Val: 23 1.2.840.113556.1.4.1907
Val: 23 1.2.840.113556.1.4.1948
Attr: supportedLDAPVersion
Val: 1 3
Val: 1 2
Attr: supportedLDAPPolicies
Val: 14 MaxPoolThreads
Val: 15 MaxDatagramRecv
Val: 16 MaxReceiveBuffer
Val: 15 InitRecvTimeout
Val: 14 MaxConnections
Val: 15 MaxConnIdleTime
Val: 11 MaxPageSize
Val: 16 MaxQueryDuration
Val: 16 MaxTempTableSize
Val: 16 MaxResultSetSize
Val: 22 MaxNotificationPerConn
Val: 11 MaxValRange
Attr: highestCommittedUSN
Val: 6 579190
Attr: supportedSASLMechanisms
Val: 6 GSSAPI
Val: 10 GSS-SPNEGO
Val: 8 EXTERNAL
Val: 10 DIGEST-MD5
Attr: dnsHostName
Val: 14 dyapp3.sml.com
Attr: ldapServiceName
Val: 23 sml.com:[email protected]
Attr: serverName
Val: 71
CN=DYAPP3,CN=Servers,CN=DR_Site,CN=Sites,CN=Configuration,DC=sml,DC=com
Attr: supportedCapabilities
Val: 22 1.2.840.113556.1.4.800
Val: 23 1.2.840.113556.1.4.1670
Val: 23 1.2.840.113556.1.4.1791
Attr: isSynchronized
Val: 4 TRUE
Attr: isGlobalCatalogReady
Val: 5 FALSE
Attr: domainFunctionality
Val: 1 2
Attr: forestFunctionality
Val: 1 2
Attr: domainControllerFunctionality
Val: 1 2

Do NTLM authenticated LDAP call to 'dyapp3.sml.com'.
Found 1 entries:
Attr: currentTime
Val: 17 20080605094036.0Z
Attr: subschemaSubentry
Val: 53 CN=Aggregate,CN=Schema,CN=Configuration,DC=sml,DC=com
Attr: dsServiceName
Val: 88 CN=NTDS
Settings,CN=DYAPP3,CN=Servers,CN=DR_Site,CN=Sites,CN=Configuration,DC=sml,DC=com
Attr: namingContexts
Val: 13 DC=sml,DC=com
Val: 30 CN=Configuration,DC=sml,DC=com
Val: 40 CN=Schema,CN=Configuration,DC=sml,DC=com
Val: 31 DC=DomainDnsZones,DC=sml,DC=com
Val: 31 DC=ForestDnsZones,DC=sml,DC=com
Attr: defaultNamingContext
Val: 13 DC=sml,DC=com
Attr: schemaNamingContext
Val: 40 CN=Schema,CN=Configuration,DC=sml,DC=com
Attr: configurationNamingContext
Val: 30 CN=Configuration,DC=sml,DC=com
Attr: rootDomainNamingContext
Val: 13 DC=sml,DC=com
Attr: supportedControl
Val: 22 1.2.840.113556.1.4.319
Val: 22 1.2.840.113556.1.4.801
Val: 22 1.2.840.113556.1.4.473
Val: 22 1.2.840.113556.1.4.528
Val: 22 1.2.840.113556.1.4.417
Val: 22 1.2.840.113556.1.4.619
Val: 22 1.2.840.113556.1.4.841
Val: 22 1.2.840.113556.1.4.529
Val: 22 1.2.840.113556.1.4.805
Val: 22 1.2.840.113556.1.4.521
Val: 22 1.2.840.113556.1.4.970
Val: 23 1.2.840.113556.1.4.1338
Val: 22 1.2.840.113556.1.4.474
Val: 23 1.2.840.113556.1.4.1339
Val: 23 1.2.840.113556.1.4.1340
Val: 23 1.2.840.113556.1.4.1413
Val: 23 2.16.840.1.113730.3.4.9
Val: 24 2.16.840.1.113730.3.4.10
Val: 23 1.2.840.113556.1.4.1504
Val: 23 1.2.840.113556.1.4.1852
Val: 22 1.2.840.113556.1.4.802
Val: 23 1.2.840.113556.1.4.1907
Val: 23 1.2.840.113556.1.4.1948
Attr: supportedLDAPVersion
Val: 1 3
Val: 1 2
Attr: supportedLDAPPolicies
Val: 14 MaxPoolThreads
Val: 15 MaxDatagramRecv
Val: 16 MaxReceiveBuffer
Val: 15 InitRecvTimeout
Val: 14 MaxConnections
Val: 15 MaxConnIdleTime
Val: 11 MaxPageSize
Val: 16 MaxQueryDuration
Val: 16 MaxTempTableSize
Val: 16 MaxResultSetSize
Val: 22 MaxNotificationPerConn
Val: 11 MaxValRange
Attr: highestCommittedUSN
Val: 6 579190
Attr: supportedSASLMechanisms
Val: 6 GSSAPI
Val: 10 GSS-SPNEGO
Val: 8 EXTERNAL
Val: 10 DIGEST-MD5
Attr: dnsHostName
Val: 14 dyapp3.sml.com
Attr: ldapServiceName
Val: 23 sml.com:[email protected]
Attr: serverName
Val: 71
CN=DYAPP3,CN=Servers,CN=DR_Site,CN=Sites,CN=Configuration,DC=sml,DC=com
Attr: supportedCapabilities
Val: 22 1.2.840.113556.1.4.800
Val: 23 1.2.840.113556.1.4.1670
Val: 23 1.2.840.113556.1.4.1791
Attr: isSynchronized
Val: 4 TRUE
Attr: isGlobalCatalogReady
Val: 5 FALSE
Attr: domainFunctionality
Val: 1 2
Attr: forestFunctionality
Val: 1 2
Attr: domainControllerFunctionality
Val: 1 2

Do Negotiate authenticated LDAP call to 'dyapp3.sml.com'.
Found 1 entries:
Attr: currentTime
Val: 17 20080605094036.0Z
Attr: subschemaSubentry
Val: 53 CN=Aggregate,CN=Schema,CN=Configuration,DC=sml,DC=com
Attr: dsServiceName
Val: 88 CN=NTDS
Settings,CN=DYAPP3,CN=Servers,CN=DR_Site,CN=Sites,CN=Configuration,DC=sml,DC=com
Attr: namingContexts
Val: 13 DC=sml,DC=com
Val: 30 CN=Configuration,DC=sml,DC=com
Val: 40 CN=Schema,CN=Configuration,DC=sml,DC=com
Val: 31 DC=DomainDnsZones,DC=sml,DC=com
Val: 31 DC=ForestDnsZones,DC=sml,DC=com
Attr: defaultNamingContext
Val: 13 DC=sml,DC=com
Attr: schemaNamingContext
Val: 40 CN=Schema,CN=Configuration,DC=sml,DC=com
Attr: configurationNamingContext
Val: 30 CN=Configuration,DC=sml,DC=com
Attr: rootDomainNamingContext
Val: 13 DC=sml,DC=com
Attr: supportedControl
Val: 22 1.2.840.113556.1.4.319
Val: 22 1.2.840.113556.1.4.801
Val: 22 1.2.840.113556.1.4.473
Val: 22 1.2.840.113556.1.4.528
Val: 22 1.2.840.113556.1.4.417
Val: 22 1.2.840.113556.1.4.619
Val: 22 1.2.840.113556.1.4.841
Val: 22 1.2.840.113556.1.4.529
Val: 22 1.2.840.113556.1.4.805
Val: 22 1.2.840.113556.1.4.521
Val: 22 1.2.840.113556.1.4.970
Val: 23 1.2.840.113556.1.4.1338
Val: 22 1.2.840.113556.1.4.474
Val: 23 1.2.840.113556.1.4.1339
Val: 23 1.2.840.113556.1.4.1340
Val: 23 1.2.840.113556.1.4.1413
Val: 23 2.16.840.1.113730.3.4.9
Val: 24 2.16.840.1.113730.3.4.10
Val: 23 1.2.840.113556.1.4.1504
Val: 23 1.2.840.113556.1.4.1852
Val: 22 1.2.840.113556.1.4.802
Val: 23 1.2.840.113556.1.4.1907
Val: 23 1.2.840.113556.1.4.1948
Attr: supportedLDAPVersion
Val: 1 3
Val: 1 2
Attr: supportedLDAPPolicies
Val: 14 MaxPoolThreads
Val: 15 MaxDatagramRecv
Val: 16 MaxReceiveBuffer
Val: 15 InitRecvTimeout
Val: 14 MaxConnections
Val: 15 MaxConnIdleTime
Val: 11 MaxPageSize
Val: 16 MaxQueryDuration
Val: 16 MaxTempTableSize
Val: 16 MaxResultSetSize
Val: 22 MaxNotificationPerConn
Val: 11 MaxValRange
Attr: highestCommittedUSN
Val: 6 579190
Attr: supportedSASLMechanisms
Val: 6 GSSAPI
Val: 10 GSS-SPNEGO
Val: 8 EXTERNAL
Val: 10 DIGEST-MD5
Attr: dnsHostName
Val: 14 dyapp3.sml.com
Attr: ldapServiceName
Val: 23 sml.com:[email protected]
Attr: serverName
Val: 71
CN=DYAPP3,CN=Servers,CN=DR_Site,CN=Sites,CN=Configuration,DC=sml,DC=com
Attr: supportedCapabilities
Val: 22 1.2.840.113556.1.4.800
Val: 23 1.2.840.113556.1.4.1670
Val: 23 1.2.840.113556.1.4.1791
Attr: isSynchronized
Val: 4 TRUE
Attr: isGlobalCatalogReady
Val: 5 FALSE
Attr: domainFunctionality
Val: 1 2
Attr: forestFunctionality
Val: 1 2
Attr: domainControllerFunctionality
Val: 1 2

Registered Service Principal Names:
ldap/dyapp3.sml.com/DomainDnsZones.sml.com
ldap/dyapp3.sml.com/ForestDnsZones.sml.com
NtFrs-88f5d2bd-b646-11d2-a6d3-00c04fc9b232/dyapp3.sml.com
DNS/dyapp3.sml.com
GC/dyapp3.sml.com/sml.com
HOST/dyapp3.sml.com/sml.com
HOST/dyapp3.sml.com/SML
ldap/1a6d2c04-fe41-4950-a501-856db04507c0._msdcs.sml.com
ldap/dyapp3.sml.com/SML
ldap/DYAPP3
ldap/dyapp3.sml.com
ldap/dyapp3.sml.com/sml.com
E3514235-4B06-11D1-AB04-00C04FC2DCD2/1a6d2c04-fe41-4950-a501-856db04507c0/sml.com
HOST/DYAPP3
HOST/dyapp3.sml.com
Since 'SMLAD.sml.com' is down, it cannot be tested.
[WARNING] Failed to query SPN registration on DC 'SMLAD.sml.com'.
Since 'smlad2.sml.com' is down, it cannot be tested.
[WARNING] Failed to query SPN registration on DC 'smlad2.sml.com'.

Do un-authenticated LDAP call to 'SMLUS-DC.sml.com'.
Found 1 entries:
Attr: currentTime
Val: 17 20080605094057.0Z
Attr: subschemaSubentry
Val: 53 CN=Aggregate,CN=Schema,CN=Configuration,DC=sml,DC=com
Attr: dsServiceName
Val: 85 CN=NTDS
Settings,CN=SMLUS-DC,CN=Servers,CN=US,CN=Sites,CN=Configuration,DC=sml,DC=com
Attr: namingContexts
Val: 13 DC=sml,DC=com
Val: 30 CN=Configuration,DC=sml,DC=com
Val: 40 CN=Schema,CN=Configuration,DC=sml,DC=com
Val: 31 DC=DomainDnsZones,DC=sml,DC=com
Val: 31 DC=ForestDnsZones,DC=sml,DC=com
Attr: defaultNamingContext
Val: 13 DC=sml,DC=com
Attr: schemaNamingContext
Val: 40 CN=Schema,CN=Configuration,DC=sml,DC=com
Attr: configurationNamingContext
Val: 30 CN=Configuration,DC=sml,DC=com
Attr: rootDomainNamingContext
Val: 13 DC=sml,DC=com
Attr: supportedControl
Val: 22 1.2.840.113556.1.4.319
Val: 22 1.2.840.113556.1.4.801
Val: 22 1.2.840.113556.1.4.473
Val: 22 1.2.840.113556.1.4.528
Val: 22 1.2.840.113556.1.4.417
Val: 22 1.2.840.113556.1.4.619
Val: 22 1.2.840.113556.1.4.841
Val: 22 1.2.840.113556.1.4.529
Val: 22 1.2.840.113556.1.4.805
Val: 22 1.2.840.113556.1.4.521
Val: 22 1.2.840.113556.1.4.970
Val: 23 1.2.840.113556.1.4.1338
Val: 22 1.2.840.113556.1.4.474
Val: 23 1.2.840.113556.1.4.1339
Val: 23 1.2.840.113556.1.4.1340
Val: 23 1.2.840.113556.1.4.1413
Val: 23 2.16.840.1.113730.3.4.9
Val: 24 2.16.840.1.113730.3.4.10
Val: 23 1.2.840.113556.1.4.1504
Val: 23 1.2.840.113556.1.4.1852
Val: 22 1.2.840.113556.1.4.802
Val: 23 1.2.840.113556.1.4.1907
Val: 23 1.2.840.113556.1.4.1948
Attr: supportedLDAPVersion
Val: 1 3
Val: 1 2
Attr: supportedLDAPPolicies
Val: 14 MaxPoolThreads
Val: 15 MaxDatagramRecv
Val: 16 MaxReceiveBuffer
Val: 15 InitRecvTimeout
Val: 14 MaxConnections
Val: 15 MaxConnIdleTime
Val: 11 MaxPageSize
Val: 16 MaxQueryDuration
Val: 16 MaxTempTableSize
Val: 16 MaxResultSetSize
Val: 22 MaxNotificationPerConn
Val: 11 MaxValRange
Attr: highestCommittedUSN
Val: 5 52048
Attr: supportedSASLMechanisms
Val: 6 GSSAPI
Val: 10 GSS-SPNEGO
Val: 8 EXTERNAL
Val: 10 DIGEST-MD5
Attr: dnsHostName
Val: 16 SMLUS-DC.sml.com
Attr: ldapServiceName
Val: 25 sml.com:[email protected]
Attr: serverName
Val: 68
CN=SMLUS-DC,CN=Servers,CN=US,CN=Sites,CN=Configuration,DC=sml,DC=com
Attr: supportedCapabilities
Val: 22 1.2.840.113556.1.4.800
Val: 23 1.2.840.113556.1.4.1670
Val: 23 1.2.840.113556.1.4.1791
Attr: isSynchronized
Val: 4 TRUE
Attr: isGlobalCatalogReady
Val: 5 FALSE
Attr: domainFunctionality
Val: 1 2
Attr: forestFunctionality
Val: 1 2
Attr: domainControllerFunctionality
Val: 1 2

Do NTLM authenticated LDAP call to 'SMLUS-DC.sml.com'.
Found 1 entries:
Attr: currentTime
Val: 17 20080605094100.0Z
Attr: subschemaSubentry
Val: 53 CN=Aggregate,CN=Schema,CN=Configuration,DC=sml,DC=com
Attr: dsServiceName
Val: 85 CN=NTDS
Settings,CN=SMLUS-DC,CN=Servers,CN=US,CN=Sites,CN=Configuration,DC=sml,DC=com
Attr: namingContexts
Val: 13 DC=sml,DC=com
Val: 30 CN=Configuration,DC=sml,DC=com
Val: 40 CN=Schema,CN=Configuration,DC=sml,DC=com
Val: 31 DC=DomainDnsZones,DC=sml,DC=com
Val: 31 DC=ForestDnsZones,DC=sml,DC=com
Attr: defaultNamingContext
Val: 13 DC=sml,DC=com
Attr: schemaNamingContext
Val: 40 CN=Schema,CN=Configuration,DC=sml,DC=com
Attr: configurationNamingContext
Val: 30 CN=Configuration,DC=sml,DC=com
Attr: rootDomainNamingContext
Val: 13 DC=sml,DC=com
Attr: supportedControl
Val: 22 1.2.840.113556.1.4.319
Val: 22 1.2.840.113556.1.4.801
Val: 22 1.2.840.113556.1.4.473
Val: 22 1.2.840.113556.1.4.528
Val: 22 1.2.840.113556.1.4.417
Val: 22 1.2.840.113556.1.4.619
Val: 22 1.2.840.113556.1.4.841
Val: 22 1.2.840.113556.1.4.529
Val: 22 1.2.840.113556.1.4.805
Val: 22 1.2.840.113556.1.4.521
Val: 22 1.2.840.113556.1.4.970
Val: 23 1.2.840.113556.1.4.1338
Val: 22 1.2.840.113556.1.4.474
Val: 23 1.2.840.113556.1.4.1339
Val: 23 1.2.840.113556.1.4.1340
Val: 23 1.2.840.113556.1.4.1413
Val: 23 2.16.840.1.113730.3.4.9
Val: 24 2.16.840.1.113730.3.4.10
Val: 23 1.2.840.113556.1.4.1504
Val: 23 1.2.840.113556.1.4.1852
Val: 22 1.2.840.113556.1.4.802
Val: 23 1.2.840.113556.1.4.1907
Val: 23 1.2.840.113556.1.4.1948
Attr: supportedLDAPVersion
Val: 1 3
Val: 1 2
Attr: supportedLDAPPolicies
Val: 14 MaxPoolThreads
Val: 15 MaxDatagramRecv
Val: 16 MaxReceiveBuffer
Val: 15 InitRecvTimeout
Val: 14 MaxConnections
Val: 15 MaxConnIdleTime
Val: 11 MaxPageSize
Val: 16 MaxQueryDuration
Val: 16 MaxTempTableSize
Val: 16 MaxResultSetSize
Val: 22 MaxNotificationPerConn
Val: 11 MaxValRange
Attr: highestCommittedUSN
Val: 5 52048
Attr: supportedSASLMechanisms
Val: 6 GSSAPI
Val: 10 GSS-SPNEGO
Val: 8 EXTERNAL
Val: 10 DIGEST-MD5
Attr: dnsHostName
Val: 16 SMLUS-DC.sml.com
Attr: ldapServiceName
Val: 25 sml.com:[email protected]
Attr: serverName
Val: 68
CN=SMLUS-DC,CN=Servers,CN=US,CN=Sites,CN=Configuration,DC=sml,DC=com
Attr: supportedCapabilities
Val: 22 1.2.840.113556.1.4.800
Val: 23 1.2.840.113556.1.4.1670
Val: 23 1.2.840.113556.1.4.1791
Attr: isSynchronized
Val: 4 TRUE
Attr: isGlobalCatalogReady
Val: 5 FALSE
Attr: domainFunctionality
Val: 1 2
Attr: forestFunctionality
Val: 1 2
Attr: domainControllerFunctionality
Val: 1 2

Do Negotiate authenticated LDAP call to 'SMLUS-DC.sml.com'.
Found 1 entries:
Attr: currentTime
Val: 17 20080605094102.0Z
Attr: subschemaSubentry
Val: 53 CN=Aggregate,CN=Schema,CN=Configuration,DC=sml,DC=com
Attr: dsServiceName
Val: 85 CN=NTDS
Settings,CN=SMLUS-DC,CN=Servers,CN=US,CN=Sites,CN=Configuration,DC=sml,DC=com
Attr: namingContexts
Val: 13 DC=sml,DC=com
Val: 30 CN=Configuration,DC=sml,DC=com
Val: 40 CN=Schema,CN=Configuration,DC=sml,DC=com
Val: 31 DC=DomainDnsZones,DC=sml,DC=com
Val: 31 DC=ForestDnsZones,DC=sml,DC=com
Attr: defaultNamingContext
Val: 13 DC=sml,DC=com
Attr: schemaNamingContext
Val: 40 CN=Schema,CN=Configuration,DC=sml,DC=com
Attr: configurationNamingContext
Val: 30 CN=Configuration,DC=sml,DC=com
Attr: rootDomainNamingContext
Val: 13 DC=sml,DC=com
Attr: supportedControl
Val: 22 1.2.840.113556.1.4.319
Val: 22 1.2.840.113556.1.4.801
Val: 22 1.2.840.113556.1.4.473
Val: 22 1.2.840.113556.1.4.528
Val: 22 1.2.840.113556.1.4.417
Val: 22 1.2.840.113556.1.4.619
Val: 22 1.2.840.113556.1.4.841
Val: 22 1.2.840.113556.1.4.529
Val: 22 1.2.840.113556.1.4.805
Val: 22 1.2.840.113556.1.4.521
Val: 22 1.2.840.113556.1.4.970
Val: 23 1.2.840.113556.1.4.1338
Val: 22 1.2.840.113556.1.4.474
Val: 23 1.2.840.113556.1.4.1339
Val: 23 1.2.840.113556.1.4.1340
Val: 23 1.2.840.113556.1.4.1413
Val: 23 2.16.840.1.113730.3.4.9
Val: 24 2.16.840.1.113730.3.4.10
Val: 23 1.2.840.113556.1.4.1504
Val: 23 1.2.840.113556.1.4.1852
Val: 22 1.2.840.113556.1.4.802
Val: 23 1.2.840.113556.1.4.1907
Val: 23 1.2.840.113556.1.4.1948
Attr: supportedLDAPVersion
Val: 1 3
Val: 1 2
Attr: supportedLDAPPolicies
Val: 14 MaxPoolThreads
Val: 15 MaxDatagramRecv
Val: 16 MaxReceiveBuffer
Val: 15 InitRecvTimeout
Val: 14 MaxConnections
Val: 15 MaxConnIdleTime
Val: 11 MaxPageSize
Val: 16 MaxQueryDuration
Val: 16 MaxTempTableSize
Val: 16 MaxResultSetSize
Val: 22 MaxNotificationPerConn
Val: 11 MaxValRange
Attr: highestCommittedUSN
Val: 5 52048
Attr: supportedSASLMechanisms
Val: 6 GSSAPI
Val: 10 GSS-SPNEGO
Val: 8 EXTERNAL
Val: 10 DIGEST-MD5
Attr: dnsHostName
Val: 16 SMLUS-DC.sml.com
Attr: ldapServiceName
Val: 25 sml.com:[email protected]
Attr: serverName
Val: 68
CN=SMLUS-DC,CN=Servers,CN=US,CN=Sites,CN=Configuration,DC=sml,DC=com
Attr: supportedCapabilities
Val: 22 1.2.840.113556.1.4.800
Val: 23 1.2.840.113556.1.4.1670
Val: 23 1.2.840.113556.1.4.1791
Attr: isSynchronized
Val: 4 TRUE
Attr: isGlobalCatalogReady
Val: 5 FALSE
Attr: domainFunctionality
Val: 1 2
Attr: forestFunctionality
Val: 1 2
Attr: domainControllerFunctionality
Val: 1 2

Registered Service Principal Names:
DNS/dyapp3.sml.com
GC/dyapp3.sml.com/sml.com
HOST/dyapp3.sml.com/sml.com
HOST/dyapp3.sml.com/SML
ldap/1a6d2c04-fe41-4950-a501-856db04507c0._msdcs.sml.com
ldap/dyapp3.sml.com/SML
ldap/DYAPP3
ldap/dyapp3.sml.com
ldap/dyapp3.sml.com/sml.com
NtFrs-88f5d2bd-b646-11d2-a6d3-00c04fc9b232/dyapp3.sml.com
ldap/dyapp3.sml.com/ForestDnsZones.sml.com
ldap/dyapp3.sml.com/DomainDnsZones.sml.com
E3514235-4B06-11D1-AB04-00C04FC2DCD2/1a6d2c04-fe41-4950-a501-856db04507c0/sml.com
HOST/DYAPP3
HOST/dyapp3.sml.com

Do un-authenticated LDAP call to 'dgdc.sml.com'.
Found 1 entries:
Attr: currentTime
Val: 17 20080605094103.0Z
Attr: subschemaSubentry
Val: 53 CN=Aggregate,CN=Schema,CN=Configuration,DC=sml,DC=com
Attr: dsServiceName
Val: 87 CN=NTDS
Settings,CN=DGDC,CN=Servers,CN=China-DG,CN=Sites,CN=Configuration,DC=sml,DC=com
Attr: namingContexts
Val: 13 DC=sml,DC=com
Val: 30 CN=Configuration,DC=sml,DC=com
Val: 40 CN=Schema,CN=Configuration,DC=sml,DC=com
Val: 31 DC=DomainDnsZones,DC=sml,DC=com
Val: 31 DC=ForestDnsZones,DC=sml,DC=com
Attr: defaultNamingContext
Val: 13 DC=sml,DC=com
Attr: schemaNamingContext
Val: 40 CN=Schema,CN=Configuration,DC=sml,DC=com
Attr: configurationNamingContext
Val: 30 CN=Configuration,DC=sml,DC=com
Attr: rootDomainNamingContext
Val: 13 DC=sml,DC=com
Attr: supportedControl
Val: 22 1.2.840.113556.1.4.319
Val: 22 1.2.840.113556.1.4.801
Val: 22 1.2.840.113556.1.4.473
Val: 22 1.2.840.113556.1.4.528
Val: 22 1.2.840.113556.1.4.417
Val: 22 1.2.840.113556.1.4.619
Val: 22 1.2.840.113556.1.4.841
Val: 22 1.2.840.113556.1.4.529
Val: 22 1.2.840.113556.1.4.805
Val: 22 1.2.840.113556.1.4.521
Val: 22 1.2.840.113556.1.4.970
Val: 23 1.2.840.113556.1.4.1338
Val: 22 1.2.840.113556.1.4.474
Val: 23 1.2.840.113556.1.4.1339
Val: 23 1.2.840.113556.1.4.1340
Val: 23 1.2.840.113556.1.4.1413
Val: 23 2.16.840.1.113730.3.4.9
Val: 24 2.16.840.1.113730.3.4.10
Val: 23 1.2.840.113556.1.4.1504
Val: 23 1.2.840.113556.1.4.1852
Val: 22 1.2.840.113556.1.4.802
Val: 23 1.2.840.113556.1.4.1907
Val: 23 1.2.840.113556.1.4.1948
Attr: supportedLDAPVersion
Val: 1 3
Val: 1 2
Attr: supportedLDAPPolicies
Val: 14 MaxPoolThreads
Val: 15 MaxDatagramRecv
Val: 16 MaxReceiveBuffer
Val: 15 InitRecvTimeout
Val: 14 MaxConnections
Val: 15 MaxConnIdleTime
Val: 11 MaxPageSize
Val: 16 MaxQueryDuration
Val: 16 MaxTempTableSize
Val: 16 MaxResultSetSize
Val: 22 MaxNotificationPerConn
Val: 11 MaxValRange
Attr: highestCommittedUSN
Val: 5 41390
Attr: supportedSASLMechanisms
Val: 6 GSSAPI
Val: 10 GSS-SPNEGO
Val: 8 EXTERNAL
Val: 10 DIGEST-MD5
Attr: dnsHostName
Val: 12 dgdc.sml.com
Attr: ldapServiceName
Val: 21 sml.com:[email protected]
Attr: serverName
Val: 70
CN=DGDC,CN=Servers,CN=China-DG,CN=Sites,CN=Configuration,DC=sml,DC=com
Attr: supportedCapabilities
Val: 22 1.2.840.113556.1.4.800
Val: 23 1.2.840.113556.1.4.1670
Val: 23 1.2.840.113556.1.4.1791
Attr: isSynchronized
Val: 4 TRUE
Attr: isGlobalCatalogReady
Val: 5 FALSE
Attr: domainFunctionality
Val: 1 2
Attr: forestFunctionality
Val: 1 2
Attr: domainControllerFunctionality
Val: 1 2

Do NTLM authenticated LDAP call to 'dgdc.sml.com'.
Found 1 entries:
Attr: currentTime
Val: 17 20080605094103.0Z
Attr: subschemaSubentry
Val: 53 CN=Aggregate,CN=Schema,CN=Configuration,DC=sml,DC=com
Attr: dsServiceName
Val: 87 CN=NTDS
Settings,CN=DGDC,CN=Servers,CN=China-DG,CN=Sites,CN=Configuration,DC=sml,DC=com
Attr: namingContexts
Val: 13 DC=sml,DC=com
Val: 30 CN=Configuration,DC=sml,DC=com
Val: 40 CN=Schema,CN=Configuration,DC=sml,DC=com
Val: 31 DC=DomainDnsZones,DC=sml,DC=com
Val: 31 DC=ForestDnsZones,DC=sml,DC=com
Attr: defaultNamingContext
Val: 13 DC=sml,DC=com
Attr: schemaNamingContext
Val: 40 CN=Schema,CN=Configuration,DC=sml,DC=com
Attr: configurationNamingContext
Val: 30 CN=Configuration,DC=sml,DC=com
Attr: rootDomainNamingContext
Val: 13 DC=sml,DC=com
Attr: supportedControl
Val: 22 1.2.840.113556.1.4.319
Val: 22 1.2.840.113556.1.4.801
Val: 22 1.2.840.113556.1.4.473
Val: 22 1.2.840.113556.1.4.528
Val: 22 1.2.840.113556.1.4.417
Val: 22 1.2.840.113556.1.4.619
Val: 22 1.2.840.113556.1.4.841
Val: 22 1.2.840.113556.1.4.529
Val: 22 1.2.840.113556.1.4.805
Val: 22 1.2.840.113556.1.4.521
Val: 22 1.2.840.113556.1.4.970
Val: 23 1.2.840.113556.1.4.1338
Val: 22 1.2.840.113556.1.4.474
Val: 23 1.2.840.113556.1.4.1339
Val: 23 1.2.840.113556.1.4.1340
Val: 23 1.2.840.113556.1.4.1413
Val: 23 2.16.840.1.113730.3.4.9
Val: 24 2.16.840.1.113730.3.4.10
Val: 23 1.2.840.113556.1.4.1504
Val: 23 1.2.840.113556.1.4.1852
Val: 22 1.2.840.113556.1.4.802
Val: 23 1.2.840.113556.1.4.1907
Val: 23 1.2.840.113556.1.4.1948
Attr: supportedLDAPVersion
Val: 1 3
Val: 1 2
Attr: supportedLDAPPolicies
Val: 14 MaxPoolThreads
Val: 15 MaxDatagramRecv
Val: 16 MaxReceiveBuffer
Val: 15 InitRecvTimeout
Val: 14 MaxConnections
Val: 15 MaxConnIdleTime
Val: 11 MaxPageSize
Val: 16 MaxQueryDuration
Val: 16 MaxTempTableSize
Val: 16 MaxResultSetSize
Val: 22 MaxNotificationPerConn
Val: 11 MaxValRange
Attr: highestCommittedUSN
Val: 5 41390
Attr: supportedSASLMechanisms
Val: 6 GSSAPI
Val: 10 GSS-SPNEGO
Val: 8 EXTERNAL
Val: 10 DIGEST-MD5
Attr: dnsHostName
Val: 12 dgdc.sml.com
Attr: ldapServiceName
Val: 21 sml.com:[email protected]
Attr: serverName
Val: 70
CN=DGDC,CN=Servers,CN=China-DG,CN=Sites,CN=Configuration,DC=sml,DC=com
Attr: supportedCapabilities
Val: 22 1.2.840.113556.1.4.800
Val: 23 1.2.840.113556.1.4.1670
Val: 23 1.2.840.113556.1.4.1791
Attr: isSynchronized
Val: 4 TRUE
Attr: isGlobalCatalogReady
Val: 5 FALSE
Attr: domainFunctionality
Val: 1 2
Attr: forestFunctionality
Val: 1 2
Attr: domainControllerFunctionality
Val: 1 2

pcnetnet · Jun 9, 2008

For Site B netdiag #2

Do Negotiate authenticated LDAP call to 'dgdc.sml.com'.
Found 1 entries:
Attr: currentTime
Val: 17 20080605094103.0Z
Attr: subschemaSubentry
Val: 53 CN=Aggregate,CN=Schema,CN=Configuration,DC=sml,DC=com
Attr: dsServiceName
Val: 87 CN=NTDS
Settings,CN=DGDC,CN=Servers,CN=China-DG,CN=Sites,CN=Configuration,DC=sml,DC=com
Attr: namingContexts
Val: 13 DC=sml,DC=com
Val: 30 CN=Configuration,DC=sml,DC=com
Val: 40 CN=Schema,CN=Configuration,DC=sml,DC=com
Val: 31 DC=DomainDnsZones,DC=sml,DC=com
Val: 31 DC=ForestDnsZones,DC=sml,DC=com
Attr: defaultNamingContext
Val: 13 DC=sml,DC=com
Attr: schemaNamingContext
Val: 40 CN=Schema,CN=Configuration,DC=sml,DC=com
Attr: configurationNamingContext
Val: 30 CN=Configuration,DC=sml,DC=com
Attr: rootDomainNamingContext
Val: 13 DC=sml,DC=com
Attr: supportedControl
Val: 22 1.2.840.113556.1.4.319
Val: 22 1.2.840.113556.1.4.801
Val: 22 1.2.840.113556.1.4.473
Val: 22 1.2.840.113556.1.4.528
Val: 22 1.2.840.113556.1.4.417
Val: 22 1.2.840.113556.1.4.619
Val: 22 1.2.840.113556.1.4.841
Val: 22 1.2.840.113556.1.4.529
Val: 22 1.2.840.113556.1.4.805
Val: 22 1.2.840.113556.1.4.521
Val: 22 1.2.840.113556.1.4.970
Val: 23 1.2.840.113556.1.4.1338
Val: 22 1.2.840.113556.1.4.474
Val: 23 1.2.840.113556.1.4.1339
Val: 23 1.2.840.113556.1.4.1340
Val: 23 1.2.840.113556.1.4.1413
Val: 23 2.16.840.1.113730.3.4.9
Val: 24 2.16.840.1.113730.3.4.10
Val: 23 1.2.840.113556.1.4.1504
Val: 23 1.2.840.113556.1.4.1852
Val: 22 1.2.840.113556.1.4.802
Val: 23 1.2.840.113556.1.4.1907
Val: 23 1.2.840.113556.1.4.1948
Attr: supportedLDAPVersion
Val: 1 3
Val: 1 2
Attr: supportedLDAPPolicies
Val: 14 MaxPoolThreads
Val: 15 MaxDatagramRecv
Val: 16 MaxReceiveBuffer
Val: 15 InitRecvTimeout
Val: 14 MaxConnections
Val: 15 MaxConnIdleTime
Val: 11 MaxPageSize
Val: 16 MaxQueryDuration
Val: 16 MaxTempTableSize
Val: 16 MaxResultSetSize
Val: 22 MaxNotificationPerConn
Val: 11 MaxValRange
Attr: highestCommittedUSN
Val: 5 41390
Attr: supportedSASLMechanisms
Val: 6 GSSAPI
Val: 10 GSS-SPNEGO
Val: 8 EXTERNAL
Val: 10 DIGEST-MD5
Attr: dnsHostName
Val: 12 dgdc.sml.com
Attr: ldapServiceName
Val: 21 sml.com:[email protected]
Attr: serverName
Val: 70
CN=DGDC,CN=Servers,CN=China-DG,CN=Sites,CN=Configuration,DC=sml,DC=com
Attr: supportedCapabilities
Val: 22 1.2.840.113556.1.4.800
Val: 23 1.2.840.113556.1.4.1670
Val: 23 1.2.840.113556.1.4.1791
Attr: isSynchronized
Val: 4 TRUE
Attr: isGlobalCatalogReady
Val: 5 FALSE
Attr: domainFunctionality
Val: 1 2
Attr: forestFunctionality
Val: 1 2
Attr: domainControllerFunctionality
Val: 1 2

Registered Service Principal Names:
DNS/dyapp3.sml.com
GC/dyapp3.sml.com/sml.com
HOST/dyapp3.sml.com/sml.com
HOST/dyapp3.sml.com/SML
ldap/1a6d2c04-fe41-4950-a501-856db04507c0._msdcs.sml.com
ldap/dyapp3.sml.com/SML
ldap/DYAPP3
ldap/dyapp3.sml.com
ldap/dyapp3.sml.com/sml.com
NtFrs-88f5d2bd-b646-11d2-a6d3-00c04fc9b232/dyapp3.sml.com
ldap/dyapp3.sml.com/ForestDnsZones.sml.com
ldap/dyapp3.sml.com/DomainDnsZones.sml.com
E3514235-4B06-11D1-AB04-00C04FC2DCD2/1a6d2c04-fe41-4950-a501-856db04507c0/sml.com
HOST/DYAPP3
HOST/dyapp3.sml.com

Routing table test . . . . . . . . : Passed
Active Routes :
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 192.168.8.4 192.168.8.70
10
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
192.168.8.0 255.255.255.0 192.168.8.70 192.168.8.70
10
192.168.8.70 255.255.255.255 127.0.0.1 127.0.0.1
10
192.168.8.255 255.255.255.255 192.168.8.70 192.168.8.70
10
192.168.9.0 255.255.255.0 192.168.8.16 192.168.8.70
1
192.168.36.0 255.255.255.0 192.168.8.16 192.168.8.70
1
224.0.0.0 240.0.0.0 192.168.8.70 192.168.8.70
10
255.255.255.255 255.255.255.255 192.168.8.70 192.168.8.70
1

Persistent Route Entries:
192.168.36.0 255.255.255.0 192.168.8.16 0
1
192.168.9.0 255.255.255.0 192.168.8.16 0
1

Netstat information test . . . . . : Passed

Interface Statistics

Received Sent
Unicast Packets 1985147639 3905662324
Non-unicast packets 2630634 346047
Discards 0 0
Errors 0 0
Unknown protocols 0 458284

Interface index = 1
Description = MS TCP Loopback interface
Type = 24
MTU = 1520
Speed = 10000000
Physical Address = 00-00-00-00-00-00
Administrative Status = 1
Operational Status = 1
Last Changed = 1031613246
Output Queue Length = 0

Interface index = 65539
Description = Broadcom NetXtreme Gigabit Ethernet
Type = 6
MTU = 1500
Speed = 1000000000
Physical Address = 00-0F-1F-67-EC-42
Administrative Status = 1
Operational Status = 1
Last Changed = 1031613256
Output Queue Length = 0

Active Connections

Proto Local Address Foreign Address
State
TCP dyapp3:domain dyapp3.sml.com:2160
LISTENING
TCP dyapp3:http dyapp3.sml.com:39102
LISTENING
TCP dyapp3:kerberos dyapp3.sml.com:22749
LISTENING
TCP dyapp3:epmap dyapp3.sml.com:38958
LISTENING
TCP dyapp3:ldap dyapp3.sml.com:37049
LISTENING
TCP dyapp3:microsoft-ds dyapp3.sml.com:10245
LISTENING
TCP dyapp3:kpasswd dyapp3.sml.com:53255
LISTENING
TCP dyapp3:http-rpc-epmap dyapp3.sml.com:10329
LISTENING
TCP dyapp3:ldaps dyapp3.sml.com:20730
LISTENING
TCP dyapp3:1025 dyapp3.sml.com:37108
LISTENING
TCP dyapp3:1027 dyapp3.sml.com:61547
LISTENING
TCP dyapp3:1044 dyapp3.sml.com:55328
LISTENING
TCP dyapp3:1062 dyapp3.sml.com:34984
LISTENING
TCP dyapp3:1071 dyapp3.sml.com:24667
LISTENING
TCP dyapp3:1311 dyapp3.sml.com:38974
LISTENING
TCP dyapp3:1352 dyapp3.sml.com:20661
LISTENING
TCP dyapp3:1494 dyapp3.sml.com:45175
LISTENING
TCP dyapp3:2512 dyapp3.sml.com:10460
LISTENING
TCP dyapp3:2513 dyapp3.sml.com:61623
LISTENING
TCP dyapp3:2598 dyapp3.sml.com:2288
LISTENING
TCP dyapp3:2967 dyapp3.sml.com:63643
LISTENING
TCP dyapp3:5631 dyapp3.sml.com:8440
LISTENING
TCP dyapp3:5800 dyapp3.sml.com:20520
LISTENING
TCP dyapp3:5900 dyapp3.sml.com:30941
LISTENING
TCP dyapp3:27000 dyapp3.sml.com:47266
LISTENING
TCP dyapp3:ldap dyapp3.sml.com:1058
ESTABLISHED
TCP dyapp3:ldap dyapp3.sml.com:1060
ESTABLISHED
TCP dyapp3:ldap dyapp3.sml.com:1061
ESTABLISHED
TCP dyapp3:ldap dyapp3.sml.com:3089
TIME_WAIT
TCP dyapp3:ldap dyapp3.sml.com:4646
ESTABLISHED
TCP dyapp3:1058 dyapp3.sml.com:ldap
ESTABLISHED
TCP dyapp3:1060 dyapp3.sml.com:ldap
ESTABLISHED
TCP dyapp3:1061 dyapp3.sml.com:ldap
ESTABLISHED
TCP dyapp3:1210 dyapp3.sml.com:36967
LISTENING
TCP dyapp3:3089 dyapp3.sml.com:ldap
TIME_WAIT
TCP dyapp3:3090 dyapp3.sml.com:epmap
TIME_WAIT
TCP dyapp3:3091 dyapp3.sml.com:1025
TIME_WAIT
TCP dyapp3:4646 dyapp3.sml.com:ldap
ESTABLISHED
TCP dyapp3:netbios-ssn dyapp3.sml.com:10258
LISTENING
TCP dyapp3:ldap testsame.sml.com:1490
FIN_WAIT_2
TCP dyapp3:ldap testsame.sml.com:1497
FIN_WAIT_2
TCP dyapp3:ldap testsame.sml.com:1498
FIN_WAIT_2
TCP dyapp3:ldap testsame.sml.com:1499
FIN_WAIT_2
TCP dyapp3:ldap testsame.sml.com:1501
FIN_WAIT_2
TCP dyapp3:ldap testsame.sml.com:1502
FIN_WAIT_2
TCP dyapp3:ldap testsame.sml.com:1503
FIN_WAIT_2
TCP dyapp3:ldap testsame.sml.com:1505
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1506
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1507
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1508
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1509
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1510
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:wins
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1513
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1514
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1519
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1520
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1521
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:ingreslock
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1525
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1526
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1528
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1529
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1530
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1531
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1532
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1534
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1536
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1537
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1538
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1542
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1543
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1544
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1546
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1547
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1548
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1552
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1554
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1555
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1558
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1559
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1560
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1562
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1563
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1564
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1570
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1571
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1572
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1573
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1574
ESTABLISHED
TCP dyapp3:ldap testsame.sml.com:1575
ESTABLISHED
TCP dyapp3:ldap dyapp3.sml.com:3112
TIME_WAIT
TCP dyapp3:ldap dyapp3.sml.com:3113
ESTABLISHED
TCP dyapp3:ldap dyapp3.sml.com:3114
TIME_WAIT
TCP dyapp3:ldap dyapp3.sml.com:4645
ESTABLISHED
TCP dyapp3:ldap DHKFIRISLIU:2563
TIME_WAIT
TCP dyapp3:1025 dyapp3.sml.com:2678
ESTABLISHED
TCP dyapp3:1025 dyapp3.sml.com:3046
ESTABLISHED
TCP dyapp3:1025 dyapp3.sml.com:3078
ESTABLISHED
TCP dyapp3:1303 uksql.sml.com:4915
ESTABLISHED
TCP dyapp3:2678 dyapp3.sml.com:1025
ESTABLISHED
TCP dyapp3:3021 dyapp3.sml.com:ldap
CLOSE_WAIT
TCP dyapp3:3039 smlad.sml.com:epmap
TIME_WAIT
TCP dyapp3:3045 dyapp3.sml.com:epmap
TIME_WAIT
TCP dyapp3:3046 dyapp3.sml.com:1025
ESTABLISHED
TCP dyapp3:3077 dyapp3.sml.com:epmap
TIME_WAIT
TCP dyapp3:3078 dyapp3.sml.com:1025
ESTABLISHED
TCP dyapp3:3083 SML_NOTES_1:1352
ESTABLISHED
TCP dyapp3:3086 dyapp3.sml.com:epmap
TIME_WAIT
TCP dyapp3:3087 dyapp3.sml.com:1025
TIME_WAIT
TCP dyapp3:3092 dyapp3.sml.com:epmap
TIME_WAIT
TCP dyapp3:3093 dyapp3.sml.com:1025
TIME_WAIT
TCP dyapp3:3094 smlus-dc.sml.com:microsoft-ds
TIME_WAIT
TCP dyapp3:3103 dgdc.sml.com:microsoft-ds
TIME_WAIT
TCP dyapp3:3105 dyapp3.sml.com:netbios-ssn
TIME_WAIT
TCP dyapp3:3108 smlad.sml.com:epmap
ESTABLISHED
TCP dyapp3:3109 smlad.sml.com:1025
ESTABLISHED
TCP dyapp3:3111 dyapp3.sml.com:ldap
TIME_WAIT
TCP dyapp3:3112 dyapp3.sml.com:ldap
TIME_WAIT
TCP dyapp3:3113 dyapp3.sml.com:ldap
ESTABLISHED
TCP dyapp3:3114 dyapp3.sml.com:ldap
TIME_WAIT
TCP dyapp3:3115 dyapp3.sml.com:epmap
TIME_WAIT
TCP dyapp3:3116 dyapp3.sml.com:1025
TIME_WAIT
TCP dyapp3:3117 smlad.sml.com:ldap
TIME_WAIT
TCP dyapp3:3121 smlus-dc.sml.com:ldap
TIME_WAIT
TCP dyapp3:3122 smlus-dc.sml.com:ldap
TIME_WAIT
TCP dyapp3:3123 smlus-dc.sml.com:ldap
ESTABLISHED
TCP dyapp3:3124 smlus-dc.sml.com:ldap
TIME_WAIT
TCP dyapp3:3125 dyapp3.sml.com:epmap
TIME_WAIT
TCP dyapp3:3126 dyapp3.sml.com:1025
TIME_WAIT
TCP dyapp3:3127 dgdc.sml.com:ldap
TIME_WAIT
TCP dyapp3:3128 dgdc.sml.com:ldap
TIME_WAIT
TCP dyapp3:3129 dgdc.sml.com:ldap
ESTABLISHED
TCP dyapp3:3130 dgdc.sml.com:ldap
FIN_WAIT_1
TCP dyapp3:3131 dyapp3.sml.com:epmap
TIME_WAIT
TCP dyapp3:ms-rule-engine dyapp3.sml.com:1025
TIME_WAIT
TCP dyapp3:3166 SMLAOS2:2512
ESTABLISHED
TCP dyapp3:4614 SMLDC:microsoft-ds
ESTABLISHED
TCP dyapp3:4645 dyapp3.sml.com:ldap
ESTABLISHED
TCP dyapp3:5900 CHIWAIXP:2133
ESTABLISHED
TCP dyapp3:5900 demo11.sml.com:4186
ESTABLISHED
UDP dyapp3:snmp *:*
UDP dyapp3:microsoft-ds *:*
UDP dyapp3:isakmp *:*
UDP dyapp3:1029 *:*
UDP dyapp3:1030 *:*
UDP dyapp3:1031 *:*
UDP dyapp3:1046 *:*
UDP dyapp3:1054 *:*
UDP dyapp3:1604 *:*
UDP dyapp3:3311 *:*
UDP dyapp3:3312 *:*
UDP dyapp3:3313 *:*
UDP dyapp3:ipsec-msft *:*
UDP dyapp3:5632 *:*
UDP dyapp3:38293 *:*
UDP dyapp3:domain *:*
UDP dyapp3:ntp *:*
UDP dyapp3:1053 *:*
UDP dyapp3:1055 *:*
UDP dyapp3:1057 *:*
UDP dyapp3:1063 *:*
UDP dyapp3:1072 *:*
UDP dyapp3:1192 *:*
UDP dyapp3:1220 *:*
UDP dyapp3:1336 *:*
UDP dyapp3:2929 *:*
UDP dyapp3:3020 *:*
UDP dyapp3:3110 *:*
UDP dyapp3:domain *:*
UDP dyapp3:kerberos *:*
UDP dyapp3:ntp *:*
UDP dyapp3:netbios-ns *:*
UDP dyapp3:netbios-dgm *:*
UDP dyapp3:389 *:*
UDP dyapp3:kpasswd *:*

IP Statistics

Packets Received = 19,420,217
Received Header Errors = 0
Received Address Errors = 1
Datagrams Forwarded = 0
Unknown Protocols Received = 0
Received Packets Discarded = 54
Received Packets Delivered = 19,419,784
Output Requests = 15,733,320
Routing Discards = 0
Discarded Output Packets = 0
Output Packet No Route = 0
Reassembly Required = 753
Reassembly Successful = 373
Reassembly Failures = 7
Datagrams successfully fragmented = 373
Datagrams failing fragmentation = 0
Fragments Created = 746
Forwarding = 2
Default TTL = 128
Reassembly timeout = 60

TCP Statistics

Active Opens = 238,706
Passive Opens = 167,749
Failed Connection Attempts = 85,050
Reset Connections = 4,674
Current Connections = 74
Received Segments = 14,457,303
Segment Sent = 14,039,270
Segment Retransmitted = 205,182
Retransmission Timeout Algorithm = vanj
Minimum Retransmission Timeout = 300
Maximum Retransmission Timeout = 120,000
Maximum Number of Connections = -1

UDP Statistics

Datagrams Received = 4,216,724
No Ports = 988,940
Receive Errors = 0
Datagrams Sent = 741,091

ICMP Statistics

Received Sent
Messages 327,591 327,591
Errors 0 0
Destination Unreachable 130 130
Time Exceeded 57 57
Parameter Problems 0 0
Source Quenchs 0 0
Redirects 1 1
Echos 174,982 174,982
Echo Replies 152,421 152,421
Timestamps 0 0
Timestamp Replies 0 0
Address Masks 0 0
Address Mask Replies 0 0

Bindings test. . . . . . . . . . . : Passed
Component Name : NDIS Usermode I/O Protocol
Bind Name: Ndisuio
Binding Paths:
Owner of the binding path : NDIS Usermode I/O Protocol
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndis5
Upper Component: NDIS Usermode I/O Protocol
Lower Component: Broadcom NetXtreme Gigabit Ethernet

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 Gigabit Ethernet #2

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 Gigabit Ethernet

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 Gigabit Ethernet #2

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

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

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

Owner of the binding path : Remote Access NDIS WAN Driver
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: ndiswan
Upper Component: Remote Access NDIS WAN Driver
Lower Component: WAN Miniport (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)

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

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

Component Name : WINS Client(TCP/IP) Protocol
Bind Name: NetBT
Binding Paths:
Owner of the binding path : WINS Client(TCP/IP) Protocol
Binding Enabled: Yes
Interfaces of the binding path:
-Interface Name: tdi
Upper Component: WINS Client(TCP/IP) Protocol
Lower Component: Internet Protocol (TCP/IP)
-Interface Name: ndis5
Upper Component: Internet Protocol (TCP/IP)
Lower Component: Broadcom NetXtreme Gigabit Ethernet

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 Gigabit Ethernet #2

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 Gigabit Ethernet

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 Gigabit Ethernet #2

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 Gigabit Ethernet

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 Gigabit Ethernet #2

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 : 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 Gigabit Ethernet

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 Gigabit Ethernet #2

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 Gigabit Ethernet

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 Gigabit Ethernet #2

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 Gigabit Ethernet

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 Gigabit Ethernet #2

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 : WAN Miniport (IP)
Bind Name: NdisWanIp
Binding Paths:

Component Name : Direct Parallel
Bind Name: {1D6E4C19-ABC7-4A7C-9BA0-E97FB099882C}
Binding Paths:

Component Name : WAN Miniport (PPPOE)
Bind Name: {6A098FDD-E862-4926-B334-1A9EDCD37B8D}
Binding Paths:

Component Name : WAN Miniport (PPTP)
Bind Name: {75B44057-2496-4593-B0FA-CD6EFAC9E4B6}
Binding Paths:

Component Name : WAN Miniport (L2TP)
Bind Name: {3609A5CA-8D97-4D5E-B6C0-3084B13A250E}
Binding Paths:

Component Name : RAS Async Adapter
Bind Name: {66DCA5CA-261E-4334-BD1E-FC2441F7A159}
Binding Paths:

Component Name : Broadcom NetXtreme Gigabit Ethernet #2
Bind Name: {14920296-4028-43BD-91DA-F8E82F50A10B}
Binding Paths:

Component Name : Broadcom NetXtreme Gigabit Ethernet
Bind Name: {885EF630-203E-4055-B650-65AF69E8CF3E}
Binding Paths:

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

pcnetnet · Jun 9, 2008

For Site B repadmin output

DR_Site\DYAPP3
DC Options: (none)
Site Options: (none)
DC object GUID: 1a6d2c04-fe41-4950-a501-856db04507c0
DC invocationID: fc35d3a6-39a2-45ac-8a3d-360b2beb4f23

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

DC=sml,DC=com
HongKong\SMLAD2 via RPC
DC object GUID: 798e9d55-ed60-4054-ab63-357fd4201d0d
Last attempt @ 2008-06-05 14:48:24 failed, result 1722 (0x6ba):
The RPC server is unavailable.
11 consecutive failure(s).
Last success @ 2008-06-04 11:46:43.
China-DG\DGDC via RPC
DC object GUID: 329a41f6-c871-405d-a367-053fee1b014d
Last attempt @ 2008-06-05 14:48:24 was successful.
US\SMLUS-DC via RPC
DC object GUID: a912b38b-f595-46e7-933f-307ae944dd1a
Last attempt @ 2008-06-05 14:48:27 was successful.

CN=Configuration,DC=sml,DC=com
HongKong\SMLAD2 via RPC
DC object GUID: 798e9d55-ed60-4054-ab63-357fd4201d0d
Last attempt @ 2008-06-05 14:47:16 failed, result 1722 (0x6ba):
The RPC server is unavailable.
11 consecutive failure(s).
Last success @ 2008-06-04 11:46:42.
China-DG\DGDC via RPC
DC object GUID: 329a41f6-c871-405d-a367-053fee1b014d
Last attempt @ 2008-06-05 14:47:37 was successful.
US\SMLUS-DC via RPC
DC object GUID: a912b38b-f595-46e7-933f-307ae944dd1a
Last attempt @ 2008-06-05 14:47:41 was successful.

CN=Schema,CN=Configuration,DC=sml,DC=com
HongKong\SMLAD2 via RPC
DC object GUID: 798e9d55-ed60-4054-ab63-357fd4201d0d
Last attempt @ 2008-06-05 14:48:02 failed, result 1722 (0x6ba):
The RPC server is unavailable.
11 consecutive failure(s).
Last success @ 2008-06-04 11:46:42.
China-DG\DGDC via RPC
DC object GUID: 329a41f6-c871-405d-a367-053fee1b014d
Last attempt @ 2008-06-05 14:48:03 was successful.
US\SMLUS-DC via RPC
DC object GUID: a912b38b-f595-46e7-933f-307ae944dd1a
Last attempt @ 2008-06-05 14:48:03 was successful.

DC=DomainDnsZones,DC=sml,DC=com
HongKong\SMLAD2 via RPC
DC object GUID: 798e9d55-ed60-4054-ab63-357fd4201d0d
Last attempt @ 2008-06-05 14:47:16 failed, result 1256 (0x4e8):
The remote system is not available. For information about
network troubleshooting, see Windows Help.
11 consecutive failure(s).
Last success @ 2008-06-04 11:46:43.
China-DG\DGDC via RPC
DC object GUID: 329a41f6-c871-405d-a367-053fee1b014d
Last attempt @ 2008-06-05 14:48:27 was successful.
US\SMLUS-DC via RPC
DC object GUID: a912b38b-f595-46e7-933f-307ae944dd1a
Last attempt @ 2008-06-05 14:48:27 was successful.

DC=ForestDnsZones,DC=sml,DC=com
HongKong\SMLAD2 via RPC
DC object GUID: 798e9d55-ed60-4054-ab63-357fd4201d0d
Last attempt @ 2008-06-05 14:47:16 failed, result 1256 (0x4e8):
The remote system is not available. For information about
network troubleshooting, see Windows Help.
11 consecutive failure(s).
Last success @ 2008-06-04 11:46:44.
China-DG\DGDC via RPC
DC object GUID: 329a41f6-c871-405d-a367-053fee1b014d
Last attempt @ 2008-06-05 14:48:27 was successful.
US\SMLUS-DC via RPC
DC object GUID: a912b38b-f595-46e7-933f-307ae944dd1a
Last attempt @ 2008-06-05 14:48:27 was successful.

Source: HongKong\SMLAD2
******* 11 CONSECUTIVE FAILURES since 2008-06-04 11:46:44
Last error: 1256 (0x4e8):
The remote system is not available. For information about
network troubleshooting, see Windows Help.

Source: RPDI\MN-FS01
******* 4465 CONSECUTIVE FAILURES since 2008-04-10 10:38:12
Last error: 1722 (0x6ba):
The RPC server is unavailable.

Naming Context: CN=Configuration,DC=sml,DC=com
Source: RPDI\MN-FS01
******* WARNING: KCC could not add this REPLICA LINK due to error.

Naming Context: DC=ForestDnsZones,DC=sml,DC=com
Source: RPDI\MN-FS01
******* WARNING: KCC could not add this REPLICA LINK due to error.

Source: HongKong\SMLAD
******* 92 CONSECUTIVE FAILURES since 2008-06-04 13:55:52
Last error: -2146893022 (0x80090322):
The target principal name is incorrect.

Naming Context: DC=ForestDnsZones,DC=sml,DC=com
Source: HongKong\SMLAD
******* WARNING: KCC could not add this REPLICA LINK due to error.

Naming Context: CN=Configuration,DC=sml,DC=com
Source: HongKong\SMLAD
******* WARNING: KCC could not add this REPLICA LINK due to error.

Naming Context: DC=DomainDnsZones,DC=sml,DC=com
Source: HongKong\SMLAD
******* WARNING: KCC could not add this REPLICA LINK due to error.

Naming Context: DC=sml,DC=com
Source: HongKong\SMLAD
******* WARNING: KCC could not add this REPLICA LINK due to error.

Source: Thailand\SMLTHAI
******* 4457 CONSECUTIVE FAILURES since 2008-04-10 12:43:48
Last error: 1722 (0x6ba):
The RPC server is unavailable.

Naming Context: DC=ForestDnsZones,DC=sml,DC=com
Source: Thailand\SMLTHAI
******* WARNING: KCC could not add this REPLICA LINK due to error.

Naming Context: CN=Configuration,DC=sml,DC=com
Source: Thailand\SMLTHAI
******* WARNING: KCC could not add this REPLICA LINK due to error.

Source: Korea\SML
******* 4449 CONSECUTIVE FAILURES since 2008-04-10 14:56:05
Last error: 1722 (0x6ba):
The RPC server is unavailable.

Naming Context: DC=ForestDnsZones,DC=sml,DC=com
Source: Korea\SML
******* WARNING: KCC could not add this REPLICA LINK due to error.

Naming Context: CN=Configuration,DC=sml,DC=com
Source: Korea\SML
******* WARNING: KCC could not add this REPLICA LINK due to error.

Source: Vietnam\SMLVN-DC01
******* 4449 CONSECUTIVE FAILURES since 2008-04-10 14:55:44
Last error: 1722 (0x6ba):
The RPC server is unavailable.

Naming Context: DC=ForestDnsZones,DC=sml,DC=com
Source: Vietnam\SMLVN-DC01
******* WARNING: KCC could not add this REPLICA LINK due to error.

Naming Context: CN=Configuration,DC=sml,DC=com
Source: Vietnam\SMLVN-DC01
******* WARNING: KCC could not add this REPLICA LINK due to error.

Source: Vietnam\SMLVN-DC02
******* 4442 CONSECUTIVE FAILURES since 2008-04-10 16:59:38
Last error: 8524 (0x214c):
The DSA operation is unable to proceed because of a DNS lookup
failure.

Naming Context: DC=ForestDnsZones,DC=sml,DC=com
Source: Vietnam\SMLVN-DC02
******* WARNING: KCC could not add this REPLICA LINK due to error.

Naming Context: CN=Configuration,DC=sml,DC=com
Source: Vietnam\SMLVN-DC02
******* WARNING: KCC could not add this REPLICA LINK due to error.

Target Principal Name is incorrect	0	Aug 29, 2008
Logon Failure: The target account name is incorrect	2	Sep 8, 2006
Logon Failure: The target account name is incorrect.	3	Sep 8, 2006
Additional DC problem	3	May 22, 2004
Movetree error	2	Aug 10, 2005
Error on DC:The Target Principal Name is incorrect	1	Nov 30, 2004
"Target account name is incorrect"	2	Nov 3, 2003
NLB Server failed - Can't get AD active again.	1	May 10, 2004

Error " The Target principal name is incorrect"

Pcnetnet

Meinolf Weber

Pcnetnet

Meinolf Weber

Meinolf Weber

Ruchi Manuja

Pcnetnet

Meinolf Weber

pcnetnet

pcnetnet

pcnetnet

Ace Fekay [MVP]

pcnetnet

pcnetnet

pcnetnet

pcnetnet

pcnetnet

pcnetnet

pcnetnet

pcnetnet

Ask a Question

Similar Threads