Connecting to SQL dbfs with existing code

No need to setup the web server as a primary domain
controller for the SQL Server connectivity to work.
After you configured the system DSN on the web server, did
you test the DSN as the very last step of setting up the
DSN? If yes, what error message did you get?
Linchi

quote:

---

>--Original Message--
>We recently moved our Access databases to SQL and are
>trying to get our pages to open the connections to the
>server. I've set the system DSNs on the server as needed.
>However, no connections are made. After reviewing several
>books, microsoft.com, etc...I'm severely frustrated. The
>only thing I can think that would possibly be an issue is
>that our webserver (Win2003) is not setup as a Primary
>Domain Server and we have to connect via http.
>Any suggestions are appreciated. THANKS!
>.
>

---

The test was completed successfully. That's what is perplexing.
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!|||Does the connection actually hit SQL Server?
Enable auditing for failed logins on SQL , then stop n start MSSQLServer
service.
Check the SQL Errorlogs after the failed connection attempt.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.sqlsql

Connecting to SQL dbfs with existing code

We recently moved our Access databases to SQL and are
trying to get our pages to open the connections to the
server. I've set the system DSNs on the server as needed.
However, no connections are made. After reviewing several
books, microsoft.com, etc...I'm severely frustrated. The
only thing I can think that would possibly be an issue is
that our webserver (Win2003) is not setup as a Primary
Domain Server and we have to connect via http.
Any suggestions are appreciated. THANKS!Does the System DSN connect if you Test it from the IIS server?
If not what is the OS error returned?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

connecting to MSDE using SSPI

Please advise: I have created a simple ASPX page to test if I can connect to MSDE on a Server 2003 system. The connection string that works ok is:

server=WS1;database=northwind;integrated security=false;user id=sa;password=xxx;

but the string that does not work is:

server=WS1;database=northwind;integrated security=SSPI;

which is the string I would like to use for normal web access. This string works fine on my development system (where I use XP Pro and IIS 5.1)

In IIS6 on the "production server" the directory security on the virtual dir is set to allow anonymous access, using user IUSR_WS1 (where WS1 is the name of the system) and to integrated security.

Please help! Thank you

John BI forgot to say the error message I am getting is:

login failed for user 'NTAUTHORITY\NETWORK SERVICE'|||There is a KB for this problem:PRB: "Login Failed" Error Message When You Create a Trusted Data Connection from ASP.NET to SQL Server. See if any of the 3 suggested Resolutions work for you.

To me, the 3rd suggestion seems to be the best course of action. And taking that further, what seems to make the most sense is to add a new database role called "webuser" or something similar, and then add the NT AUTHORITY\NETWORK SERVICE user to that role. This will give you more flexibility if the web app moves to a Windows 2000 machine -- you would just be able to add the ASPNET account as another member of that webuser role.

Terri|||Thank you for your reply. I looked at the article, but I regret to say it does not make much sense to me at this stage. I have bought the MSDE Admin tool to administer MSDE, or could use the osql tool, but am not clear how to:

a. add a new database role (is this adding a "normal" user group)? I dont see any reference to a "database role".

b. add the NTAUTHORITY\NETWORK SERVICE user to that role. I have looked at the list of users and there is no such name. I must be looking in the wrong place.

Excuse my ignorance!

TIA

John B|||You should downloadSQL Server 2000 Books Online. This is a huge download but an essential reference.

I have to admit, I am confused on this issue. I have now come across an article right on this siteRunning ASP.NET 1.1 with IIS 6.0, and part of it covers supporting integrated authentication with SQL Server. The suggestion I gave you was based on something I read elsewhere that seemed to make sense.

Further information on the path I suggested:

The system stored procedure to add a database role is sp_addrole. You'd use it like this:

EXEC sp_addrole 'webuser'

The system stored procedure to add a security account for a Windows user to the current database and enable it to be granted permissions to perform activities in the database is sp_grantdbaccess.

EXEC sp_grantdbaccess 'NT AUTHORITY\NETWORK SERVICE', 'Network Service'

The system stored procedure to add a security account as a member of an existing database role in the current database is sp_addrolemember.

EXEC sp_addrolemember 'webuser', 'Network Service'

