Re: VPN Ok for Win2K client but not XP

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Joe (joe_at_jretrading.com)
Date: 01/02/05


Date: Sun, 2 Jan 2005 20:24:19 +0000

In message <7823E52A-F95B-4650-B5C1-2FC8D0F43271@microsoft.com>, neilm
<neilm@discussions.microsoft.com> writes
>Hi
>
>We've been running SBS2003 for about a year now with few problems. We have a
>fixed IP and use VPN to allow staff access from home.
>
>For some reason in the last couple of months VPN access from WinXP clients
>seems to have stopped working! I wasn't the first to notice as the desktop I
>usually use for VPN access has Win2k and is still working fine.
>
>However, some staff using WinXP say it has stopped working, and producing
>Error: 721 during the Username and Password verification phase. I have since
>tried to access the VPN (both using Remote Connection Manager and a raw VPN
>connection) with my XP laptop and I receive the same error.
>
>Have I inadvertantly installed a patch on the server which could cause this
>problem? All of the XP machines are running SP2 - could that be an issue?
>
>The only KB article I could find which seemed promising is 810839, but
>installing the registry fix on my laptop has made no difference.
>
>Does anyone have any ideas? What are the differences in the VPN client
>between 2K and XP?
>
No ideas, just some more data. I had a call at home to say that a
regular user of VPN was setting up a new machine on the local network
and VPN didn't work, nor did his own laptop when he tried it. I had
recently connected from home using Win98, and did so again without
trouble. I tried it from an XP Pro machine at home and it didn't work,
several times. Back to Win98, OK. I tried from my son's XP Home, no
good, from Win98 still OK. I fired up W2K Server, no good. Tried it a
second time and it connected, though after a longer delay than usual.
Tried XP Pro, now OK. Called customer and they were now OK.

This must have happened after a reboot the day before, as the customer
had connected successfully the day before that. I'm not sure what, but
something got stuck somewhere and was cleared by the W2K connections.
Obviously this isn't happening for you, but I thought this case was
close enough to be another data point for someone. I had been thinking
along the lines of levels of encryption, which is lower from Win98, but
presumably W2K has the same level as XP. It was a few months ago, I
didn't think it was worth asking here as I had no information. Nothing
in any logs anywhere.

-- 
Joe


Relevant Pages

  • RE: PPTP VPN connection problems
    ... Since you want to contact your local MS support for help, ... Additional, you can establish the VPN connection from internal client, that ... | A ping to the server would result in "Request timed out". ...
    (microsoft.public.windows.server.sbs)
  • RE: PPTP VPN connection problems
    ... But I do not think it is in the ADSL router itself. ... They do not say it but maybe they prohibit VPN connections ... fix IP for my connection – PPPoE/PPPoA) subscription at belgacom in Belgium ... | A ping to the server would result in "Request timed out". ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN Client
    ... Thanks for the help on losing the remote connection when you connect to VPN. ... Regarding the router port forward issue, you should point the port 1723 to ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN Ports to Open
    ... the VPN connection after you change the firewall before SBS. ... On the server, please stop the Routing and Remote Access service. ... Total GRE packets sent = 1 ...
    (microsoft.public.windows.server.sbs)
  • RE: VPN connection not passing the password auth stage.
    ... I understand that when you try to establish a VPN ... connection, the connection fails in the process of verifying the ... PPTP client and a PPTP server. ... The router must be able to pass Generic ...
    (microsoft.public.windows.server.sbs)