Prev: AD GPO to control Windows Firewall Settings
Next: Logon Failure: The target account name is incorrect.
From: Ada Pan [MSFT] on 5 Sep 2006 05:54
Hello Allen,

How are you?

We have not heard from you regarding this issue. Please post back here at
your convenience if we can assist further.

Regards,

Ada Pan

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

From: Allen on 5 Sep 2006 06:42
Well, last night I transfered the 5 roles over to DC2. I also did a D2 on
DC1. Now the good news is that it rebuilt the SYSVOL with some help of
creating two directories. What I am concerned about right now is that DC2 is
not updating the profiles. I am starting to see events of 13508 on DC2
showing replication issues. It is failing to replicate from DC1 to DC2.

Would re-building the connectors be advised? Or would doing a Directory
Service restore on DC2 be recommended?

I am still trying to figure out why replication isnt completely working. I
am starting to think it has to do with RPC connections which is why I want to
rebuild the connection. But I would have to do this on a weekend at night.

Any suggestions are welcome. Thanks.

"Ada Pan [MSFT]" wrote:

> Hello Allen,
>
> How are you?
>
> We have not heard from you regarding this issue. Please post back here at
> your convenience if we can assist further.
>
> Regards,
>
> Ada Pan
>
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
> ====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ====================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
From: Harj on 5 Sep 2006 13:23
Hi,

Not sure what you mean by re-building the connectors but I would highly
recommend to let the KCC do it on its own and not for you to create
manual connection objects.

I would point both these DC's to the PDC emulator for primary DNS.
I would then run the following commands on both DC's
ipconfig /flushdns & ipconfig /registerdns & net stop netlogon & net
start netlogon.
Go to Sites/Services and delete the connection objects from both
machines.
Then stop and start the NTFRS service.
Trigger the KCC by right clicking the NTDS Settings under the Domain
controllers in Sites/Services, all tasks and click Check Replication
Topology.
Wait for the connection objects to be recreated and then look for any
errors in the event logs.

Good luck

Harj Singh
Power Your Active Directory Investment
www.specopssoft.com


Allen wrote:
> Well, last night I transfered the 5 roles over to DC2. I also did a D2 on
> DC1. Now the good news is that it rebuilt the SYSVOL with some help of
> creating two directories. What I am concerned about right now is that DC2 is
> not updating the profiles. I am starting to see events of 13508 on DC2
> showing replication issues. It is failing to replicate from DC1 to DC2.
>
> Would re-building the connectors be advised? Or would doing a Directory
> Service restore on DC2 be recommended?
>
> I am still trying to figure out why replication isnt completely working. I
> am starting to think it has to do with RPC connections which is why I want to
> rebuild the connection. But I would have to do this on a weekend at night.
>
> Any suggestions are welcome. Thanks.
>
> "Ada Pan [MSFT]" wrote:
>
> > Hello Allen,
> >
> > How are you?
> >
> > We have not heard from you regarding this issue. Please post back here at
> > your convenience if we can assist further.
> >
> > Regards,
> >
> > Ada Pan
> >
> > Microsoft Online Partner Support
> > Get Secure! - www.microsoft.com/security
> > ====================================================
> > When responding to posts, please "Reply to Group" via your newsreader so
> > that others may learn and benefit from your issue.
> > ====================================================
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> >

From: Allen on 6 Sep 2006 07:19
That was what I was refering to. I will give that a shot. Have you ever had
this interfere with users in a very noticable way? If not I will give this a
shot today. If it does interfere I will have to wait until Friday night to do
it. I havent done this part before so I want to make sure.



"Harj" wrote:

