Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Unable to PPTP from XP Client to WG X700

Status
Not open for further replies.

AndyPunt

Technical User
Jul 10, 2007
13
US
I am trying to set up remote access for a user from his XP VPN Client at home to the office X700 (Version 7.2B1501). I have set up the X700 as the documentation suggests; however, it still does not work. RDP from the outside to an internal server works (NAT) and the user is able to VPN to our other site without any problems.

On the client side, Windows returns a 619 error; sometimes immediately, sometimes after trying to "Verify username and password". On the X700, this is what we are getting:
10/01/08 10:24 tunneld[125]: connected to 192.168.1.2:2354
10/01/08 10:24 tunneld[125]: 156 bytes received from socket 10
10/01/08 10:24 tunneld[125]: recv start-control-connection-request from 192.168.1.2
10/01/08 10:24 tunneld[125]: sent start-control-connection-reply
10/01/08 10:24 tunneld[125]: 168 bytes received from socket 10
10/01/08 10:24 tunneld[125]: recv outgoing-call-request from 192.168.1.2
10/01/08 10:24 tunneld[125]: gre rule added for 192.168.1.2
10/01/08 10:24 tunneld[125]: spawned PPTPD with process id #5514
10/01/08 10:24 tunneld[125]: sent outgoing-call-reply
10/01/08 10:24 tunneld[5514]: starting PPTPD server
10/01/08 10:24 tunneld[5514]: pptpd
10/01/08 10:24 tunneld[5514]: silent
10/01/08 10:24 tunneld[5514]: 192.168.1.1:192.168.1.190
10/01/08 10:24 tunneld[5514]: -vj
10/01/08 10:24 tunneld[5514]: remotename
10/01/08 10:24 tunneld[5514]: 192.168.1.2
10/01/08 10:24 tunneld[5514]: gre
10/01/08 10:24 tunneld[5514]: 0:37093
10/01/08 10:24 tunneld[5514]: channel
10/01/08 10:24 tunneld[5514]: 0
10/01/08 10:24 tunneld[5514]: +chap
10/01/08 10:24 tunneld[5514]: dns-addr
10/01/08 10:24 tunneld[5514]: 192.168.1.2
10/01/08 10:24 tunneld[5514]: dns-addr
10/01/08 10:24 tunneld[5514]: 4.2.2.2
10/01/08 10:24 tunneld[5514]: nbns-addr
10/01/08 10:24 tunneld[5514]: 192.168.1.2
10/01/08 10:24 tunneld[5514]: debug
10/01/08 10:24 tunneld[5514]: required_group
10/01/08 10:24 tunneld[5514]: pptp_users
10/01/08 10:24 tunneld[5514]: ccp-max-reset
10/01/08 10:24 tunneld[5514]: 257
10/01/08 10:24 tunneld[5514]: mppecomp
10/01/08 10:24 tunneld[5514]: drop
10/01/08 10:24 tunneld[5514]: nocomp
10/01/08 10:24 tunneld[5514]: stateless
10/01/08 10:24 tunneld[5514]: proxyarp
10/01/08 10:24 tunneld[5514]: setpptpmtu
10/01/08 10:24 tunneld[5514]: 1436
10/01/08 10:24 tunneld[125]: rcvd SIGCHLD--ignoring
10/01/08 10:24 tunneld[125]: child pid 5514 died
10/01/08 10:24 tunneld[125]: child pid 5514 died without us killing it
10/01/08 10:24 tunneld[125]: killing tunnel from 192.168.1.2
10/01/08 10:24 tunneld[125]: killing child pid 5514
10/01/08 10:24 tunneld[125]: setting channel 192.168.1.1:192.168.1.190 to be re-used

Any help in this would be greatly appreciated.

 
The WatchGuard should be handling the VPN traffic.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top