Odd issue with dial-up connections

[cypher_key]

I don't believe this problem is specially related to C#, but since my
app is written in that language I thought this would be a good place
to start.

I have a binary written in C++ (not by me) that makes a connection to
Windows servers using WNetAddConnection2() to perform various
functions. I don't have the ability to modify that code for that
binary but I must use it.

My requirement is that I establish a dial-up connection to the server
first. My C# app is responsible for doing this. Initially I ran the
rasdial Windows utility and then changed to use the InternetDial() API
call from the WinInet.DLL. Both yield the same odd problem. The
problem is that after my application establishes the connection, this C
++ binary is unable to make a connection to the remote server. It gets
the error:
"No network provider accepted the given network path"

If I first establish the connection on the command line using the
rasdial Windows utility and then run the C++ binary, it works.

The only thing that comes to mind is that the only processes that can
access the remote network connection are child processes of what made
the connection. That seems odd but it matches the behavior I am
seeing.

Any suggestions or thoughts on a better location to track this
information down would be greatly appreciated.

Also please let me know if I can provide any additional information.