RE: VPN error 619 Windows 2003 SBS NO ISA

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

Hello Frankie,

Thank you for using newsgroup!

Based on my research, for more information about this error, please refer
to:
923944: List of Error Codes that you may receive when you try to make a
dial-up connection or a VPN connection in Windows Vista
http://support.microsoft.com/default.aspx?scid=kb;EN-US;923944

I have the following suggestions for your reference:

The following tools or content are available to expedite troubleshooting of
this symptom:
Note: This solution contains a list of troubleshooting steps that may
assist in resolving many symptom-specific issues. Please also continue to
leverage your local resources for additional assistance.

1. Common PPTP client connection errors include error 721 (sometimes error
619 on XP clients, or error 650). There are 2 likely causes for these
errors:

A. GRE protocol being blocked somewhere between the client and server
B. The PPTP client gets a GRE packet from a different IP address than it
tried to connect to.
This is described in KB article 271731
PPTP clients cannot connect to a PPTP server that has multiple IP addresses
<http://support.microsoft.com/default.aspx?scid=kb;EN-US;271731>

2. Common problems seen with L2TP and IPsec negotiation failures are with
certificate configuration. If you suspect that certificates are preventing
a successful L2TP/IPsec connection, a pre-shared key can be used to test
the connection. For more information on this, see KB article 240262
240262: How to configure an L2TP/IPSec connection by using Preshared Key
Authentication
<http://support.microsoft.com/default.aspx?scid=kb;EN-US;240262>

3. If your remote access server is configured with a static IP address
pool, verify that there are enough addresses in the pool. In this case, the
remote access server will be unable to allocate an IP address to the remote
access client.

4. You can verify whether all of the remote access ports on the remote
access server are already being used by clicking Ports in Routing and
Remote Access. If all ports are busy, disconnect any inactive connections,
or consider adding more ports.

5. For password-based authentication, verify that the VPN client's user
credentials are correct and can be validated by the authentication server
(the VPN server or the RADIUS server). Verify that the user account of the
VPN client is not locked out, expired, or disabled, and that the time the
connection is being made corresponds to the configured logon hours.

6. Verify that the remote access client and the remote access server are
configured to use at least one common authentication method and at least
one common encryption method. Windows Vista clients will be configured by
default to require 128-bit encryption, and may fail to connect while XP
clients succeed if server encryption levels are set to 40 or 56-bit. For
more information on this issue, see KB article 929857.
929857: You receive error code 741 when you try to make a PPTP-based VPN
connection on a computer that is running Windows Vista
<http://support.microsoft.com/default.aspx?scid=kb;EN-US;929857>


Additional Links:
=========================
Remote Access Troubleshooting:
<http://technet2.microsoft.com/WindowsServer/en/library/7a68b680-81d9-4140-9
d47-a86de2f600e11033.mspx?mfr=true>

Troubleshooting Windows 2000 Remote Access Connections:
<http://www.microsoft.com/technet/prodtechnol/windows2000serv/support/ra_ts5
mspx>

Remote Access Best Practices:
<http://technet2.microsoft.com/WindowsServer/en/library/80842301-6d42-4ffe-9
100-d8b64e8fffa81033.mspx?mfr=true>

Remote Access How To:
<http://technet2.microsoft.com/WindowsServer/en/library/16b7eba2-86ab-4c7c-b
cf7-488bbb97644c1033.mspx?mfr=true>

Thanks & Regards,

Ken Zhao

Microsoft Online Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security <http://www.microsoft.com/security>
====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.




--------------------
| Thread-Topic: VPN error 619 Windows 2003 SBS NO ISA
| thread-index: Aceb7cuHWDpvdS0fR9OAa2rcELj0dQ==
| X-WBNR-Posting-Host: 207.46.19.197
| From: =?Utf-8?B?ZnJhbmtpZQ==?= <frankie@xxxxxxxxxxxxxx>
| Subject: VPN error 619 Windows 2003 SBS NO ISA
| Date: Mon, 21 May 2007 14:20:02 -0700
| Lines: 15
| Message-ID: <E5B3451F-3F56-416E-BDB0-B71A9383ED51@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
| Newsgroups: microsoft.public.windows.server.networking
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.server.networking:4676
| NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| X-Tomcat-NG: microsoft.public.windows.server.networking
|
| I have setup a WORKING VPN on a Windows 2003 SBS. I say WORKING because
OTHER
| users are able to connect with no problem. When *I* try to connect from
my
| office, I get an error 619. I am CURRENTLY using VISTA, but have also
used XP
| with the same results. I am NOT using ISA on the SBS. On this end, I am
| behind a linksys WRT54G with VPN passthru enabled (same router and setup
on
| the SBS end). I CAN connect to the server via Remote Desktop using the
SAME
| username and password that fails with VPN. I have OTHER clients setup
with
| VPN, also on Windows 2003 SBS and I *CAN* connect to them with NO
problem. My
| ISP is Comcast Cable, the ISP on the SBS I can't connect to is OptOnline
| Cable. I have read ALL the Technet articles and have tried everything
from
| registering the SBS server as a RAS server, to setting it to assign staic
| IP's. Nothing has helped. The client I am trying to connect to uses
DYNDNS to
| keep track of its IP since Optonline assigns them a static IP, but THAT
does
| not seem to be an issue since I can connect to them via remote desktop
using
| the VERY same DYNDNS URL. Can anyone help?
|

.

Relevant Pages

  • Re: VPN clients unable to connect to other resources.
    ... gateway matches the IP of the remote client, and DNS and WINS point to the ... remote (although it takes close to a minute to connect, ... This is just regular Windows VPN, ... VPN server, remote routing and access running on the SBS 2003 server ...
    (microsoft.public.windows.server.sbs)
  • RE: Remote access recurrent disconnection
    ... My VPN and RWW is already configured as you have described below. ... server and rerun the CEICW for the remote access to work. ... As from then every 3 hours I have to run this wizard for remote access to ...
    (microsoft.public.windows.server.sbs)
  • RE: Problems with connectcomputer and active directory
    ... I understand that you would like to join a remote client to the domain. ... If you have hardware VPN tunnel setup using Linksys or others, ... In this scenario you have to configure the SBS Server computer to enable ... Create a VPN connection to ISA/RRAS on the Internet ...
    (microsoft.public.windows.server.sbs)
  • RE: Remote connectivity problems
    ... do you mean you have added a remote client to SBS ... If you have hardware VPN tunnel setup using Linksys or others, ... In this scenario you have to configure the SBS Server computer to enable ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN disconnection
    ... Server 2003 SP2 or the Scalable Networking Pack on a Windows Small Business ... Please Run the Configure Remote Access wizard to configure VPN. ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)