Terri|||Thank you. The article you suggested in the last post is very helpful. I have now solved the problem, thanks to an article I found www.cgnit.com/resources/ntauthority_networkservice_error.html

which hits it bang on the nose, and may be useful to others.

It seems to me that all the books, and many of the forums suggest that when you run an ASP.NET app and use anonymous access, the system uses the identity mcxxx\aspnet (where mcxxx is the domain or machine no). But what I have found so far is that under Server 2003, the identity assumed is the mysterious user NTAUTHORITY\NETWORKSERVICE which is NOT found in the list of users, but is apparently a member of the IIS_WPG group, so configuring this group to access the database solves the problem and allows an anonymous user to access records according to the permissions set within MSDE or SQL Server.

Can anyone confirm this is true? Is the ASPNET user in fact NEVER used in Server 2003, but only in W2000 or XP?|||Yes, I can confirm that. I ran into this today, setting up ibuyspy on a Windows2003 server. Here's the quote I found in the machine.config file:
When ASP.NET is running under IIS 6 in native mode, the IIS 6 process model is
used and settings in this section are ignored. Please use the IIS administrative
UI to configure things like process identity and cycling for the IIS
worker process for the desired application

I went ahead and added the IIS_WPG to access the DB I cared about, but you could also setup your own IIS6 AppPool with seperate identity information.

/Brad|||

I cannot but say, its a great thread !!

regards

connecting to MSDE on Windows 2003 SBS Server

I have an application (Point of Sale System) that utilizes a MSDE
database. The server came loaded with MSDE instances already and I
installed one for the POS System. The client PCs can see the other 3
MSDE instances, but cannot see the one I installed. Any ideas on how
the new instance can appear on the network. The new instance was not
named. The other three were named instances of MSDE.
hi,
auschnet@.gmail.com wrote:
> I have an application (Point of Sale System) that utilizes a MSDE
> database. The server came loaded with MSDE instances already and I
> installed one for the POS System. The client PCs can see the other 3
> MSDE instances, but cannot see the one I installed. Any ideas on how
> the new instance can appear on the network. The new instance was not
> named. The other three were named instances of MSDE.
please verify the required/desired network protocols are enabled... MSDE
installs by default disabling them and you can override this behavior
providing the
DISABLENETWORKPROTOCOLS=0
parameter to the setup.exe boostrap installer, or later, at run time, using
the Server Network Utility (svrnetcn.exe) and enabling the preferred network
protocol..
additionally, WinXP sp2 ships with a built-in Firewall that's enabled by
default, preventing network connections to... if this is a case, you have to
specify an exception for the service or for the MSDE used port, usually
specifying a subnet or individual remot IP addreses to restrict
connections...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

connecting to an SQL2005 Server

Hi

I am trying to upgrade a system from SQL 2000 to SQL2005.

I have installed the Server on a PC with Win XP SP2. Using another PC (also Win XP SP2) on the LAN I need to ODBC to the Server.

The Server is NOT the default instance.

I cannot connect via ODBC from the Client PC. This all worked fine with SQL 2000.

As a test I also tried a fresh install of SQL2005 where it was the default instance, this worked fine.

SO the problem is when you have multiple instances.

What do I have to do to sort it out?

Cheers

Eugene

Hi,

What is a error message !? Untill you provide error message we cannot suggest you answer.

Hemantgiri S. Goswami

|||

The error is

Cannot connect to Fred\Fredsql

SQL server does not allow remote connections etc, SQL error 10060

I have used the Surface Area program and Allow remote connections is ticked

Cheers

Eugene

|||Did you had a look in the surface area for this particular instance ? These settings are configured per instance and therefore if you enabled remote connections for the default instance, it does not mean that it is enabled for the named instance as well.

HTH, jens K. Suessmeyer.

http://www.sqlserver2005.de
|||

There are three things that you need to check for...

1) Insure remote connections is enabled for your database instance via the Surface Area Configuration tool for the named instance you are using. By default, SQL Express and DEV SKU has this disabled. Based on the error message posted, this seems to be the issue.

2) Since you are using a non-default (named) instance, this requires that the SQL Browser service to be configured and running properly.

3) Also on Windows XP SP2, you need to insure the firewall exceptions are set up properly. Here is a link with information on how to do this...

http://support.microsoft.com/default.aspx/kb/841249

Hope this helps,

Tom

This posting is provided AS IS with no warranties, and confers no rights.

Connecting SQL Server 2000 to legacy (AS/400) systems in a real time view?

Has anyone used SQL Server 2000 to attempt to get a real time view of a AS/400 system? Can you do it thru setting up a Linked Server?
Thanks,
Warren
Thanks Sue I will try this and let you know!
Thanks Again,
Warren

Connecting SQL Server 2000 to legacy (AS/400) systems in a real time view?

Has anyone used SQL Server 2000 to attempt to get a real time view of a AS/4
00 system? Can you do it thru setting up a Linked Server?
Thanks,
WarrenYes and yes.
Install Client Access on the SQL Server box and the
configure the linked server. For data source, use the IP
address of the AS400. For provider string, you need to
include the library you are using, connect timeout setting
and code page. There is some documentation for the settings
in the Client Access help files. You'd set the provider
string somewhat like:
InitCat=YourLibrary;CCSID=37;PCCodePage=
1252;
Data Source=xxx.xxx.xxx.xxx
Settings will depend on how your AS400 is configured. Again,
the Client Access help files have information on the
necessary connection string settings.
-Sue
On Tue, 6 Apr 2004 07:51:06 -0700, Warren
<anonymous@.discussions.microsoft.com> wrote:

>Has anyone used SQL Server 2000 to attempt to get a real time view of a AS/
400 system? Can you do it thru setting up a Linked Server?
>Thanks,
>Warren|||Thanks Sue I will try this and let you know!
Thanks Again,
Warren

Connecting SQL server 2000 from different domain.

Please help to connect SQL server 2000 on different domain.

Please correct if I m wrong.

System details as follows

Client

Domain : DomainA

System: System1

IP Address : 10.10.225.19

SQL server 2000 installed

SQL Server

Domain : DomainB

System: System2

IP Address : 10.108.22.19

SQl Server : System2\inst2 ( My database is under inst2 instance)

SQL login : TestUser1

Password : Users123

I have Opened firewall port to access 10.108.22.19 from 10.10.225.19

While connecting the SQL server “System2\inst2” from the client machine enterprise manager with the SQL authentication, I am getting error Login failed for user “TestUser1”

And I have noticed in the SQL server log the login attempt shows under System2 default instance ( no instance). Actually I want to connect system2\inst2.

Please let me know the steps to connect.

Thanks in advance.

For named instance, you also need to open UDP port 1434 for firewall on 10.108.22.19(the server). This is requried to find named instances. You said "default instance (no instance)", which errorlog were you checking?|||

Thanks for your reply,

I got solution and i am able to connect all my SQL servers from my domain.

It is a firewall issue , buy default they opened for 1433 it is goes to Default instance , but i need to connect a different SQL server instance.

then i opened firewall for that port it is connecting .

Thanks

CONNECTING SQL 2005 TO SYSTEM DNS ODBC?

Hi

I have a server with SQL 2005 and I have second server with spesial database program on it from IBM and I have installed a spesial ODBC DRIVER from IBM so I can make a connection in system dns.

On my server 1 where I have the sql 2005 I have made a connection in system dns.

HOW CAN I TELL SQL 2005 TO CONNECT TO MY CONNECTION AND GET DATA FROM DER?

It's DSN rather than DNS.

Please check this page for connection string using DSN: http://www.connectionstrings.com/?carrier=dsn

CONNECTING SQL 2005 TO SYSTEM DNS ODBC?

Hi

I have a server with SQL 2005 and I have second server with spesial database program on it from IBM and I have installed a spesial ODBC DRIVER from IBM so I can make a connection in system dns.

On my server 1 where I have the sql 2005 I have made a connection in system dns.

HOW CAN I TELL SQL 2005 TO CONNECT TO MY CONNECTION AND GET DATA FROM DER?

It's DSN rather than DNS.

Please check this page for connection string using DSN: http://www.connectionstrings.com/?carrier=dsn

Connecting from outside world

