I experimented with those parameters but had no success with them in place (I still have the commented line in my profile for when I get bored).
I believe the SECURE on the port definition forces it - I know for a fact that I cannot connect to the system without SSL enabled in my client (and a forced port definition of 23 - we use the RUMBA client here and it seems to assume that SSL should travel over some other, unspecified port). On Wed, Aug 3, 2011 at 4:15 PM, Betsy Jeffery <betsy_jeff...@mgic.com>wrote: > Thanks. You didn't have to add any INTERNALCLIENTPARMS in the PROFILE > TCPIP? How did you override the SECURECONNECTION NEVER default for port 23? >
