The active Directory property cannot be found in the cache!!!!

[Sam]

Hi folks

can anyone help me out on this. I get it when in sites and services when I
check the replication topology on a NTDS Setting.

we have 2 sites connected over a wan link every thing else seems to work
except the domain controller in the second site will share the sysvol and
netlogon folders to complete the promotion the DC. I'm stumped I have tried
changing dns servers deleting and creating new links, net stop ntfrs, net
stop netlogon, using regedit doing a restore but nothing at all.

Any ideas anyone!!!!!

[Matjaz Ladava]

If it is a DC then it is normal to share out sysvol and netlogon folder. If
you suspect any unusual behavior on your system, then please run dcdiag and
netdiag to get extended diagnose report on your problem.

--
Regards

Matjaz Ladava, MCSE (NT4 & 2000)
mat...@ladava.com
http://ladava.com

"Sam" <bone...@hotmail.com> wrote in message
news:OCFRbRLN...@tk2msftngp13.phx.gbl...

[Sam]

Sorry typo error the DC has not shared the sysvol and netlogon folder. I
have already run the diag tools and the only error I can see is in File
replication service. It says it carnt find the other DC in the othersite in
event log. Yet you can ping it by IP address and FQDN and see it using
NSlookup?

"Matjaz Ladava" <matjaz@_nospam_ladava.com> wrote in message
news:eXBonWLN...@TK2MSFTNGP12.phx.gbl...

[Matjaz Ladava]

You must see if your DC is registering SRV records in your DNS server ? Are
betwean those servers any NAT/firewalls which could filter/block trafic.
Try connecting \\server\sysvol from each location (each DC) to verify that
you can connect sysvol folder.

--
Regards

Matjaz Ladava, MCSE (NT4 & 2000)
mat...@ladava.com
http://ladava.com

"Sam" <bone...@hotmail.com> wrote in message

news:uUOt7iLN...@TK2MSFTNGP12.phx.gbl...

[Sam]

I can see SRV records for both domain controllers in both DNS servers
(running AD DNS) there are no firwalls as its leased line and filtering. The
Dc in the other site can be connecting to \\server\sysvol but the newer dc
that has the problem cannot be seen using \\server\sysvol.

"Matjaz Ladava" <matjaz@_nospam_ladava.com> wrote in message

news:ux3TE0LN...@tk2msftngp13.phx.gbl...

[Travis Albrecht]

I had this problem recently, it was because of DNS records, even though they
appeared OK. It ended up being the CNAME to GUID record under
_msdcs.domain.tld.

Verify that all records are the same in the zones on all servers. Check to
see what REPLMON reports as the GUID for the troubled server, compare that
to the GUID reported in NETDIAG, and DNS.

After I deleted the offending record, created it with the proper GUID and
then re-ran NETDIAG /fix on the offending server all other SRV records were
fixed. The changes took a while to replicate and then everything smoothed
out.

here is a Q article to point you in the right direction
http://support.microsoft.com/?kbid=224544

If you need more help feel free to email me.

Travis Albrecht
Werner Electric Supply
Business Systems Engineer

"Matjaz Ladava" <matjaz@_nospam_ladava.com> wrote in message

news:ux3TE0LN...@tk2msftngp13.phx.gbl...