Prev: AD GPO to control Windows Firewall Settings
Next: Logon Failure: The target account name is incorrect.
From: Ada Pan [MSFT] on 2 Oct 2006 02:44
Hello Allen,

As only the DFS share for profiles did not work, I think that we may
recreate the DFS link for the share to see if the folder can be replicated
successfully? I will be here standing by for your update.

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 2 Oct 2006 06:26
Hi Ada,

Well so far none of the profiles have replicated from DC1 to DC2. The
"warnings" I am getting on DC1 are in direct correlation to the profiles
(i.e. 13508). The other warnings on DC1 have stopped. On DC2 however, the
13509's are in relation to replication on the e:\sysvol\domain, e:\user\incl,
and e:\user\logs. I am thinking these are in relation to each other. Would I
be correct by thinking that?

Best Regards,
Allen

"Ada Pan [MSFT]" wrote:

> Hello Allen,
>
> As only the DFS share for profiles did not work, I think that we may
> recreate the DFS link for the share to see if the folder can be replicated
> successfully? I will be here standing by for your update.
>
> 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: Ada Pan [MSFT] on 3 Oct 2006 21:56
Hello Allen,

The event 13508 on the DC1 may not be relevant to the event 13509 on the
DC2 in this case. This is the reason that I suggest recreating the DFS link
for the profile folder individually.

Hope this helps!

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 4 Oct 2006 13:10
Hi Ada,

Yeah i was going to re-create the DFS link anyways for the Profiles. I just
wasnt sure if that was a seperate issue or the same. So I figured I would
ask. I will let you know how it turns out. I will give you an update Thursday
before I leave for the day.

Best Regards,
Allen

"Ada Pan [MSFT]" wrote:

> Hello Allen,
>
> The event 13508 on the DC1 may not be relevant to the event 13509 on the
> DC2 in this case. This is the reason that I suggest recreating the DFS link
> for the profile folder individually.
>
> Hope this helps!
>
> 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: "Ada Pan [MSFT]" on 11 Oct 2006 08:03
Hello Allen,

I am glad to hear that you will apply my suggestion to rebuild the DFS root
and links. Hope to hear from you with good news.

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.

First  |  Prev  |  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.