DNS Server problem

  • Thread starter Thread starter Rich
  • Start date Start date
R

Rich

Hello,

Please pardon if this is not a DNS problem and I've posted to the wrong
list.

I have a small home win2k network with 2 DC's and a 3rd standalone server
and 1 XP desktop on a single subnet. I am trying to run dcpromo on the 2nd
DC to remove AD. I want to clean up/refresh AD/DNS due to some other
issues. When I try to remove AD, it fails with the following message:

The operation failed because:
Managing the network session with server01.mydomain.com failed
"Logon failure: The target account name is incorrect."

Can anyone help me figure this out?

TIA,
Rich
 
<snip>
I have a small home win2k network with 2 DC's and a 3rd standalone server
and 1 XP desktop on a single subnet. I am trying to run dcpromo on the 2nd
DC to remove AD. I want to clean up/refresh AD/DNS due to some other
issues. When I try to remove AD, it fails with the following message:

The operation failed because:
Managing the network session with server01.mydomain.com failed
"Logon failure: The target account name is incorrect."
<end snip>

I don't know if this is a DNS problem or not, many problems with AD are
caused by improper DNS configuration.
Your ipconfig /all should show only DNS servers that support the AD domain,
it should show the Primary DNS suffix, which must much match the DNS name of
the AD domain.
If your AD domain is a single-label name, your domain will have many
problems with communication and registration.
At this point I would recommend using netdiag and dcdiag to find problems
with your DCs. Simply removing AD then re-installing AD will not fix most
problems, unless replication has been broken for 60+ days. Uninstalling and
re-installing won't fix replication issues, you have to fix the cause of the
replication failures first.

Run these tests:
netdiag /fix
netdiag /v
dcdiag /fix
dcdiag /v
dcdiag /e /v

Look for errors in each of these, if you post back make sure you include the
ipconfig /all from the DCs.
 
Wow!!!

On the netdiag /g run, output below.

1. During the DNS portion of the output, there is a server there that has
been gone for a year. how do I get rid of this?

2. The server that I want to get rid of now, which is my 2nd DC is there.

3. There are a lot of errors related to my DSL modem/router which is a 2nd
DNS server on my network. I thought I needed this to resolve names on the
internet. I'm 80% sure my internal DNS is config'd to fwd. requests to
that device.

4. What do I do???




Kevin D. Goodknecht Sr. said:
<snip>
I have a small home win2k network with 2 DC's and a 3rd standalone server
and 1 XP desktop on a single subnet. I am trying to run dcpromo on the 2nd
DC to remove AD. I want to clean up/refresh AD/DNS due to some other
issues. When I try to remove AD, it fails with the following message:

The operation failed because:
Managing the network session with server01.mydomain.com failed
"Logon failure: The target account name is incorrect."
<end snip>

I don't know if this is a DNS problem or not, many problems with AD are
caused by improper DNS configuration.
Your ipconfig /all should show only DNS servers that support the AD domain,
it should show the Primary DNS suffix, which must much match the DNS name of
the AD domain.
If your AD domain is a single-label name, your domain will have many
problems with communication and registration.
At this point I would recommend using netdiag and dcdiag to find problems
with your DCs. Simply removing AD then re-installing AD will not fix most
problems, unless replication has been broken for 60+ days. Uninstalling and
re-installing won't fix replication issues, you have to fix the cause of the
replication failures first.

Run these tests:
netdiag /fix
netdiag /v
dcdiag /fix
dcdiag /v
dcdiag /e /v

Look for errors in each of these, if you post back make sure you include the
ipconfig /all from the DCs.



***********************************************************************
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

Sending name query to primary WINS server 192.168.1.51 - Passed

There is no secondary WINS server defined for this adapter.

Gathering Winsock information.

Testing DNS

The DNS registration for server01.RPS.COM is correct on all DNS servers

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

[WARNING] The DNS entries for this DC are not registered correctly on DNS
server '192.168.1.254'. Please wait for 30 minutes for DNS server
replication.

Testing redirector and browser... Passed

Testing DC discovery.

Looking for a DC

Looking for a PDC emulator

Looking for a Windows 2000 DC

Gathering the list of Domain Controllers for domain 'RPS'

Testing trust relationships... Skipped

Testing Kerberos authentication... Passed

Testing LDAP servers in Domain RPS ...

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: SERVER01

DNS Host Name: server01.RPS.COM

DNS Domain Name: RPS.COM

System info : Windows 2000 Server (Build 2195)

Processor : x86 Family 6 Model 8 Stepping 10, GenuineIntel

Hotfixes :

Installed? Name

Yes Q147222



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

Information of Netcard drivers:

---------------------------------------------------------------------------

Description: D-Link DFE-530TX+ PCI Adapter

Device: \DEVICE\{2C908C56-C45C-4FF0-AE34-6B0E2022D3C7}

Media State: Connected

Device State: Connected

Connect Time: 23 days, 11:52:38

Media Speed: 100 Mbps

Packets Sent: 707123

Bytes Sent (Optional): 0

Packets Received: 1335541

Directed Pkts Recd (Optional): 573506

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 . . . . . . . . : {2C908C56-C45C-4FF0-AE34-6B0E2022D3C7}

Netcard queries test . . . : Passed

Adapter type . . . . . . . : Ethernet

Host Name. . . . . . . . . : server01

Description. . . . . . . . : D-Link DFE-530TX+ PCI Adapter

Physical Address . . . . . : 00-0D-88-22-0E-07

Dhcp Enabled . . . . . . . : No

DHCP ClassID . . . . . . . :

Autoconfiguration Enabled. : Yes

IP Address . . . . . . . . : 192.168.1.51

Subnet Mask. . . . . . . . : 255.255.255.0

Default Gateway. . . . . . : 192.168.1.254

Primary WINS Server. . . . : 192.168.1.51

Dns Servers. . . . . . . . : 192.168.1.51

192.168.1.254

IpConfig results . . . . . : Passed

Pinging the Primary WINS server 192.168.1.51 - reachable

AutoConfiguration results. . . . . . : Passed

AutoConfiguration is not in use.

Default gateway test . . . : Passed

Pinging gateway 192.168.1.254 - reachable

At least one gateway reachable for this adapter.

NetBT name test. . . . . . : Passed

NetBT_Tcpip_{2C908C56-C45C-4FF0-AE34-6B0E2022D3C7}

SERVER01 <00> UNIQUE REGISTERED

SERVER01 <20> UNIQUE REGISTERED

RPS <00> GROUP REGISTERED

RPS <1C> GROUP REGISTERED

RPS <1B> UNIQUE REGISTERED

RPS <1E> GROUP REGISTERED

SERVER01 <03> UNIQUE REGISTERED

RPS <1D> UNIQUE REGISTERED

...__MSBROWSE__.<01> GROUP REGISTERED

INet~Services <1C> GROUP REGISTERED

IS~SERVER01....<00> UNIQUE REGISTERED

SERVER01 <BE> UNIQUE REGISTERED

RKS <03> UNIQUE REGISTERED

NetBios Resolution : Enabled

Netbios Remote Cache Table

