The following 2 DNS servers were checked for records related to AD forest
replication:
DNS server: earthstar.bklighting.com
IP Address: 192.168.1.2
UDP port 53 responding to queries: YES
TCP port 53 responding to queries: Not tested
Answering authoritatively for domain: YES
SOA record data from server:
Authoritative name server: earthstar.bklighting.com
Hostmaster: admin
Zone serial number: 11232
Zone expires in: 1.00 day(s)
Refresh period: 900 seconds
Retry delay: 600 seconds
Default (minimum) TTL: 3600 seconds
Additional authoritative (NS) records from server:
earthstar.bklighting.com Unknown
deathstar.bklighting.com Unknown
Alias (CNAME) and glue (A) records for forest GUIDs from server:
CNAME: 4e712a28-93a6-456a-89e1-ff6d73b91fb7._msdcs.bklighting.com
Alias: earthstar.bklighting.com
Glue: 192.168.1.2
Total number of CNAME records found on this server: 4
Total number of CNAME records missing on this server: 0
Total number of glue (A) records this server could not find: 0
--------------------------------------------------------------------------------
DNS server: deathstar.bklighting.com
IP Address: 192.168.1.200
UDP port 53 responding to queries: NO
TCP port 53 responding to queries: Not tested
Answering authoritatively for domain: Unknown
SOA record data from server:
Authoritative name server: Unknown
Hostmaster: Unknown
Zone serial number: Unknown
Zone expires in: Unknown
Refresh period: Unknown
Retry delay: Unknown
Default (minimum) TTL: Unknown
Total number of CNAME records found on this server: 0
Total number of CNAME records missing on this server: 0
Total number of glue (A) records this server could not find: 0
Notes:
One or more DNS servers may not be authoritative for the domain
Additional name server records were not identical on every DNS server
One or more DNS servers did not respond to UDP queries
One or more zone files may have expired
SOA record data was unavailable and/or missing on one or more DNS servers
Legend: warning, error
DNSLint developed by Tim Rains
--
RF
Network Admin
B-K Lighting, Inc.
Madera CA
"Meinolf Weber" wrote:
> Hello USS,
>
> Do you use a single label domain name, domain instead domain.com? Run netdiag
> /fix on the DC. Is this the only DNS server? Make sure that under the DNS
> zones all DC's are listed with the correct names. Can you ping between the
> DC's with ip address, computername and FQDN?
>
> Best regards
>
> Meinolf Weber
(Msg. 10) Posted: Wed Aug 06, 2008 10:39 am
Post subject: Re: NetDiag & DCDiag errors [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
Ping Results from DNS
C:\Program Files\Dnslint>ping earthstar.bklighting.com
Pinging earthstar.bklighting.com [192.168.1.2] with 32 bytes of data:
Reply from 192.168.1.2: bytes=32 time<10ms TTL=128
Reply from 192.168.1.2: bytes=32 time<10ms TTL=128
Reply from 192.168.1.2: bytes=32 time<10ms TTL=128
Reply from 192.168.1.2: bytes=32 time<10ms TTL=128
Ping statistics for 192.168.1.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Pinging battlestar.bklighting.com [192.168.1.251] with 32 bytes of data:
Reply from 192.168.1.251: bytes=32 time<10ms TTL=128
Reply from 192.168.1.251: bytes=32 time<10ms TTL=128
Reply from 192.168.1.251: bytes=32 time<10ms TTL=128
Reply from 192.168.1.251: bytes=32 time<10ms TTL=128
Ping statistics for 192.168.1.251:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Pinging deathstar.bklighting.com [192.168.1.200] with 32 bytes of data:
Reply from 192.168.1.200: bytes=32 time<10ms TTL=128
Reply from 192.168.1.200: bytes=32 time<10ms TTL=128
Reply from 192.168.1.200: bytes=32 time<10ms TTL=128
Reply from 192.168.1.200: bytes=32 time<10ms TTL=128
Ping statistics for 192.168.1.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Pinging litestar.bklighting.com [192.168.1.170] with 32 bytes of data:
Reply from 192.168.1.170: bytes=32 time<10ms TTL=128
Reply from 192.168.1.170: bytes=32 time<10ms TTL=128
Reply from 192.168.1.170: bytes=32 time<10ms TTL=128
Reply from 192.168.1.170: bytes=32 time<10ms TTL=128
Ping statistics for 192.168.1.170:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Program Files\Dnslint>
--
RF
Network Admin
B-K Lighting, Inc.
Madera CA
"Meinolf Weber" wrote:
> Hello USS,
>
> Do you use a single label domain name, domain instead domain.com? Run netdiag
> /fix on the DC. Is this the only DNS server? Make sure that under the DNS
> zones all DC's are listed with the correct names. Can you ping between the
> DC's with ip address, computername and FQDN?
>
> Best regards
>
> Meinolf Weber
(Msg. 11) Posted: Wed Aug 06, 2008 10:46 am
Post subject: Re: NetDiag & DCDiag errors [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
Testing server: Default-First-Site-Name\EARTHSTAR
Starting test: Replications
......................... EARTHSTAR passed test Replications
Starting test: NCSecDesc
......................... EARTHSTAR passed test NCSecDesc
Starting test: NetLogons
[EARTHSTAR] An net use or LsaPolicy operation failed with error
1231, The network location cannot be reached. For information about network t
roubleshooting, see Windows Help..
......................... EARTHSTAR failed test NetLogons
Starting test: Advertising
......................... EARTHSTAR passed test Advertising
Starting test: KnowsOfRoleHolders
......................... EARTHSTAR passed test KnowsOfRoleHolders
Starting test: RidManager
......................... EARTHSTAR passed test RidManager
Starting test: MachineAccount
Could not open pipe with [EARTHSTAR]:failed with 1231: The network
location cannot be reached. For information about network troubleshooting,
see Windows Help.
Could not get NetBIOSDomainName
Failed can not test for HOST SPN
Failed can not test for HOST SPN
* Missing SPN :(null)
* Missing SPN :(null)
......................... EARTHSTAR failed test MachineAccount
Starting test: Services
Could not open Remote ipc to [EARTHSTAR]:failed with 1231: The
network location cannot be reached. For information about network troubleshoot
ing, see Windows Help.
......................... EARTHSTAR failed test Services
Starting test: ObjectsReplicated
......................... EARTHSTAR passed test ObjectsReplicated
Starting test: frssysvol
[EARTHSTAR] An net use or LsaPolicy operation failed with error
1231, The network location cannot be reached. For information about network t
roubleshooting, see Windows Help..
......................... EARTHSTAR passed test frssysvol
Starting test: kccevent
Failed to enumerate event log records, error The network location
cannot be reached. For information about network troubleshooting, see Windo
ws Help.
......................... EARTHSTAR failed test kccevent
Starting test: systemlog
Failed to enumerate event log records, error The network location
cannot be reached. For information about network troubleshooting, see Windo
ws Help.
......................... EARTHSTAR failed test systemlog
Testing server: Default-First-Site-Name\DEATHSTAR
Starting test: Replications
......................... DEATHSTAR passed test Replications
Starting test: NCSecDesc
......................... DEATHSTAR passed test NCSecDesc
Starting test: NetLogons
[DEATHSTAR] An net use or LsaPolicy operation failed with error
1231, The network location cannot be reached. For information about network t
roubleshooting, see Windows Help..
......................... DEATHSTAR failed test NetLogons
Starting test: Advertising
Fatal Error:DsGetDcName (DEATHSTAR) call failed, error 1722
The Locator could not find the server.
......................... DEATHSTAR failed test Advertising
Starting test: KnowsOfRoleHolders
......................... DEATHSTAR passed test KnowsOfRoleHolders
Starting test: RidManager
......................... DEATHSTAR passed test RidManager
Starting test: MachineAccount
Could not open pipe with [DEATHSTAR]:failed with 53: The network
path was not found.
Could not get NetBIOSDomainName
Failed can not test for HOST SPN
Failed can not test for HOST SPN
* Missing SPN :(null)
* Missing SPN :(null)
......................... DEATHSTAR failed test MachineAccount
Starting test: Services
Could not open Remote ipc to [DEATHSTAR]:failed with 1231: The
network location cannot be reached. For information about network troubleshoot
ing, see Windows Help.
......................... DEATHSTAR failed test Services
Starting test: ObjectsReplicated
......................... DEATHSTAR passed test ObjectsReplicated
Starting test: frssysvol
[DEATHSTAR] An net use or LsaPolicy operation failed with error
1231, The network location cannot be reached. For information about network t
roubleshooting, see Windows Help..
......................... DEATHSTAR failed test frssysvol
Starting test: kccevent
Failed to enumerate event log records, error The network location
cannot be reached. For information about network troubleshooting, see Windo
ws Help.
......................... DEATHSTAR failed test kccevent
Starting test: systemlog
Failed to enumerate event log records, error The network location
cannot be reached. For information about network troubleshooting, see Windo
ws Help.
......................... DEATHSTAR failed test systemlog
Testing server: Default-First-Site-Name\LITESTAR
Starting test: Replications
......................... LITESTAR passed test Replications
Starting test: NCSecDesc
......................... LITESTAR passed test NCSecDesc
Starting test: NetLogons
[LITESTAR] An net use or LsaPolicy operation failed with error
1231, The network location cannot be reached. For information about network tr
oubleshooting, see Windows Help..
......................... LITESTAR failed test NetLogons
Starting test: Advertising
Fatal Error:DsGetDcName (LITESTAR) call failed, error 1722
The Locator could not find the server.
......................... LITESTAR failed test Advertising
Starting test: KnowsOfRoleHolders
......................... LITESTAR passed test KnowsOfRoleHolders
Starting test: RidManager
......................... LITESTAR passed test RidManager
Starting test: MachineAccount
Could not open pipe with [LITESTAR]:failed with 53: The network
path was not found.
Could not get NetBIOSDomainName
Failed can not test for HOST SPN
Failed can not test for HOST SPN
* Missing SPN :(null)
* Missing SPN :(null)
......................... LITESTAR failed test MachineAccount
Starting test: Services
Could not open Remote ipc to [LITESTAR]:failed with 1231: The
network location cannot be reached. For information about network
troubleshooti
ng, see Windows Help.
......................... LITESTAR failed test Services
Starting test: ObjectsReplicated
......................... LITESTAR passed test ObjectsReplicated
Starting test: frssysvol
[LITESTAR] An net use or LsaPolicy operation failed with error
1231, The network location cannot be reached. For information about network tr
oubleshooting, see Windows Help..
......................... LITESTAR failed test frssysvol
Starting test: kccevent
Failed to enumerate event log records, error The network location
cannot be reached. For information about network troubleshooting, see Windo
ws Help.
......................... LITESTAR failed test kccevent
Starting test: systemlog
Failed to enumerate event log records, error The network location
cannot be reached. For information about network troubleshooting, see Windo
ws Help.
......................... LITESTAR failed test systemlog
Testing server: Default-First-Site-Name\BATTLESTAR
Starting test: Replications
......................... BATTLESTAR passed test Replications
Starting test: NCSecDesc
......................... BATTLESTAR passed test NCSecDesc
Starting test: NetLogons
[BATTLESTAR] An net use or LsaPolicy operation failed with error
1231, The network location cannot be reached. For information about network
troubleshooting, see Windows Help..
......................... BATTLESTAR failed test NetLogons
Starting test: Advertising
Fatal Error:DsGetDcName (BATTLESTAR) call failed, error 1722
The Locator could not find the server.
......................... BATTLESTAR failed test Advertising
Starting test: KnowsOfRoleHolders
......................... BATTLESTAR passed test KnowsOfRoleHolders
Starting test: RidManager
......................... BATTLESTAR passed test RidManager
Starting test: MachineAccount
Could not open pipe with [BATTLESTAR]:failed with 1231: The network
location cannot be reached. For information about network troubleshooting
, see Windows Help.
Could not get NetBIOSDomainName
Failed can not test for HOST SPN
Failed can not test for HOST SPN
* Missing SPN :(null)
* Missing SPN :(null)
......................... BATTLESTAR failed test MachineAccount
Starting test: Services
Could not open Remote ipc to [BATTLESTAR]:failed with 1231: The
network location cannot be reached. For information about network troubleshoo
ting, see Windows Help.
......................... BATTLESTAR failed test Services
Starting test: ObjectsReplicated
......................... BATTLESTAR passed test ObjectsReplicated
Starting test: frssysvol
[BATTLESTAR] An net use or LsaPolicy operation failed with error
1231, The network location cannot be reached. For information about network
troubleshooting, see Windows Help..
......................... BATTLESTAR failed test frssysvol
Starting test: kccevent
Failed to enumerate event log records, error The network location
cannot be reached. For information about network troubleshooting, see Windo
ws Help.
......................... BATTLESTAR failed test kccevent
Starting test: systemlog
Failed to enumerate event log records, error The network location
cannot be reached. For information about network troubleshooting, see Windo
ws Help.
......................... BATTLESTAR failed test systemlog
Running enterprise tests on : bklighting.com
Starting test: Intersite
......................... bklighting.com passed test Intersite
Starting test: FsmoCheck
......................... bklighting.com passed test FsmoCheck
C:\Program Files\Dnslint>
--
RF
Network Admin
B-K Lighting, Inc.
Madera CA
"Meinolf Weber" wrote:
> Hello USS,
>
> Do you use a single label domain name, domain instead domain.com? Run netdiag
> /fix on the DC. Is this the only DNS server? Make sure that under the DNS
> zones all DC's are listed with the correct names. Can you ping between the
> DC's with ip address, computername and FQDN?
>
> Best regards
>
> Meinolf Weber
(Msg. 12) Posted: Wed Aug 06, 2008 12:23 pm
Post subject: Re: NetDiag & DCDiag errors. [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
DNS Console Results.
I did find something.
DNS>Earthstar>Forward Lookup Zones>BKLighting.com>MSDCS>Litestar.bklighting.
(incomplete FQDN) This entry should not be there.
Also listed is the FQDN Litestar.bklighting.com
--
RF
Network Admin
B-K Lighting, Inc.
Madera CA
"Meinolf Weber" wrote:
> Hello USS,
>
> Do you use a single label domain name, domain instead domain.com? Run netdiag
> /fix on the DC. Is this the only DNS server? Make sure that under the DNS
> zones all DC's are listed with the correct names. Can you ping between the
> DC's with ip address, computername and FQDN?
>
> 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 >
> > Need help Please.
> >
> > Windows 2000 Server SP4.
> > Single Site. Runs DHCP, DNS WINS.
> > Primary Active Directory Domain Controller.
> > Restart states Duplicate name on Network.
> > Single NIC.
> > This started when I could no longer browse the network.
> > NETBIOS over TCPI P is turned on the NIC.
> > I checked the Registry entries for NetBT.
> > HKEY_Local_Machine\System\CurrentControlSet|Services\NetBT\Parameters
> > SmbDeviceEnabled & TransportBindName
> > I can ping the IP address and the Domain Name.
> > I performed a IPCONFIG /flushdns and a registerdns.
> > WINSOCK looks good. But who can tell for sure?
> > Still getting errors
> > Starting test: NetLogons
> > [DOMAIN] An net use or LsaPolicy operation failed with error
> > 1231,
> > The network location cannot be reached. For information about network
> > troubleshooting, see Windows Help..
> > ......................... DOMAIN failed test NetLogons
> > Starting test: MachineAccount
> > Could not open pipe with [DOMAIN]:failed with 1231: The
> > network
> > location cannot be reached. For information about network
> > troubleshooting,
> > see Windows Help.
> > Could not get NetBIOSDomainName
> > Failed can not test for HOST SPN
> > Failed can not test for HOST SPN
> > * Missing SPN :(null)
> > * Missing SPN :(null)
> > ......................... DOMAIN failed test MachineAccount
> > Starting test: Services
> > Could not open Remote ipc to [DOMAIN]:failed with 1231: The
> > network
> > location cannot be reached. For information about network
> > troubleshooting,
> > see Windows Help.
> > ......................... DOMAIN failed test Services
> > Starting test: frssysvol
> > [DOMAIN] An net use or LsaPolicy operation failed with error
> > 1231,
> > The network location cannot be reached. For information about network
> > troubleshooting, see Windows Help..
> > ......................... DOMAIN passed test frssysvol
> > Starting test: kccevent
> > Failed to enumerate event log records, error The network
> > location
> > cannot be reached. For information about network troubleshooting, see
> > Windows
> > Help.
> > ......................... DOMAIN failed test kccevent
> > Starting test: systemlog
> > Failed to enumerate event log records, error The network
> > location
> > cannot be reached. For information about network troubleshooting, see
> > Windows
> > Help.
> >
> > netdiag
> >
> > .......................................
> >
> > Computer Name: COMPUTERNAME
> > DNS Host Name: computername.domainname.com
> > System info : Windows 2000 Server (Build 2195)
> > Processor : x86 Family 6 Model 8 Stepping 3, GenuineIntel
> > List of installed hotfixes :
> > KB820888
> > KB822831
> > KB823182
> > KB823559
> > KB824105
> > KB824141
> > KB824146
> > KB825119
> > KB826232
> > KB828035
> > KB828741
> > KB828749
> > KB830352
> > KB835732
> > KB837001
> > Q147222
> > Q295688
> > Q816093
> > Q828026
> > Netcard queries test . . . . . . . : Passed
> >
> > Per interface results:
> >
> > Adapter : Local Area Connection
> >
> > Netcard queries test . . . : Passed
> >
> > Host Name. . . . . . . . . : earthstar
> > IP Address . . . . . . . . : 192.168.1.2
> > Subnet Mask. . . . . . . . : 255.255.255.0
> > Default Gateway. . . . . . : 192.168.1.1
> > Primary WINS Server. . . . : 192.168.1.2
> > Dns Servers. . . . . . . . : 192.168.1.2
> > AutoConfiguration results. . . . . . : Passed
> >
> > Default gateway test . . . : Passed
> >
> > NetBT name test. . . . . . : Passed
> > No remote names have been found.
> > WINS service test. . . . . : Passed
> >
> > Global results:
> >
> > Domain membership test . . . . . . : Passed
> >
> > NetBT transports test. . . . . . . : Failed
> > List of NetBt transports currently configured:
> > [FATAL] Unable to retrieve transport list from Redir.
> > [ERROR_NETWORK_UNREACHABLE]
> > Autonet address test . . . . . . . : Passed
> >
> > IP loopback ping test. . . . . . . : Passed
> >
> > Default gateway test . . . . . . . : Passed
> >
> > NetBT name test. . . . . . . . . . : Passed
> >
> > Winsock test . . . . . . . . . . . : Passed
> >
> > DNS test . . . . . . . . . . . . . : Passed
> > PASS - All the DNS entries for DC are registered on DNS server
> > '192.168.1.2' and other DCs also have some of the names registered.
> > Redir and Browser test . . . . . . : Failed
> > List of NetBt transports currently bound to the Redir
> > [FATAL] Unable to retrieve transport list from Redir.
> > [ERROR_NETWORK_UNREACHABLE]
> > List of NetBt transports currently bound to the browser
> > [FATAL] The browser isn't bound to any NetBt transports.
> > [FATAL] Cannot send mailslot message to
> > '\\DOMAIN*\MAILSLOT\NET\NETLOGON' via redir.
> > [ERROR_NETWORK_UNREACHABLE]
> > DC discovery test. . . . . . . . . : Passed
> >
> > DC list test . . . . . . . . . . . : Passed
> >
> > Trust relationship test. . . . . . : Skipped
> >
> > Kerberos test. . . . . . . . . . . : Passed
> >
> > LDAP test. . . . . . . . . . . . . : Passed
> >
> > Bindings test. . . . . . . . . . . : Passed
> >
> > WAN configuration test . . . . . . : Skipped
> > No active remote access connections.
> > Modem diagnostics test . . . . . . : Failed
> > [FATAL] Cannot initialize TAPI. Failed with error(0x80000048).
> > IP Security test . . . . . . . . . : Passed
> > IPSec policy service is active, but no policy is assigned.
> > C:\>
> >
>
>
>
(Msg. 13) Posted: Thu Aug 07, 2008 6:54 am
Post subject: Re: NetDiag & DCDiag errors [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
Hello USS,
The output states that you have another DNS server:
deathstar.bklighting.com
Was it used for DNS, can you clarify this?
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
(Msg. 14) Posted: Thu Aug 07, 2008 6:55 am
Post subject: Re: NetDiag & DCDiag errors. [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
Hello USS,
Please post an unedited ipconfig /all from all DC's
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
> DNS Console Results.
> I did find something.
DNS>> Earthstar>Forward Lookup
DNS>> Zones>BKLighting.com>MSDCS>Litestar.bklighting.
DNS>>
> (incomplete FQDN) This entry should not be there.
>
> Also listed is the FQDN Litestar.bklighting.com
>
> "Meinolf Weber" wrote:
>
>> Hello USS,
>>
>> Do you use a single label domain name, domain instead domain.com? Run
>> netdiag /fix on the DC. Is this the only DNS server? Make sure that
>> under the DNS zones all DC's are listed with the correct names. Can
>> you ping between the DC's with ip address, computername and FQDN?
>>
>> 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 >>> Need help Please.
>>>
>>> Windows 2000 Server SP4.
>>> Single Site. Runs DHCP, DNS WINS.
>>> Primary Active Directory Domain Controller.
>>> Restart states Duplicate name on Network.
>>> Single NIC.
>>> This started when I could no longer browse the network.
>>> NETBIOS over TCPI P is turned on the NIC.
>>> I checked the Registry entries for NetBT.
>>> HKEY_Local_Machine\System\CurrentControlSet|Services\NetBT\Parameter
>>> s
>>> SmbDeviceEnabled & TransportBindName
>>> I can ping the IP address and the Domain Name.
>>> I performed a IPCONFIG /flushdns and a registerdns.
>>> WINSOCK looks good. But who can tell for sure?
>>> Still getting errors
>>> Starting test: NetLogons
>>> [DOMAIN] An net use or LsaPolicy operation failed with error
>>> 1231,
>>> The network location cannot be reached. For information about
>>> network
>>> troubleshooting, see Windows Help..
>>> ......................... DOMAIN failed test NetLogons
>>> Starting test: MachineAccount
>>> Could not open pipe with [DOMAIN]:failed with 1231: The
>>> network
>>> location cannot be reached. For information about network
>>> troubleshooting,
>>> see Windows Help.
>>> Could not get NetBIOSDomainName
>>> Failed can not test for HOST SPN
>>> Failed can not test for HOST SPN
>>> * Missing SPN :(null)
>>> * Missing SPN :(null)
>>> ......................... DOMAIN failed test MachineAccount
>>> Starting test: Services
>>> Could not open Remote ipc to [DOMAIN]:failed with 1231: The
>>> network
>>> location cannot be reached. For information about network
>>> troubleshooting,
>>> see Windows Help.
>>> ......................... DOMAIN failed test Services
>>> Starting test: frssysvol
>>> [DOMAIN] An net use or LsaPolicy operation failed with error
>>> 1231,
>>> The network location cannot be reached. For information about
>>> network
>>> troubleshooting, see Windows Help..
>>> ......................... DOMAIN passed test frssysvol
>>> Starting test: kccevent
>>> Failed to enumerate event log records, error The network
>>> location
>>> cannot be reached. For information about network troubleshooting,
>>> see
>>> Windows
>>> Help.
>>> ......................... DOMAIN failed test kccevent
>>> Starting test: systemlog
>>> Failed to enumerate event log records, error The network
>>> location
>>> cannot be reached. For information about network troubleshooting,
>>> see
>>> Windows
>>> Help.
>>> netdiag
>>>
>>> .......................................
>>>
>>> Computer Name: COMPUTERNAME
>>> DNS Host Name: computername.domainname.com
>>> System info : Windows 2000 Server (Build 2195)
>>> Processor : x86 Family 6 Model 8 Stepping 3, GenuineIntel
>>> List of installed hotfixes :
>>> KB820888
>>> KB822831
>>> KB823182
>>> KB823559
>>> KB824105
>>> KB824141
>>> KB824146
>>> KB825119
>>> KB826232
>>> KB828035
>>> KB828741
>>> KB828749
>>> KB830352
>>> KB835732
>>> KB837001
>>> Q147222
>>> Q295688
>>> Q816093
>>> Q828026
>>> Netcard queries test . . . . . . . : Passed
>>> Per interface results:
>>>
>>> Adapter : Local Area Connection
>>>
>>> Netcard queries test . . . : Passed
>>>
>>> Host Name. . . . . . . . . : earthstar
>>> IP Address . . . . . . . . : 192.168.1.2
>>> Subnet Mask. . . . . . . . : 255.255.255.0
>>> Default Gateway. . . . . . : 192.168.1.1
>>> Primary WINS Server. . . . : 192.168.1.2
>>> Dns Servers. . . . . . . . : 192.168.1.2
>>> AutoConfiguration results. . . . . . : Passed
>>> Default gateway test . . . : Passed
>>>
>>> NetBT name test. . . . . . : Passed
>>> No remote names have been found.
>>> WINS service test. . . . . : Passed
>>> Global results:
>>>
>>> Domain membership test . . . . . . : Passed
>>>
>>> NetBT transports test. . . . . . . : Failed
>>> List of NetBt transports currently configured:
>>> [FATAL] Unable to retrieve transport list from Redir.
>>> [ERROR_NETWORK_UNREACHABLE]
>>> Autonet address test . . . . . . . : Passed
>>> IP loopback ping test. . . . . . . : Passed
>>>
>>> Default gateway test . . . . . . . : Passed
>>>
>>> NetBT name test. . . . . . . . . . : Passed
>>>
>>> Winsock test . . . . . . . . . . . : Passed
>>>
>>> DNS test . . . . . . . . . . . . . : Passed
>>> PASS - All the DNS entries for DC are registered on DNS server
>>> '192.168.1.2' and other DCs also have some of the names registered.
>>> Redir and Browser test . . . . . . : Failed
>>> List of NetBt transports currently bound to the Redir
>>> [FATAL] Unable to retrieve transport list from Redir.
>>> [ERROR_NETWORK_UNREACHABLE]
>>> List of NetBt transports currently bound to the browser
>>> [FATAL] The browser isn't bound to any NetBt transports.
>>> [FATAL] Cannot send mailslot message to
>>> '\\DOMAIN*\MAILSLOT\NET\NETLOGON' via redir.
>>> [ERROR_NETWORK_UNREACHABLE]
>>> DC discovery test. . . . . . . . . : Passed
>>> DC list test . . . . . . . . . . . : Passed
>>>
>>> Trust relationship test. . . . . . : Skipped
>>>
>>> Kerberos test. . . . . . . . . . . : Passed
>>>
>>> LDAP test. . . . . . . . . . . . . : Passed
>>>
>>> Bindings test. . . . . . . . . . . : Passed
>>>
>>> WAN configuration test . . . . . . : Skipped
>>> No active remote access connections.
>>> Modem diagnostics test . . . . . . : Failed
>>> [FATAL] Cannot initialize TAPI. Failed with error(0x80000048).
>>> IP Security test . . . . . . . . . : Passed
>>> IPSec policy service is active, but no policy is assigned.
>>> C:\>
(Msg. 15) Posted: Thu Aug 07, 2008 8:21 am
Post subject: Re: NetDiag & DCDiag errors [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
Deathstar is a test server used for various things.
I do not know why it is listed as a DNS?
I've never wanted this server to perform this role.
I do not recall ever setting it up to do so?
I would like to run DCpromo and remove it as a DC.
Thoughts?
Regards, Robert.
--
RF
Network Admin
B-K Lighting, Inc.
Madera CA
"Meinolf Weber" wrote:
> Hello USS,
>
> The output states that you have another DNS server:
>
> deathstar.bklighting.com
>
> Was it used for DNS, can you clarify this?
>
> 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 >
> > DNS server: deathstar.bklighting.com
> >
>
>
>
(Msg. 16) Posted: Thu Aug 07, 2008 10:56 am
Post subject: Re: NetDiag & DCDiag errors. [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.
All times are: Eastern Time (US & Canada) (change) Goto page Previous1, 2, 3
Page 2 of 3
You can post new topics in this forum You can reply to topics in this forum You can edit your posts in this forum You can delete your posts in this forum You can vote in polls in this forum