Windows Server

Jon G · Guest

We just noticed this morning that some of our DCs are not up to date with
files in the netlogon share. We have examined all of our event logs, and
there are no reported problems.

We are a mixed 2000/2003 domain. Our "hub" site has 2 recently upgraded
2003 domain controllers. All of our "spoke" sites are 2000sp4. This
problem is only happening at 2 or 3 (of our 9) sites.

I don't even know where to start in troubleshooting this type of problem.
Heck, I don't even know if this is the correct newsgroup :)

Jill Zoeller [MSFT] · Guest

You've come to the right place! Check out our FRS monitoring tools up on
http://www.microsoft.com/windowsserver2003/technologies/fileandprint/file/dfs/tshootfrs.mspx.
You can try Ultrasound, Sonar, or FRSDiag; the latter two are faster to
install/run but Ultrasound will give you the richest monitoring.

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

"Jon G" <jgarlock@jhcohn.com> wrote in message
news:OHlJa992EHA.3336@TK2MSFTNGP11.phx.gbl...

Glenn L · Guest

John,

The first place to look if the FRS event logs. Youv'e stated they are clean.
Do not manually copy the missing or older files onto the DCs that are not up
to date. This does not help FRS to recover.
The next thing to do is place a canary file into the netlogon share on a DC
that is up to date. An empty text file with the name of the server and
current time as the file name.
Does it replicate around to all DCs?
No.......install FRSdiag on your XP workstation and run it against the DCs
that did not pickup the file and review the results.
Yes.......Make a benign change to one of the 'affected' files in the
netlogon share on a DC that is up to date. This could be adding a security
descriptor, or adding a REM entry in one of the files.

Does it replicate around to all DCs?
No.........FRSDIAG against the DC that did not receive the change and review
the results.

--
Glenn L

CCNA, MCSE (2000,2003) + Security
"Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
news:u0ngo%23%232EHA.3820@TK2MSFTNGP11.phx.gbl...

Guest

Glenn L wrote:

I wrote
run replmon on the dc,s and check if sysvol is consistant eg: check the
numbers for sysvol.

are any dc,s flapping frs eg: stoping starting the service.

Jon G · Guest

Thanks for your prompt and helpful response! I guess I've found the tip of
the iceberg here, and it's enough to get me started.

The problem is limited to a single domain controller. Not coincidentally,
this server recently experienced some disk troubles and had system state
restored from backup. Still, to be sure, I ran FRSDiag against all domain
controllers .. and, sure enough, the only one with problems was that guy.

FRSDiag reports this:
Checking Overall Disk Space and SYSVOL structure (note: integrity is not
checked)...
ERROR: Junction Point missing on "\\SERVER\d$\winnt\sysvol\sysvol"
ERROR: Junction Point missing on "\\SERVER\d$\winnt\sysvol\staging areas"
......... failed 2

Amd I'm not sure how to troubleshoot/resolve. Google doesn't reveal much of
anything, and searching this newsgroup pointed me at kb 315457, which is
*very* intimidating. Stopping FRS on *all* DC's? Hell, I'd rather demote
and re-promote that one DC, but I don't know if that's even an option.
Basically, anything that doesn't require me to coordinate with 8 offices
would be preffered!

Any advice appreciated ..

"Jill Zoeller [MSFT]" <jillz@online.microsoft.com> wrote in message
news:u0ngo%23%232EHA.3820@TK2MSFTNGP11.phx.gbl...

Jill Zoeller [MSFT] · Guest

Try a combination of http://support.microsoft.com/?id=324175 and
http://support.microsoft.com/Default.aspx?id=205524.

I believe a non-authoritative restore on the troubled member will also fix
the junction point: http://support.microsoft.com/?id=290762.

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

"Jon G" <jgarlock@jhcohn.com> wrote in message
news:O8J0E2G3EHA.3932@TK2MSFTNGP12.phx.gbl...

	Windows Server Forum Index -> DFS and FRS	All times are GMT
Page 1 of 1