Name Type HostAddress Life [sec]

---------------------------------------------------------------

RPS <1C> GROUP 192.168.1.51 562

BOTH <20> UNIQUE 192.168.1.5 565



WINS service test. . . . . : Passed

Sending name query to primary WINS server 192.168.1.51 - 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. . . . . . . . . . . : Hybrid

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. . . . . . : RPS

Dns domain name. . . . . . . . : RPS.COM

Dns forest name. . . . . . . . : RPS.COM

Domain Guid. . . . . . . . . . : {FAE75F8B-11AA-48B6-974A-B1DD9FF77074}

Domain Sid . . . . . . . . . . : S-1-5-21-796845957-179605362-725345543

Logon User . . . . . . . . . . : rks

Logon Domain . . . . . . . . . : RPS



NetBT transports test. . . . . . . : Passed

List of NetBt transports currently configured:

NetBT_Tcpip_{2C908C56-C45C-4FF0-AE34-6B0E2022D3C7}

1 NetBt transport currently configured.



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

PASS - you have at least one non-autoconfigured IP address



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

PASS - pinging IP loopback address was successful.

Your IP stack is most probably OK.



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

PASS - you have at least one reachable gateway.



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

No NetBT scope defined

PASS - The NetBT is properly configured.

There is at least one interface where the <00> 'WorkStation Service',

<03> 'Messenger Service', <20> 'WINS' names are defined and they are

not in conflict.



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

The number of protocols which have been reported : 10

Description: MSAFD Tcpip [TCP/IP]

Provider Version :2

Max message size : Stream Oriented

Description: MSAFD Tcpip [UDP/IP]

Provider Version :2

Description: RSVP UDP Service Provider

Provider Version :4

Description: RSVP TCP Service Provider

Provider Version :4

Max message size : Stream Oriented

Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{2C908C56-C45C-4FF0-AE34-6B0E2022D3C7}] SEQPACKET 0

Provider Version :2

Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{2C908C56-C45C-4FF0-AE34-6B0E2022D3C7}] DATAGRAM 0

Provider Version :2

Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{85B3EF21-86FE-444E-A593-7187DABCB51F}] SEQPACKET 1

Provider Version :2

Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{85B3EF21-86FE-444E-A593-7187DABCB51F}] DATAGRAM 1

Provider Version :2

Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{BF1769A0-3F65-472B-B297-10BC5F3D448B}] SEQPACKET 2

Provider Version :2

Description: MSAFD NetBIOS
[\Device\NetBT_Tcpip_{BF1769A0-3F65-472B-B297-10BC5F3D448B}] DATAGRAM 2

Provider Version :2

Max UDP size : 65507 bytes



DNS test . . . . . . . . . . . . . : Passed

Interface {2C908C56-C45C-4FF0-AE34-6B0E2022D3C7}

DNS Domain:

DNS Servers: 192.168.1.51 192.168.1.254

IP Address: 192.168.1.51

Expected registration with PDN (primary DNS domain name):

Hostname: server01.RPS.COM.

Authoritative zone: RPS.COM.

Primary DNS server: server01.RPS.COM 192.168.1.51

Authoritative NS:192.168.1.51

Verify DNS registration:

Name: server01.RPS.COM

Expected IP: 192.168.1.51

Server 192.168.1.51: NO_ERROR

The DNS registration for server01.RPS.COM is correct on all DNS servers

Check the DNS registration for DCs entries on DNS server '192.168.1.51'

The Record is different on DNS server '192.168.1.51'.

DNS server has more than one entries for this name, usually this means there
are multiple DCs for this domain.

Your DC entry is one of them on DNS server '192.168.1.51', no need to
re-register.

+------------------------------------------------------+

The record on your DC is:

DNS NAME = _ldap._tcp.RPS.COM.

DNS DATA =

SRV 0 100 389 server01.RPS.COM.

The record on DNS server 192.168.1.51 is:

DNS NAME = _ldap._tcp.RPS.COM

DNS DATA =

SRV 0 100 389 both.rps.com

SRV 0 100 389 server01.rps.com

+------------------------------------------------------+

The Record is different on DNS server '192.168.1.51'.

DNS server has more than one entries for this name, usually this means there
are multiple DCs for this domain.

Your DC entry is one of them on DNS server '192.168.1.51', no need to
re-register.

+------------------------------------------------------+

The record on your DC is:

DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.RPS.COM.

DNS DATA =

SRV 0 100 389 server01.RPS.COM.

The record on DNS server 192.168.1.51 is:

DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.RPS.COM

DNS DATA =

SRV 0 100 389 both.rps.com

SRV 0 100 389 server01.rps.com

+------------------------------------------------------+

The Record is correct on DNS server '192.168.1.51'.

The Record is correct on DNS server '192.168.1.51'.

The Record is correct on DNS server '192.168.1.51'.

The Record is different on DNS server '192.168.1.51'.

DNS server has more than one entries for this name, usually this means there
are multiple DCs for this domain.

Your DC entry is one of them on DNS server '192.168.1.51', no need to
re-register.

+------------------------------------------------------+

The record on your DC is:

DNS NAME =
_ldap._tcp.fae75f8b-11aa-48b6-974a-b1dd9ff77074.domains._msdcs.RPS.COM.

DNS DATA =

SRV 0 100 389 server01.RPS.COM.

The record on DNS server 192.168.1.51 is:

DNS NAME =
_ldap._tcp.fae75f8b-11aa-48b6-974a-b1dd9ff77074.domains._msdcs.RPS.COM

DNS DATA =

SRV 0 100 389 both.rps.com

SRV 0 100 389 server01.rps.com

SRV 0 100 389 server02.rps.com

+------------------------------------------------------+

The Record is correct on DNS server '192.168.1.51'.

The Record is different on DNS server '192.168.1.51'.

DNS server has more than one entries for this name, usually this means there
are multiple DCs for this domain.

Your DC entry is one of them on DNS server '192.168.1.51', no need to
re-register.

+------------------------------------------------------+

The record on your DC is:

DNS NAME = _kerberos._tcp.dc._msdcs.RPS.COM.

DNS DATA =

SRV 0 100 88 server01.RPS.COM.

The record on DNS server 192.168.1.51 is:

DNS NAME = _kerberos._tcp.dc._msdcs.RPS.COM

DNS DATA =

SRV 0 100 88 both.rps.com

SRV 0 100 88 server01.rps.com

SRV 0 100 88 server02.rps.com

+------------------------------------------------------+

The Record is different on DNS server '192.168.1.51'.

DNS server has more than one entries for this name, usually this means there
are multiple DCs for this domain.

Your DC entry is one of them on DNS server '192.168.1.51', no need to
re-register.

+------------------------------------------------------+

The record on your DC is:

DNS NAME = _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.RPS.COM.

DNS DATA =

SRV 0 100 88 server01.RPS.COM.

The record on DNS server 192.168.1.51 is:

DNS NAME = _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.RPS.COM

DNS DATA =

SRV 0 100 88 both.rps.com

SRV 0 100 88 server01.rps.com

+------------------------------------------------------+

The Record is different on DNS server '192.168.1.51'.

