On Saturday 30 December 2006 14:17, Leen de Braal wrote:
> > On Saturday 30 December 2006 13:40, Kai Ponte wrote:
> >> On Saturday 30 December 2006 12:09, Leen de Braal wrote:
> >>
> >> Hmm, let us know! I'm curious.
> >>
> >> Are you connecting via a different VPN to the MS Workstation?
> >
> > It sounds like he is connecting via Cisco concentrator and then
> > trying to make a connection to a M$ VPN. Since Cisco uses IPSEC,
> > it would be difficult to also use pptp which is used by M$.
> > I have no idea why he would be trying this, he already has a VPN
> > by Cisco which is more secure then M$. :-)
>
> That's always what I thought too ;-)
> So I have a customer with cisco VPN3000 in the network, and that works
> well with vpnc.
> Now I am having to do some work at another site, and there is only a
> SBS2003 server with ISA2004, directly connected to the Internet. So cisco
> has nothing to do with this problem, I just have to connect to a VPN on an
> ISA2004 firewall. If I can connect, I can use krdc to establish an rdp
> session to maintain the network.
> Again: this has nothing to do with the cisco. Its just that i have some
> experience with vpnc, and I never saw something about M$ VPN, that it
> could do. This type of VPN is just a black hole to me. I do know, that in
> WinXP it is quite easy to make a connection, make a new VPN-connection
> with all settings default just works.
>
I just looked at my system and it has pptp which is the pptp client
which should work with M$. I have never used it as I have always
used Cisco.
From the Man Page:
Connection to a Microsoft Windows VPN Server
pppd noauth nobsdcomp nodeflate mppe-40 mppe-128 mppe-stateless name
domain\\\\username remotename PPTP require-chapms-v2 pty "pptp 10.0.0.5
--nolaunchpppd"
Note that the chap-secrets file used by pppd must include an entry for
domain\\username
Mike
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
