24th April 08:28
RasDial throws error 756 - line already in use
That KB article describes a situation where the user stops RRAS while a
connection is up, thus orphaning the connection. I assume you're not doing
that in your code somewhere. :-)
Perhaps you could enable RAS logging as below and make the logs available?
To enable logging, type the following in a cmd.exe window:
netsh ras set tracing * enabled
Now let your application connect, and run until the point of first failure.
Now you can turn tracing off:
netsh ras set tracing * disabled
The log files are in a directory named 'tracing' under the Windows
This posting is provided "AS IS" with no warranties, and confers no rights.