DNS server has more than one entries for this name, usually this means there
are multiple DCs for this domain.

Your DC entry is one of them on DNS server '192.168.1.51', no need to
re-register.

+------------------------------------------------------+

The record on your DC is:

DNS NAME = _ldap._tcp.dc._msdcs.RPS.COM.

DNS DATA =

SRV 0 100 389 server01.RPS.COM.

The record on DNS server 192.168.1.51 is:

DNS NAME = _ldap._tcp.dc._msdcs.RPS.COM

DNS DATA =

SRV 0 100 389 both.rps.com

SRV 0 100 389 server01.rps.com

+------------------------------------------------------+

The Record is different on DNS server '192.168.1.51'.

DNS server has more than one entries for this name, usually this means there
are multiple DCs for this domain.

Your DC entry is one of them on DNS server '192.168.1.51', no need to
re-register.

+------------------------------------------------------+

The record on your DC is:

DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.RPS.COM.

DNS DATA =

SRV 0 100 389 server01.RPS.COM.

The record on DNS server 192.168.1.51 is:

DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.RPS.COM

DNS DATA =

SRV 0 100 389 both.rps.com

SRV 0 100 389 server01.rps.com

+------------------------------------------------------+

The Record is different on DNS server '192.168.1.51'.

DNS server has more than one entries for this name, usually this means there
are multiple DCs for this domain.

Your DC entry is one of them on DNS server '192.168.1.51', no need to
re-register.

+------------------------------------------------------+

The record on your DC is:

DNS NAME = _kerberos._tcp.RPS.COM.

DNS DATA =

SRV 0 100 88 server01.RPS.COM.

The record on DNS server 192.168.1.51 is:

DNS NAME = _kerberos._tcp.RPS.COM

DNS DATA =

SRV 0 100 88 both.rps.com

SRV 0 100 88 server01.rps.com

+------------------------------------------------------+

The Record is different on DNS server '192.168.1.51'.

DNS server has more than one entries for this name, usually this means there
are multiple DCs for this domain.

Your DC entry is one of them on DNS server '192.168.1.51', no need to
re-register.

+------------------------------------------------------+

The record on your DC is:

DNS NAME = _kerberos._tcp.Default-First-Site-Name._sites.RPS.COM.

DNS DATA =

SRV 0 100 88 server01.RPS.COM.

The record on DNS server 192.168.1.51 is:

DNS NAME = _kerberos._tcp.Default-First-Site-Name._sites.RPS.COM

DNS DATA =

SRV 0 100 88 both.rps.com

SRV 0 100 88 server01.rps.com

+------------------------------------------------------+

The Record is correct on DNS server '192.168.1.51'.

The Record is correct on DNS server '192.168.1.51'.

The Record is different on DNS server '192.168.1.51'.

DNS server has more than one entries for this name, usually this means there
are multiple DCs for this domain.

Your DC entry is one of them on DNS server '192.168.1.51', no need to
re-register.

+------------------------------------------------------+

The record on your DC is:

DNS NAME = _kerberos._udp.RPS.COM.

DNS DATA =

SRV 0 100 88 server01.RPS.COM.

The record on DNS server 192.168.1.51 is:

DNS NAME = _kerberos._udp.RPS.COM

DNS DATA =

SRV 0 100 88 both.rps.com

SRV 0 100 88 server01.rps.com

+------------------------------------------------------+

The Record is different on DNS server '192.168.1.51'.

DNS server has more than one entries for this name, usually this means there
are multiple DCs for this domain.

Your DC entry is one of them on DNS server '192.168.1.51', no need to
re-register.

+------------------------------------------------------+

The record on your DC is:

DNS NAME = _kpasswd._tcp.RPS.COM.

DNS DATA =

SRV 0 100 464 server01.RPS.COM.

The record on DNS server 192.168.1.51 is:

DNS NAME = _kpasswd._tcp.RPS.COM

DNS DATA =

SRV 0 100 464 both.rps.com

SRV 0 100 464 server01.rps.com

+------------------------------------------------------+

The Record is different on DNS server '192.168.1.51'.

DNS server has more than one entries for this name, usually this means there
are multiple DCs for this domain.

Your DC entry is one of them on DNS server '192.168.1.51', no need to
re-register.

+------------------------------------------------------+

The record on your DC is:

DNS NAME = _kpasswd._udp.RPS.COM.

DNS DATA =

SRV 0 100 464 server01.RPS.COM.

The record on DNS server 192.168.1.51 is:

DNS NAME = _kpasswd._udp.RPS.COM

DNS DATA =

SRV 0 100 464 both.rps.com

SRV 0 100 464 server01.rps.com

+------------------------------------------------------+

The Record is different on DNS server '192.168.1.51'.

DNS server has more than one entries for this name, usually this means there
are multiple DCs for this domain.

Your DC entry is one of them on DNS server '192.168.1.51', no need to
re-register.

+------------------------------------------------------+

The record on your DC is:

DNS NAME = RPS.COM.

DNS DATA =

A 192.168.1.51

The record on DNS server 192.168.1.51 is:

DNS NAME = RPS.COM

DNS DATA =

A 192.168.1.51

A 192.168.1.0

A 192.168.1.5

+------------------------------------------------------+

The Record is different on DNS server '192.168.1.51'.

DNS server has more than one entries for this name, usually this means there
are multiple DCs for this domain.

Your DC entry is one of them on DNS server '192.168.1.51', no need to
re-register.

+------------------------------------------------------+

The record on your DC is:

DNS NAME = gc._msdcs.RPS.COM.

DNS DATA =

A 192.168.1.51

The record on DNS server 192.168.1.51 is:

DNS NAME = gc._msdcs.RPS.COM

DNS DATA =

A 192.168.1.51

A 192.168.1.45

A 192.168.168.3

+------------------------------------------------------+

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

Check the DNS registration for DCs entries on DNS server '192.168.1.254'

Query for DC DNS entry _ldap._tcp.RPS.COM. on DNS server 192.168.1.254
failed.

DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)

Query for DC DNS entry _ldap._tcp.Default-First-Site-Name._sites.RPS.COM. on
DNS server 192.168.1.254 failed.

DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)

Query for DC DNS entry _ldap._tcp.pdc._msdcs.RPS.COM. on DNS server
192.168.1.254 failed.

DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)

Query for DC DNS entry _ldap._tcp.gc._msdcs.RPS.COM. on DNS server
192.168.1.254 failed.

DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)

Query for DC DNS entry
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.RPS.COM. on DNS server
192.168.1.254 failed.

DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)

Query for DC DNS entry
_ldap._tcp.fae75f8b-11aa-48b6-974a-b1dd9ff77074.domains._msdcs.RPS.COM. on
DNS server 192.168.1.254 failed.

DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)

Query for DC DNS entry 409d51ef-1173-4ad0-ac0f-9d169d60a3b1._msdcs.RPS.COM.
on DNS server 192.168.1.254 failed.

DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)

Query for DC DNS entry _kerberos._tcp.dc._msdcs.RPS.COM. on DNS server
192.168.1.254 failed.

DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)

