Roaming Profiles

[Guest]

Random users on ourWin2K network periodically recieve an
error stating that they cannot be logged on because
Windows cannot find their roaming profile. They are then
logged on with a local profile. Can anyone tell me what
might be causing this?
Also, does the EVERYONE group need read permission on the
users' network share. As it is now, in the user's network
share properties, under SECURITY everyone has full control
and in the properties for SHARING the user and
Administrator have full control. Does EVERYONE need read
permission here? Would this affect the availibility of the
roaming profile?

Thanks

 

[Brian Oakes [MSFT]]

Check on the user account properties to see if they have a profile path set.
If they do, then when they login they are unable to contact that server in x
time. That could be a name resolution issue or something like that.

That is the difference between File and Share Level Access. By default in
most cases, the file level is open to everyone full control, the sharing is
what is locked down. The logic is once you connect to the share you need be
able to see the files.

So you can get pretty granular if needed. I am not the best guy on
permissions so hopefully this will get you going.

For the permissions questions, check out the active directory news groups.

--

Brian Oakes

This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit.