Provide wrong filter with search query, AD returning wrong err cod

[Guest]

I am using Active Directory on Windows Server 2003. I am connected to the AD
from a remote Windows 2000 machine using the ldp utility.

While running a search query, If I provide a wrong filter then AD returns an
"LDAP_SERVER_DOWN" error. My server is up and if I provide a valid filter, it
returns me the correct results.

Is this a known bug with Active Directory? If so, is there any service pack
available to resolve this issue?

I am connecting to AD using a remote machine and I am connected to the
network through VPN. Can this be an issue?

Any help will be greatly appreciated.

Thanks.
Somank

 

[Guest]

I want to update you all with one more observation. Following is the list of
the filters and the behavior of AD with those filters.

1.) (objectclass=user)(uid=%uid%) -- Ldap Server Down
2.) &(objectclass=user)(uid=%uid) -- Filter Error
3.) &((objectclass=user)(uid=%uid)) -- No Error (returning
0 values)

In case 1 and 2 both the filter is wrong but in first case it is giving the
error as Ldap Server Down and in second it is giving the error as Wrong
Filter. Why in first case it is not giving the error as wrong filter.