And that, I hope, is enough to start you down the path of Stunnel
mayhem. As usual, I've scratched only the surface. I leave it up to you to
explore Stunnel's ability to authenticate tunnels with client-certificate
checking, its support for TCPwrappers-style access controls and the
myriad global and service-specific options supported in stunnel.conf. Let
the stunnel(8) man page be your guide, and may your single-TCP-port-using
unencrypted-TCP applications be eavesdroppable no more.

Our network is connected to proxie server and we already set our proxie server to accept port 992 but when the client computer connects logon the the website it will be block by the proxie server so we need to change the port 23 to port 992. Pls advise if you have any detailed suggestion on how to do this. The client PC is running windows XP pro and the server is running windows server 2000