Roaming Profile fails to update on one XP machine

I have set up roaming profiles on our small business network. We are running
W2k3 Server. Most profiles roam fine, but my profile will neither download
to the computer I primarily use nor upload from it back to the server. My
profile does, however, update on other computers. It's just that any changes
I make on my computer are not reflected on the others and vice versa.

I basically have a roaming profile on all of the workstations except for my
own, where I practically have a local profile. Our workstations are running
XP Pro with a mix of SP1 and SP2. My computer has SP1.

I'm not getting any errors about it being unable to load my profile. I even
installed UPHClean, but the problem persists.

My profile is about 50MB. (It was about 200 MB before I redirected the My
Documents folder to a network drive.) The problem preceded that change.

I have full control of the folder where my profile is stored.

Thanks for any help.

WW

"Wesley Wilson" <(E-Mail Removed)> wrote in message
news:71CD37DA-A929-481A-9845-(E-Mail Removed)...
> I have set up roaming profiles on our small business network. We are
running
> W2k3 Server. Most profiles roam fine, but my profile will neither
download
> to the computer I primarily use nor upload from it back to the server. My
> profile does, however, update on other computers. It's just that any
changes
> I make on my computer are not reflected on the others and vice versa.

That sounds like an authentication (which is usually
a name resolution) problem or a pure name resolution
problem.

IF the client cannot resolve the roaming profiles server
or is operating from cached credentials because it cannot
find a DC or otherwise authenticate the above symptoms
would be expected.

> I basically have a roaming profile on all of the workstations except for
my
> own, where I practically have a local profile. Our workstations are
running
> XP Pro with a mix of SP1 and SP2. My computer has SP1.

You can localize a single machine (or machines) using
the local System control panel.

> I'm not getting any errors about it being unable to load my profile. I
even
> installed UPHClean, but the problem persists.
>
> My profile is about 50MB. (It was about 200 MB before I redirected the My
> Documents folder to a network drive.) The problem preceded that change.
>
> I have full control of the folder where my profile is stored.

Check your authentication and name resolution for
both the DCs and the Share - it could even be a WINS
problem if you have more than one subnet.

DNS for AD
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2

Restart NetLogon on any DC if you change any of the above that
affects a DC and/or use:

nltest /dsregdns /serverC-ServerNameGoesHere

Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.

--
Herb Martin


>
> Thanks for any help.
>
> WW

"Herb Martin" wrote:

>
> That sounds like an authentication (which is usually
> a name resolution) problem or a pure name resolution
> problem.
>
> IF the client cannot resolve the roaming profiles server
> or is operating from cached credentials because it cannot
> find a DC or otherwise authenticate the above symptoms
> would be expected.
>

I can run my logon script fine, which maps my drives. I can access files on
the DC, which is also serving as a file server.

>
> You can localize a single machine (or machines) using
> the local System control panel.

I have changed my profile on my local machine to a local profile and then
back to a roaming profile, but it still isn't working.

>
> Check your authentication and name resolution for
> both the DCs and the Share - it could even be a WINS
> problem if you have more than one subnet.
>
> DNS for AD
> 1) Dynamic for the zone supporting AD
> 2) All internal DNS clients NIC\IP properties must specify SOLELY
> that internal, dynamic DNS server (set.)
> 3) DCs and even DNS servers are DNS clients too -- see #2
>
> Restart NetLogon on any DC if you change any of the above that
> affects a DC and/or use:
>
> nltest /dsregdns /serverC-ServerNameGoesHere
>
> Ensure that DNS zones/domains are fully replicated to all DNS
> servers for that (internal) zone/domain.
>
> --
> Herb Martin
>

I do have some DNS problems. We had a secondary DC temporarily, and then we
removed it. We get errors in the event log about the primary DC being unable
to replicate with the removed secondary DC. I just don't know how to tell it
that the secondary DC is gone.

I'm going to look into the DNS and WINS issues. We do have two subnets, and
the DC is multi-homed.

I appreciate the help, Herb. Any further thoughts would help, too.

Thanks,
Wesley

> > That sounds like an authentication (which is usually
> > a name resolution) problem or a pure name resolution
> > problem.
> >
> > IF the client cannot resolve the roaming profiles server
> > or is operating from cached credentials because it cannot
> > find a DC or otherwise authenticate the above symptoms
> > would be expected.
>
> I can run my logon script fine, which maps my drives. I can access files
on
> the DC, which is also serving as a file server.

Are you conflating the User property "logon script" with
the GPO supplied "Logon script"?

Have you tried simple things like running GPResult to
see which are applied?


> > You can localize a single machine (or machines) using
> > the local System control panel.
>
> I have changed my profile on my local machine to a local profile and then
> back to a roaming profile, but it still isn't working.

Maybe you didn't really change it back?

That right there would account for your problem.

> I do have some DNS problems. We had a secondary DC temporarily, and then
we
> removed it. We get errors in the event log about the primary DC being
unable
> to replicate with the removed secondary DC. I just don't know how to tell
it
> that the secondary DC is gone.

Normally the DNS Primary does not initiate replication
so this would be an odd message.

Perhaps you have the Primary setup to NOTIFY the secondary?
Or you were using AD-Integrated DNS rather than Primary-
Secondary.

The latter would be an AD issue. DNS servers don't much
care if their (true) secondaries are missing.

> I'm going to look into the DNS and WINS issues. We do have two subnets,
and
> the DC is multi-homed.

There are issues with multi-homes DC-WINS servers.

You can google that.


> I appreciate the help, Herb. Any further thoughts would help, too.
>
> Thanks,
> Wesley