ODBC connection using NT authentication

I want to create an ODBC connection with windows NT authentication on two servers the domain are different and their operating
systems r also different.
(one is Windows 2K other is NT).
how can i have to go about if i have to do this.sorry i forgot to mention the version
im using SQL SERVER 7|||This should be doable as long as there is a trust relationship established between the NT domain and the W2K domain. Depending on your requirements, this might have to be a two-way trust.

Regards,

hmscott|||My $0.02 ...

I think you could do a 'pass-through' if you cant get the domains to trust eachother. Create a user on the sql server and create the same user with the same password on the other server and you should be able to connect via windows authentication. Is it a good practice? I would say No. But a work aroud if you can't have the domains trust each other.

Originally posted by hmscott
This should be doable as long as there is a trust relationship established between the NT domain and the W2K domain. Depending on your requirements, this might have to be a two-way trust.

Regards,

hmscott|||Hi,

Thanks for ur reply. My client is not beliveing tht we need trust relationship, can u please provide any link
or url where it is mentioned.
Waiting for ur reply

TIA

Originally posted by hmscott
This should be doable as long as there is a trust relationship established between the NT domain and the W2K domain. Depending on your requirements, this might have to be a two-way trust.

Regards,

hmscott|||It is very unlikely that you will get two servers in different domains (NT&W2k) working without setting up a trust between the two domains. Windows authentication uses a SID (security identifier) each computer and each user has a unique SID and the authentication should use the SID not the username. It is true to say that NT4 could be fooled depending on what service pack you used, but W2k with Active Directory will require a trust.

I recently upgraded a whole network of users from NT4 to W2k with AD in a different domain. I researched this and it will only work with a trust relationship as HMScott says. In our original plan we were going to use replication and migrate the users one by one, in the end we moved every9one ov

The way we get around such problems is to use a Role, we have one SQL username in the Role and have our application use that username. Granting ODBC connections may be quick and easy but it leaves you a bit exposed to other issues of Security & Support.

Imagine if this was not the case, any old hacker could access you databases.sql

odbc connection multi domain no trust

If you have one domain of application servers running win2000 and seperate
user domains with no trust relationships accessing sql databases on the
application domain what needs to be done rights wise and is this possible
without connectivity issues. Currently these servers are standalone not in a
domain and users can currenlty access this through local logon sql rights on
the stand alone servers. Thanks.
If there is no domain trust then you will either need to use SQL
authentication or create NT accounts on the SQL Server machines that mirror
the accounts that the users logon to their client machines with. The
accounts will have to have the same name and password. Using this method
you can use NT authentication to SQL Server.
Rand
This posting is provided "as is" with no warranties and confers no rights.

odbc connection multi domain no trust

If you have one domain of application servers running win2000 and seperate
user domains with no trust relationships accessing sql databases on the
application domain what needs to be done rights wise and is this possible
without connectivity issues. Currently these servers are standalone not in
a
domain and users can currenlty access this through local logon sql rights on
the stand alone servers. Thanks.If there is no domain trust then you will either need to use SQL
authentication or create NT accounts on the SQL Server machines that mirror
the accounts that the users logon to their client machines with. The
accounts will have to have the same name and password. Using this method
you can use NT authentication to SQL Server.
Rand
This posting is provided "as is" with no warranties and confers no rights.sql

ODBC and Enterprise Manager (still) don't show databases with users other than sa

I have several Win2000 servers running SQL Server 2000, SP2 (8.00.665)
and only one of them developed this problem. When trying to set up a
new ODBC setting using any other login than sa, it doesn't show any
databases besides the system db's. When logging in with Enterprise
manager (all other logins except sa), the Databases list shows 'No
items'. All logins work fine with Query Analyzer. I already recreated
missing guest accounts in some of the databases, but that didn't help.
I've also installed the latest MDAC (2.7 SP1) and after that didn't
correct the problem, I installed SP3a. It's still not working.
I'm thinking about reinstalling SQL Server, but my client doesn't like
the idea. So if anyone has any idea what might help, I'd be greatful.
Thank you!
br,
AnnaAnna
Firstly you need to have SQL SP3 if you have not applied the patch to stop
the SQL Slammer on the server.
Are you using ODBC/ Query Analyzer from the server or the client?
I am getting a few problems as well after install MDAC 2.71 which has
somehow deleted my ODBC drivers from the Drivers tab window.
Regards
Z
Is the SQL a named instance?
"Anna N." <amnikol@.hotmail.com> wrote in message
news:6e225598.0307160146.5fadd9f2@.posting.google.com...
> I have several Win2000 servers running SQL Server 2000, SP2 (8.00.665)
> and only one of them developed this problem. When trying to set up a
> new ODBC setting using any other login than sa, it doesn't show any
> databases besides the system db's. When logging in with Enterprise
> manager (all other logins except sa), the Databases list shows 'No
> items'. All logins work fine with Query Analyzer. I already recreated
> missing guest accounts in some of the databases, but that didn't help.
> I've also installed the latest MDAC (2.7 SP1) and after that didn't
> correct the problem, I installed SP3a. It's still not working.
> I'm thinking about reinstalling SQL Server, but my client doesn't like
> the idea. So if anyone has any idea what might help, I'd be greatful.
> Thank you!
>
> br,
> Anna|||FYI:
First, I would try determine if it is an Server or Client Problem. ( The
Server has both Client and Server DLLs on it.)
To see if it is an client problem try to make the ODBC from a machine
without the problem to the Server with the problem.
If the problem is NOT there then it is an client problem.
If the problem is there confirm it by making an ODBC connect to one of the
Good Servers from the same test client.
If it is an server problem, I have nothing to suggest.
( Note my company spent over 40 man hours on an "Server Problem" that
turned out to be an client DLL issuse in SQL SP3)
If an client problem.
First check the version of SQLSRV32.dll ; is the correct one.
Link to version of SQLSRV32.dll
http://support.microsoft.com/default.aspx?scid=http%3a%2f%2fsupport.microsoft.com%2fservicedesks%2ffileversion%2fdllinfo.asp&fp=1
Then, I would try running the component checker ( on the MDAC ).
Link to info on component checker
http://support.microsoft.com/default.aspx?scid=kb;EN-US;307255
Link to download componet checker
http://www.microsoft.com/downloads/details.aspx?FamilyId=8F0A8DF6-4A21-4B43-BF53-14332EF092C9&displaylang=en
Tim S
"Zenduce" <james@.zenduce.net> wrote in message
news:%238XHwp4SDHA.1664@.TK2MSFTNGP11.phx.gbl...
> Anna
> Firstly you need to have SQL SP3 if you have not applied the patch to
stop
> the SQL Slammer on the server.
> Are you using ODBC/ Query Analyzer from the server or the client?
> I am getting a few problems as well after install MDAC 2.71 which has
> somehow deleted my ODBC drivers from the Drivers tab window.
> Regards
> Z
>
> Is the SQL a named instance?
> "Anna N." <amnikol@.hotmail.com> wrote in message
> news:6e225598.0307160146.5fadd9f2@.posting.google.com...
> > I have several Win2000 servers running SQL Server 2000, SP2 (8.00.665)
> > and only one of them developed this problem. When trying to set up a
> > new ODBC setting using any other login than sa, it doesn't show any
> > databases besides the system db's. When logging in with Enterprise
> > manager (all other logins except sa), the Databases list shows 'No
> > items'. All logins work fine with Query Analyzer. I already recreated
> > missing guest accounts in some of the databases, but that didn't help.
> > I've also installed the latest MDAC (2.7 SP1) and after that didn't
> > correct the problem, I installed SP3a. It's still not working.
> >
> > I'm thinking about reinstalling SQL Server, but my client doesn't like
> > the idea. So if anyone has any idea what might help, I'd be greatful.
> > Thank you!
> >
> >
> > br,
> > Anna
>|||"Zenduce" <james@.zenduce.net> wrote in message news:<#8XHwp4SDHA.1664@.TK2MSFTNGP11.phx.gbl>...
> Firstly you need to have SQL SP3 if you have not applied the patch to stop
> the SQL Slammer on the server.
I already have SP3a installed, as you can see from my original post.
> Are you using ODBC/ Query Analyzer from the server or the client?
Several clients.
> I am getting a few problems as well after install MDAC 2.71 which has
> somehow deleted my ODBC drivers from the Drivers tab window.
This problem emerged BEFORE installing MDAC 2.71, as you can see from
my original post.
> Is the SQL a named instance?
No.
- Anna|||"Tim S" <stahta01@.juno.com> wrote in message news:<XamRa.4637$C71.307@.fe01.atl2.webusenet.com>...
> First, I would try determine if it is an Server or Client Problem. ( The
> Server has both Client and Server DLLs on it.)
It is most definitely a server problem. I wouldn't have posted a
question without making sure where the problem is exactly.
- Anna

ODBC

I go to install sql server 2000 in one of our servers, would like to
know if after the installation I lose connections ODBC that already I
possess using SQL Server 7If the database names and the servernames are the same ( like in an
upgrade ) the ODBC DSNs need not be changed. Otherwise you'll have to click
configure and reset the values.
--
- Anith
( Please reply to newsgroups only )

Obscure linked server error

Hello,

I've got 2 SQL servers in a test environment - one is 2000 and the other is MSDE and they are seperate machines. I have added the MSDE server as a linked server to my 2000 box by issuing the following command:

EXEC sp_addlinkedserver '192.168.1.108', N'SQL Server'

I can query the database using an openquery in a select statement like so:

select * from openquery([192.168.1.108], 'select * from remote_test.dbo.products')

but when I try a direct query like the following:

select * from [192.168.1.108].remote_test.dbo.products

I get the following error:

An error occurred while executing batch. Error message is: Processing of results from SQL Server failed because of an invalid multipart name "192.168.1.108.remote_test.dbo.products", the current limit of "4" is insufficient.

I can't seem to figure out anything about this error. Anyone have any ideas?

Thanks,

Jeff Balcerzak

What about choosing another name than the IP ;-) ?

Jens K. Suessmeyer.

http://www.sqlserver2005.de
--|||That does work if I specify the server name on my local network. If the production server is not going to be in the local network, would I create an alias to it with the public IP address?|||What about using an entry in the lmhost file to the outside IP?

Jens K. Suessmeyer.

http://www.sqlserver2005.de
|||I actually added an entry in hosts file and created an alias to my public IP to test. I physically moved my test server to a different part of my network so it is not visible to the lan and created a port forward on my router to direct wan traffic on 1433 to the test server. Now when I execute the sp_addlinked server with the server name, it seems to work fine. Thanks for your help.