Sysvol and netlogon shares

Help!

I just reinstalled Windows 2000 Advanced Server (new motherboard to
replace the somewhat unstable old one). All service packs and updates,
everything seemed to work fine, DCPROMO seemed to work.

Now a few things are odd, rebooting takes 5 minutes of "preparing
network connections". But most things work fine except for event log
entries that says Windows cannot determine the user or computer name,
and default group policy object cannot be created.

The problem is most likely that there are no shares named SYSVOL and
NETLOGON.

This is a very simple system. It is the Active Directory domain
controller, the only domain controller, and the only server (it supports
8 client computers). It is the DNS server. There's no Exchange server,
no IIS, and at 2.4 GHz and 512MB memory, I don't think it will be
overloaded. :-)

The users don't use anything on the netlogon share; we don't run any
logon scripts. But I suppose the share should exist, along with SYSVOL.

I read article http://support.microsoft.com/default.aspx?scid=kb;en-
us;315457 about rebuilding the SYSVOL tree and its contents in a domain.

Good grief that's a complicated article. I don't have any replication
to worry about, and the folders are there. But how am I supposed to
"verify" that the reparse points are there? Article says:

"b. Verify that the following reparse points exist:
\SYSVOL\SYSVOL\ DNS Domain Name
This reparse point must be linked to the \SYSVOL\domain folder.

\SYSVOL\staging\DNS Domain Name
This reparse point must be linked to the \SYSVOL\staging\domain folder.

I know what reparse points are, how do I verify that they point to the
right thing? There appears a folder call \SYSVOL\SYSVOL\<My domain
name>, and I suppose that's the reparse point.

If I'm supposed to use LINKD to verify the reparse points, that's a
problem: I don't have LINKD on my system, and I installed the support
tools from the CD.

The next problem is that the article says to also use the ntfrsutl tool
(although in the next sentence it's called the ntfrsutil tool, spelled
differently). That tool doesn't come with Windows 2000 Advanced Server,
even in the support tools (using either spelling), and I can't find it
for download.

Lastly, I have read, in the vastness of the Internet, that I should not
use Windows Explorer to manually recreate those shares. So I am stuck
following this complex KB article that talks about replication partners,
and what to do if you have more than 15 "downstream partners of any
particular source domain controlle", when all I probably need is these
shares re-created.

Any suggestions? Any simple way out of this situation?

Thanks for any advice.

David Walker

run dcdiag and netdiag. post back with any errors.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"DWalker" <(E-Mail Removed)> wrote in message news:%(E-Mail Removed)...
Help!

I just reinstalled Windows 2000 Advanced Server (new motherboard to
replace the somewhat unstable old one). All service packs and updates,
everything seemed to work fine, DCPROMO seemed to work.

Now a few things are odd, rebooting takes 5 minutes of "preparing
network connections". But most things work fine except for event log
entries that says Windows cannot determine the user or computer name,
and default group policy object cannot be created.

The problem is most likely that there are no shares named SYSVOL and
NETLOGON.

This is a very simple system. It is the Active Directory domain
controller, the only domain controller, and the only server (it supports
8 client computers). It is the DNS server. There's no Exchange server,
no IIS, and at 2.4 GHz and 512MB memory, I don't think it will be
overloaded. :-)

The users don't use anything on the netlogon share; we don't run any
logon scripts. But I suppose the share should exist, along with SYSVOL.

I read article http://support.microsoft.com/default.aspx?scid=kb;en-
us;315457 about rebuilding the SYSVOL tree and its contents in a domain.

Good grief that's a complicated article. I don't have any replication
to worry about, and the folders are there. But how am I supposed to
"verify" that the reparse points are there? Article says:

"b. Verify that the following reparse points exist:
\SYSVOL\SYSVOL\ DNS Domain Name
This reparse point must be linked to the \SYSVOL\domain folder.

\SYSVOL\staging\DNS Domain Name
This reparse point must be linked to the \SYSVOL\staging\domain folder.

I know what reparse points are, how do I verify that they point to the
right thing? There appears a folder call \SYSVOL\SYSVOL\<My domain
name>, and I suppose that's the reparse point.

If I'm supposed to use LINKD to verify the reparse points, that's a
problem: I don't have LINKD on my system, and I installed the support
tools from the CD.

The next problem is that the article says to also use the ntfrsutl tool
(although in the next sentence it's called the ntfrsutil tool, spelled
differently). That tool doesn't come with Windows 2000 Advanced Server,
even in the support tools (using either spelling), and I can't find it
for download.

Lastly, I have read, in the vastness of the Internet, that I should not
use Windows Explorer to manually recreate those shares. So I am stuck
following this complex KB article that talks about replication partners,
and what to do if you have more than 15 "downstream partners of any
particular source domain controlle", when all I probably need is these
shares re-created.

Any suggestions? Any simple way out of this situation?

Thanks for any advice.

David Walker

"Robert L [MS-MVP]" <(E-Mail Removed)> wrote in
news:(E-Mail Removed):

