Re: enumerating computers

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance


"Tcs" <TSmithATEastPointCityDOTorg@> wrote in message
news:6emvl1pmajo6g140bk1o555jb92p3eu9eu@xxxxxxxxxx
> Sorry.
>
> I tried it this way 1st (using my domain name of course):
>
> FROM 'LDAP://fabrikam.org/DC=fabrikam,DC=org'
>
> and it immediately came back with the same error.
>
> I tried this way 2nd:
>
> FROM 'LDAP://DC=fabrikam,DC=org'
>
> and it took several seconds (approx 15), but it eventually came back
with...the
> same error.
>
> Is there some way I can test AD to see if it's running and/or set up
correctly?


My domain is named "optimumx.net", and the original script
(http://www.microsoft.com/technet/scriptcenter/guide/sas_srv_lxfr.mspx) runs
fine after I change "fabrikam" to "optimumx" and "com" to "net".


Here's some suggestions:

- Change the domain to a wrong name and see if the error changes.

- Make sure your computer is a member of the new AD domain.

- Make sure you are logged on with an account from the new AD domain.

- As a test, create a small sample script with just these 2 lines:
Set objRootDSE = GetObject("LDAP://RootDSE";)
Wscript.Echo objRootDSE.Get("defaultNamingContext")
Then, use the output in your LDAP query string.

- As a test, try adding these lines before the line "Set objRecordSet =
objCommand.Execute":
objCommand.Properties("User ID") = "MYDOMAIN\myaccount"
objCommand.Properties("Password") = "mypassword"
objCommand.Properties("Encrypt Password") = True

- Make sure port 389 is not being blocked by a client firewall or network
firewall.

- Make sure your domain admins didn't change the TCP port from the default of
389




.