Re: XP PPTP VPN Error 721

From: Bob (spam_at_spam.com)
Date: 03/30/04 

Date: Tue, 30 Mar 2004 13:01:19 GMT

On Mon, 29 Mar 2004 23:35:46 -0500, "Bill Sanderson"
<Bill_Sanderson@msn.com.plugh.org> wrote:

>So--what about those routers, firewalls, etc?

I assume, based on past experience, that there is no router or
firewall issue with the VPN Client. The only router/firewall problems
are on the Server side of the connection. Just to make absolutely
sure, I put the Client in the DMZ - and it made no difference.

The router is a brand new Netopia 3546 Cayman DSL router installed by
SBC (Southwestern Bell) as part of their DSL service. We asked Netopia
tech support to Telnet into it and check our configuration. We had
forwarded port 1723 to static IP address 192.168.1.100 on the LAN,
which is the VPN Server. We also enabled PPTP Passthru in the router.
In addition we restricted the LAN DHCP in the router to an address
range 192.168.1.1 - 192.168.1.50. That way no one would be able to
take 192.168.1.100 in case the VPN Server machine was offline. Netopia
tech support took a look at all this and said everything was set up
correctly for PPTP VPN Passthru.

Earlier we were getting Error 678, the "No Connection" error. The man
at the office looked in the process tableon the VPN Server and
discovered that, although we had exited a firewall program, something
associated with it was still running. He killed that process and then
we were able to make some headway.

Now I, at another location running the VPN Client, was able to get
beyond Error 678 and begin to "Verify username and password". But it
would terminate there with Error 721.

I removed the password from the VPN Client connection dialog to see if
it was the username or the password that was causing the problem.
Everything was the same as before, so I assume that the VPN Server is
not able to verify the username and never gets to the password.

>You've done it before, so you know what needs to be done--what is different
>about the hardware/software in this set of links?

The VPN Server I set up for test purposes the other day was on Win2K.
The VPN Client was XP. Now the situation is reversed in terms of
operating system versions. Also, the other machine is a different
machine in a different environment.

Why would the VPN Server not be able to verify the VPN Client
username?

Is this a matter of another firewall blocking the process of username
verification or is this an XP VPN configuration issue?

Or does the fact that we are making it to verification rule out any
blocking from a firewall? 

-- 
Map Of The Vast Right Wing Conspiracy:
http://www.freewebs.com/vrwc/
You know you are in Hell when you have to make a
distinction between what is moral and what is legal.

Relevant Pages

  • Re: Help With VPN Server
    ... the PPTP VPN server on a XP box needs to have both TCP Port 1723 ... forwarded through the router to the static LAN IP of the PPTP VPN server box ... Al Jarvi (MS-MVP Windows Networking) ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Help With VPN Server
    ... specific pc (the machine running as the VPN server). ... The router is a Telkom rebranded Marconi router (that is a rebrand of ... VPN Pass Through is enabled as well. ... > Al Jarvi (MS-MVP Windows Networking) ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: xp vpn connection problem
    ... through the modem/router to the VPN server PC. ... Make sure you have TCP Port 1723 forwarded to the local private *STATIC* LAN IP of the PPTP VPN ... is being passed through the router... ... > Trying to set up VPN connection to office LAN using xp VPN ...
    (microsoft.public.windowsxp.work_remotely)
  • xp vpn connection problem
    ... Trying to set up VPN connection to office LAN using xp VPN ... The router has port tcp 1723 redirected to ... local ip address of the xp machine acting as vpn server. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: HIPAA and firewalls
    ... >compliant manner using VPN. ... this is a bad and expensive method of purchasing a router. ... the VPN is setup in 5 steps. ... network IP block to both sides of the VPN tunnel. ...
    (comp.security.firewalls)
Loading