Query for DC DNS entry
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.RPS.COM. on DNS
server 192.168.1.254 failed.

DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)

Query for DC DNS entry _ldap._tcp.dc._msdcs.RPS.COM. on DNS server
192.168.1.254 failed.

DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)

Query for DC DNS entry
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.RPS.COM. on DNS server
192.168.1.254 failed.

DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)

Query for DC DNS entry _kerberos._tcp.RPS.COM. on DNS server 192.168.1.254
failed.

DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)

Query for DC DNS entry
_kerberos._tcp.Default-First-Site-Name._sites.RPS.COM. on DNS server
192.168.1.254 failed.

DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)

Query for DC DNS entry _gc._tcp.RPS.COM. on DNS server 192.168.1.254 failed.

DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)

Query for DC DNS entry _gc._tcp.Default-First-Site-Name._sites.RPS.COM. on
DNS server 192.168.1.254 failed.

DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)

Query for DC DNS entry _kerberos._udp.RPS.COM. on DNS server 192.168.1.254
failed.

DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)

Query for DC DNS entry _kpasswd._tcp.RPS.COM. on DNS server 192.168.1.254
failed.

DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)

Query for DC DNS entry _kpasswd._udp.RPS.COM. on DNS server 192.168.1.254
failed.

DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)

The Record is different on DNS server '192.168.1.254'.

+------------------------------------------------------+

The record on your DC is:

DNS NAME = RPS.COM.

DNS DATA =

A 192.168.1.51

The record on DNS server 192.168.1.254 is:

DNS NAME = RPS.COM

DNS DATA =

A 199.46.198.87

A 199.46.199.88

+------------------------------------------------------+

Query for DC DNS entry gc._msdcs.RPS.COM. on DNS server 192.168.1.254
failed.

DNS Error code: DNS_ERROR_RCODE_NAME_ERROR (Name does not exist on DNS
server)

[WARNING] The DNS entries for this DC are not registered correctly on DNS
server '192.168.1.254'. Please wait for 30 minutes for DNS server
replication.



Redir and Browser test . . . . . . : Passed

List of transports currently bound to the Redir

NetbiosSmb

NetBT_Tcpip_{2C908C56-C45C-4FF0-AE34-6B0E2022D3C7}

The redir is bound to 1 NetBt transport.

List of transports currently bound to the browser

NetBT_Tcpip_{2C908C56-C45C-4FF0-AE34-6B0E2022D3C7}

The browser is bound to 1 NetBt transport.

Mailslot test for RPS* passed.



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

Find DC in domain 'RPS':

Found this DC in domain 'RPS':

DC. . . . . . . . . . . : \\server01.RPS.COM

Address . . . . . . . . : \\192.168.1.51

Domain Guid . . . . . . : {FAE75F8B-11AA-48B6-974A-B1DD9FF77074}

Domain Name . . . . . . : RPS.COM

Forest Name . . . . . . : RPS.COM

DC Site Name. . . . . . : Default-First-Site-Name

Our Site Name . . . . . : Default-First-Site-Name

Flags . . . . . . . . . : PDC emulator GC DS KDC TIMESERV WRITABLE DNS_DC
DNS_DOMAIN DNS_FOREST CLOSE_SITE 0x8

Find PDC emulator in domain 'RPS':

Found this PDC emulator in domain 'RPS':

DC. . . . . . . . . . . : \\server01.RPS.COM

Address . . . . . . . . : \\192.168.1.51

Domain Guid . . . . . . : {FAE75F8B-11AA-48B6-974A-B1DD9FF77074}

Domain Name . . . . . . : RPS.COM

Forest Name . . . . . . : RPS.COM

DC Site Name. . . . . . : Default-First-Site-Name

Our Site Name . . . . . : Default-First-Site-Name

Flags . . . . . . . . . : PDC emulator GC DS KDC TIMESERV WRITABLE DNS_DC
DNS_DOMAIN DNS_FOREST CLOSE_SITE 0x8

Find Windows 2000 DC in domain 'RPS':

Found this Windows 2000 DC in domain 'RPS':

DC. . . . . . . . . . . : \\server01.RPS.COM

Address . . . . . . . . : \\192.168.1.51

Domain Guid . . . . . . : {FAE75F8B-11AA-48B6-974A-B1DD9FF77074}

Domain Name . . . . . . : RPS.COM

Forest Name . . . . . . : RPS.COM

DC Site Name. . . . . . : Default-First-Site-Name

Our Site Name . . . . . : Default-First-Site-Name

Flags . . . . . . . . . : PDC emulator GC DS KDC TIMESERV WRITABLE DNS_DC
DNS_DOMAIN DNS_FOREST CLOSE_SITE 0x8



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

List of DCs in Domain 'RPS':

server01.RPS.COM

both.RPS.COM (this DC is down)



Trust relationship test. . . . . . : Skipped



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

Cached Tickets:

Server: krbtgt/RPS.COM

End Time: 1/14/2006 10:54:20

Renew Time: 1/21/2006 0:54:20

Server: krbtgt/RPS.COM

End Time: 1/14/2006 2:00:27

Renew Time: 1/20/2006 16:00:27

Server: SERVER01$

End Time: 1/14/2006 10:54:20

Renew Time: 1/21/2006 0:54:20

Server: ldap/server01.RPS.COM/RPS.COM

End Time: 1/14/2006 2:00:27

Renew Time: 1/20/2006 16:00:27

Server: BOTH$

End Time: 1/12/2006 4:08:25

Renew Time: 1/18/2006 18:08:25



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

Do un-authenticated LDAP call to 'server01.RPS.COM'.

Found 1 entries:

Attr: currentTime

Val: 17 20060114055549.0Z

Attr: subschemaSubentry

Val: 53 CN=Aggregate,CN=Schema,CN=Configuration,DC=RPS,DC=com

Attr: dsServiceName

Val: 106 CN=NTDS
Settings,CN=SERVER01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi
guration,DC=RPS,DC=com

Attr: namingContexts

Val: 40 CN=Schema,CN=Configuration,DC=RPS,DC=com

Val: 30 CN=Configuration,DC=RPS,DC=com

Val: 13 DC=RPS,DC=com

Attr: defaultNamingContext

Val: 13 DC=RPS,DC=com

Attr: schemaNamingContext

Val: 40 CN=Schema,CN=Configuration,DC=RPS,DC=com

Attr: configurationNamingContext

Val: 30 CN=Configuration,DC=RPS,DC=com

Attr: rootDomainNamingContext

Val: 13 DC=RPS,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

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: 16 MaxActiveQueries

Val: 11 MaxPageSize

Val: 16 MaxQueryDuration

Val: 16 MaxTempTableSize

Val: 16 MaxResultSetSize

Val: 22 MaxNotificationPerConn

Attr: highestCommittedUSN

Val: 6 126092

Attr: supportedSASLMechanisms

Val: 6 GSSAPI

Val: 10 GSS-SPNEGO

Attr: dnsHostName

Val: 16 server01.RPS.COM

Attr: ldapServiceName

Val: 25 RPS.COM:[email protected]

Attr: serverName

