Re: NTFRSUTIL error 1753

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



In news:OMemEJ5nJHA.4392@xxxxxxxxxxxxxxxxxxxx,
Thomas R Grassi Jr <thomasgrassi@xxxxxxxxxxx>, posted the following:
Isaac

It was about 1 week ago I brought it online
Yes DC2 did not complete initialzation of sysvol

I turned off windows firewall on both dc's

made some changes to the registry per kb319553 kb224196

I was at work today and when I came home I saw that SYSVOL and
NETLOGON was created as shares and now when I run
ntfrsutl dc dc1 it shows valid info

now the big test will be turning on the firewalls on both dcs to see
what happens

Thanks

tom

Tom,

AD communication between DCs requires 29 ports opened and free and clear, including the dynamic ephemeral response ports (UDP > 1023). I recommend there are no firewalls (whether local or on a VPN/router) between domain controllers in a forest blocking ports. This will insure DCs can communicate with each other, as well as clients can communicate with the DCs.

--
Ace

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

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer
aceman@xxxxxxxxxxxxxxxxxxxxxxx

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.


.



Relevant Pages

  • Re: Floating Computer between domains
    ... Windows itself is generally weak in this area but with DCs it can get especially bad with DNS registrations and other issues. ... can I simply put a second network card into the domain ... communicate with eachother, all other machines in the respective ... networks would have to talk to the domain controller that is connected ...
    (microsoft.public.windows.server.active_directory)
  • Re: Group policy and File Replication Service
    ... > I was referring to the instance when it is on the network, but its SYSVOL ... >>> DCs from a GP perspective is to run GPOTool.exe against all your DCs. ... the Windows Group Policy Guide is out from Microsoft Press!!! ...
    (microsoft.public.windows.group_policy)
  • RE: migration prolems from NT 4.0 to W2k
    ... the out new Win2K server cannot communicate with the other DCs in ... DCs in Headquarter and the Windows 2k DC? ... This posting is provided "AS IS" with no warranties, ...
    (microsoft.public.windows.server.migration)
  • Re: SYSVOL not replicating on 2003 DCs
    ... One thing I just realized is two of the DCs are missing NETLOGON shares. ... seen the sysvolready registry key to enable the sysvol share and I know ... you're not supposed to share out netlogon and sysvol with windows explorer, ...
    (microsoft.public.windows.server.active_directory)
  • RE: AD Client vs Sites and Services
    ... Also a tip to decrease you SYSVOL size by removing duplicated admin ... FSMO Roles DCs ... Services says it contains location B's subnet? ...
    (microsoft.public.windows.server.active_directory)