There are a few conceptual problems with what you're trying to do. Usually people sign and decrypt with a secret key, and verify and encrypt with a public key. Although mathematically possible to do the reverse, think about the roles of the two keys:
- secret key - meant to be secret, owned by a single entity
- public key - as the name suggests, *not* secret, known to anyone
Hence if you encrypt with a private key, there's really no protection, since everybody can know the public key. Of course you *may* try and keep the public key private too, but that is just asking for trouble.
So in short, use only the public RSA for encryption. Usually encrypted protocols have a handshake where each side uses their RSA keys to agree upon a single symmetric key (i.e. key exchange protocol) and use that key afterwards. There are various exchange protocols that have different requirements and support a different set of guarantees (DH, STS, etc).
Take a bit of time to read up on encryption in general: symmetric ones (AES specifically), asymmetric ones (RSA specifically) and a few extras like ElGamal. If you're not in too much of a hurry, I would suggest going through this
Stanford online crypto course. It started today if I'm not mistaking and is a brilliant one!
Cheers,
Peter