> Hi,
>
> Not sure what you mean by re-building the connectors but I would highly
> recommend to let the KCC do it on its own and not for you to create
> manual connection objects.
>
> I would point both these DC's to the PDC emulator for primary DNS.
> I would then run the following commands on both DC's
> ipconfig /flushdns & ipconfig /registerdns & net stop netlogon & net
> start netlogon.
> Go to Sites/Services and delete the connection objects from both
> machines.
> Then stop and start the NTFRS service.
> Trigger the KCC by right clicking the NTDS Settings under the Domain
> controllers in Sites/Services, all tasks and click Check Replication
> Topology.
> Wait for the connection objects to be recreated and then look for any
> errors in the event logs.
>
> Good luck
>
> Harj Singh
> Power Your Active Directory Investment
> www.specopssoft.com
>
>
> Allen wrote:
> > Well, last night I transfered the 5 roles over to DC2. I also did a D2 on
> > DC1. Now the good news is that it rebuilt the SYSVOL with some help of
> > creating two directories. What I am concerned about right now is that DC2 is
> > not updating the profiles. I am starting to see events of 13508 on DC2
> > showing replication issues. It is failing to replicate from DC1 to DC2.
> >
> > Would re-building the connectors be advised? Or would doing a Directory
> > Service restore on DC2 be recommended?
> >
> > I am still trying to figure out why replication isnt completely working. I
> > am starting to think it has to do with RPC connections which is why I want to
> > rebuild the connection. But I would have to do this on a weekend at night.
> >
> > Any suggestions are welcome. Thanks.
> >
> > "Ada Pan [MSFT]" wrote:
> >
> > > Hello Allen,
> > >
> > > How are you?
> > >
> > > We have not heard from you regarding this issue. Please post back here at
> > > your convenience if we can assist further.
> > >
> > > Regards,
> > >
> > > Ada Pan
> > >
> > > Microsoft Online Partner Support
> > > Get Secure! - www.microsoft.com/security
> > > ====================================================
> > > When responding to posts, please "Reply to Group" via your newsreader so
> > > that others may learn and benefit from your issue.
> > > ====================================================
> > > This posting is provided "AS IS" with no warranties, and confers no rights.
> > >
> > >
>
>
From: Harj on 6 Sep 2006 11:08
Hi,

It will not interfere with the end users as we are working on fixing
replication.
As long as the DC's and GC's are reachable, users will be ok.

Just make sure that the users are still pointed to a valid DNS server
is all I can think of.

Good luck

Harj Singh
Power Your Active Directory Investment
www.specopssoft.com


Allen wrote:
> That was what I was refering to. I will give that a shot. Have you ever had
> this interfere with users in a very noticable way? If not I will give this a
> shot today. If it does interfere I will have to wait until Friday night to do
> it. I havent done this part before so I want to make sure.
>
>
>
> "Harj" wrote:
>
> > Hi,
> >
> > Not sure what you mean by re-building the connectors but I would highly
> > recommend to let the KCC do it on its own and not for you to create
> > manual connection objects.
> >
> > I would point both these DC's to the PDC emulator for primary DNS.
> > I would then run the following commands on both DC's
> > ipconfig /flushdns & ipconfig /registerdns & net stop netlogon & net
> > start netlogon.
> > Go to Sites/Services and delete the connection objects from both
> > machines.
> > Then stop and start the NTFRS service.
> > Trigger the KCC by right clicking the NTDS Settings under the Domain
> > controllers in Sites/Services, all tasks and click Check Replication
> > Topology.
> > Wait for the connection objects to be recreated and then look for any
> > errors in the event logs.
> >
> > Good luck
> >
> > Harj Singh
> > Power Your Active Directory Investment
> > www.specopssoft.com
> >
> >
> > Allen wrote:
> > > Well, last night I transfered the 5 roles over to DC2. I also did a D2 on
> > > DC1. Now the good news is that it rebuilt the SYSVOL with some help of
> > > creating two directories. What I am concerned about right now is that DC2 is
> > > not updating the profiles. I am starting to see events of 13508 on DC2
> > > showing replication issues. It is failing to replicate from DC1 to DC2.
> > >
> > > Would re-building the connectors be advised? Or would doing a Directory
> > > Service restore on DC2 be recommended?
> > >
> > > I am still trying to figure out why replication isnt completely working. I
> > > am starting to think it has to do with RPC connections which is why I want to
> > > rebuild the connection. But I would have to do this on a weekend at night.
> > >
> > > Any suggestions are welcome. Thanks.
> > >
> > > "Ada Pan [MSFT]" wrote:
> > >
> > > > Hello Allen,
> > > >
> > > > How are you?
> > > >
> > > > We have not heard from you regarding this issue. Please post back here at
> > > > your convenience if we can assist further.
> > > >
> > > > Regards,
> > > >
> > > > Ada Pan
> > > >
> > > > Microsoft Online Partner Support
> > > > Get Secure! - www.microsoft.com/security
> > > > ====================================================
> > > > When responding to posts, please "Reply to Group" via your newsreader so
> > > > that others may learn and benefit from your issue.
> > > > ====================================================
> > > > This posting is provided "AS IS" with no warranties, and confers no rights.
> > > >
> > > >
> >
> >

 |  Next  |  Last
Pages: 1 2 3 4 5
Prev: AD GPO to control Windows Firewall Settings
Next: Logon Failure: The target account name is incorrect.