Val: 89
CN=SERVER01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,
DC=RPS,DC=com

Attr: supportedCapabilities

Val: 22 1.2.840.113556.1.4.800

Val: 23 1.2.840.113556.1.4.1791

Attr: isSynchronized

Val: 4 TRUE

Attr: isGlobalCatalogReady

Val: 4 TRUE

Do NTLM authenticated LDAP call to 'server01.RPS.COM'.

Found 1 entries:

Attr: currentTime

Val: 17 20060114055549.0Z

Attr: subschemaSubentry

Val: 53 CN=Aggregate,CN=Schema,CN=Configuration,DC=RPS,DC=com

Attr: dsServiceName

Val: 106 CN=NTDS
Settings,CN=SERVER01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi
guration,DC=RPS,DC=com

Attr: namingContexts

Val: 40 CN=Schema,CN=Configuration,DC=RPS,DC=com

Val: 30 CN=Configuration,DC=RPS,DC=com

Val: 13 DC=RPS,DC=com

Attr: defaultNamingContext

Val: 13 DC=RPS,DC=com

Attr: schemaNamingContext

Val: 40 CN=Schema,CN=Configuration,DC=RPS,DC=com

Attr: configurationNamingContext

Val: 30 CN=Configuration,DC=RPS,DC=com

Attr: rootDomainNamingContext

Val: 13 DC=RPS,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

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: 16 MaxActiveQueries

Val: 11 MaxPageSize

Val: 16 MaxQueryDuration

Val: 16 MaxTempTableSize

Val: 16 MaxResultSetSize

Val: 22 MaxNotificationPerConn

Attr: highestCommittedUSN

Val: 6 126092

Attr: supportedSASLMechanisms

Val: 6 GSSAPI

Val: 10 GSS-SPNEGO

Attr: dnsHostName

Val: 16 server01.RPS.COM

Attr: ldapServiceName

Val: 25 RPS.COM:[email protected]

Attr: serverName

Val: 89
CN=SERVER01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,
DC=RPS,DC=com

Attr: supportedCapabilities

Val: 22 1.2.840.113556.1.4.800

Val: 23 1.2.840.113556.1.4.1791

Attr: isSynchronized

Val: 4 TRUE

Attr: isGlobalCatalogReady

Val: 4 TRUE

Do Negotiate authenticated LDAP call to 'server01.RPS.COM'.

Found 1 entries:

Attr: currentTime

Val: 17 20060114055549.0Z

Attr: subschemaSubentry

Val: 53 CN=Aggregate,CN=Schema,CN=Configuration,DC=RPS,DC=com

Attr: dsServiceName

Val: 106 CN=NTDS
Settings,CN=SERVER01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Confi
guration,DC=RPS,DC=com

Attr: namingContexts

Val: 40 CN=Schema,CN=Configuration,DC=RPS,DC=com

Val: 30 CN=Configuration,DC=RPS,DC=com

Val: 13 DC=RPS,DC=com

Attr: defaultNamingContext

Val: 13 DC=RPS,DC=com

Attr: schemaNamingContext

Val: 40 CN=Schema,CN=Configuration,DC=RPS,DC=com

Attr: configurationNamingContext

Val: 30 CN=Configuration,DC=RPS,DC=com

Attr: rootDomainNamingContext

Val: 13 DC=RPS,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

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: 16 MaxActiveQueries

Val: 11 MaxPageSize

Val: 16 MaxQueryDuration

Val: 16 MaxTempTableSize

Val: 16 MaxResultSetSize

Val: 22 MaxNotificationPerConn

Attr: highestCommittedUSN

Val: 6 126092

Attr: supportedSASLMechanisms

Val: 6 GSSAPI

Val: 10 GSS-SPNEGO

Attr: dnsHostName

Val: 16 server01.RPS.COM

Attr: ldapServiceName

Val: 25 RPS.COM:[email protected]

Attr: serverName

Val: 89
CN=SERVER01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,
DC=RPS,DC=com

Attr: supportedCapabilities

Val: 22 1.2.840.113556.1.4.800

Val: 23 1.2.840.113556.1.4.1791

Attr: isSynchronized

Val: 4 TRUE

Attr: isGlobalCatalogReady

Val: 4 TRUE

Registered Service Principal Names:

SMTPSVC/SERVER01

SMTPSVC/server01.RPS.COM

NtFrs-88f5d2bd-b646-11d2-a6d3-00c04fc9b232/server01.RPS.COM

DNS/server01.RPS.COM

GC/server01.RPS.COM/RPS.COM

HOST/server01.RPS.COM/RPS

HOST/SERVER01

HOST/server01.RPS.COM

HOST/server01.RPS.COM/RPS.com

E3514235-4B06-11D1-AB04-00C04FC2DCD2/409d51ef-1173-4ad0-ac0f-9d169d60a3b1/RP
S.com

LDAP/409d51ef-1173-4ad0-ac0f-9d169d60a3b1._msdcs.RPS.COM

LDAP/server01.RPS.COM/RPS

LDAP/SERVER01

LDAP/server01.RPS.COM

LDAP/server01.RPS.COM/RPS.com

Since 'both.RPS.COM' is down, it cannot be tested.

[WARNING] Failed to query SPN registration on DC 'both.RPS.COM'.



Routing table test . . . . . . . . : Passed

Active Routes :

Network Destination Netmask Gateway Interface Metric

0.0.0.0 0.0.0.0 192.168.1.254 192.168.1.51 1

127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1

192.168.1.0 255.255.255.0 192.168.1.51 192.168.1.51 1

192.168.1.51 255.255.255.255 127.0.0.1 127.0.0.1 1

192.168.1.255 255.255.255.255 192.168.1.51 192.168.1.51 1

224.0.0.0 224.0.0.0 192.168.1.51 192.168.1.51 1

255.255.255.255 255.255.255.255 192.168.1.51 192.168.1.51 1

No persistent route entries.



Netstat information test . . . . . : Passed



Interface Statistics

Received Sent

Unicast Packets 718135479 554471749

Non-unicast packets 849342 87308

Discards 0 0

Errors 0 0

Unknown protocols 0 457224

Interface index = 1

Description = MS TCP Loopback interface

Type = 24

MTU = 1500

Speed = 10000000

Physical Address = 00-00-00-00-00-00

Administrative Status = 1

Operational Status = 1

Last Changed = 2360891477

Output Queue Length = 0



Interface index = 16777219

Description = D-Link DFE-530TX+ PCI Adapter

Type = 6

MTU = 1500

Speed = 100000000

Physical Address = 00-0D-88-22-0E-07

Administrative Status = 1

Operational Status = 1

Last Changed = 2360891483

Output Queue Length = 0





Active Connections

Proto Local Address Foreign Address State

TCP server01:smtp server01.RPS.COM:10346 LISTENING

TCP server01:nameserver server01.RPS.COM:34988 LISTENING

TCP server01:domain server01.RPS.COM:43011 LISTENING

TCP server01:http server01.RPS.COM:34882 LISTENING

TCP server01:kerberos server01.RPS.COM:18484 LISTENING

