Offline file resynchronization

[Steve Steinbeck]

Help.

I have an executive that likes to take her work home with
her and sync up when she gets back in.

She was using her laptop that syncs to one W2k AD, she
logs into her local laptop and then attachs and validates
to the shares on the shared drives. We have recently
created a second W2K AD forest. There are two people who
access these files. Both are getting strange errors after
sync, i.e. file is being used by a user who was
terminated some time ago, or its in use by the person
trying to access the file, or its not even there.

This is something I didn't set up and am unsure where to
look. I have a two-way trust setup between the two AD
forests. I didn't have time to check the security, I
suspect that my problem may be there. While we had it
running in an NT domain and her W2k AD structure
everything was fine. I wanted to use domain local groups
for security so I went to native mode, her domain is
mixed. I plan on killing her AD domain and incorporating
her server as a member server soon.

I have no idea where to look. Point me in a direction
plesae.

 

[SaltPeter]

Have you tried modifying "Opportunistic Locking" on that server?
Configuring Opportunistic Locking in Windows
http://support.microsoft.com/default.aspx?scid=kb;EN-US;296264

 

[Steve Steinbeck]

I have adjusted the opportunistic locking on the server,
one key was missing and the other was not in the default
state. Also their were references to other keys fro fine
tuning, as this made no reference to where they should be
located I assumed they were optional and I ignored them.

I have them testing not and will post whether I was
successful or not in a day or two.

Thanks,

Steve

 

[SaltPeter]

I have adjusted the opportunistic locking on the server,
one key was missing and the other was not in the default
state. Also their were references to other keys fro fine
tuning, as this made no reference to where they should be
located I assumed they were optional and I ignored them.

I have them testing not and will post whether I was
successful or not in a day or two.

Thanks for feedback. There is also a problem related with documents and
auto-diconnecting clients you may be interested in:

How Autodisconnect Works in Windows NT and Windows 2000
http://support.microsoft.com/?kbid=138365

and for more info on Opportunistic Locking:
http://www.dataaccess.com/whitepapers/opportunlockingreadcaching.html

 

[Steve Steinbeck]

The opportunistic locking suggestion did not solve the
problem. Apparently she tends to work on a share in the
second AD domain from the primary AD domain that she logs
into. She has created a share on the 2nd domain, when
she works on a file and then quits the file the temp
files created by Word or Excel are not automatically
deleted. This is apparently the root cause of her
complaints. If she goes to the share and deletes the
files herself then the data file opens as it should.

Help.

 

[Steve Steinbeck]

Looks like you've answered the second part of my headache
that I need to look at. It appears that hte files are
NOT automatically disconnecting and I will look at this
file fro answers. If you have any more ideas based on my
previous posting please feel free to let me know.

Thanks again fro helping.

How Autodisconnect Works in Windows NT and Windows 2000
http://support.microsoft.com/?kbid=138365