Topic: PPTP error 734 in beta 6.3

[The Nerd Guy]

I am trying to establish a VPN connection from a 2K client. It is going less than ideal.

I am running a beta 6.3 server and have applied all the updates using the "rpm -Uvh filename". No errors. rebooted and all looks well. I can SSH into the server and do anything I want, to the server, even run Lynx. However,, when I try and make a VPN connection from the same win2K client, It goes all the way to "registering your computer on the network" then throws me out with an error 734.

Anything??

[brian kirk]

Google is your friend -
Q. What does it mean when I receive the message "Error 734" and then get disconnected?

This error indicates that the router and the PC cannot negotiate authentication. For example, if you set the PC authentication protocols for Shiva PAP (SPAP) and MS-CHAP version 2 (when the router can't do version 2), and you set the router for CHAP, then the debug ppp negotiation command on the router will show the following output.

04:30:55: Vi1 LCP: Failed to negotiate with peer
Another example is if the router is set for vpdn group 1 ppp encrypt mppe 40 required and the PC is set for "no encryption allowed." The PC would not connect and would produce an "Error 734," and the debug ppp negotiation command on the router would show the following.

04:51:55: Vi1 LCP: I PROTREJ
      [Open] id 3 len 16 protocol CCP (0x80FD0157000A120601000020)

Look in the log files to see what is happening.
Good luck
Brian

[Steve Bush]

I know the answer is likely YES, but....
In the server-manager, did you set
Security>Remote Access>Number of PPTP Clients to at least 1?
In server-manager, did you set
Users>VPN Client Access>Yes for the user who is trying to connect?

Not that it will fix this particular problem, but did you run
/sbin/e-smith/signal-event post-upgrade
after applying the updates?

I have tested a WinXP client attaching to a 6.0b3+patches server and it worked for me.