id: 1000, id: 13540

[miguel]

Help please
HELP!

Event ID: 1000

Windows cannot access the registry information at
\\myred.local\sysvol\myred.local\Policies\{31B2F340-016D-
11D2-945F-00C04FB984F9}\Machine\registry.pol with (53).

This is only one domain controller with one network
card!... problems with sysvol
Can't open (in AD Users and Computers) domain controllers
group policy (domain controller not found).. and File
Replication Service logs:

The File Replication Service cannot replicate
d:\winnt\sysvol\domain because the pathname of the
customer designated staging directory:
d:\winnt\sysvol\staging\domain
is not the fully qualified pathname of an existing,
accessible local directory.

Please advice!!

 

[Ace Fekay [MVP]]

In

Help please
HELP!

Event ID: 1000

Windows cannot access the registry information at
\\myred.local\sysvol\myred.local\Policies\{31B2F340-016D-
11D2-945F-00C04FB984F9}\Machine\registry.pol with (53).

This is only one domain controller with one network
card!... problems with sysvol
Can't open (in AD Users and Computers) domain controllers
group policy (domain controller not found).. and File
Replication Service logs:

The File Replication Service cannot replicate
d:\winnt\sysvol\domain because the pathname of the
customer designated staging directory:
d:\winnt\sysvol\staging\domain
is not the fully qualified pathname of an existing,
accessible local directory.

Please advice!!

Couple things can cause this:

1. You are not using your internal DNS server on your DCs and clients' IP
properties.
2. You have an ISP DNS listed in DCs and clients' IP properties. They need
to be removed and only use your internal DNS. You can configure a forwarder
for efficient Internet resolution.
3. Your domain may be a single label name (such as "domain" instead of the
required "domain.com" or "domain.net", etc, format.

My feeling is #2.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Guest]

-----Original Message-----
In miguel <[email protected]> posted their thoughts, then I
offered mine

Couple things can cause this:

1. You are not using your internal DNS server on your DCs and clients' IP
properties.
2. You have an ISP DNS listed in DCs and clients' IP properties. They need
to be removed and only use your internal DNS. You can configure a forwarder
for efficient Internet resolution.
3. Your domain may be a single label name (such as "domain" instead of the
required "domain.com" or "domain.net", etc, format.

My feeling is #2.


--
Regards,
Ace

=================================


my domain is as stated on event id 13540. not single

label.

all my machines go though my server for name resolution
and get assinged ip by dhcp from the same sever. they get
on the internet using my server.

 

[Ace Fekay [MVP]]

In

my domain is as stated on event id 13540. not single label.

all my machines go though my server for name resolution
and get assinged ip by dhcp from the same sever. they get
on the internet using my server.

Hi

See if these two articles help with this issue:

http://www.eventid.net/display.asp?eventid=13540&source=
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q265085


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[miguel ramirez]

-----Original Message-----
In (e-mail address removed)

posted their thoughts, then I offered mine


Hi

See if these two articles help with this issue:

http://www.eventid.net/display.asp?eventid=13540&source=
http://support.microsoft.com/default.aspx?scid=kb;en- us;Q265085


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

TAPE... I HAD TO COPY SYSVOL (PREVIOUSLY ON DRIVE C
BEFORE RESTORING) ON DRIVE D AND THAT FIXED IT, THEN I
FOLLOWED LOGIC!!!
THANKS MAN!!!!!!!!!!!!!

 

[Ace Fekay [MVP]]

In

TAPE... I HAD TO COPY SYSVOL (PREVIOUSLY ON DRIVE C
BEFORE RESTORING) ON DRIVE D AND THAT FIXED IT, THEN I
FOLLOWED LOGIC!!!
THANKS MAN!!!!!!!!!!!!!

Sounds good! Glad to have been of assistance.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory