Connecting to a SQL Server 2005 over SSH using PuTTY

I'm having a problem connecting to my remote db from Management Studio, but I
am able to create an ODBC connection from the Data Sources applet in the
Control Panel.
PuTTY is setup to convert localhost:21433 to 192.168.100.242:1433 (the
address of my remote db server).
When I specify localhost:21433, provide the username, password, and catalog
to the Data Sources applet it connects fine. I then can use that DSN in
Visual Studio 2005 as a connection to the db.
However, when I try localhost,21433 in Management Studio, it gives me the
default connection error which talks about not having remote access enabled.
Please give me a hand with this as it is very important that I be able to
use the Management Studio tools for my app development.
Thanks in advance.
Trevor Murphy wrote:
> I'm having a problem connecting to my remote db from Management Studio, but I
> am able to create an ODBC connection from the Data Sources applet in the
> Control Panel.
> PuTTY is setup to convert localhost:21433 to 192.168.100.242:1433 (the
> address of my remote db server).
> When I specify localhost:21433, provide the username, password, and catalog
> to the Data Sources applet it connects fine. I then can use that DSN in
> Visual Studio 2005 as a connection to the db.
> However, when I try localhost,21433 in Management Studio, it gives me the
> default connection error which talks about not having remote access enabled.
> Please give me a hand with this as it is very important that I be able to
> use the Management Studio tools for my app development.
> Thanks in advance.
Does the connection error mention Named Pipes? If so, in the connection
dialog, click on Options, and under Connection Properties, make sure the
protocol explicitly states "TCP/IP".
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||I had gone to options>>connection properties and I set he network protocol to
tcp/ip. I couldn't set the connect to database b/c it wasn't connecting with
the server.
Anything else?
"Tracy McKibben" wrote:

> Trevor Murphy wrote:
> Does the connection error mention Named Pipes? If so, in the connection
> dialog, click on Options, and under Connection Properties, make sure the
> protocol explicitly states "TCP/IP".
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>

Connecting to a SQL Server 2005 over SSH using PuTTY

I'm having a problem connecting to my remote db from Management Studio, but
I
am able to create an ODBC connection from the Data Sources applet in the
Control Panel.
PuTTY is setup to convert localhost:21433 to 192.168.100.242:1433 (the
address of my remote db server).
When I specify localhost:21433, provide the username, password, and catalog
to the Data Sources applet it connects fine. I then can use that DSN in
Visual Studio 2005 as a connection to the db.
However, when I try localhost,21433 in Management Studio, it gives me the
default connection error which talks about not having remote access enabled.
Please give me a hand with this as it is very important that I be able to
use the Management Studio tools for my app development.
Thanks in advance.Trevor Murphy wrote:
> I'm having a problem connecting to my remote db from Management Studio, bu
t I
> am able to create an ODBC connection from the Data Sources applet in the
> Control Panel.
> PuTTY is setup to convert localhost:21433 to 192.168.100.242:1433 (the
> address of my remote db server).
> When I specify localhost:21433, provide the username, password, and catalo
g
> to the Data Sources applet it connects fine. I then can use that DSN in
> Visual Studio 2005 as a connection to the db.
> However, when I try localhost,21433 in Management Studio, it gives me the
> default connection error which talks about not having remote access enable
d.
> Please give me a hand with this as it is very important that I be able to
> use the Management Studio tools for my app development.
> Thanks in advance.
Does the connection error mention Named Pipes? If so, in the connection
dialog, click on Options, and under Connection Properties, make sure the
protocol explicitly states "TCP/IP".
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I had gone to options>>connection properties and I set he network protocol t
o
tcp/ip. I couldn't set the connect to database b/c it wasn't connecting with
the server.
Anything else?
"Tracy McKibben" wrote:

> Trevor Murphy wrote:
> Does the connection error mention Named Pipes? If so, in the connection
> dialog, click on Options, and under Connection Properties, make sure the
> protocol explicitly states "TCP/IP".
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||Trevor Murphy wrote:
> I had gone to options>>connection properties and I set he network protocol
to
> tcp/ip. I couldn't set the connect to database b/c it wasn't connecting wi
th
> the server.
> Anything else?
>
What happens if you telnet to localhost:21433 ?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hi Tracy,
This is what I got. Forgive my ignorance, but I haven't used telnet in
decades.
Microsoft Telnet> open localhost:21433
Connecting To localhost:21433...Could not open connection to the host, on
port 23: Connect failed
Microsoft Telnet>
"Tracy McKibben" wrote:

