I am trying to store a users log in and password after they enter it at encryption so that when they go to log on to our terminal server they do not have to enter a user name and password. It would be entered in via LDAP.
I'm having a lot of trouble parsing your question. Explaining a bit more about what you're trying to accomplish would be helpful.
I assume when you say "terminal server" you're talking about a Windows Server offering Remote Desktop services. If that's the case, why not use the built-in single-sign-on functionality in Windows-- that is, joining the server computer to an Active Directory (AD) domain.
I can tell you that a stock AD deployment doesn't store any plaintext passwords. You can't query stored password hashes from AD via LDAP, either. Storing plaintext passwords in AD (known as "reversible encryption" by Microsoft) is a bad idea from a security perspective.
In general, you really shouldn't be writing software that's storing users credentials, either. If you need single-sign-on functionality you should be looking at using something like Kerberos or a federated authentication mechanism like SAML.