.NET 2.0 - code to create VPN connection?

[Rob R. Ainscough]

Can anyone point me in the right direction for using .NET 2.0 to code a
solution that will create a VPN connection on a client PC?

Thanks Rob.

 

[Carl Daniel [VC++ MVP]]

Can anyone point me in the right direction for using .NET 2.0 to code
a solution that will create a VPN connection on a client PC?

VPN connections are normally established one of three ways:

1. Automatically at startup (or by external hardware)
2. By a vendor-specific utility
3. Through RAS - Remote Access Services

For case 1, there's nothing to do. For case 2, you're probably out of luck.
For case 3, in native (unmanaged) code you'd use RasDial, which isn't
supported directly by the .NET framework yet. Do a bit of Googling - it
looks like there are a number of .NET wrappers for RasDial. I haven't used
any of them so I can't make any recommendations.

-cd

 

[William Stacey [MVP]]

Do you need a VPN or just a secure connection to server?

--
William Stacey [MVP]

| Can anyone point me in the right direction for using .NET 2.0 to code a
| solution that will create a VPN connection on a client PC?
|
| Thanks Rob.
|
|

 

[Rob R. Ainscough]

Doesn't have to be a VPN (but for some of my large clients a VPN is
required) -- a secure connection would work, but this is to avoid the Port
1433 issues on SQL server so VPNs are created for split tunnel router
setup -- web services (soap) are NOT an option in this case, just toooo slow
and too worky and too many other security issues with them.

Regardless, I would still like to create a VPN via code. RASDIAL doesn't
let me modify some of the configuration settings of my PPTP - such as
Gateway.

I wonder if CMAKE would be a solution?

 

[Guest]

Doesn't have to be a VPN (but for some of my large clients a VPN is
required) -- a secure connection would work, but this is to avoid the
Port 1433 issues on SQL server so VPNs are created for split tunnel
router setup -- web services (soap) are NOT an option in this case,
just toooo slow and too worky and too many other security issues with
them.

Take a look at remoting. .NET 2.0 supports a couple of secure channels (TCP
and HTTP).

If you find the built in implementation of remoting to be limiting, take a
look at Geniune Channels Remoting Components.