'No access' on first offline file sync...

[Jake]

Hei,

One of our domain users experience the following with regard of his
offline files 'feature':

When this user is offline he logs in as normal to the domain (but
without being connected) and as an example writes two new documents. He
shuts off his computer and returns to the office.

Having connected and logged on to the office domain network, the offline
sync process window pops up to syncronize all 'offline' files between
the computer and the server.

At the end of this process it displays an error page displaying the
filenames of these two new files stating that they could not be synced
due to 'No acces' or 'Access denied' (I'm not sure of the exact message).

The funny thing is that if the user immediately logs off and then on
again, everything is synced perferctly and these new files are correctly
copied to the server with no error message.

However it's cumbersome to login twice, and I hope that someone here has
a cure for this situation. Why should the second login be more
successful that the first one? No other user in our domain experience
this behaviour.

Thanks for any hint or comment.

jake

 

[Terry R.]

The date and time was Friday, March 13, 2009 5:14:04 AM, and on a whim,
Jake pounded out on the keyboard:

Hei,

One of our domain users experience the following with regard of his
offline files 'feature':

When this user is offline he logs in as normal to the domain (but
without being connected) and as an example writes two new documents. He
shuts off his computer and returns to the office.

Having connected and logged on to the office domain network, the offline
sync process window pops up to syncronize all 'offline' files between
the computer and the server.

At the end of this process it displays an error page displaying the
filenames of these two new files stating that they could not be synced
due to 'No acces' or 'Access denied' (I'm not sure of the exact message).

The funny thing is that if the user immediately logs off and then on
again, everything is synced perferctly and these new files are correctly
copied to the server with no error message.

However it's cumbersome to login twice, and I hope that someone here has
a cure for this situation. Why should the second login be more
successful that the first one? No other user in our domain experience
this behaviour.

Thanks for any hint or comment.

jake

Hi Jake,

Network issues can cause failures like that. Since the network is
completely connected by the second login, it completes.

Read this for a Group Policy setting (or local setting if not disabled
in GP for the domain):
http://www.itnewsgroups.net/group/microsoft.public.windows.server.general/topic16733.aspx


Terry R.

 

[Jake]

Terry R. skrev:

Hi Jake,

Network issues can cause failures like that. Since the network is
completely connected by the second login, it completes.

Read this for a Group Policy setting (or local setting if not disabled
in GP for the domain):
http://www.itnewsgroups.net/group/microsoft.public.windows.server.general/topic16733.aspx



Terry R.

We have already the "Always wait for network at computer startup and
logon" enabled in the default domain group policy.

As I said this only affects *one* user (all the other 49 users have no
problems with this).

Any other clues on the 'no access' message when syncronizing?

jake

 

[Terry R.]

The date and time was Monday, March 16, 2009 4:08:53 AM, and on a whim,
Jake pounded out on the keyboard:

Terry R. skrev:

We have already the "Always wait for network at computer startup and
logon" enabled in the default domain group policy.

As I said this only affects *one* user (all the other 49 users have no
problems with this).

Any other clues on the 'no access' message when syncronizing?

jake

Jake,

If you can get the exact error message, it might help.


Terry R.