Test Lab Fails, Error 734 with PPTP VPN

From: stephen (stephen.bebb_at_sydneywater.com.au)
Date: 09/26/03 

Date: Thu, 25 Sep 2003 18:25:50 -0700

Hi,

I have set up 5 fresh windows 2003 boxes and have followed
the labs exactly. However I have run into a show stopper
and hoping that I can get some help.

I am trying to get a test lab up and running to prove and
show the capability of WinXP and Win2003 and associated
products instead of Unix.

I am using the Microsoft article :
http://www.microsoft.com/technet/treeview/default.asp?
url=/technet/prodtechnol/windowsserver2003/deploy/confeat/r
motevpn.asp

So I have problems with the PPTP example especially around
the VPN server and XP client sides of things.

I have followed and used the architecture as the document
suggests and I believe that everything appears to be setup
fine. Therefore, I am currently stopped at the section in
the PPTP under CLIENT1 (the WinXP client).

The Steps I followed:
1.) Followed the instructions to log the XP box onto the
domain and could successfully log on to the domain with
VPNUser and ping the 172.16.0.X boxes and ping their
respective hostname.domain etc..
2.) I then shutdown the XP box.
3.) I then moved the connected the XP box to the Internet
isolated hub and started up the XP box and logged on using
the VPNUser domain account.
2.) I then tested that my ipconfig was 10.0.0.1 and I
couldn't ping any of the 172.16.0.X boxes and I couldn't.
3.) I then successfully tested pinging the VPN1 server box
on the Internet IP of 10.0.0.2 network connection.
4.) I then followed the second part of the CLIENT1 install
guide in setting up a network connection eg. changing the
Network Tab , Type of VPN to PPTP VPN etc..
5.) I then connected to this network connection with the
username of domain\VPNUser and also tried it with
domain/VPNUser (as stated in the doco which seems
different to my normal domain\username format ??).
6.) Then I get the Error 734. It seems to get further then
last time but I couldn't guarentee this. The error comes
up extremely fast.

Therefore, the error dialog that comes up with has the
following title : "Verify username and password"

Error 734: The PPP link control prototcol was terminated.

I looked at the help associated with the error from the
error dialog and it suggests to disable LCP. I did this
and I still get the same error. It also suggests to
switch the security setting for the network connection
to "Allow unsecured password". I didn't have this in my
dropdown list just the default and the smartcard option.
I'm really not sure why one would want to use this setting
anyway ???

I also have searched for Error 734 throughout the
Microsoft sites and found only errors relating to Dialup's
and not VPN's.

Anyway, I tried their documented work around by turning
off (no check box) the negotiate multi link for single
link connections. This didn't have any affect, I am still
getting rh same error as documented in my previous news
item (eg Error 734).

Please help so I can prove how great win2003 and WinXP
are .....

Cheers Steve

Relevant Pages

  • Test Lab Fails, Error 734 with PPTP VPN
    ... I have set up 5 fresh windows 2003 boxes and have followed ... However I have run into a show stopper ... the VPN server and XP client sides of things. ... on the Internet IP of 10.0.0.2 network connection. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: IAS Log Missing
    ... able to succesfully use IAS i would bet that its not even being contacted ... "Users with 802.1x authenticated switch client connections with EAP or PEAP ... The icon for the network connection must be displayed in the ... Configure the switch to initiate authentication." ...
    (microsoft.public.windows.server.general)
  • Re: ICS isnt working??
    ... >>and enable each client's network connection. ... On a client computer, right click the local area network connection ... >> ping 192.168.0.1 ... However, changing the DNS server ...
    (microsoft.public.windowsxp.network_web)
  • Re: Communicating over a network
    ... network connection for you between a client and server, ... The only reason I could advocate not using WCF would be because the ... then i presume the added overhead of ...
    (microsoft.public.dotnet.languages.csharp)
  • Dial up Network Connection
    ... When I attempt to set up a dial up network connection to ... my ISP manually, the boxes that I need to complete, ... including that requiring a password to be entered, ... There are settings in the registry with ...
    (microsoft.public.windowsxp.general)