On Wed, May 20, 2009 at 1:41 AM, dani ville <[email protected]> wrote: > /etc/ppp/pptpd-options > ############################################################################### > # $Id: pptpd-options 4643 2006-11-06 18:42:43Z rene $ > # > # Sample Poptop PPP options file /etc/ppp/pptpd-options > # Options used by PPP when a connection arrives from a client. > # This file is pointed to by /etc/pptpd.conf option keyword. > # Changes are effective on the next connection. See "man pppd". > # > # You are expected to change this file to suit your system. As > # packaged, it requires PPP 2.4.2 and the kernel MPPE module. > ############################################################################### > > > # Authentication > > # Name of the local system for authentication purposes > # (must match the second field in /etc/ppp/chap-secrets entries) > name seal > > # Optional: domain name to use for authentication > # domain mydomain.net > > # Strip the domain prefix from the username before authentication. > # (applies if you use pppd with chapms-strip-domain patch) > #chapms-strip-domain > > > # Encryption > # Debian: on systems with a kernel built with the package > # kernel-patch-mppe >= 2.4.2 and using ppp >= 2.4.2, ... > # {{{ > refuse-pap > refuse-chap > refuse-mschap > # Require the peer to authenticate itself using MS-CHAPv2 [Microsoft > # Challenge Handshake Authentication Protocol, Version 2] authentication. > require-mschap-v2 > # Require MPPE 128-bit encryption > # (note that MPPE requires the use of MSCHAP-V2 during authentication) > require-mppe-128 > # }}} > > > > > # Network and Routing > > # If pppd is acting as a server for Microsoft Windows clients, this > # option allows pppd to supply one or two DNS (Domain Name Server) > # addresses to the clients. The first instance of this option > # specifies the primary DNS address; the second instance (if given) > # specifies the secondary DNS address. > # Attention! This information may not be taken into account by a Windows > # client. See KB311218 in Microsoft's knowledge base for more information. > #ms-dns 192.168.1.1 > #ms-dns 10.0.0.2 > > # If pppd is acting as a server for Microsoft Windows or "Samba" > # clients, this option allows pppd to supply one or two WINS (Windows > # Internet Name Services) server addresses to the clients. The first > # instance of this option specifies the primary WINS address; the > # second instance (if given) specifies the secondary WINS address. > #ms-wins 192.168.1.1 > #ms-wins 10.0.0.4 > > # Add an entry to this system's ARP [Address Resolution Protocol] > # table with the IP address of the peer and the Ethernet address of this > # system. This will have the effect of making the peer appear to other > # systems to be on the local ethernet. > # (you do not need this if your PPTP server is responsible for routing > # packets to the clients -- James Cameron) > proxyarp > > # Debian: do not replace the default route > defaultroute > > > # Logging > > # Enable connection debugging facilities. > # (see your syslog configuration for where pppd sends to) > debug > > # Print out all the option values which have been set. > # (often requested by mailing list to verify options) > dump > > > # Miscellaneous > > # Create a UUCP-style lock file for the pseudo-tty to ensure exclusive > # access. > lock > > # Disable BSD-Compress compression > nobsdcomp > > El 19 de mayo de 2009 13:50, Marc Aymerich <[email protected]> escribió: >> >> On Tue, May 19, 2009 at 6:06 PM, dani ville <[email protected]> wrote: >> > hola lista, el motivo de este correo es que ya después de mucho buscar y >> > buscar no pude encontrar la solucion a mi problema. >> > tengo un servidor corriendo debian lenny, el cual tiene varios >> > servicios, >> > incluido samba, como toda la red interna esta bajo windows, los clientes >> > hacen conexion vía VPN a servidor y así acceden a los archivos >> > compartidos >> > por samba. >> > al momento de instalar y configurar pptpd todo funciono de maravilla, la >> > conexioa fue rapiday sin problemas y los archivos se compartian sin >> > ningun >> > problema, la cuaestion es que de un momento a otro se pueso inestable y >> > aveces conecta y otras no (creo que ahora simplemente no conecta :( ), >> > el >> > error que me da por la parte cliente (es decir desde windows), es un >> > error >> > 619 al intentar la conexion (el usuario y password si lo verifica y >> > después >> > el error). >> > >> > >> > bueno he buscado mucho en internet y no encuentro nada, espero alguien >> > tenga >> > la solución y pueda ayudarme a confogurar correctamente todo. dejo >> > además >> > los log (al momento de intentar coexion) y archivos de configuracion >> > para >> > que les echen una mirada. >> > >> > >> >> cat /etc/ppp/pptpd-options >> >> >> -- >> To UNSUBSCRIBE, email to [email protected] >> with a subject of "unsubscribe". Trouble? Contact >> [email protected] >> > >
Yo lo veo todo bién. ¿No tendrás un firewall por enmedio? Asegurate que el cliente y el servidor tienen libre el puerto 1723 y que tienen permitido el "protocolo 43" ya que hay muchos firewalls que filtran este tipo de protocolo. http://www.clarkconnect.com/docs/PPTP_Passthrough_Mode -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
