On Tue, 1 Dec 2009 10:20:06 -0500, "JohnB" <> wrote:
>It turns out that the problem is specific to my workstation. I installed
>admin pak on another computer today, and I didn't have this problem.
>Windows firewall on my computer is disabled, and on the DCs.
>
>I guess the next step would be to remove my workstation from the domain, and
>rejoin it. Am I going to get a new profile on my workstation when I do
>that? I would hate to have to set this up all over again. I guess I could
>just copy the profile?
Make sure your workstation is not having password issues when opening the trust
to the domain. I have seen this a few times and using the Computer
Properties/Computer Name/Network ID button to reset the password (use existing
computer account) will fix that. It just takes seconds so it is worth trying. If
this a problem then you will also have event logs about the issue.
>
>
>
>
>
>"Ace Fekay [MCT]" <> wrote in message
>news:%...
>> "Dusko Savatovic" <> wrote in message
>> news:%...
>>>I would also create a brand new OU (TempTestOU) and see if Edit option is
>>>grayed there as well.
>>> BTW permissions on objedcts in AD are much more complex than NTFS
>>> permissions.
>>>
>>
>> I surely hope permissions weren't altered in AD (ADSI Edite, ADUC, etc).
>> :-)
>>
>> Ace
>>
>>
>>
>
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.
|