VPN error 619 Windows 2003 SBS NO ISA

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?

This search result may help,

ras error codeReceiving RAS error 619 while connecting to a VPN via SBC VPN error 619 - Case Study Error 624 Error 628 Error 629 Error 630 - The port was disconnected due ...
http://www.chicagotech.net/raserrors.htm


Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"frankie" <(E-Mail Removed)> wrote in message news:E5B3451F-3F56-416E-BDB0-(E-Mail Removed)...
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?

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...b;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/Window...80-81d9-4140-9
d47-a86de2f600e11033.mspx?mfr=true>

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

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

Remote Access How To:
<http://technet2.microsoft.com/Window...a2-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==?= <(E-Mail Removed)>
| 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-(E-Mail Removed)>
| 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?
|

I appreciate the response. Unfortunately none of the articles or suggestions
work. I think the key here is "Why can others connect to the same server and
I cannot?" Obviously, the server is configured correctly otherwise NO ONE
would be able to connect via VPN. In addition, I *CAN* connect to *EVERY*
other Windows 2003 SBS server that I have configured for VPN access. I am
using the SAME computer and the *EXACT* same settings both on the server end
and the client end. It is NOT a permissions issue as I am logging on as the
administrator account. I have even tried loggin on with the accounts of
others who HAVE successfully connected from THEIR computers with no luck. Do
you have any suggestions for this specific type of problem?

""Ken Zhao [MSFT]"" wrote:

> 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...b;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/Window...80-81d9-4140-9
> d47-a86de2f600e11033.mspx?mfr=true>
>
> Troubleshooting Windows 2000 Remote Access Connections:
> <http://www.microsoft.com/technet/pro...support/ra_ts5
> .mspx>
>
> Remote Access Best Practices:
> <http://technet2.microsoft.com/Window...01-6d42-4ffe-9
> 100-d8b64e8fffa81033.mspx?mfr=true>
>
> Remote Access How To:
> <http://technet2.microsoft.com/Window...a2-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==?= <(E-Mail Removed)>
> | 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-(E-Mail Removed)>
> | 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?
> |
>
>

I appreciate the response. Unfortunately none of the articles or suggestions
work. I think the key here is "Why can others connect to the same server and
I cannot?" Obviously, the server is configured correctly otherwise NO ONE
would be able to connect via VPN. In addition, I *CAN* connect to *EVERY*
other Windows 2003 SBS server that I have configured for VPN access. I am
using the SAME computer and the *EXACT* same settings both on the server end
and the client end. It is NOT a permissions issue as I am logging on as the
administrator account. I have even tried loggin on with the accounts of
others who HAVE successfully connected from THEIR computers with no luck. Do
you have any suggestions for this specific type of problem?


"Robert L [MVP - Networking]" wrote:

> This search result may help,
>
> ras error codeReceiving RAS error 619 while connecting to a VPN via SBC VPN error 619 - Case Study Error 624 Error 628 Error 629 Error 630 - The port was disconnected due ...
> http://www.chicagotech.net/raserrors.htm
>
>
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
> "frankie" <(E-Mail Removed)> wrote in message news:E5B3451F-3F56-416E-BDB0-(E-Mail Removed)...
> 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?

Hi Frankie,

Thanks for your response.

