Re: Connecting remotely through VPN
- From: BrassicaNigra <brassica_nigra@xxxxxxxxxxxxxxxx>
- Date: Wed, 11 Feb 2009 14:57:01 -0800
Ports and protocols are enabled. Browser server is running. All of this is
evidenced by the fact I can connect to my instance using a static IP. Since
the SQL instance is configured for dynamic ports the port on which it
connects can change, but it does connect.
The VPN is configured to allow all port traffic, but I cannot connect to my
SQL server when connected to my VPN.
"William Vaughn (MVP)" wrote:
Okay, did you enable the ports and protocols on the SQL Server instance?.
What about the SQL Browser service? Is it running? What port are you using
when connecting directly? Is this port open through the system firewall?
--
__________________________________________________________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker’s Guide to Visual Studio and SQL Server (7th Edition)
http://betav.com http://betav.com/blog/billva
____________________________________________________________________________________________
"BrassicaNigra" <brassica_nigra@xxxxxxxxxxxxxxxx> wrote in message
news:2A0A9F79-BFDE-4E89-86F8-719F36FFDB0D@xxxxxxxxxxxxxxxx
Charles,
Finally I get to return to this project (at least for a while).
A few new things have come to light regarding this. What started as a
project to resolve this issue at one client turned up at a different
client
that had the same configuration and the same problem.
I replicated their setups in my development lab and ran into the same
results. No connectivity to SQL server over the VPN. My development
machine
has a static IP as well so I tried connecting directly (no VPN) to it and
it
worked just fine.
All of these machines are running MS SBS2003 R2. On all three VPN was
setup
using the server management tools and default settings. All of them allow
you to connect to SQLExpress via Remote Desktop. All have mixed mode
authentication and user accounts setup for external access using SQL
authentication.
SP2 is installed on 2 of these machines and SQLExpress 2008 is installed
on
the other. The error message in all cases is the same one I sent in my
original email (network related). The machines have been rebooted
numerous
times so I do not believe traffic or too many connections are at issue.
It seems like it must be something in the default VPN settings on SBS2003.
Hope this helps,
Dale Hoffman
""Charles Wang [MSFT]"" wrote:
Hi Dale,
Thank you for sending the error logs to me. Your descriptions had
indicated
that you could access the TCP port on which your SQL Server Express
instance was listening.
From the log files, I found the following error messages:
2009-01-14 16:07:24.14 Logon Error: 17187, Severity: 16, State: 1.
2009-01-14 16:07:24.14 Logon SQL Server is not ready to accept new
client connections. Wait a few minutes before trying again. If you have
access to the error log, look for the informational message that
indicates
that SQL Server is ready before trying to connect again. [CLIENT:
10.0.1.20]
2009-01-14 16:07:24.14 Logon Error: 17187, Severity: 16, State: 1.
2009-01-14 16:07:24.14 Logon SQL Server is not ready to accept new
client connections. Wait a few minutes before trying again. If you have
access to the error log, look for the informational message that
indicates
that SQL Server is ready before trying to connect again. [CLIENT:
10.0.1.128]
Based on my research, it is most likely the known issue dedicatedly
addressed by this KB article:
FIX: A "17187" error message may be logged in the Errorlog file when an
instance of SQL Server 2005 is under a heavy load
http://support.microsoft.com/kb/929376
I recommend that you first check if SQL Server 2005 Express SP2 has been
installed on your computer, if not, please install it first and then
check
if it works. You can download it from this link:
http://www.microsoft.com/downloads/details.aspx?familyid=31711D5D-725C-4AFA-
9D65-E4465CDFF1E7&displaylang=en
Also from the error logs, it seemed that your SQL Server was using a
certificate for SSL encryption, if this issue persists after you apply
SP2,
I recommend that you refer to this article to reconfigure your SSL
encryption for your SQL Server:
How to enable SSL encryption for an instance of SQL Server by using
Microsoft Management Console
http://support.microsoft.com/kb/316898
Thank you!
Best regards,
Charles Wang
Microsoft Online Community Support
=========================================================
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg@xxxxxxxxxxxxxx
=========================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.
=========================================================
- Follow-Ups:
- Re: Connecting remotely through VPN
- From: "Charles Wang [MSFT]"
- Re: Connecting remotely through VPN
- References:
- RE: Connecting remotely through VPN
- From: BrassicaNigra
- Re: Connecting remotely through VPN
- From: William Vaughn \(MVP\)
- RE: Connecting remotely through VPN
- Prev by Date: Re: Connecting remotely through VPN
- Next by Date: Re: Connecting remotely through VPN
- Previous by thread: Re: Connecting remotely through VPN
- Next by thread: Re: Connecting remotely through VPN
- Index(es):
Relevant Pages
|