TCP server01:epmap server01.RPS.COM:2080 LISTENING

TCP server01:ldap server01.RPS.COM:51382 LISTENING

TCP server01:https server01.RPS.COM:34982 LISTENING

TCP server01:microsoft-ds server01.RPS.COM:43019 LISTENING

TCP server01:kpasswd server01.RPS.COM:18686 LISTENING

TCP server01:593 server01.RPS.COM:10343 LISTENING

TCP server01:ldaps server01.RPS.COM:10379 LISTENING

TCP server01:1026 server01.RPS.COM:43218 LISTENING

TCP server01:1029 server01.RPS.COM:2198 LISTENING

TCP server01:1043 server01.RPS.COM:2081 LISTENING

TCP server01:1061 server01.RPS.COM:18516 LISTENING

TCP server01:1062 server01.RPS.COM:2122 LISTENING

TCP server01:1063 server01.RPS.COM:2064 LISTENING

TCP server01:1067 server01.RPS.COM:2058 LISTENING

TCP server01:1129 server01.RPS.COM:18638 LISTENING

TCP server01:1133 server01.RPS.COM:43061 LISTENING

TCP server01:1146 server01.RPS.COM:2048 LISTENING

TCP server01:1171 server01.RPS.COM:2132 LISTENING

TCP server01:1194 server01.RPS.COM:35065 LISTENING

TCP server01:1196 server01.RPS.COM:43133 LISTENING

TCP server01:1220 server01.RPS.COM:18554 LISTENING

TCP server01:1227 server01.RPS.COM:18542 LISTENING

TCP server01:1229 server01.RPS.COM:10248 LISTENING

TCP server01:1269 server01.RPS.COM:2080 LISTENING

TCP server01:1334 server01.RPS.COM:26756 LISTENING

TCP server01:1448 server01.RPS.COM:10483 LISTENING

TCP server01:1457 server01.RPS.COM:34839 LISTENING

TCP server01:1682 server01.RPS.COM:43163 LISTENING

TCP server01:1689 server01.RPS.COM:2126 LISTENING

TCP server01:1690 server01.RPS.COM:43195 LISTENING

TCP server01:1755 server01.RPS.COM:10460 LISTENING

TCP server01:1774 server01.RPS.COM:10268 LISTENING

TCP server01:1775 server01.RPS.COM:43131 LISTENING

TCP server01:1918 server01.RPS.COM:59612 LISTENING

TCP server01:2662 server01.RPS.COM:18590 LISTENING

TCP server01:3268 server01.RPS.COM:2208 LISTENING

TCP server01:3269 server01.RPS.COM:26743 LISTENING

TCP server01:3372 server01.RPS.COM:10377 LISTENING

TCP server01:3389 server01.RPS.COM:2058 LISTENING

TCP server01:6101 server01.RPS.COM:34824 LISTENING

TCP server01:6666 server01.RPS.COM:18602 LISTENING

TCP server01:7007 server01.RPS.COM:34950 LISTENING

TCP server01:7778 server01.RPS.COM:59479 LISTENING

TCP server01:9305 server01.RPS.COM:51267 LISTENING

TCP server01:ldap server01.RPS.COM:1061 ESTABLISHED

TCP server01:ldap server01.RPS.COM:1062 ESTABLISHED

TCP server01:ldap server01.RPS.COM:1067 ESTABLISHED

TCP server01:ldap server01.RPS.COM:1689 ESTABLISHED

TCP server01:1061 server01.RPS.COM:ldap ESTABLISHED

TCP server01:1062 server01.RPS.COM:ldap ESTABLISHED

TCP server01:1067 server01.RPS.COM:ldap ESTABLISHED

TCP server01:1171 server01.RPS.COM:ldap CLOSE_WAIT

TCP server01:1448 server01.RPS.COM:ldap CLOSE_WAIT

TCP server01:1689 server01.RPS.COM:ldap ESTABLISHED

TCP server01:netbios-ssn server01.RPS.COM:43243 LISTENING

TCP server01:ldap server01.RPS.COM:1690 ESTABLISHED

TCP server01:ldap server01.RPS.COM:1771 TIME_WAIT

TCP server01:ldap server01.RPS.COM:1772 TIME_WAIT

TCP server01:ldap server01.RPS.COM:1839 TIME_WAIT

TCP server01:ldap server01.RPS.COM:1840 TIME_WAIT

TCP server01:ldap server01.RPS.COM:1844 TIME_WAIT

TCP server01:ldap server01.RPS.COM:1916 TIME_WAIT

TCP server01:ldap server01.RPS.COM:1917 TIME_WAIT

TCP server01:ldap server01.RPS.COM:1918 ESTABLISHED

TCP server01:ldap server01.RPS.COM:1919 TIME_WAIT

TCP server01:1026 IS~BOTH:2598 TIME_WAIT

TCP server01:1026 IS~BOTH:2600 TIME_WAIT

TCP server01:1026 IS~BOTH:2602 TIME_WAIT

TCP server01:1026 server01.RPS.COM:1227 ESTABLISHED

TCP server01:1026 server01.RPS.COM:1334 ESTABLISHED

TCP server01:1227 server01.RPS.COM:1026 ESTABLISHED

TCP server01:1334 server01.RPS.COM:1026 ESTABLISHED

TCP server01:1457 server01.RPS.COM:ldap CLOSE_WAIT

TCP server01:1466 server01.RPS.COM:10310 LISTENING

TCP server01:1682 server01.RPS.COM:ldap CLOSE_WAIT

TCP server01:1690 server01.RPS.COM:ldap ESTABLISHED

TCP server01:1764 server01.RPS.COM:microsoft-ds TIME_WAIT

TCP server01:1765 server01.RPS.COM:epmap TIME_WAIT

TCP server01:1766 server01.RPS.COM:1026 TIME_WAIT

TCP server01:1767 server01.RPS.COM:epmap TIME_WAIT

TCP server01:1768 server01.RPS.COM:1026 TIME_WAIT

TCP server01:1769 server01.RPS.COM:epmap TIME_WAIT

TCP server01:1770 server01.RPS.COM:1026 TIME_WAIT

TCP server01:1774 msnews.microsoft.com:nntp ESTABLISHED

TCP server01:1775 msnews.microsoft.com:nntp ESTABLISHED

TCP server01:1836 server01.RPS.COM:epmap TIME_WAIT

TCP server01:1837 server01.RPS.COM:1026 TIME_WAIT

TCP server01:1838 server01.RPS.COM:26764 LISTENING

TCP server01:1838 IS~BOTH:netbios-ssn ESTABLISHED

TCP server01:1845 server01.RPS.COM:epmap TIME_WAIT

TCP server01:1846 server01.RPS.COM:1026 TIME_WAIT

TCP server01:1855 server01.RPS.COM:epmap TIME_WAIT

TCP server01:1856 server01.RPS.COM:1196 TIME_WAIT

TCP server01:1914 server01.RPS.COM:epmap TIME_WAIT

TCP server01:1915 server01.RPS.COM:1026 TIME_WAIT

TCP server01:1918 server01.RPS.COM:ldap ESTABLISHED

TCP server01:1920 server01.RPS.COM:epmap TIME_WAIT

TCP server01:1921 server01.RPS.COM:1026 TIME_WAIT

UDP server01:nameserver *:*

UDP server01:bootpc *:*

UDP server01:epmap *:*

UDP server01:snmp *:*

UDP server01:microsoft-ds *:*

UDP server01:1028 *:*

UDP server01:1039 *:*

UDP server01:1047 *:*

UDP server01:1053 *:*

UDP server01:1060 *:*

UDP server01:1080 *:*

UDP server01:1084 *:*

UDP server01:1096 *:*

UDP server01:1186 *:*

UDP server01:1187 *:*

UDP server01:1195 *:*

UDP server01:1221 *:*

UDP server01:1224 *:*

UDP server01:1232 *:*

UDP server01:1336 *:*

UDP server01:1471 *:*

UDP server01:1629 *:*

UDP server01:1645 *:*

UDP server01:1646 *:*

UDP server01:1755 *:*

UDP server01:radius *:*

UDP server01:radacct *:*

UDP server01:1908 *:*

UDP server01:3456 *:*

UDP server01:4011 *:*

UDP server01:4458 *:*

UDP server01:domain *:*

UDP server01:1139 *:*

UDP server01:1140 *:*

UDP server01:1185 *:*

UDP server01:domain *:*

UDP server01:bootps *:*

UDP server01:bootpc *:*

UDP server01:tftp *:*

UDP server01:kerberos *:*

UDP server01:ntp *:*

UDP server01:netbios-ns *:*

UDP server01:netbios-dgm *:*

UDP server01:389 *:*

UDP server01:kpasswd *:*

UDP server01:isakmp *:*

UDP server01:2535 *:*



IP Statistics

Packets Received = 3,052,625

Received Header Errors = 0

Received Address Errors = 842

Datagrams Forwarded = 0

Unknown Protocols Received = 0

Received Packets Discarded = 0

Received Packets Delivered = 3,052,592

Output Requests = 2,897,499

Routing Discards = 0

Discarded Output Packets = 0

Output Packet No Route = 0

Reassembly Required = 66

Reassembly Successful = 33

Reassembly Failures = 0

Datagrams successfully fragmented = 33

Datagrams failing fragmentation = 0

Fragments Created = 66

Forwarding = 2

Default TTL = 128

Reassembly timeout = 60



TCP Statistics

Active Opens = 42,126

Passive Opens = 81,133

Failed Connection Attempts = 3,993

Reset Connections = 2,353

Current Connections = 23

Received Segments = 2,511,851

Segment Sent = 2,413,910

Segment Retransmitted = 12,928

Retransmission Timeout Algorithm = vanj

Minimum Retransmission Timeout = 300

Maximum Retransmission Timeout = 240,000

Maximum Number of Connections = -1



UDP Statistics

Datagrams Received = 388,014

No Ports = 99,497

Receive Errors = 0

Datagrams Sent = 325,630



ICMP Statistics

Received Sent

Messages 172,801 172,801

Errors 0 0

Destination Unreachable 28,282 28,282

Time Exceeded 4 4

Parameter Problems 0 0

Source Quenchs 0 0

Redirects 0 0

Echos 73,392 73,392

Echo Replies 71,123 71,123

Timestamps 0 0

Timestamp Replies 0 0

Address Masks 0 0

Address Mask Replies 0 0



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

Component Name : Network Monitor Driver

Bind Name: NM

Binding Paths:

Owner of the binding path : Network Monitor Driver

Binding Enabled: Yes

Interfaces of the binding path:

-Interface Name: ndis5

Upper Component: Network Monitor Driver

Lower Component: D-Link DFE-530TX+ PCI Adapter

Owner of the binding path : Network Monitor Driver

Binding Enabled: Yes

Interfaces of the binding path:

-Interface Name: ndiswanbh

Upper Component: Network Monitor Driver

Lower Component: WAN Miniport (Network Monitor)



Component Name : Point to Point Tunneling Protocol

Bind Name: mspptp

Binding Paths:

Component Name : Layer 2 Tunneling Protocol

Bind Name: msl2tp

Binding Paths:

Component Name : Remote Access NDIS WAN Driver

Bind Name: NdisWan

Binding Paths:

Owner of the binding path : Remote Access NDIS WAN Driver

Binding Enabled: Yes

Interfaces of the binding path:

-Interface Name: ndiscowan

Upper Component: Remote Access NDIS WAN Driver

Lower Component: Direct Parallel

Owner of the binding path : Remote Access NDIS WAN Driver

Binding Enabled: Yes

Interfaces of the binding path:

-Interface Name: ndiswan

Upper Component: Remote Access NDIS WAN Driver

Lower Component: WAN Miniport (PPTP)

Owner of the binding path : Remote Access NDIS WAN Driver

Binding Enabled: Yes

Interfaces of the binding path:

-Interface Name: ndiscowan

Upper Component: Remote Access NDIS WAN Driver

Lower Component: WAN Miniport (L2TP)

Owner of the binding path : Remote Access NDIS WAN Driver

Binding Enabled: Yes

Interfaces of the binding path:

-Interface Name: ndiswanasync

Upper Component: Remote Access NDIS WAN Driver

Lower Component: RAS Async Adapter



Component Name : Message-oriented TCP/IP Protocol (SMB session)

Bind Name: NetbiosSmb

Binding Paths:

Component Name : WINS Client(TCP/IP) Protocol

Bind Name: NetBT

Binding Paths:

Owner of the binding path : WINS Client(TCP/IP) Protocol

Binding Enabled: Yes

Interfaces of the binding path:

-Interface Name: tdi

Upper Component: WINS Client(TCP/IP) Protocol

Lower Component: Internet Protocol (TCP/IP)

-Interface Name: ndis5

Upper Component: Internet Protocol (TCP/IP)

Lower Component: D-Link DFE-530TX+ PCI Adapter

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: D-Link DFE-530TX+ PCI Adapter

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: D-Link DFE-530TX+ PCI Adapter

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 : DHCP Server

Bind Name: DHCPServer

Binding Paths:

Component Name : Steelhead

Bind Name: RemoteAccess

Binding Paths:

Component Name : Dial-Up Server

Bind Name: msrassrv

Binding Paths:

Component Name : Remote Access Connection Manager

Bind Name: RasMan

Binding Paths:

Component Name : Dial-Up Client

Bind Name: msrascli

Binding Paths:

Component Name : File and Printer Sharing for Microsoft Networks

Bind Name: LanmanServer

Binding Paths:

Owner of the binding path : File and Printer Sharing for Microsoft Networks

Binding Enabled: Yes

Interfaces of the binding path:

-Interface Name: netbios_smb

Upper Component: File and Printer Sharing for Microsoft Networks

Lower Component: Message-oriented TCP/IP Protocol (SMB session)

Owner of the binding path : File and Printer Sharing for Microsoft Networks

Binding Enabled: Yes

Interfaces of the binding path:

-Interface Name: netbios

Upper Component: File and Printer Sharing for Microsoft Networks

