stephen
January 10th 04, 12:34 AM
Hi,
I have set up 5 fresh windows 2003 boxes and have followed
the labs exactly. However I have run into a show stopper
with teh Error 734: on my WinXP Box that is trying to act
as an internet client to the rest of the architecture.
I am trying very hard to get a test lab up and running and
really need to get over this major problem so I can sho
wit off and demo it to the business.
I have setup my architecture to reflect the published
Microsoft article :
http://www.microsoft.com/technet/treeview/default.asp?
url=/technet/prodtechnol/windowsserver2003/deploy/confeat/r
motevpn.asp
So I have a problem with the first example : the PPTP
example. It seems to be between the VPN Server and the XP
client.
Therefore at the CLIENT1 section of the PPTP Test Lab, 1/2-
> 1/3 of the way through the above referenced document I
get the following Error: 734 when I try to use the VPN
network connection that I set up.
The Steps I followed under the CLIENT1 stage in the
document are:
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 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 the 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
I have set up 5 fresh windows 2003 boxes and have followed
the labs exactly. However I have run into a show stopper
with teh Error 734: on my WinXP Box that is trying to act
as an internet client to the rest of the architecture.
I am trying very hard to get a test lab up and running and
really need to get over this major problem so I can sho
wit off and demo it to the business.
I have setup my architecture to reflect the published
Microsoft article :
http://www.microsoft.com/technet/treeview/default.asp?
url=/technet/prodtechnol/windowsserver2003/deploy/confeat/r
motevpn.asp
So I have a problem with the first example : the PPTP
example. It seems to be between the VPN Server and the XP
client.
Therefore at the CLIENT1 section of the PPTP Test Lab, 1/2-
> 1/3 of the way through the above referenced document I
get the following Error: 734 when I try to use the VPN
network connection that I set up.
The Steps I followed under the CLIENT1 stage in the
document are:
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 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 the 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