Re: NTFRSUTIL error 1753
- From: "Ace Fekay [Microsoft Certified Trainer]" <firstnamelastname@xxxxxxxxxxx>
- Date: Sun, 8 Mar 2009 03:27:32 -0400
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.
.
- Follow-Ups:
- Re: NTFRSUTIL error 1753
- From: Thomas R Grassi Jr
- Re: NTFRSUTIL error 1753
- References:
- NTFRSUTIL error 1753
- From: Thomas R Grassi Jr
- Re: NTFRSUTIL error 1753
- From: Isaac Oben -MCSE, MCITP
- Re: NTFRSUTIL error 1753
- From: Thomas R Grassi Jr
- NTFRSUTIL error 1753
- Prev by Date: Re: NTFRSUTIL error 1753
- Next by Date: Re: New DC added need help
- Previous by thread: Re: NTFRSUTIL error 1753
- Next by thread: Re: NTFRSUTIL error 1753
- Index(es):
Relevant Pages
|