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 to a Datacom DB data source

I recently installed SQL Server 2000 Reporting Services and connect to
a number of disparate data sources -- except a CA Datacom/DB
(mainframe) data source.
Any ideas on how to connect to the mainframe data so that it has the
look and feel of an ODBC database? And if so, what are the products
involved?
Thanks,
RBollinger
I'm using CA-Visual Express to hit Datacom through the Client ODBC Driver. It's a bit tricky with the authorities. You have to make sure they're set at the ODBC level if you want more than read-only access. We've not quite worked out the details on this yet. However, you can import any datacom table through the same ODBC driver using MS Access and perform all queries through there. (Not graceful, granted, but it does work!)
Good Luck,
rrowe.

Connecting to a Datacom DB data source

I recently installed SQL Server 2000 Reporting Services and connect to
a number of disparate data sources -- except a CA Datacom/DB
(mainframe) data source.
Any ideas on how to connect to the mainframe data so that it has the
look and feel of an ODBC database? And if so, what are the products
involved?
Thanks,
RBollingerI'm using CA-Visual Express to hit Datacom through the Client ODBC
Driver. It's a bit tricky with the authorities. You have to make sure
they're set at the ODBC level if you want more than read-only access.
We've not quite worked out the details on this yet. However, you can
import any datacom table through the same ODBC driver using MS Access
and perform all queries through there. (Not graceful, granted, but it
does work!)
Good Luck,
rrowe.
rrowe
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message535356.html