Roaming Profiles do not load over slow link

[newzboy81]

Posting in this forum is my last step before calling Microsoft about this problem. OK, here goes...

I have a remote location in my domain. This location has a 128/384kb frame relay circuit going to it. There is no DC at this location (the DC is at the main location). There are about 5 PCs at this location. My problem is that when users log on and off the domain from different PCs at this location their roaming profile is not saved. At first I thought this had something to do with the fact that they have FAT32 file systems on their PCs because we upgraded their PCs from 98 to XP instead of doing a clean install. However, this idea was blown out of the water when I brought my laptop with NTFS on it (Windows XP also) to the location and plugged it into the network and had the same problem. I have looked through my group policy and disabled the "detect slow link connection" option for computers. Basically, it seems like the profile for the user is being stored locally on each PC even though I have roaming profiles enabled. By the way, my roaming profiles work just fine at my main site with the DC. Please help!

Is there something that I am missing? Is there any way I can track what is happening at logon? Would a slow link logon event be in event viewer on the local PC?

 

[arlems]

Sure enough, this is the way roaming profiles work. They save themselves locally, and update the server if they were modified by the users. You can disable the roaming profile to save locally by changing a policy setting on your active directory on the server, but I won't do this because it will slow down the users login procedure by 5 X.

 

[LoJACK]

At your remote location, are the computers' DNS setting correct? They have to point to a DNS server that is able to resolve the name of your DC.

What is the IP address of your DNS server?
What are the DNS setting at your remote location?

LoJACK

 

[newzboy81]

Arlen:
I understand that the roaming profile saves itself to the local PC and then updates on the server. However, on these PCs the server copy of the profile is not being updated it seems. By the way, I changed the group policy setting, which tells the profiles to not be saved on the local machine and it made no difference.

LoJACK:
The IP Address of My DNS server is 192.168.3.20. My DC is my Primary DNS server. On each of the remote clients I have the Primary DNS set to 192.168.3.20. I have left the Secondary DNS blank since I have no secondary DNS server. Here is some other info that may be useful

IP Address Scheme of Remote Clients: 192.168.6.x
Default Gateway setting of Remote Clients: 192.168.6.1