Does the issue only occur on this specific Windows Vista client or the
specific user account?

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: AcecxymNALqG9F8pQMGhj7VZoJYaMA==
| X-WBNR-Posting-Host: 207.46.19.197
| From: =?Utf-8?B?ZnJhbmtpZQ==?= <(E-Mail Removed)>
| References: <E5B3451F-3F56-416E-BDB0-(E-Mail Removed)>
<(E-Mail Removed)>
| Subject: RE: VPN error 619 Windows 2003 SBS NO ISA
| Date: Tue, 22 May 2007 16:16:01 -0700
| Lines: 166
| Message-ID: <5A9BB32E-C220-433F-BD08-(E-Mail Removed)>
| 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:4704
| NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| X-Tomcat-NG: microsoft.public.windows.server.networking
|
| I appreciate the response. Unfortunately none of the articles or
suggestions
| work. I think the key here is "Why can others connect to the same server
and
| I cannot?" Obviously, the server is configured correctly otherwise NO ONE
| would be able to connect via VPN. In addition, I *CAN* connect to *EVERY*
| other Windows 2003 SBS server that I have configured for VPN access. I am
| using the SAME computer and the *EXACT* same settings both on the server
end
| and the client end. It is NOT a permissions issue as I am logging on as
the
| administrator account. I have even tried loggin on with the accounts of
| others who HAVE successfully connected from THEIR computers with no luck.
Do
| you have any suggestions for this specific type of problem?
|
| ""Ken Zhao [MSFT]"" wrote:
|
| > 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...b;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/Window...80-81d9-4140-9
| > d47-a86de2f600e11033.mspx?mfr=true>
| >
| > Troubleshooting Windows 2000 Remote Access Connections:
| >
<http://www.microsoft.com/technet/pro...support/ra_ts5
| > .mspx>
| >
| > Remote Access Best Practices:
| >
<http://technet2.microsoft.com/Window...01-6d42-4ffe-9
| > 100-d8b64e8fffa81033.mspx?mfr=true>
| >
| > Remote Access How To:
| >
<http://technet2.microsoft.com/Window...a2-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==?= <(E-Mail Removed)>
| > | 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-(E-Mail Removed)>
| > | 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?
| > |
| >
| >
|

Hi Ken,

I have tried numerous user accounts on the remote server INCLUDING the
administrator account. The accounts I tried *DO* work from OTHER computers
(not on my network), just not mine

So far I have tried it from two XP clients and one Vista client. None can
connect via VPN to this ONE server. The only thing they have in common is
that we are all behind the same Linksys WRT54GS wireless router (connected
both wirelessly and harwired) and of course we are also behind the same
Comcast service connected through a Motorola SB5120 cable modem.

However, please keep in mind that these *VERY* same computers and accounts
behind the *VERY* same router and cable modem *ARE* able to connect to OTHER
VPN servers that I have set up, and that the other servers are all running
the *VERY* same OS (Windows 2003 SBS) including the server we CAN'T connect
to. So, you can see why I am frustrated and confused. It is not like I
haven't done this successfully before.

""Ken Zhao [MSFT]"" wrote:

> Hi Frankie,
>
> Thanks for your response.
>
> Does the issue only occur on this specific Windows Vista client or the
> specific user account?
>
> 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: AcecxymNALqG9F8pQMGhj7VZoJYaMA==
> | X-WBNR-Posting-Host: 207.46.19.197
> | From: =?Utf-8?B?ZnJhbmtpZQ==?= <(E-Mail Removed)>
> | References: <E5B3451F-3F56-416E-BDB0-(E-Mail Removed)>
> <(E-Mail Removed)>
> | Subject: RE: VPN error 619 Windows 2003 SBS NO ISA
> | Date: Tue, 22 May 2007 16:16:01 -0700
> | Lines: 166
> | Message-ID: <5A9BB32E-C220-433F-BD08-(E-Mail Removed)>
> | 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:4704
> | NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
> | X-Tomcat-NG: microsoft.public.windows.server.networking
> |
> | I appreciate the response. Unfortunately none of the articles or
> suggestions
> | work. I think the key here is "Why can others connect to the same server
> and
> | I cannot?" Obviously, the server is configured correctly otherwise NO ONE
> | would be able to connect via VPN. In addition, I *CAN* connect to *EVERY*
> | other Windows 2003 SBS server that I have configured for VPN access. I am
> | using the SAME computer and the *EXACT* same settings both on the server
> end
> | and the client end. It is NOT a permissions issue as I am logging on as
> the
> | administrator account. I have even tried loggin on with the accounts of
> | others who HAVE successfully connected from THEIR computers with no luck.
> Do
> | you have any suggestions for this specific type of problem?
> |
> | ""Ken Zhao [MSFT]"" wrote:
> |
> | > 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...b;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/Window...80-81d9-4140-9
> | > d47-a86de2f600e11033.mspx?mfr=true>
> | >
> | > Troubleshooting Windows 2000 Remote Access Connections:
> | >
> <http://www.microsoft.com/technet/pro...support/ra_ts5
> | > .mspx>
> | >
> | > Remote Access Best Practices:
> | >
> <http://technet2.microsoft.com/Window...01-6d42-4ffe-9
> | > 100-d8b64e8fffa81033.mspx?mfr=true>
> | >
> | > Remote Access How To:
> | >
> <http://technet2.microsoft.com/Window...a2-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==?= <(E-Mail Removed)>
> | > | 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-(E-Mail Removed)>
> | > | 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?
> | > |
> | >
> | >
> |
>
>

