I have a windows 98 pc trying to connect to a sql server running on Windows Server 2003 via a frame relay. The 98 pc will connect to the domain and it is able to ping the server. However, when I try to use my MS Access program that connects to the sql server, I get this error message:
Connection Failed
SqlState: '01000'
Sql ServerError: 11001
[Microsoft][ODBC Sql Server Driver][TCP/IP Sockets] Connection Open (Connect ()).
Connection Failed
SqlState: '08001'
Sql ServerError: 6
[Microsoft][ODBC Sql Server Driver][TCP/IP Sockets] Specified Sql server not found.
I have other pcs that connect to the Sql Server fine but they are located locally in the same building as the server. I've tried connecting through named pipes but for some reason, I get the same error. I have downloaded and installed the new MDAC drivers for the 98 pc. Any suggestions?Just a couple of things to check:
1. Are all the DSN names the same on all machines (are you using linked tables into MSAccess?) Does a DSN name exist on the PC?
2. If they are linked tables into MSAccess, when you linked the table in MSAccess, did you check the "Save Password".
3. Does the user have permissions to the tables in SQL Server? Is their loginID or their domain group set up for permissions to the database?
Hope any of these helps.|||Yes, the DSN names are the same, and the user name and password are the same. There are multiple users that use the "generic" username and password and it works fine for them. I looked into the linked tables idea and this is what happened. When I link the tables in Access, it worked. However, when I exited the program and went back into it, it did not work anymore. Now when I try to link the tables again, it will not let me and the program will not work and I get that error message again. Any other ideas?
Showing posts with label domain. Show all posts
Showing posts with label domain. Show all posts
Monday, March 26, 2012
Friday, March 23, 2012
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
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.
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
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
Subscribe to:
Posts (Atom)