[ale] pptp and ppp continued

Bao Ha baoh at linuxwizardry.com
Fri Jan 19 10:24:30 EST 2001



Put 
that in front of your username, i.e. domain\\username.
<SPAN 
class=215511915-19012001> 
Why do 
you need PoPToP to get into a Microsoft VPN server?  PoPToP is a VPN 
server,
not a 
client.
<SPAN 
class=215511915-19012001> 
<SPAN 
class=215511915-19012001>Bao

  <FONT face=Tahoma 
  size=2>-----Original Message-----From: owner-ale at ale.org 
  [mailto:owner-ale at ale.org]On Behalf Of Chris FowlerSent: 
  Thursday, January 18, 2001 8:58 PMTo: 'Joe Steele '; ''Wandered 
  Inn' 'Cc: ''ALE' 'Subject: RE: [ale] pptp and ppp 
  continued
   Did you guys figure out how to specify the DOMAIN 
  option?  I need to use poptop to gain access to a Microsoft VPN 
  server.
  Thanks, Chris 
  -----Original Message----- From: Joe 
  Steele To: 'Wandered Inn' Cc: 
  'ALE' Sent: 1/18/01 1:44 PM <FONT 
  size=2>Subject: RE: [ale] pptp and ppp continued 
  I guess I wasn't making much sense, was I?  I admit to 
  being less familiar with the mechanics of pptp than 
  ppp.  But it appears that the pptp process is 
  working properly, based on your tcpdump.  The ppp 
  process is not.  And the sticking point is not in 
  authentication with chap or encryption with mppe, <FONT 
  size=2>because these issues are not tackled until after ppp negotiates 
  lcp.  
  Generally speaking, when the remote end of a ppp connection 
  does not send any lcp packets (which is the first 
  thing to be sent when ppp is initiated), it often 
  means that it is waiting on some event (such as the 
  receipt of a login name and password, or a string such 
  as ppp or 'CLIENT') before it starts sending ppp 
  packets.  It doesn't seem like this sort of thing should be 
  necessary, but something is holding up the start of 
  ppp on the remote end. 
  You *should* be able to feed the word 'CLIENT' to the server 
  this way: 
  1)  create a chat script file called 'client.chat' with 
  the following: 
  #wait 1 sec., then send it <FONT 
  size=2>''   \dCLIENT #send it again for safe 
  measure ''   \dCLIENT 
  2) run pptp(command wrapped on 2 lines): 
  pptp VPN_SERVER name gamyers remotename VP_SERVER connect 
  '/usr/sbin/chat -v -f client.chat' 
  The -v should log the chat conversation, which may help with 
  debugging.  Although sending 'CLIENT' may or may 
  not help, it shouldn't hurt anything, and it shouldn't 
  result in script failure errors. 
  One more (possibly important) thing -- Your log contained 
  the following: 
    Jan 15 15:37:18 a modprobe: modprobe: Can't locate 
  module char-major-108 
  The README.linux file that comes with ppp makes reference to 
  char-major-108, but it looks like it only applies to 
  kernel versions >=2.3.13;  lessor kernels 
  should not generate the error.  If this error is 
  still occurring, it may be the root of your 
  problem. 
  --Joe 
  -----Original Message----- <FONT 
  size=2>From:   Wandered Inn [SMTP:esoteric at denali.atlnet.com] 
  Sent:   Wednesday, January 17, 2001 8:36 PM 
  To:     'ALE' <FONT 
  size=2>Subject:        Re: [ale] pptp and 
  ppp continued 
  Joe Steele wrote: > 
  > You say you can't get pptp to call a 
  script.  But aren't you already > using a chat 
  script to control your modem, telling it to dial a number <FONT 
  size=2>> and so forth?  That's where they are saying the 'CLIENT' 
  string should > be put, as part of an expect/send 
  pair. 
  Yeah, but the way it works is you have two ppp 
  processes.  You first connect to the internet via 
  ppp0, you then fire up pptp which uses ppp to create a 
  second ppp process using ppp1.  So, when I dial up the <FONT 
  size=2>first, sending a client string at that time will do no good.  The 
  syntax for pptp is: 
  pptp VPN_SERVER name gamyers remotename VP_SERVER 
  Note, there's no need for a chat script.  I tried to 
  stick one in there, but all iterations fail and pptp 
  exits pre-maturely. 
  -- To unsubscribe: mail 
  majordomo at ale.org with "unsubscribe ale" in message <FONT 
  size=2>body. 




More information about the Ale mailing list