> Of course I did! So what? I am using PoSH 2.0 CTP3 on Windows Server
> 2008. It applies to Windows Server 2003, PoSH 1 and both the Quest and
> regular cmdlets.
> So what he suggests is to use explicit bind. I did that by invoking
> Connect-QADService -Service 'ourdc'
> And yes, I did it by authenticating against the Active Directory as
> well by invoking
> Connect-QADService -Service 'ourdc' -Credential ( Get-Credential )
> And nope. This did not help.
> Am I missing something, Karl? You are speaking in riddles. Could you
> please say it explicitly what do you suggest?
> Once again, thank you for helping.
> "Karl Mitschke" wrote:
>> Hello Exotic,
>> Did you read the whole page?
>> APPLIES TO
>> Windows 2003 Active Directory Windows PowerShell 1.0 Both AD cmdlets
>> and native PowerShell [ADSI] support
>> Please try his suggestion and let us know if it fixes your problem.
I'm not meaning to speak in riddles - all I was doing was attempting to provide
As you can see, the error is ""An invalid dn syntax has been specified."
When I go back and review your code, I see that you vave , domain at the
end of your DN - why is that?
Remove it, and it should work - works fine for me with my DN.