Hi Frankie,

For the VPN error 619, please refer to:
314485: "Error 619" or "Error 645" error message when you attempt to
connect to a Routing and Remote Access server
http://support.microsoft.com/default...b;EN-US;314485

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: Aceey8Pkcddw6LraTpGmpLwhFLPgPQ==
| X-WBNR-Posting-Host: 207.46.19.197
| From: =?Utf-8?B?ZnJhbmtpZQ==?= <(E-Mail Removed)>
| References: <E5B3451F-3F56-416E-BDB0-(E-Mail Removed)>
<(E-Mail Removed)>
<5A9BB32E-C220-433F-BD08-(E-Mail Removed)>
<(E-Mail Removed)>
| Subject: RE: VPN error 619 Windows 2003 SBS NO ISA
| Date: Fri, 25 May 2007 05:54:00 -0700
| Lines: 283
| Message-ID: <CE16851E-CA9B-4888-B355-(E-Mail Removed)>
| 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:4784
| NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| X-Tomcat-NG: microsoft.public.windows.server.networking
|
| Hi Ken,
|
| I have tried numerous user accounts on the remote server INCLUDING the
| administrator account. The accounts I tried *DO* work from OTHER
computers
| (not on my network), just not mine
|
| So far I have tried it from two XP clients and one Vista client. None can
| connect via VPN to this ONE server. The only thing they have in common is
| that we are all behind the same Linksys WRT54GS wireless router
(connected
| both wirelessly and harwired) and of course we are also behind the same
| Comcast service connected through a Motorola SB5120 cable modem.
|
| However, please keep in mind that these *VERY* same computers and
accounts
| behind the *VERY* same router and cable modem *ARE* able to connect to
OTHER
| VPN servers that I have set up, and that the other servers are all
running
| the *VERY* same OS (Windows 2003 SBS) including the server we CAN'T
connect
| to. So, you can see why I am frustrated and confused. It is not like I
| haven't done this successfully before.
|
| ""Ken Zhao [MSFT]"" wrote:
|
| > Hi Frankie,
| >
| > Thanks for your response.
| >
| > Does the issue only occur on this specific Windows Vista client or the
| > specific user account?
| >
| > 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: AcecxymNALqG9F8pQMGhj7VZoJYaMA==
| > | X-WBNR-Posting-Host: 207.46.19.197
| > | From: =?Utf-8?B?ZnJhbmtpZQ==?= <(E-Mail Removed)>
| > | References: <E5B3451F-3F56-416E-BDB0-(E-Mail Removed)>
| > <(E-Mail Removed)>
| > | Subject: RE: VPN error 619 Windows 2003 SBS NO ISA
| > | Date: Tue, 22 May 2007 16:16:01 -0700
| > | Lines: 166
| > | Message-ID: <5A9BB32E-C220-433F-BD08-(E-Mail Removed)>
| > | 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:4704
| > | NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| > | X-Tomcat-NG: microsoft.public.windows.server.networking
| > |
| > | I appreciate the response. Unfortunately none of the articles or
| > suggestions
| > | work. I think the key here is "Why can others connect to the same
server
| > and
| > | I cannot?" Obviously, the server is configured correctly otherwise NO
ONE
| > | would be able to connect via VPN. In addition, I *CAN* connect to
*EVERY*
| > | other Windows 2003 SBS server that I have configured for VPN access.
I am
| > | using the SAME computer and the *EXACT* same settings both on the
server
| > end
| > | and the client end. It is NOT a permissions issue as I am logging on
as
| > the
| > | administrator account. I have even tried loggin on with the accounts
of
| > | others who HAVE successfully connected from THEIR computers with no
luck.
| > Do
| > | you have any suggestions for this specific type of problem?
| > |
| > | ""Ken Zhao [MSFT]"" wrote:
| > |
| > | > 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...b;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/Window...80-81d9-4140-9
| > | > d47-a86de2f600e11033.mspx?mfr=true>
| > | >
| > | > Troubleshooting Windows 2000 Remote Access Connections:
| > | >
| >
<http://www.microsoft.com/technet/pro...support/ra_ts5
| > | > .mspx>
| > | >
| > | > Remote Access Best Practices:
| > | >
| >
<http://technet2.microsoft.com/Window...01-6d42-4ffe-9
| > | > 100-d8b64e8fffa81033.mspx?mfr=true>
| > | >
| > | > Remote Access How To:
| > | >
| >
<http://technet2.microsoft.com/Window...a2-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==?= <(E-Mail Removed)>
| > | > | 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-(E-Mail Removed)>
| > | > | 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?
| > | > |
| > | >
| > | >
| > |
| >
| >
|

