DCdiag output with errors

[RW]

I'm having problems joining AD domain from remote site. Found DCdiag.exe in
the resource kit and ran that against one of the DC's in the main site, and
it came up with several errors. I don't know exactly what these errors mean
in this particular case.

DC machine name is GDW2k1 and domain is ortec.intranet

----------------------------------------------------------------------------
-----------------------------------------------------------------
Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: ORTECSite1\GDW2K1
Starting test: Connectivity
......................... GDW2K1 passed test Connectivity

Doing primary tests

Testing server: ORTECSite1\GDW2K1
Starting test: Replications
......................... GDW2K1 passed test Replications
Starting test: NCSecDesc
......................... GDW2K1 passed test NCSecDesc
Starting test: NetLogons
[GDW2K1] An net use or LsaPolicy operation failed with error 53,
The network path was not found..
......................... GDW2K1 failed test NetLogons
Starting test: Advertising
Fatal Error:DsGetDcName (GDW2K1) call failed, error 1722
The Locator could not find the server.
......................... GDW2K1 failed test Advertising
Starting test: KnowsOfRoleHolders
......................... GDW2K1 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... GDW2K1 passed test RidManager
Starting test: MachineAccount
Could not open pipe with [GDW2K1]: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)
......................... GDW2K1 failed test MachineAccount
Starting test: Services
Could not open Remote ipc to [GDW2K1]:failed with 53: The network
path was not found.
......................... GDW2K1 failed test Services
Starting test: ObjectsReplicated
......................... GDW2K1 passed test ObjectsReplicated
Starting test: frssysvol
[GDW2K1] An net use or LsaPolicy operation failed with error 53,
The network path was not found..
......................... GDW2K1 failed test frssysvol
Starting test: kccevent
Failed to enumerate event log records, error The network path was
not found.
......................... GDW2K1 failed test kccevent
Starting test: systemlog
Failed to enumerate event log records, error The network path was
not found.
......................... GDW2K1 failed test systemlog

Running enterprise tests on : ortec.intranet
Starting test: Intersite
......................... ortec.intranet passed test Intersite
Starting test: FsmoCheck
Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1722
A Global Catalog Server could not be located - All GC's are down.
Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1722
A Primary Domain Controller could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(TIME_SERVER) call failed, error 1722
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error
1722
A Good Time Server could not be located.
Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1722
A KDC could not be located - All the KDCs are down.
......................... ortec.intranet failed test FsmoCheck

-RW
tec...@ortec.nl

[David Dee (MSFT)]

Make sure that this server is pointing to the internal DNS server that hosts
the SRV records for AD. Additionaly you may try some NSlookup from command
line to verify.

HTH

--
David Dee (MSFT)

Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
"RW" <tec...@ortec.nl> wrote in message
news:3e913603$0$28926$edd6...@news.versatel.net...

[Matjaz Ladava]

This point to DNS problem. Check, that your server, that you are promoting
points to a valid internal DNS server. Check DNS registrations.

Regards

Matjaz Ladava

"RW" <tec...@ortec.nl> wrote in message
news:3e913603$0$28926$edd6...@news.versatel.net...

[RW]

DNS settings are correct. I'm pointing this machine to 2 DNS servers in the
main site. Main site works fine. I can ping and NSlookup names without
problems. Also, a third site had the exact same settings and does NOT give
me the same join problems.

-RW

"David Dee (MSFT)" <davi...@microsoft.com> wrote in message
news:uxMwdCO$CHA....@TK2MSFTNGP12.phx.gbl...

[RW]

Found it. Or at least, this error.
I wasn't using WINS. After I supplied a WINS server, error was gone. So much
for W2k being completely independant of WINS.

But the problem with joining AD domain from remote site is still there.

"RW" <tec...@ortec.nl> wrote in message

news:3e914bb4$0$57462$edd6...@news.versatel.net...

[Snowdog]

I problem is that I would bet your missing the IPC$ share. Run net share at
a command line or check the shares from the computer management console. You
are probably missing the default admin shares of C$ and admin$ as well.

If the above is true then you have a virus in the order of something like
the mIRC trojan virus. You need the IPC$ share in order to join machines to
the domain and 98 clients need the share to logon to.

Snowdog

"RW" <tec...@ortec.nl> wrote in message

news:3e915f61$0$28923$edd6...@news.versatel.net...