Archived from groups: microsoft.public.win2000.active_directory (More info?)
What gives? I get this message when I try to logon to a domain with a
particular limited user account. I can logon to the domain no problem
using my admin account on that same machine.
I found in another forum that the cause could be due to not having a
Default User account folder within Documents and Settings, but this is
not the case in my situation. I *DO* have a Default User account
folder in there, and even tried copying over another user's Default
User account folder only to come about the same results.
Archived from groups: microsoft.public.win2000.active_directory (More info?)
The account in AD may have a roaming profile folder set, but if the
folder doesn't exist on the server in that UNC path, you'll get that
error.
Sample roaming profile path would be \\server\share\username and would
be located on the AD users profile tab in Profile Path:
You'd need to make sure that the folder exists and the users account
has at least change permissions on it.
Archived from groups: microsoft.public.win2000.active_directory (More info?)
Try to start regedt32 from the server and load the users USER.DAT from
the user profile.
check the permision from the regedit 32
rwh@rodharrison.com wrote:
> The account in AD may have a roaming profile folder set, but if the
> folder doesn't exist on the server in that UNC path, you'll get that
> error.
>
> Sample roaming profile path would be \\server\share\username and would
> be located on the AD users profile tab in Profile Path:
> You'd need to make sure that the folder exists and the users account
> has at least change permissions on it.
Archived from groups: microsoft.public.win2000.active_directory (More info?)
Nope, no roaming profiles set. This account is a clone of all our other limited user accounts. I actually needed to replace this user's workstation anyway, so I set the account on a new machine and surprise surprise, it connects to the domain no problem. So apparently the issue was with her particular local account on that workstation. I'm still not sure what could have caused it though. For what it's worth, the detail message given on that pop-up window was simply "access is denied".
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.