Hi Frankie,

I am just writing to see how everything is going. If you have any updates
or need any further assistance on this issue, please feel free to let me
know.

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.




--------------------
| X-Tomcat-ID: 62871764
| References: <E5B3451F-3F56-416E-BDB0-(E-Mail Removed)>
<(E-Mail Removed)>
<5A9BB32E-C220-433F-BD08-(E-Mail Removed)>
<(E-Mail Removed)>
<CE16851E-CA9B-4888-B355-(E-Mail Removed)>
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
| From: v-(E-Mail Removed) ("Ken Zhao [MSFT]")
| Organization: Microsoft
| Date: Mon, 28 May 2007 06:39:37 GMT
| Subject: RE: VPN error 619 Windows 2003 SBS NO ISA
| X-Tomcat-NG: microsoft.public.windows.server.networking
| Message-ID: <(E-Mail Removed)>
| Newsgroups: microsoft.public.windows.server.networking
| Lines: 349
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.server.networking:4816
| NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182
|
| Hi Frankie,
|
| For the VPN error 619, please refer to:
| 314485: "Error 619" or "Error 645" error message when you attempt to
| connect to a Routing and Remote Access server
| http://support.microsoft.com/default...b;EN-US;314485
|
| 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: Aceey8Pkcddw6LraTpGmpLwhFLPgPQ==
| | X-WBNR-Posting-Host: 207.46.19.197
| | From: =?Utf-8?B?ZnJhbmtpZQ==?= <(E-Mail Removed)>
| | References: <E5B3451F-3F56-416E-BDB0-(E-Mail Removed)>
| <(E-Mail Removed)>
| <5A9BB32E-C220-433F-BD08-(E-Mail Removed)>
| <(E-Mail Removed)>
| | Subject: RE: VPN error 619 Windows 2003 SBS NO ISA
| | Date: Fri, 25 May 2007 05:54:00 -0700
| | Lines: 283
| | Message-ID: <CE16851E-CA9B-4888-B355-(E-Mail Removed)>
| | 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:4784
| | NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| | X-Tomcat-NG: microsoft.public.windows.server.networking
| |
| | Hi Ken,
| |
| | I have tried numerous user accounts on the remote server INCLUDING the
| | administrator account. The accounts I tried *DO* work from OTHER
| computers
| | (not on my network), just not mine
| |
| | So far I have tried it from two XP clients and one Vista client. None
can
| | connect via VPN to this ONE server. The only thing they have in common
is
| | that we are all behind the same Linksys WRT54GS wireless router
| (connected
| | both wirelessly and harwired) and of course we are also behind the same
| | Comcast service connected through a Motorola SB5120 cable modem.
| |
| | However, please keep in mind that these *VERY* same computers and
| accounts
| | behind the *VERY* same router and cable modem *ARE* able to connect to
| OTHER
| | VPN servers that I have set up, and that the other servers are all
| running
| | the *VERY* same OS (Windows 2003 SBS) including the server we CAN'T
| connect
| | to. So, you can see why I am frustrated and confused. It is not like I
| | haven't done this successfully before.
| |
| | ""Ken Zhao [MSFT]"" wrote:
| |
| | > Hi Frankie,
| | >
| | > Thanks for your response.
| | >
| | > Does the issue only occur on this specific Windows Vista client or
the
| | > specific user account?
| | >
| | > 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: AcecxymNALqG9F8pQMGhj7VZoJYaMA==
| | > | X-WBNR-Posting-Host: 207.46.19.197
| | > | From: =?Utf-8?B?ZnJhbmtpZQ==?= <(E-Mail Removed)>
| | > | References: <E5B3451F-3F56-416E-BDB0-(E-Mail Removed)>
| | > <(E-Mail Removed)>
| | > | Subject: RE: VPN error 619 Windows 2003 SBS NO ISA
| | > | Date: Tue, 22 May 2007 16:16:01 -0700
| | > | Lines: 166
| | > | Message-ID: <5A9BB32E-C220-433F-BD08-(E-Mail Removed)>
| | > | 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:4704
| | > | NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| | > | X-Tomcat-NG: microsoft.public.windows.server.networking
| | > |
| | > | I appreciate the response. Unfortunately none of the articles or
| | > suggestions
| | > | work. I think the key here is "Why can others connect to the same
| server
| | > and
| | > | I cannot?" Obviously, the server is configured correctly otherwise
NO
| ONE
| | > | would be able to connect via VPN. In addition, I *CAN* connect to
| *EVERY*
| | > | other Windows 2003 SBS server that I have configured for VPN
access.
| I am
| | > | using the SAME computer and the *EXACT* same settings both on the
| server
| | > end
| | > | and the client end. It is NOT a permissions issue as I am logging
on
| as
| | > the
| | > | administrator account. I have even tried loggin on with the
accounts
| of
| | > | others who HAVE successfully connected from THEIR computers with no
| luck.
| | > Do
| | > | you have any suggestions for this specific type of problem?
| | > |
| | > | ""Ken Zhao [MSFT]"" wrote:
| | > |
| | > | > 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...b;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/Window...80-81d9-4140-9
| | > | > d47-a86de2f600e11033.mspx?mfr=true>
| | > | >
| | > | > Troubleshooting Windows 2000 Remote Access Connections:
| | > | >
| | >
|
<http://www.microsoft.com/technet/pro...support/ra_ts5
| | > | > .mspx>
| | > | >
| | > | > Remote Access Best Practices:
| | > | >
| | >
|
<http://technet2.microsoft.com/Window...01-6d42-4ffe-9
| | > | > 100-d8b64e8fffa81033.mspx?mfr=true>
| | > | >
| | > | > Remote Access How To:
| | > | >
| | >
|
<http://technet2.microsoft.com/Window...a2-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==?= <(E-Mail Removed)>
| | > | > | 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-(E-Mail Removed)>
| | > | > | 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?
| | > | > |
| | > | >
| | > | >
| | > |
| | >
| | >
| |
|
|