|
|
You're in the
sql server connect
group:Encrypted Connection
sql server connect:
If this is not the correct groups to post this, please redirect me. I have a .NET application and SQL Server 2005 Express running on a Windows Server 2003 Web Edition. Both connect to a remote SQL Server 2000 database running on Windows 2000. SQL Server Express 2005 has the 2000 server set up as a linked server. What are my options for encrypting the connections to the SQL Server 2000? For the .NET app, I assume that I can use multiprotocol. Correct? Other suggestions? What about the SQL Server 2005 linked server to 2000? TIA -- AG Email: discuss at adhdata dot com
SQL Server supports SSL encryption for connections. See the following
articles: http://support.microsoft.com/kb/276553 http://msdn2.microsoft.com/en-us/library/ms189067.aspx http://msdn2.microsoft.com/en-us/library/ms191192.aspx Regards, Plamen Ratchev http://www.SQLStudio.com [quoted text, click to view] "AG" <NOSPAMa-giam@newsgroups.nospam> wrote in message news:%23JeihNoKHHA.960@TK2MSFTNGP04.phx.gbl... > Hi all, > > If this is not the correct groups to post this, please redirect me. > > I have a .NET application and SQL Server 2005 Express running on a Windows > Server 2003 Web Edition. Both connect to a remote SQL Server 2000 database > running on Windows 2000. > SQL Server Express 2005 has the 2000 server set up as a linked server. > > What are my options for encrypting the connections to the SQL Server 2000? > For the .NET app, I assume that I can use multiprotocol. Correct? Other > suggestions? > > What about the SQL Server 2005 linked server to 2000? > > TIA > > -- > > AG > Email: discuss at adhdata dot com > > > >
Thanks for the quick response Plamen,
That all requires a SSL cert, which the 2000 server does not have. Is there some way to use multiprotocol with the linked server? The current setup is using a VPN, but we are moving to a new server and there may be a problem setting up a VPN. -- AG Email: discuss at adhdata dot com [quoted text, click to view] "Plamen Ratchev" <Plamen@SQLStudio.com> wrote in message news:Oyn6mApKHHA.4992@TK2MSFTNGP04.phx.gbl... > SQL Server supports SSL encryption for connections. See the following > articles: > http://support.microsoft.com/kb/276553 > http://msdn2.microsoft.com/en-us/library/ms189067.aspx > http://msdn2.microsoft.com/en-us/library/ms191192.aspx > > Regards, > > Plamen Ratchev > http://www.SQLStudio.com > > > "AG" <NOSPAMa-giam@newsgroups.nospam> wrote in message > news:%23JeihNoKHHA.960@TK2MSFTNGP04.phx.gbl... >> Hi all, >> >> If this is not the correct groups to post this, please redirect me. >> >> I have a .NET application and SQL Server 2005 Express running on a >> Windows Server 2003 Web Edition. Both connect to a remote SQL Server 2000 >> database running on Windows 2000. >> SQL Server Express 2005 has the 2000 server set up as a linked server. >> >> What are my options for encrypting the connections to the SQL Server >> 2000? >> For the .NET app, I assume that I can use multiprotocol. Correct? Other >> suggestions? >> >> What about the SQL Server 2005 linked server to 2000? >> >> TIA >> >> -- >> >> AG >> Email: discuss at adhdata dot com >> >> >> >> > >
The multiprotocol has been depreciated in SQL Server 2005. See this post for
details (look under the Changes section): http://blogs.msdn.com/sql_protocols/archive/2005/09/22/473111.aspx If you do not have a local Certificate Server you can always purchase a third-party certificate. Regards, Plamen Ratchev http://www.SQLStudio.com [quoted text, click to view] "AG" <NOSPAMa-giam@newsgroups.nospam> wrote in message news:%23kAVctpKHHA.4384@TK2MSFTNGP03.phx.gbl... > Thanks for the quick response Plamen, > > That all requires a SSL cert, which the 2000 server does not have. > Is there some way to use multiprotocol with the linked server? > > The current setup is using a VPN, but we are moving to a new server and > there may be a problem setting up a VPN. > > -- > > AG > Email: discuss at adhdata dot com > > > > "Plamen Ratchev" <Plamen@SQLStudio.com> wrote in message > news:Oyn6mApKHHA.4992@TK2MSFTNGP04.phx.gbl... >> SQL Server supports SSL encryption for connections. See the following >> articles: >> http://support.microsoft.com/kb/276553 >> http://msdn2.microsoft.com/en-us/library/ms189067.aspx >> http://msdn2.microsoft.com/en-us/library/ms191192.aspx >> >> Regards, >> >> Plamen Ratchev >> http://www.SQLStudio.com >> >> >> "AG" <NOSPAMa-giam@newsgroups.nospam> wrote in message >> news:%23JeihNoKHHA.960@TK2MSFTNGP04.phx.gbl... >>> Hi all, >>> >>> If this is not the correct groups to post this, please redirect me. >>> >>> I have a .NET application and SQL Server 2005 Express running on a >>> Windows Server 2003 Web Edition. Both connect to a remote SQL Server >>> 2000 database running on Windows 2000. >>> SQL Server Express 2005 has the 2000 server set up as a linked server. >>> >>> What are my options for encrypting the connections to the SQL Server >>> 2000? >>> For the .NET app, I assume that I can use multiprotocol. Correct? Other >>> suggestions? >>> >>> What about the SQL Server 2005 linked server to 2000? >>> >>> TIA >>> >>> -- >>> >>> AG >>> Email: discuss at adhdata dot com >>> >>> >>> >>> >> >> > >
Hello AG,
I agree with Plamen that you could use a third party certificate if necessary. Also, you may consider configure IPsec between the servers so that all IP traffic is protected between them. Pleas esee the following articles for more details: TechNet Support WebCast: How to use IPSec to help secure network traffic http://support.microsoft.com/default.aspx?kbid=888266 IPsec http://www.microsoft.com/technet/network/ipsec/default.mspx If you have further comments or feedback, please feel free to let's know. Thank you. Best Regards, Peter Yang MCSE2000/2003, MCSA, MCDBA Microsoft Online Community Support ================================================== Get notification to my posts through email? Please refer to http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif ications <http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>. Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at <http://msdn.microsoft.com/subscriptions/support/default.aspx>. ================================================== This posting is provided "AS IS" with no warranties, and confers no rights.
Thanks Peter,
Sorry, I did not get back to you sooner. I wanted to get the client's networking person involved and that will happen today. IPsec looks like it might do the job. -- AG Email: discuss at adhdata dot com [quoted text, click to view] "Peter Yang [MSFT]" <petery@online.microsoft.com> wrote in message news:Jj1YdPvKHHA.2304@TK2MSFTNGHUB02.phx.gbl... > Hello AG, > > I agree with Plamen that you could use a third party certificate if > necessary. > > Also, you may consider configure IPsec between the servers so that all IP > traffic is protected between them. Pleas esee the following articles for > more details: > > TechNet Support WebCast: How to use IPSec to help secure network traffic > http://support.microsoft.com/default.aspx?kbid=888266 > > IPsec > http://www.microsoft.com/technet/network/ipsec/default.mspx > > If you have further comments or feedback, please feel free to let's know. > Thank you. > > Best Regards, > > Peter Yang > MCSE2000/2003, MCSA, MCDBA > Microsoft Online Community Support > ================================================== > Get notification to my posts through email? Please refer to > http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif > ications > <http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>. > Note: The MSDN Managed Newsgroup support offering is for non-urgent issues > where an initial response from the community or a Microsoft Support > Engineer within 1 business day is acceptable. Please note that each follow > up response may take approximately 2 business days as the support > professional working with you may need further investigation to reach the > most efficient resolution. The offering is not appropriate for situations > that require urgent, real-time or phone-based interactions or complex > project analysis and dump analysis issues. Issues of this nature are best > handled working with a dedicated Microsoft Support Engineer by contacting > Microsoft Customer Support Services (CSS) at > <http://msdn.microsoft.com/subscriptions/support/default.aspx>. > ================================================== > This posting is provided "AS IS" with no warranties, and confers no > rights. >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |