connecting to SQL Server 2000 from a VB.net app using ADO.net

Hi
I can connect from my app to sql server on the local lan, but I can't connect over the
Internet. I can't create a remote connection in Enterprise Manager. However, I can
ping the IP address of the server just fine.
The app uses the following connect string:
Provider=SQLOLEDB;User
ID=******;Password=******;Server=******;Database=* *****;Network Address=******
Where 'Network Address' = the IP address of the machine where SQL Server is
installed.
This connect string works great from any machine connected to the same lan as the
SQL Server machine. However, whenever I try to connect across the Internet (from my
home machine, using the exact same software and connect string), I take the
following error:
Client unable to establish connection ConnectionOpen(CreateFile()
Question 1: Does anybody have any suggestions as to why I can connect over the LAN
but not over the Internet? I suspect some networking thing, like a firewall on the
lan where I am trying to connect, but I am not a networking expert.
Question 2: Does anyone have any opinion about whether this is a valid DBIO
technique? Most databases that are accessed over the Internet have thin-client
interfaces implemented in front of them. I have never tried to do this from a Windows
fat-client, and I suspect very poor performance and excess resource utilization on
the server
Any help or article will be appriciated
In terms of connectivity issues over the Internet, firewall
issues would be my first guess. You may want to take a look
at the following article:
INF: TCP Ports Needed for Communication to SQL Server
Through a Firewall
http://support.microsoft.com/?id=287932
In terms of the application issues, it depends on the app.
The resource problems on the database server are most often
due to coding issues, not really what type of client is
used. Either can perform well or perform poorly depending on
how they are coded.
-Sue
On Thu, 15 Apr 2004 09:56:07 -0700, "Lisa Jones"
<anonymous@.discussions.microsoft.com> wrote:

>Hi
>I can connect from my app to sql server on the local lan, but I can't connect over the
>Internet. I can't create a remote connection in Enterprise Manager. However, I can
>ping the IP address of the server just fine.
>The app uses the following connect string:
>Provider=SQLOLEDB;User
>ID=******;Password=******;Server=******;Database= ******;Network Address=******
>Where 'Network Address' = the IP address of the machine where SQL Server is
>installed.
>This connect string works great from any machine connected to the same lan as the
>SQL Server machine. However, whenever I try to connect across the Internet (from my
>home machine, using the exact same software and connect string), I take the
>following error:
>Client unable to establish connection ConnectionOpen(CreateFile()
>Question 1: Does anybody have any suggestions as to why I can connect over the LAN
>but not over the Internet? I suspect some networking thing, like a firewall on the
>lan where I am trying to connect, but I am not a networking expert.
>Question 2: Does anyone have any opinion about whether this is a valid DBIO
>technique? Most databases that are accessed over the Internet have thin-client
>interfaces implemented in front of them. I have never tried to do this from a Windows
>fat-client, and I suspect very poor performance and excess resource utilization on
>the server
>Any help or article will be appriciated
sqlsql

connecting to SQL Server 2000 from a VB.net app using ADO.net

Hi
I can connect from my app to sql server on the local lan, but I can't connec
t over the
Internet. I can't create a remote connection in Enterprise Manager. However,
I can
ping the IP address of the server just fine.
The app uses the following connect string:
Provider=SQLOLEDB;User
ID=******;Password=******;Server=******;
Database=******;Network Address=****
**
Where 'Network Address' = the IP address of the machine where SQL Server is
installed.
This connect string works great from any machine connected to the same lan a
s the
SQL Server machine. However, whenever I try to connect across the Internet (
from my
home machine, using the exact same software and connect string), I take the
following error:
Client unable to establish connection ConnectionOpen(CreateFile()
Question 1: Does anybody have any suggestions as to why I can connect over t
he LAN
but not over the Internet? I suspect some networking thing, like a firewall
on the
lan where I am trying to connect, but I am not a networking expert.
Question 2: Does anyone have any opinion about whether this is a valid DBIO
technique? Most databases that are accessed over the Internet have thin-clie
nt
interfaces implemented in front of them. I have never tried to do this from
a Windows
fat-client, and I suspect very poor performance and excess resource utilizat
ion on
the server
Any help or article will be appriciatedIn terms of connectivity issues over the Internet, firewall
issues would be my first guess. You may want to take a look
at the following article:
INF: TCP Ports Needed for Communication to SQL Server
Through a Firewall
http://support.microsoft.com/?id=287932
In terms of the application issues, it depends on the app.
The resource problems on the database server are most often
due to coding issues, not really what type of client is
used. Either can perform well or perform poorly depending on
how they are coded.
-Sue
On Thu, 15 Apr 2004 09:56:07 -0700, "Lisa Jones"
<anonymous@.discussions.microsoft.com> wrote:

>Hi
>I can connect from my app to sql server on the local lan, but I can't conne
ct over the
>Internet. I can't create a remote connection in Enterprise Manager. However
, I can
>ping the IP address of the server just fine.
>The app uses the following connect string:
>Provider=SQLOLEDB;User
> ID=******;Password=******;Server=******;
Database=******;Network Address=***
***
>Where 'Network Address' = the IP address of the machine where SQL Server is
>installed.
>This connect string works great from any machine connected to the same lan
as the
>SQL Server machine. However, whenever I try to connect across the Internet
(from my
>home machine, using the exact same software and connect string), I take the
>following error:
>Client unable to establish connection ConnectionOpen(CreateFile()
>Question 1: Does anybody have any suggestions as to why I can connect over
the LAN
>but not over the Internet? I suspect some networking thing, like a firewall
on the
>lan where I am trying to connect, but I am not a networking expert.
>Question 2: Does anyone have any opinion about whether this is a valid DBIO
>technique? Most databases that are accessed over the Internet have thin-cli
ent
>interfaces implemented in front of them. I have never tried to do this from
a Windows
>fat-client, and I suspect very poor performance and excess resource utiliza
tion on
>the server
>Any help or article will be appriciated

Connecting to SQL Failed

I am trying to connect to SQL following the directions in Learn ASP.NET in 24 hours I am on page 332-334 where i try to create a Data base for the first time.

I am using a localhost configuration.

I get the following message

"Unable to connect to database server.

SQL does not exist or access denied.

ConnectionOpen(Connect())"

However I see that SQL server(SQLEXPRESS) and SQL server browser are both running and their start state is automatic

Hi,

You can reach SQLEXPRESS instance as ComputerName\SQLExpress

connecting to SQL DB through a firewall

Hi there!

I'm a bit new to all this, so please bear with me! :)

I've got a webserver in our DMZ and I'm trying to create an ODBC connection from that server to a db server within our firewall. When I try and connect, the following message appears:

Connection failed:
SQLState: '01000'
SQL Server Error: 10060
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen (Connect()),
Connection failed:
SQL State: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied

I'm at a bit of a loss as to what's going on, as we have an application on the webserver that connects to another SQL DB server within our firewall with no problem!

webserver:
OS - win2000 standard server sp4

db server:
OS - WinNT 4.0
SQL - 7.0

If anyone can help, it would be much appreciated!!

Cheers,

Ewan :)I'd recommend (so does MS) to have a VPN tunnel for intrasver communications, especially if they are on opposite sides of the firewall.

Connecting To Server

Hi,

As you know in SQL Server we must connect to a server to create , manage and execute databases. My problem is, I can't connect. I have searched the web for some information, they all say "write to server name your machine name to connect". I did so and get an error.

the message is ;
An error has occured 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)(Microsoft SQL Server,Error :53)

My pc is not connected to a server.

How can I make my pc act like a server so that i can connect to it.

Hi,

This is a usual problem that occurs whilst using SQL Server 2005.

You can resolve this issue by following steps...

Use Surface Area Configuration tool to manage your connection protocol Add SQL Server Service as an Exception in Windows Firewall Use MACHINE_NAME\INSTANCE_NAME to reduce conflicts.|||

firstly thanks for the advise, Now i have a proble in Surface Area Configuration tool.

when I click to surface area configuration for services and connections an error occurs.

it says.

TITLE: Surface Area Configuration

No SQL Server 2005 components were found on the specified computer. Either no components are installed, or you are not an administrator on this computer. (SQLSAC)

now how can i solve this question ?

|||

Welcome,

First, have you logged in as administrator? If not, then do so. If you are using Windows Vista, then even if you are logged in as an administrator, right click the Surface Area Configuration tool and say "Run As Administrator".

This should solve your problem.

I guess, there are no further issues related with this.

Lastly, if all fails, the genuine solution is - re-install If still you are facing problems, let me know.

Mayur Tendulkar

Microsoft Student Partner

|||

Have you installed a SQL Server Edition on your local computer?

|||

Thats a good question, you have to confirm what edition of SQL 2005 you have installed here.

http://www.sql-server-performance.com//faq/?f=143 too fyi.

|||

thanks to everyone tryin to help.

I have solved the problem

|||

Hi,

Its good to know that you have solved the problem.

But if you could post the exact cause and solution over here, then someday - somewhere, it might help others.

Mayur Tendulkar

Microsoft Student Partner

Connecting to Database on a Server

Hi,

I'm new to SQLExpress, and I need some help. I am trying to create a SQL database that will sit on a shared server in our organisation. I go into SSMSE and click on New Database which takes me to the New database screen. I now want to change the default path name to our server name, but when I click on the Locate Folder button (...), it only allows me to select folders from my Local drive. Is this a limitation of SQL Express, is there a way around this...?

Thanks in advance...

You will need to install the engine onto the server which you plan to use, then use the following MS Article to allow remote connections to the server. Then you should use the Management tool to connect to the new server and configure the application paths.

|||

Thanks Glenn,

Even if I do all that, I can't connect to any database except for the ones on my hard drive. I have even tried attaching databases in SSMSE and it only allows you to attach Local databases. There is nowhere where I can connect to a drive other than C.

Connecting to Analysis Services cubes from Reporting Services

Hi,
I have created cubes using Analysis Services. Could I please know how to create a data source to connect to those cubes in Reporting Services to generate reports out of them. When I choose to create a data source in Reporting Services, I am able to see options only to connect to Sql Server, ODBC and Oracle. I do not see an option like 'OLAP Services' to connect to cubes in Analysis Services. I would be happy if anyone could help by giving me the steps to connect to the cubes in Analysis Services and to generate report/pivot table out of it.
Thanks,
Raj.Information on the integration of Reporting Services (RS) 2000 and Analysis
Services (AS) 2000 is provided at:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql2k/html/olapasandrs.asp
It describes how to connect to AS 2000 cubes and use multidimensional data
in RS 2000. The data provider is OleDB provider for OLAP 8.0.
You might also want to check out some samples on parameterized MDX available
for download:
http://www.microsoft.com/downloads/details.aspx?FamilyID=f9b6e945-1f4c-4b7c-9c83-c6801f0576ff&DisplayLang=en
Note: The upcoming SQL 2005 Beta 2 will contain graphical MDX and DMX query
designers, which will work best against AS 2005 cubes, but they also support
AS 2000 cubes.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Raj" <Raj@.discussions.microsoft.com> wrote in message
news:66825BE3-5342-4C34-AD06-589B73491B01@.microsoft.com...
> Hi,
> I have created cubes using Analysis Services. Could I please know how to
create a data source to connect to those cubes in Reporting Services to
generate reports out of them. When I choose to create a data source in
Reporting Services, I am able to see options only to connect to Sql Server,
ODBC and Oracle. I do not see an option like 'OLAP Services' to connect to
cubes in Analysis Services. I would be happy if anyone could help by giving
me the steps to connect to the cubes in Analysis Services and to generate
report/pivot table out of it.
> Thanks,
> Raj.

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 Clients SQL server

I am not sure if its possible, hopefully it is. I would like to create a custom page for one of my clients to log into and access information from their SQL server. If I have all the connection information, i.e user id and password etc. Can this be done. I know how to connect to an SQL server locally. If anyone can give me a point in the right direction, it would be greatly appreciative.

If this is possible, I am looking at adding a button on this page to allow the client to transfer records that meet specific criteria in a column in their database into a designated database on my server.

Thanks for any help.If your server can access their SQL Server, sure. Ask them for the TCP/IP connection information, and if you can see their server, you should be able to pull it off.

The difference from what you may be doing locally, is that instead of server=(local), you'll likely have the IP address of their server, and you may be using Windows Authentication locally, but you'll use SQL security to connect to their machine.

Regards,

Xander

connecting SQLExpress & Visual C# 2005

Hi

I have started to create a databse using SQL Server Management Studio Express, just a few tables, one with data. I now want to creat a some windows forms to populate the tables. However when I try to use the Add New Data Source wizard, I get an error when I try to create the connection string, but I have managed to connect to a copy of AdventureWorks located in the same parent directory.

Error is :
Unable to open the physical file "...". Operating system error 32: "32(The process cannot access the file because it is being used by another process.)".
An attemp to attach an auto-named database for file ... failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.

As I can connect to AdventureWorks, I presume Windows thinks the file is open, but I have no idea why, how to check, or how to close it.

TIA

Graham

Now Sorted not quite sure what I did, but I have downloaded some updates today, and I did start by looking at the data in Adveture works before I opened my project

Connecting a stored procedure to another server

I created a new stored procedure on one server because this is the only
server we can create new stored procedures on, however, all of my select
statements in this procedures are on a different server. How do I execute
this stored procedure on the other server, database, table, and login?Create a REMOTE Server or LINK Server, which you may not be able to do. You
can setup a Linked server to run under the context of one account.
"Ryan D" <RyanD@.discussions.microsoft.com> wrote in message
news:C749A1D6-F81F-4F50-8CDA-6681AF057BCD@.microsoft.com...
>I created a new stored procedure on one server because this is the only
> server we can create new stored procedures on, however, all of my select
> statements in this procedures are on a different server. How do I execute
> this stored procedure on the other server, database, table, and login?
>|||Andy,
I need the syntax for this please. Do you mean to use the
sp_addlinkedserver command? And then do I use the USE statement, followed b
y
the query?
"Andy Wilbourn" wrote:

> Create a REMOTE Server or LINK Server, which you may not be able to do. Yo
u
> can setup a Linked server to run under the context of one account.
> "Ryan D" <RyanD@.discussions.microsoft.com> wrote in message
> news:C749A1D6-F81F-4F50-8CDA-6681AF057BCD@.microsoft.com...
>
>|||Off the top of my head:
1. create a linked server.
2. change your select statements to have fully qualified names.
for example,
select colA, colB
from MyLinkServer.MyDatabase.dbo.MyTable
if you need to execute a stored procedure that exists on another server or
dynamic sql and it should run on that other server, exec
MyLinkServer.master.dbo.sp_executesql MySPName/@.SQL
Hope that helps,
Joe
"Ryan D" wrote:

> I created a new stored procedure on one server because this is the only
> server we can create new stored procedures on, however, all of my select
> statements in this procedures are on a different server. How do I execute
> this stored procedure on the other server, database, table, and login?
>

Connect to SQL2000 & SQL 2005

Our current program use ADO to connect oto SQL2000 and run fine.
We are planning to migrate to SQL2005.
When we clean install the SQL2005, create the database, set compatibility
level to 80 and generate the db structure, and migrate data.
When everything is done, we try to use our program to connect to SQL2005
database and find the connection fail.
Even when we use sa as login user and still fail to connect.
Is there any different in connection for SQL2000 & SQL2005?
I remember I have tried upgrade SQL2000 to SQL2005 before and the connection
had no problem to sql2005.
Is there something I forgot to set?
KanAm Tue, 29 Aug 2006 17:38:51 +0800 schrieb Ivan:

> Our current program use ADO to connect oto SQL2000 and run fine.
> We are planning to migrate to SQL2005.
> When we clean install the SQL2005, create the database, set compatibility
> level to 80 and generate the db structure, and migrate data.
> When everything is done, we try to use our program to connect to SQL2005
> database and find the connection fail.
> Even when we use sa as login user and still fail to connect.
> Is there any different in connection for SQL2000 & SQL2005?
> I remember I have tried upgrade SQL2000 to SQL2005 before and the connecti
on
> had no problem to sql2005.
> Is there something I forgot to set?
> Kan
If you did a standard installation then SQL2005 uses the named instance
SQLExpress wich you have to use in your connect string.
If your SQL2005 runs on the same machine as your SQL2000 then maybe SQL2005
listen on another port than the standard port.
And have you allowed remote access in SQL2005?
bye, Helmut|||No, MDAC will work fine with the SQL Server 2005 instance. Although you
can=B4t use some of the new cool features its compatible. Which error do
you get ? Is the SQL Server 2k5 located on the same machine as the 2k
instance ?
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--

Connect to SQL 6.5 from Win XP Pro

I need to create a system DSN SQL connection (Data Source) on my machine to
a server that is a domain controller in a different domain in preparation
for a C# program I'm writing. It is running NT 4.0 server with SQL 6.5 SP6.
I have an account on that domain but I can't get authenticated even though I
have administrative privileges and we have a trusted connection between the
two domains. What am I doing wrong?
thanks
chuck
Charles,
Check the SQL 6.5 Servers authentication mode. In 6.5 it can be set to
Standard, Integrated, or Mixed. Authentication using trusted connections
will fail if it's set to Standard.
Jon Jahren
"Charles MacLean" <charlesmaclean@.sbcglobal.net> wrote in message
news:HjQkd.7644$L92.1112@.newssvr16.news.prodigy.co m...
> I need to create a system DSN SQL connection (Data Source) on my machine
to
> a server that is a domain controller in a different domain in preparation
> for a C# program I'm writing. It is running NT 4.0 server with SQL 6.5
SP6.
> I have an account on that domain but I can't get authenticated even though
I
> have administrative privileges and we have a trusted connection between
the
> two domains. What am I doing wrong?
> thanks
> chuck
>
|||If by C# program, you mean a managed program using datasets, datareaders and
the like; I doubt that you will be able to do so for SQL Server 6.5; as the
..NET environment doesn't offer support for ODBC or OLEDB drivers version 2.5
and less. (I'm not sure about the exact number version, however SQL 6.5 is
quite probably older than the minimum requirement for an SQL-Server OLEDB
driver.)
However, if you intention is to use ADO and interoperability, then of course
you will have no problem.
S. L.
"Charles MacLean" <charlesmaclean@.sbcglobal.net> wrote in message
news:HjQkd.7644$L92.1112@.newssvr16.news.prodigy.co m...
>I need to create a system DSN SQL connection (Data Source) on my machine to
>a server that is a domain controller in a different domain in preparation
>for a C# program I'm writing. It is running NT 4.0 server with SQL 6.5 SP6.
>I have an account on that domain but I can't get authenticated even though
>I have administrative privileges and we have a trusted connection between
>the two domains. What am I doing wrong?
> thanks
> chuck
>
|||Oups!
After verification, I'm wrong. The framework 1.1 now allows connection to
ODBC and SQL-Server 6.5. See:
http://www.able-consulting.com/dotne...anagedProvider
S. L.
"Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)>
wrote in message news:ejszvxayEHA.2540@.TK2MSFTNGP09.phx.gbl...
> If by C# program, you mean a managed program using datasets, datareaders
> and the like; I doubt that you will be able to do so for SQL Server 6.5;
> as the .NET environment doesn't offer support for ODBC or OLEDB drivers
> version 2.5 and less. (I'm not sure about the exact number version,
> however SQL 6.5 is quite probably older than the minimum requirement for
> an SQL-Server OLEDB driver.)
> However, if you intention is to use ADO and interoperability, then of
> course you will have no problem.
> S. L.
> "Charles MacLean" <charlesmaclean@.sbcglobal.net> wrote in message
> news:HjQkd.7644$L92.1112@.newssvr16.news.prodigy.co m...
>

Connect to SQL 6.5 from Win XP Pro

I need to create a system DSN SQL connection (Data Source) on my machine to
a server that is a domain controller in a different domain in preparation
for a C# program I'm writing. It is running NT 4.0 server with SQL 6.5 SP6.
I have an account on that domain but I can't get authenticated even though I
have administrative privileges and we have a trusted connection between the
two domains. What am I doing wrong?
thanks
chuckCharles,
Check the SQL 6.5 Servers authentication mode. In 6.5 it can be set to
Standard, Integrated, or Mixed. Authentication using trusted connections
will fail if it's set to Standard.
Jon Jahren
"Charles MacLean" <charlesmaclean@.sbcglobal.net> wrote in message
news:HjQkd.7644$L92.1112@.newssvr16.news.prodigy.com...
> I need to create a system DSN SQL connection (Data Source) on my machine
to
> a server that is a domain controller in a different domain in preparation
> for a C# program I'm writing. It is running NT 4.0 server with SQL 6.5
SP6.
> I have an account on that domain but I can't get authenticated even though
I
> have administrative privileges and we have a trusted connection between
the
> two domains. What am I doing wrong?
> thanks
> chuck
>|||If by C# program, you mean a managed program using datasets, datareaders and
the like; I doubt that you will be able to do so for SQL Server 6.5; as the
.NET environment doesn't offer support for ODBC or OLEDB drivers version 2.
5
and less. (I'm not sure about the exact number version, however SQL 6.5 is
quite probably older than the minimum requirement for an SQL-Server OLEDB
driver.)
However, if you intention is to use ADO and interoperability, then of course
you will have no problem.
S. L.
"Charles MacLean" <charlesmaclean@.sbcglobal.net> wrote in message
news:HjQkd.7644$L92.1112@.newssvr16.news.prodigy.com...
>I need to create a system DSN SQL connection (Data Source) on my machine to
>a server that is a domain controller in a different domain in preparation
>for a C# program I'm writing. It is running NT 4.0 server with SQL 6.5 SP6.
>I have an account on that domain but I can't get authenticated even though
>I have administrative privileges and we have a trusted connection between
>the two domains. What am I doing wrong?
> thanks
> chuck
>|||Oups!
After verification, I'm wrong. The framework 1.1 now allows connection to
ODBC and SQL-Server 6.5. See:
r" target="_blank">http://www.able-consulting.com/dotn...rovide
r
S. L.
"Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)>
wrote in message news:ejszvxayEHA.2540@.TK2MSFTNGP09.phx.gbl...
> If by C# program, you mean a managed program using datasets, datareaders
> and the like; I doubt that you will be able to do so for SQL Server 6.5;
> as the .NET environment doesn't offer support for ODBC or OLEDB drivers
> version 2.5 and less. (I'm not sure about the exact number version,
> however SQL 6.5 is quite probably older than the minimum requirement for
> an SQL-Server OLEDB driver.)
> However, if you intention is to use ADO and interoperability, then of
> course you will have no problem.
> S. L.
> "Charles MacLean" <charlesmaclean@.sbcglobal.net> wrote in message
> news:HjQkd.7644$L92.1112@.newssvr16.news.prodigy.com...
>