Link to home
Start Free TrialLog in
Avatar of exx1976
exx1976Flag for United States of America

asked on

Bind to a specific server using LDAP (VB.NET 2003)

I am currently using LDAP to bind to active directory, however, the command process I am calling (TSCMD) to modify AD users requires a servername to bind to, instead of just a domain name.  Every once in a while, my program will bind to DC2 instead of DC1, and then when I go to set the properties of the user on DC1 with TSCMD, the account has not yet replicated to DC1 because it was created on DC2.  Is there a way to bind to a specific server in AD using LDAP so that I can always guarantee that the accounts will be created on the same server as TSCMD references?

Thanks,
exx
Avatar of Mikal613
Mikal613
Flag of United States of America image

are you running windows 2000?
Avatar of exx1976

ASKER

Yes, Windows 2000.  Sorry..   In 2003 the TS properties are uncovered and available via APIs, in 2000 they are stored as BLOBs and the only way I know how to get at them is with this third party command line tool...

Avatar of exx1976

ASKER

Huh??  That doesn't seem related at all...   "The Microsoft LDAP API (wldap32.dll) cannot access LDAP servers that are multi-homed and have more than 51 IP addresses registered. This problem prevents the Active Directory Administration tools from accessing multi-homed Windows 2000 Domain Controllers with more than 51 IP addresses"


??
ASKER CERTIFIED SOLUTION
Avatar of exx1976
exx1976
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Sorry i could nt help

I should give you points
Avatar of exx1976

ASKER

LOL  don't worry about it.

lets close this baby