> So - is it the VPN client that is leaking memory? Or is it

repeated

> connections created by the app client, that are not being freed?
>

It is the app, growing by the second.

Thanks for the perspective - I know from some other work with TSocket
that windows apps hang onto memory when TCP/IP connections go wrong.
Call me an idiot, but it didn't occur to me that the gds32.dll would
end up in the same hole - failed connection, memory eaten. If that
is the case, then I have workaround strategies.

What I was hoping for was that I could somehow poll the server to see
if it was available and ready to connect. However, that polling
would require a TCP/IP socket, and there we go again.

It looks like I am off to "socket memory preservation strategy" world.

Thanks again for your help.
George Helmke