Hello,
I have just set up SQL server on our system.
I would like to be able to connect from accross the internet, like I can
with exchange. (Using EM)
What do I have to do in order to do this?
Many thanks,
NEIL
Take a look at our Product ISA Server. You can use this to publish your
SQL Server.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||"Neil Jarman" <neil@.tNOiSPAMvPLEASEy.co.uk> wrote in message
news:cmtfbd$qi5$1$8302bc10@.news.demon.co.uk...
> I have just set up SQL server on our system.
> I would like to be able to connect from accross the internet, like I can
> with exchange. (Using EM)
> What do I have to do in order to do this?
The most efficient way would be a server (or desktop) that you could run
remote desktop with a copy of EM tools. In this way the MMC is local to SQL
Server and screen and keyboard updates are sent over the WAN. I'd recommend
a VPN solution for connectivity to the remote device.
Steve
|||Mr. Thompson...perhaps you can help me. I have set up SQL server 2000 on a
dual processor machine in a WAN/LAN environment. After several hours of being
"idle", SQL server begins transmitting "Chatter" accross both the LAN and
WAN, flooding the router and bringing the network to its knees. Subsequent
pings either time out or are finally successful yet at very high ms counts.
I also have SQL server 2000 running in a single processor environment where
this is not an issue.
Have you encountered this before? Can you offer any suggestion as to how to
address this problem?
Thanks,
Steve S
"Steve Thompson" wrote:

> "Neil Jarman" <neil@.tNOiSPAMvPLEASEy.co.uk> wrote in message
> news:cmtfbd$qi5$1$8302bc10@.news.demon.co.uk...
> The most efficient way would be a server (or desktop) that you could run
> remote desktop with a copy of EM tools. In this way the MMC is local to SQL
> Server and screen and keyboard updates are sent over the WAN. I'd recommend
> a VPN solution for connectivity to the remote device.
> Steve
>
>
|||"Steve S" <SteveS@.discussions.microsoft.com> wrote in message
news:504D0B59-2D64-4FC1-8D72-CCD724E78B7B@.microsoft.com...
> Mr. Thompson...perhaps you can help me. I have set up SQL server 2000 on a
> dual processor machine in a WAN/LAN environment. After several hours of
being
> "idle", SQL server begins transmitting "Chatter" accross both the LAN and
> WAN, flooding the router and bringing the network to its knees. Subsequent
> pings either time out or are finally successful yet at very high ms
counts.
> I also have SQL server 2000 running in a single processor environment
where
> this is not an issue.
> Have you encountered this before? Can you offer any suggestion as to how
to
> address this problem?
Hi Steve,
That is not normal activity -- have your scanned your server for a virus,
such as the blaster virus?
Steve

Connecting from outside world

Hello,
I have just set up SQL server on our system.
I would like to be able to connect from accross the internet, like I can
with exchange. (Using EM)
What do I have to do in order to do this?
Many thanks,
NEILTake a look at our Product ISA Server. You can use this to publish your
SQL Server.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||"Neil Jarman" <neil@.tNOiSPAMvPLEASEy.co.uk> wrote in message
news:cmtfbd$qi5$1$8302bc10@.news.demon.co.uk...
> I have just set up SQL server on our system.
> I would like to be able to connect from accross the internet, like I can
> with exchange. (Using EM)
> What do I have to do in order to do this?
The most efficient way would be a server (or desktop) that you could run
remote desktop with a copy of EM tools. In this way the MMC is local to SQL
Server and screen and keyboard updates are sent over the WAN. I'd recommend
a VPN solution for connectivity to the remote device.
Steve|||Mr. Thompson...perhaps you can help me. I have set up SQL server 2000 on a
dual processor machine in a WAN/LAN environment. After several hours of bein
g
"idle", SQL server begins transmitting "Chatter" accross both the LAN and
WAN, flooding the router and bringing the network to its knees. Subsequent
pings either time out or are finally successful yet at very high ms counts.
I also have SQL server 2000 running in a single processor environment where
this is not an issue.
Have you encountered this before? Can you offer any suggestion as to how to
address this problem?
Thanks,
Steve S
"Steve Thompson" wrote:

> "Neil Jarman" <neil@.tNOiSPAMvPLEASEy.co.uk> wrote in message
> news:cmtfbd$qi5$1$8302bc10@.news.demon.co.uk...
> The most efficient way would be a server (or desktop) that you could run
> remote desktop with a copy of EM tools. In this way the MMC is local to SQ
L
> Server and screen and keyboard updates are sent over the WAN. I'd recommen
d
> a VPN solution for connectivity to the remote device.
> Steve
>
>|||"Steve S" <SteveS@.discussions.microsoft.com> wrote in message
news:504D0B59-2D64-4FC1-8D72-CCD724E78B7B@.microsoft.com...
> Mr. Thompson...perhaps you can help me. I have set up SQL server 2000 on a
> dual processor machine in a WAN/LAN environment. After several hours of
being
> "idle", SQL server begins transmitting "Chatter" accross both the LAN and
> WAN, flooding the router and bringing the network to its knees. Subsequent
> pings either time out or are finally successful yet at very high ms
counts.
> I also have SQL server 2000 running in a single processor environment
where
> this is not an issue.
> Have you encountered this before? Can you offer any suggestion as to how
to
> address this problem?
Hi Steve,
That is not normal activity -- have your scanned your server for a virus,
such as the blaster virus'
Steve

Connecting ASP.NET to SQLServer,Somebody,Please!

It is now 3 months that we are trying to connect ASP.NET to a SQLServer located on another system.
However we act,we get a fatal error.
We need someone to explain the way of connecting to SQLServer step by step from either VisualStudio.NET or FrontPage 2003.
Our goal is to retrieve records from SQLServer and display them in ASP.NET pages,edit them,and return them to SQLServer.
Thanx in advance.
Mohammad,
in Server Explorer, register the other sql server. Once it is registered, navigate to a table on this server and drag and drop a small table from this server to an aspx page. This will create a sqldataconnection and sqldataadapter. Right-click the sqldata
adapter and select generate dataset. This dataset now needs matching to eg a datagrid, using the dataadpater.fill method and datagrid.bind method. There are loads of examples of this type of thing on the net and in books. Which part in particular do you h
ave problems with? Making the grid editable is more tricky as you'll need to use command objects. If you email me on my address here, I'll post you an example you can use against the northwind database to see how it works.
HTH,
Paul Ibison

Connecting ASP.NET to SQLServer,Somebody,Please!

It is now 3 months that we are trying to connect ASP.NET to a SQLServer loca
ted on another system.
However we act,we get a fatal error.
We need someone to explain the way of connecting to SQLServer step by step f
rom either VisualStudio.NET or FrontPage 2003.
Our goal is to retrieve records from SQLServer and display them in ASP.NET p
ages,edit them,and return them to SQLServer.
Thanx in advance.Mohammad,
in Server Explorer, register the other sql server. Once it is registered, na
vigate to a table on this server and drag and drop a small table from this s
erver to an aspx page. This will create a sqldataconnection and sqldataadapt
er. Right-click the sqldata
adapter and select generate dataset. This dataset now needs matching to eg a
datagrid, using the dataadpater.fill method and datagrid.bind method. There
are loads of examples of this type of thing on the net and in books. Which
part in particular do you h
ave problems with? Making the grid editable is more tricky as you'll need to
use command objects. If you email me on my address here, I'll post you an e
xample you can use against the northwind database to see how it works.
HTH,
Paul Ibison

connect to sqlserver by sqlconnection from windows CE 5.0

Currently I cannot connect to a database, I got the system.exception “PlatformNotSupportedExcoption”. This database is Polish (COLLATE Polish_CI_AS), when I collate this database to latin general it works fine. I connect by using the system.data.sqlclient.sqlconnection, as far as I can see I cannot set the locale identifier here… What can I do?

Thanks for your help!

regards, Jan

You'd need a device with Polish locale support or you would need to change database collation.

|||

thx.

Is it possible to update only the localized sqlce components at the device?

Thanks!

Connect to SQL Server

Hi!
I tried to connect to SQL Server database by the following code:

Private Sub Page_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load

Try

Dim con As New SqlConnection("Persist Security Info=False;Integrated Security=SSPI;database=northwind;server=myServerName;Connect Timeout=30")
con.Open()

Catch ex As Exception

Response.Write(ex.Message)

End Try

End Sub

And this error occured:

Login failed for user 'NT AUTHORITY\NETWORK SERVICE'

Please tell me the reason.

Regards!
M.Sadegh Samiei

checkwww.connectionstrings.com for the right connection string.

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...
>