Lower Component: WINS Client(TCP/IP) Protocol

-Interface Name: tdi

Upper Component: WINS Client(TCP/IP) Protocol

Lower Component: Internet Protocol (TCP/IP)

-Interface Name: ndis5

Upper Component: Internet Protocol (TCP/IP)

Lower Component: D-Link DFE-530TX+ PCI Adapter

Owner of the binding path : File and Printer Sharing for Microsoft Networks

Binding Enabled: Yes

Interfaces of the binding path:

-Interface Name: netbios

Upper Component: File and Printer Sharing for Microsoft Networks

Lower Component: WINS Client(TCP/IP) Protocol

-Interface Name: tdi

Upper Component: WINS Client(TCP/IP) Protocol

Lower Component: Internet Protocol (TCP/IP)

-Interface Name: ndiswanip

Upper Component: Internet Protocol (TCP/IP)

Lower Component: WAN Miniport (IP)



Component Name : NetBIOS Interface

Bind Name: NetBIOS

Binding Paths:

Owner of the binding path : NetBIOS Interface

Binding Enabled: Yes

Interfaces of the binding path:

-Interface Name: netbios

Upper Component: NetBIOS Interface

Lower Component: WINS Client(TCP/IP) Protocol

-Interface Name: tdi

Upper Component: WINS Client(TCP/IP) Protocol

Lower Component: Internet Protocol (TCP/IP)

-Interface Name: ndis5

Upper Component: Internet Protocol (TCP/IP)

Lower Component: D-Link DFE-530TX+ PCI Adapter

Owner of the binding path : NetBIOS Interface

Binding Enabled: Yes

Interfaces of the binding path:

-Interface Name: netbios

Upper Component: NetBIOS Interface

Lower Component: WINS Client(TCP/IP) Protocol

-Interface Name: tdi

Upper Component: WINS Client(TCP/IP) Protocol

Lower Component: Internet Protocol (TCP/IP)

-Interface Name: ndiswanip

Upper Component: Internet Protocol (TCP/IP)

Lower Component: WAN Miniport (IP)



Component Name : QoS RSVP

Bind Name: RSVP

Binding Paths:

Component Name : Generic Packet Classifier

Bind Name: Gpc

Binding Paths:

Component Name : D-Link DFE-530TX+ PCI Adapter

Bind Name: {2C908C56-C45C-4FF0-AE34-6B0E2022D3C7}

Binding Paths:

Component Name : WAN Miniport (Network Monitor)

Bind Name: NdisWanBh

Binding Paths:

Component Name : WAN Miniport (IP)

Bind Name: NdisWanIp

Binding Paths:

Component Name : Direct Parallel

Bind Name: {58F6F5E5-D0D5-45B7-A879-FD978DA9F0EF}

Binding Paths:

Component Name : WAN Miniport (PPTP)

Bind Name: {437C0325-ADDC-4524-9B65-9DAFC9F3DB2E}

Binding Paths:

Component Name : WAN Miniport (L2TP)

Bind Name: {B1E7C645-70BD-4238-8FC7-D02D9F4DA82F}

Binding Paths:

Component Name : RAS Async Adapter

Bind Name: {346680AE-067E-4297-8B7F-9F3EAD603950}

Binding Paths:





WAN configuration test . . . . . . : Skipped

No active remote access connections.



Modem diagnostics test . . . . . . : Passed

Name . . . . . . . . . . . . . : Communications cable between two computers

DeviceID . . . . . . . . . : 0

Port . . . . . . . . . . . : COM1

Negotiated Speed . . . . . : 0

Compression. . . . . . . . : Off

Error control. . . . . . . : Off

Forced error control . . . : Off

Cellular . . . . . . . . . : Off

Flowcontrol hard . . . . . : Off

Flowcontrol soft . . . . . : Off

CCITT override . . . . . . : Off

Speed adjust . . . . . . . : Off

Tone dial. . . . . . . . . : Off

Blind dial . . . . . . . . : Off

V23 override . . . . . . . : Off

IP Security test . . . . . . . . . : Passed

IPSec policy service is active, but no policy is assigned.

IPSec Statistics

Oakley Main Modes : 0

Oakley Quick Modes : 0

Active Associations : 0

Soft Associations : 0

Authenticated Bytes Sent : 0

Authenticated Bytes Received : 0

Confidential Bytes Sent : 0

Confidential Bytes Received : 0

Offloaded Bytes Sent : 0

Offloaded Bytes Received : 0

ReKeys : 0

Authentication Failures : 0

Negotiation Failures : 0

Packets not decrypted : 0

Packets not authenticated : 0

Invalid Cookies Rcvd : 0

Acquire fail : 0

Receive fail : 0

Send fail : 0

GetSpiFail : 0

KeyAddFail : 0

KeyUpdateFail : 0

Active Acquire : 1

Active Rcv : 0

Active Send : 0

Total Acquire : 0

TotalGetSpi : 0

TotalKeyAdd : 0

TotalKeyUpdate : 0

Inactive Associations : 0

Dead Associations : 0

Pending Keys : 0

Key Flushes : 0

Key Additions : 0

Key Deletes : 0

Phase 1 offers count is 4

OFFER #1:

PFS : No, Encryption : 3DES, Hash : SHA1, Group : Medium (2)

Quickmodes per MainMode : 0, Lifetime Seconds : 28800

OFFER #2:

PFS : No, Encryption : 3DES, Hash : MD5, Group : Medium (2)

Quickmodes per MainMode : 0, Lifetime Seconds : 28800

OFFER #3:

PFS : No, Encryption : DES, Hash : SHA1, Group : Low (1)

Quickmodes per MainMode : 0, Lifetime Seconds : 28800

OFFER #4:

PFS : No, Encryption : DES, Hash : MD5, Group : Low (1)

Quickmodes per MainMode : 0, Lifetime Seconds : 28800

Current Phase 1 SAs:

No SAs.



Current Phase 2 SAs:

No SAs.







The command completed successfully
 
Rich said:

First and foremost, remove the router's address from the list of DNS servers
in TCP/IP properties on all domain members and DCs.
On the netdiag /g run, output below.

1. During the DNS portion of the output, there is a server there
that has been gone for a year. how do I get rid of this?

Did you demote this server or did you just turn it off and remove it from
the network?
2. The server that I want to get rid of now, which is my 2nd DC is
there.

<Kevin reads this statement with a puzzled look>
I always recommend having at least two DCs, even if one is on a cheapo box,
the chance of losing both DCs simultaneously is
3. There are a lot of errors related to my DSL modem/router which is
a 2nd DNS server on my network. I thought I needed this to resolve
names on the internet. I'm 80% sure my internal DNS is config'd to
fwd. requests to that device.

Only 80% sure your DNS forwards to the router?
While a forwarder is not required, forwarding to your router will give you a
cache only DNS to use as a forwarder. Which, can speed resolution up
considerably, if you have several users using the same sites.
4. What do I do???

Remove the router's address form the DNS server list, and run ipconfig
/flushdns to remove any cached records from the DNS cache for records that
may have been returned by the router.
run netdiag /test:dns /v
 
Back
Top