> run dcdiag and netdiag. post back with any errors.
>
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on
> http://www.ChicagoTech.net How to Setup Windows, Network, VPN & Remote

DCDiag shows lots of errors. Here's the whole thing. (By the way, on
system log, what's with the truncated message that says "Event String:
DCOM got error "%1058" attempting to start the"????)

----

DC Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial non skippeable tests

Testing server: Default-First-Site-Name\NTAS
Starting test: Connectivity
......................... NTAS passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\NTAS
Starting test: Replications
......................... NTAS passed test Replications
Starting test: NCSecDesc
......................... NTAS passed test NCSecDesc
Starting test: NetLogons
......................... NTAS passed test NetLogons
Starting test: Advertising
Fatal ErrorsGetDcName (NTAS) call failed, error 1355
The Locator could not find the server.
......................... NTAS failed test Advertising
Starting test: KnowsOfRoleHolders
......................... NTAS passed test KnowsOfRoleHolders
Starting test: RidManager
......................... NTAS passed test RidManager
Starting test: MachineAccount
......................... NTAS passed test MachineAccount
Starting test: Services
TrkWks Service is stopped on [NTAS]
IISADMIN Service is stopped on [NTAS]
SMTPSVC Service is stopped on [NTAS]
......................... NTAS failed test Services
Starting test: ObjectsReplicated
......................... NTAS passed test ObjectsReplicated
Starting test: frssysvol
Error: No record of File Replication System, SYSVOL started.
The Active Directory may be prevented from starting.
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
......................... NTAS passed test frssysvol
Starting test: kccevent
An Warning Event occured. EventID: 0x80000679
Time Generated: 10/17/2005 10:31:45
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC00005BA
Time Generated: 10/17/2005 10:31:45
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x80000581
Time Generated: 10/17/2005 10:31:45
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC000055D
Time Generated: 10/17/2005 10:31:45
(Event String could not be retrieved)
......................... NTAS failed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0xC0002715
Time Generated: 10/17/2005 10:01:45
Event String: DCOM got error "%1058" attempting to start the

An Error Event occured. EventID: 0xC0002715
Time Generated: 10/17/2005 10:31:45
Event String: DCOM got error "%1058" attempting to start the

......................... NTAS failed test systemlog

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

"Robert L [MS-MVP]" <(E-Mail Removed)> wrote in
news:(E-Mail Removed):

> run dcdiag and netdiag. post back with any errors.
>
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on
> http://www.ChicagoTech.net How to Setup Windows, Network, VPN & Remote
> Access on http://www.HowToNetworking.com

Oh, sorry, Netdiag just says this:

[FATAL] Failed to get system information of this machine.

And thanks for your help, I appreciate it.

David

Any advice from anyone after seeing the DCDIAG and NETDIAG results I
posted?

Should I run DCPromo to un-promote and re-promote the domain controller?

Thanks.

David Walker

DWalker <(E-Mail Removed)> wrote in news:uqJ5kFM1FHA.3864
@TK2MSFTNGP12.phx.gbl:

> Any advice from anyone after seeing the DCDIAG and NETDIAG results I
> posted?
>
> Should I run DCPromo to un-promote and re-promote the domain controller?
>
> Thanks.
>
> David Walker
>

I guess Robert L is busy. Does anyone else have any advice? I would
appreciate it.

David Walker

DWalker <(E-Mail Removed)> wrote in news:#8oaoRZ1FHA.3568
@TK2MSFTNGP15.phx.gbl:

> DWalker <(E-Mail Removed)> wrote in news:uqJ5kFM1FHA.3864
> @TK2MSFTNGP12.phx.gbl:
>
>> Any advice from anyone after seeing the DCDIAG and NETDIAG results I
>> posted?
>>
>> Should I run DCPromo to un-promote and re-promote the domain
controller?
>>
>> Thanks.
>>
>> David Walker
>>
>
> I guess Robert L is busy. Does anyone else have any advice? I would
> appreciate it.
>
> David Walker
>

As I posted in another NG in an effort to find suggestions on how to fix
this...

I discovered that the real problem was addressed in 819268: the increase
in the size of the journal for FRS wants 512 MB disk space.

I know that the guidelines for where to put SYSVOL says the disk should
have "adequate space", but since we don't USE the distributed file
system, and there are no other domain controllers for Active Directory
replication, I figured 400 MB free space on the C drive (where I left
SYSVOL) would be plenty.

After all, how much disk space does it take to store a journal for a
system that's not going to replicate with anyone? (I started with a 4
GB partition, but then I copied the Windows 2000 AD source to the same
disk along with a copy of the motherboard's driver CD, which itself took
600 meg -- mostly useless audio drivers.) Then Windows server itself.

Now I know better... next time, I'll make the system partition 20 GB.

In article 819268, I followed the option to set the USN journal size
back to 128 MB. Then I did the D4 thing, and everything is working. It
took me a week to get this figured out.

David