> Trevor Murphy wrote:
> What happens if you telnet to localhost:21433 ?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||Trevor Murphy wrote:
> Hi Tracy,
> This is what I got. Forgive my ignorance, but I haven't used telnet in
> decades.
> Microsoft Telnet> open localhost:21433
> Connecting To localhost:21433...Could not open connection to the host, on
> port 23: Connect failed
> Microsoft Telnet>
>
Try this at the command line:
telnet localhost 21433
If it connects, you should get a blank DOS window with a blinking
cursor. Otherwise, you'll get some sort of error message - I'm curious
what that error message will be.
Tracy McKibben
MCDBA
http://www.realsqlguy.com

Connecting Securely?

Hi,
I have SQL Server 2000 running on one box and IIS running on another box. I
am connecting to the SQL Server via ASP pages on the IIS box. My concern is
security -- currently I am using this kind of code to connect:
var setListings = Server.CreateObject("ADODB.Recordset");
setListings.ActiveConnection =
"Provider=SQLOLEDB.1;Password=PASSWORD;Persist Security Info=True;User
ID=USERID;Initial Catalog=tableName;Data Source=127.0.0.1"
My concern is that the username and password are being sent via plain text
from one box to the other.. Is this in fact the case? Is there another way
to make the connection? I think I could use Windows 2000 user accounts but
that would require trusted domains, etc. and neither box is a domain
controller (they are running at my ISP)
Thanks,
RichYou want to enable SSL for communication between the servers.
http://support.microsoft.com/defaul...kb;en-us;276553
-oj
http://www.rac4sql.net
"Richard Morey" <rwmorey71@.hotmail.com> wrote in message
news:ONWK0C4CEHA.2908@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have SQL Server 2000 running on one box and IIS running on another box.
I
> am connecting to the SQL Server via ASP pages on the IIS box. My concern
is
> security -- currently I am using this kind of code to connect:
> var setListings = Server.CreateObject("ADODB.Recordset");
> setListings.ActiveConnection =
> "Provider=SQLOLEDB.1;Password=PASSWORD;Persist Security Info=True;User
> ID=USERID;Initial Catalog=tableName;Data Source=127.0.0.1"
> My concern is that the username and password are being sent via plain text
> from one box to the other.. Is this in fact the case? Is there another way
> to make the connection? I think I could use Windows 2000 user accounts but
> that would require trusted domains, etc. and neither box is a domain
> controller (they are running at my ISP)
> Thanks,
> Rich
>
>|||Hi,
I have quickly glanced at the link you provided and will read it more
closely later.. Quick question -- we have SSL on the web server, not on the
SQL Server - will this still work?
Rich
"oj" <nospam_ojngo@.home.com> wrote in message
news:%230cwcK4CEHA.1128@.TK2MSFTNGP11.phx.gbl...
> You want to enable SSL for communication between the servers.
> http://support.microsoft.com/defaul...kb;en-us;276553
> --
> -oj
> http://www.rac4sql.net
>
> "Richard Morey" <rwmorey71@.hotmail.com> wrote in message
> news:ONWK0C4CEHA.2908@.TK2MSFTNGP09.phx.gbl...
box.
> I
> is
Server.CreateObject("ADODB.Recordset");
text
way
but
>|||SSL will have to be (at least) on sqlserver box for it to work.
-oj
http://www.rac4sql.net
"Richard Morey" <rwmorey71@.hotmail.com> wrote in message
news:%23fmWqq5CEHA.3344@.tk2msftngp13.phx.gbl...
> Hi,
> I have quickly glanced at the link you provided and will read it more
> closely later.. Quick question -- we have SSL on the web server, not on
the
> SQL Server - will this still work?
> Rich
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:%230cwcK4CEHA.1128@.TK2MSFTNGP11.phx.gbl...
> box.
concern
> Server.CreateObject("ADODB.Recordset");
> text
> way
> but
>

Connecting Remote sql server for Asp.net 2.0

Hi all,

I have an application in asp.net 2.0 and iam trying to connect database which is in remote server(Sql server 2000).But iam getting error as follows:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

i know this is because asp.net 2.0 try to connect sql serverexpress by default.i have removed sql server express from my machine,Still iam getting the same error..any body have an idea how to solve this ...

regards

anitha

Hi welcome to asp.net.

You don't have to remove sqlserver express ,it is OK to have both sqlserver 2000 and sqlserver express installed on you machine.

That error means if you are connecting to sqlserver 2005,this failure may be caused by the fact ......but you are not

First make sure your connection string is right,you can check this website:http://www.connectionstrings.com

If that is correctmake sure Named Pipes and TCP/IP network libraries are enabled for the SQL2000 instance and no firewall blocks the connection.

And you can take a look at this :http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=258082&SiteID=1