1. Diese Seite verwendet Cookies. Wenn du dich weiterhin auf dieser Seite aufhältst, akzeptierst du unseren Einsatz von Cookies. Weitere Informationen

Talk Freetz | PPTPD Konfiguration | Fehler 734: PPP-Verbindungssteuerungsprotokoll ...

Dieses Thema im Forum "Fritzbox Talk" wurde erstellt von Fredde008, 7. Februar 2013.

  1. Fredde008
    Offline

    Fredde008 Newbie

    Registriert:
    4. Januar 2013
    Beiträge:
    3
    Zustimmungen:
    0
    Punkte für Erfolge:
    0
    Hallo,

    habe einen PPTPD auf einer Fritte laufen.

    Ich habe versucht die Konfiguration auf mein Netz anzupassen, allerdings ist mir dies nicht gelungen. Resultat : Beim Versuch die Verbindung aufzubauen in mein Netz, kommt der Fehler 734: PPP-Verbindungssteuerungsprotokoll wurde beendet. ( Bei : Der Computer wird im Netzwerk registriert ).

    Habe schon sämtliche Einstellungen am Client geändert, hat jedoch nichts gebracht.

    Meine Netzwerkdaten :

    Router : 192.168.100.2
    DNS : 192.168.100.2

    Freetz Fritte : 192.168.100.1

    VPN-IP-Kreis : 192.168.100.221-229

    pptp.conf :

    # TAG: ppp
    # Path to the pppd program, default '/usr/sbin/pppd' on Linux
    #
    ppp /usr/sbin/pppd

    # TAG: option
    # Specifies the location of the PPP options file.
    # By default PPP looks in '/etc/ppp/options'
    #
    option /etc/ppp/options.pptpd

    # TAG: debug
    # Turns on (more) debugging to syslog
    #
    #debug

    # TAG: stimeout
    # Specifies timeout (in seconds) on starting ctrl connection
    #
    #stimeout 10

    # TAG: noipparam
    # Suppress the passing of the client's IP address to PPP, which is
    # done by default otherwise.
    #
    #noipparam

    # TAG: logwtmp
    # Use wtmp(5) to record client connections and disconnections.
    #
    #logwtmp

    # TAG: bcrelay <if>
    # Turns on broadcast relay to clients from interface <if>
    #
    #bcrelay lan

    # TAG: localip
    # TAG: remoteip
    # Specifies the local and remote IP address ranges.
    #
    # Any addresses work as long as the local machine takes care of the
    # routing. But if you want to use MS-Windows networking, you should
    # use IP addresses out of the LAN address space and use the proxyarp
    # option in the pppd options file, or run bcrelay.
    #
    # You can specify single IP addresses separated by commas or you can
    # specify ranges, or both. For example:
    #
    # 192.168.0.234,192.168.0.245-249,192.168.0.254
    #
    # IMPORTANT RESTRICTIONS:
    #
    # 1. No spaces are permitted between commas or within addresses.
    #
    # 2. If you give more IP addresses than MAX_CONNECTIONS, it will
    # start at the beginning of the list and go until it gets
    # MAX_CONNECTIONS IPs. Others will be ignored.
    #
    # 3. No shortcuts in ranges! ie. 234-8 does not mean 234 to 238,
    # you must type 234-238 if you mean this.
    #
    # 4. If you give a single localIP, that's ok - all local IPs will
    # be set to the given one. You MUST still give at least one remote
    # IP for each simultaneous client.
    #
    # (Recommended)
    localip 192.168.100.2
    remoteip 192.168.100.221-229
    # or
    #localip 192.168.0.234-238,192.168.0.245
    #remoteip 192.168.1.234-238,192.1

    options.pptp :

    # Name of the local system for authentication purposes
    # (must match the second field in /etc/ppp/chap-secrets entries)
    name fritzbox

    # Strip the domain prefix from the username before authentication.
    # (applies if you use pppd with chapms-strip-domain patch)
    #chapms-strip-domain

    # Authentication
    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

    # Encryption
    # Require MPPE 128-bit encryption
    # (note that MPPE requires the use of MSCHAP-V2 during authentication)
    mppe required
    #mppe stateless

    # 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.
    ms-dns 192.168.100.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
    #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

    # 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

    # Disable Deflate compression
    #nodeflate

    # Disable Van Jacobson compression
    # (needed on some networks with Windows 9x/ME/XP clients, see posting to
    # poptop-server on 14th April 2005 by Pawel Pokrywka and followups,
    #

    Dieser Link ist nur für Mitglieder!!! Jetzt kostenlos Registrieren ?

    )
    novj
    novjccomp

    # turn off logging to stderr, since this may be redirected to pptpd
    #nologfd
     
    #1
  2. phantom

    Nervigen User Advertisement

  3. Fredde008
    Offline

    Fredde008 Newbie

    Registriert:
    4. Januar 2013
    Beiträge:
    3
    Zustimmungen:
    0
    Punkte für Erfolge:
    0
    Weiß keiner was ich falsch gemacht habe ? :(

    So... nachdem ich den Punkt mppe required auskommentiert habe, baut sich das VPN von einem Windows XP Client auf.

    Allerdings ist dann weder der Client pingbar noch ist ein Ping vom Client zu einem beliebigen Rechner im VPN-Netz möglich.

    Restart vom PPTPD

    modprobe: can't load module arc4 (kernel/crypto/arc4.ko): unknown symbol in module, or unknown parameter
    modprobe: can't load module sha1 (kernel/crypto/sha1.ko): unknown symbol in module, or unknown parameter
    modprobe: can't load module ppp_mppe_mppc (kernel/drivers/net/ppp_mppe_mppc.ko): unknown symbol in module, or unknown parameter
    Stopping pptpd ... failed.
    Starting pptpd ... done.
     
    Zuletzt von einem Moderator bearbeitet: 8. Februar 2013
    #2
  4. rolu2
    Offline

    rolu2 Moderator Digital Eliteboard Team

    Registriert:
    16. November 2009
    Beiträge:
    6.320
    Zustimmungen:
    3.908
    Punkte für Erfolge:
    113
    AW: Freetz | PPTPD Konfiguration | Fehler 734: PPP-Verbindungssteuerungsprotokoll ...

    Du solltes vllt mal im ip-phone-forum vorbeischauen. Dort gibt es reichlich Info
     
    #3
    Fredde008 und Pilot gefällt das.

Diese Seite empfehlen