Re: missing netlogon & Sysvol Share

Tech-Archive recommends: Fix windows errors by optimizing your registry



check DNS and TCP/IP settings of servers

--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)

# Jorge de Almeida Pinto # MVP Windows Server - Directory Services

BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
"rknapke" <rknapke@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8A6835D6-8060-44CD-8FAC-D661CB51B297@xxxxxxxxxxxxxxxx
I have 2 servers in my domain. One is W2K (server1) and the other is W2K3
(server2). Both are DC's. I want to eventually get rid of server1. My
problem is server2 is missing the Sysvol and Netlogon Shares. I can
manually
create them but after a reboot they disappear. AD seems to replicate just
fine and my DNS is working properly. I have both servers set to Server2
as
primary and Server1 as secondary. I can ping both by name and IP. The
only
thing not working properly is my policies and logon scripts are
replicating.
In the event log of server2, i am constantly getting warning 13508 in the
FRS
log:

The File Replication Service is having trouble enabling replication from
SERVER1 to SERVER2 for c:\windows\sysvol\domain using the DNS name
server.domain.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name server.domain.local from
this computer.
[2] FRS is not running on server.domain.local.
[3] The topology information in the Active Directory for this replica has
not yet replicated to all the Domain Controllers.

This event log message will appear once per connection, After the problem
is fixed you will see another event log message indicating that the
connection has been established.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

On Server1, i am getting error 5719 in the system log:

No Windows NT or Windows 2000 Domain Controller is available for domain
DOMAIN. The following error occurred:
There are currently no logon servers available to service the logon
request.

Can someone please help me with this issue.
Thanks in advance.
Rich


.



Relevant Pages

  • Re: missing netlogon & Sysvol Share
    ... Active Directory Operations Overview ... Troubleshooting File Replication Service ... problem is server2 is missing the Sysvol and Netlogon Shares. ... This event log message will appear once per connection, ...
    (microsoft.public.windows.server.active_directory)
  • Re: missing netlogon & Sysvol Share
    ... Troubleshooting File Replication Service ... problem is server2 is missing the Sysvol and Netlogon Shares. ... This event log message will appear once per connection, ... No Windows NT or Windows 2000 Domain Controller is available for domain ...
    (microsoft.public.windows.server.active_directory)
  • Re: Sysvol Rep issues..tried many things
    ... that using ADI with 2003 and 2000 requires that you configure the DNS ... zone properties to allow replication to windows 2000. ... Try not to mess with sysvol perm. ... DC (server2). ...
    (microsoft.public.windows.server.active_directory)
  • Re: missing netlogon & Sysvol Share
    ... DNS is working properly and TCP is set correctly also. ... problem is server2 is missing the Sysvol and Netlogon Shares. ... The File Replication Service is having trouble enabling replication from ... This event log message will appear once per connection, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Active directory replication problems
    ... Server1 is still configured to use Server2 for it's only DNS. ... Warning: SERVER2 is the Schema Owner, but is not responding to DS ... The File Replication Service Event log test ...
    (microsoft.public.windows.server.sbs)