Roaming profile not working on two nodes

[Rajiv K Khandelwal]

Am using SBS 2002 with 5 nodes with Windows XP SP3 - one of the nodes was
formatted yesterday. In one node, except for one profile, no other roaming
profile is working. The same is the situation with the new installation.

I shall appreciate if some one can guide where I am going wrong.

Thanking you in advance,

R. K. Khandelwal

 

[Holz]

Am using SBS 2002 with 5 nodes with Windows XP SP3 - one of the nodes was
formatted yesterday. In one node, except for one profile, no other roaming
profile is working. The same is the situation with the new installation.

I shall appreciate if some one can guide where I am going wrong.

Thanking you in advance,

R. K. Khandelwal

Any entries in the event viewer?
How about your settings? Can you post?
Much more details needed.

 

[Rajiv K Khandelwal]

Dear Holz,

Thank you for your response. I am copying a few event logs both from the SBS
and Client below:

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1053
Date: 9/23/2008
Time: 12:36:09 PM
User: NT AUTHORITY\SYSTEM
Computer: V2
Description:
Windows cannot determine the user or computer name. (The specified domain
either does not exist or could not be contacted. ). Group Policy processing
aborted.

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


Event Type: Error
Event Source: AutoEnrollment
Event Category: None
Event ID: 15
Date: 9/23/2008
Time: 12:36:10 PM
User: N/A
Computer: V2
Description:
Automatic certificate enrollment for local system failed to contact the
active directory (0x8007052b). Unable to update the password. The value
provided as the current password is incorrect.
Enrollment will not be performed.

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

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1511
Date: 9/23/2008
Time: 10:06:33 AM
User: S-1-5-21-3988696794-1301930184-1235530033-1139
Computer: V2
Description:
Windows cannot find the local profile and is logging you on with a temporary
profile. Changes you make to this profile will be lost when you log off.

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

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5722
Date: 23/09/2008
Time: 12:52:33 PM
User: N/A
Computer: SERVER
Description:
The session setup from the computer V2 failed to authenticate. The name(s)
of the account(s) referenced in the security database is V2$. The following
error occurred:
Access is denied.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 22 00 00 c0 "..À

R. K. Khandelwal

 

[Rajiv K Khandelwal]

Dear Cliff,

I am using Windows XP Professional in all nodes.

My SBS has been working uninterupedly for the past 3 years and when ever I
formatted a node and connected to the domain, it got connected and the
profiles worked. I never used the connectcomputer wizard.

Have posted the event logs as asked by Holz prior to you.

Thanking you,

R. K. Khandelwal

 

[Rajiv K Khandelwal]

Cliff,

Thanks for your advice. I have followed it and had to recreate the profiles.
Fortunately, I do not have many users and so was able to do it.

Can someone guide me of learning how to deploy the settings from one site
and to restrict internet to users?

Thanking you once again.

R. K. Khandelwal

 

[SteveB]

Its best to start a new thread/topic for your additional questions.

 

[Holz]

As I indicated in my previous post, the roaming profile share cannot
be accessed. Of course, what I didn't know at the time was the WHY.
But your logs indicate that your machine's account password does not
match the password in Active Directory. This is usually caused
because a machine was not properly added using the connectcomputer
wizard. You will have to unjoin the computer from the domain, delete
the account in AD, and then rejoin the domain. That'll create a new
account with a new password and allow the computer to properly
authenticate. Once it is authenticating it *should* be able to access
the roaming profile share, assuming those permissions are correct. I
have no reason to believe the permissions are wrong though, being
other computers roam properly.

-Cliff


"

Cliff, what's with the **XXXX** ?