hi ,
i must to connect sql server that located in one domain from client that located the other domain.
please help me.
thanks alot:confused: :confused:if you are using server side authentication this is NOT a problem. Just define the login and access to the needed DB and you are ready to go.
If you are using NT authentication, you will need to have the user's domain trust the sql server's domain. I probably have that backwards but your network admin will know how to set the trusts up. After that you can define the login and continue as normal.
Can you give a little more detail about your problem?|||hi
I must connect to sql server by ODBC and when I define DSN i visited sql server in list but i meet this message"connection fail"
please guide me.
Showing posts with label domain. Show all posts
Showing posts with label domain. Show all posts
Sunday, 25 March 2012
Thursday, 22 March 2012
Connect to named instance on different domain
I am having trouble connecting to a named instance on a different domain. For example, I am in the domain mydomain.com, the machine is in ops.mydomain.com.
In Query Analyzer I have tried to connect (without success) to:
machinename\instance
machinename
i.p. address
i.p. address\instance
Within the same domain I can successfully connect to
machinename\instance
Any ideas? Also, this machine is part of a cluster...not sure if that matters. I have full permissions to connect to this machine.
ThanksNever mind...the instance was setup to a port different than 1433. We changed it to 1433, rebooted the server, and now I can connect.
One issue though: I can only connect by specifying the i.p. address, i.e.
255.255.255.0\instancename
Using the server name or setting up an alias doesn't seem to work.
Originally posted by banderson
I am having trouble connecting to a named instance on a different domain. For example, I am in the domain mydomain.com, the machine is in ops.mydomain.com.
In Query Analyzer I have tried to connect (without success) to:
machinename\instance
machinename
i.p. address
i.p. address\instance
Within the same domain I can successfully connect to
machinename\instance
Any ideas? Also, this machine is part of a cluster...not sure if that matters. I have full permissions to connect to this machine.
Thanks
In Query Analyzer I have tried to connect (without success) to:
machinename\instance
machinename
i.p. address
i.p. address\instance
Within the same domain I can successfully connect to
machinename\instance
Any ideas? Also, this machine is part of a cluster...not sure if that matters. I have full permissions to connect to this machine.
ThanksNever mind...the instance was setup to a port different than 1433. We changed it to 1433, rebooted the server, and now I can connect.
One issue though: I can only connect by specifying the i.p. address, i.e.
255.255.255.0\instancename
Using the server name or setting up an alias doesn't seem to work.
Originally posted by banderson
I am having trouble connecting to a named instance on a different domain. For example, I am in the domain mydomain.com, the machine is in ops.mydomain.com.
In Query Analyzer I have tried to connect (without success) to:
machinename\instance
machinename
i.p. address
i.p. address\instance
Within the same domain I can successfully connect to
machinename\instance
Any ideas? Also, this machine is part of a cluster...not sure if that matters. I have full permissions to connect to this machine.
Thanks
Tuesday, 20 March 2012
Connect to Analysis Manager over HTTPS and non domain account
Please, I need your help... I`m desperate...
I`m trying to connect to the Analysis Services (AS 2000 Enterprise Edition SP4 on Windows Server 2003 EE, respository is in Access DB) throught Analysis Manager over HTTPS(HTTP) connection. I dont want to use domain account.
I need to specify USER_ID and PASSWORD to the Analysis Manager, but in registration of new server is only IP address or HTTP adress (for http://server) - but it doesnt work - it says Unauthorized. But I`ve tried to use Anonymous account and it doesn`t work (client wan`t able to make connection)... I would like to use Basic Authentification... Thise account is member of OLAP_Administrators... but the problem is where should I put USER_ID and PASSWORD?
It works perfect in Excel 2003... MSOLAP.asp work fine in IE...
Thanks very much for your advise
RicmondIs it due to "BUG: Analysis Manager Does Not Support HTTP or HTTPS onnections"
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q311310
Ricmond
I`m trying to connect to the Analysis Services (AS 2000 Enterprise Edition SP4 on Windows Server 2003 EE, respository is in Access DB) throught Analysis Manager over HTTPS(HTTP) connection. I dont want to use domain account.
I need to specify USER_ID and PASSWORD to the Analysis Manager, but in registration of new server is only IP address or HTTP adress (for http://server) - but it doesnt work - it says Unauthorized. But I`ve tried to use Anonymous account and it doesn`t work (client wan`t able to make connection)... I would like to use Basic Authentification... Thise account is member of OLAP_Administrators... but the problem is where should I put USER_ID and PASSWORD?
It works perfect in Excel 2003... MSOLAP.asp work fine in IE...
Thanks very much for your advise
RicmondIs it due to "BUG: Analysis Manager Does Not Support HTTP or HTTPS onnections"
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q311310
Ricmond
Monday, 19 March 2012
connect the SQL Server in different domains
HI ALL
I have tow domains, in the same forest. From one domain, which has a SQL Ser
ver A , I want to use the Enterprise manager or the Query Analyzer to connec
t the SQL Server B in the other domain and vise versa. Could any one elabora
te all the method to do tha
t.
thank you very much.I'm assuming this is more than just opening Query Analyzer and connecting to
a server name. What you probably want to do is add a linked server -- go to
SQL Enterprise Manager and add a new linked server under the security
section. That will let you run queries such as
select * from serverb.<database>.<owner>.<table>
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"ALLEN" <anonymous@.discussions.microsoft.com> wrote in message
news:3F57F4DF-7BB7-4C66-A362-5C112F850ABE@.microsoft.com...
> HI ALL
> I have tow domains, in the same forest. From one domain, which has a SQL
Server A , I want to use the Enterprise manager or the Query Analyzer to
connect the SQL Server B in the other domain and vise versa. Could any one
elaborate all the method to do that.
> thank you very much.|||You should not find any difference in normal connectivity, but there is one
thing that you might want to be aware of in this particular scenario. If you
want to use Kerberos Authenticatin then you will have to register an SPN for
the SQL Server using NETBIOS name.
Generally SPN should be registered in the following format
MSSQLSvc/sqlmachine.domain.net:1433 sqlserviceact
But to enable Kerberos protocol in this inter domain scenario, you will also
need to register an SPN using the NETBIOS name
MSSQLSvc/sqlmachine:1433 sqlserviceact
Thanks,
Bala.
This posting is provided "AS IS" with no warranties, and confers no
rights.
"ALLEN" <anonymous@.discussions.microsoft.com> wrote in message
news:3F57F4DF-7BB7-4C66-A362-5C112F850ABE@.microsoft.com...
> HI ALL
> I have tow domains, in the same forest. From one domain, which has a SQL
Server A , I want to use the Enterprise manager or the Query Analyzer to
connect the SQL Server B in the other domain and vise versa. Could any one
elaborate all the method to do that.
> thank you very much.
I have tow domains, in the same forest. From one domain, which has a SQL Ser
ver A , I want to use the Enterprise manager or the Query Analyzer to connec
t the SQL Server B in the other domain and vise versa. Could any one elabora
te all the method to do tha
t.
thank you very much.I'm assuming this is more than just opening Query Analyzer and connecting to
a server name. What you probably want to do is add a linked server -- go to
SQL Enterprise Manager and add a new linked server under the security
section. That will let you run queries such as
select * from serverb.<database>.<owner>.<table>
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"ALLEN" <anonymous@.discussions.microsoft.com> wrote in message
news:3F57F4DF-7BB7-4C66-A362-5C112F850ABE@.microsoft.com...
> HI ALL
> I have tow domains, in the same forest. From one domain, which has a SQL
Server A , I want to use the Enterprise manager or the Query Analyzer to
connect the SQL Server B in the other domain and vise versa. Could any one
elaborate all the method to do that.
> thank you very much.|||You should not find any difference in normal connectivity, but there is one
thing that you might want to be aware of in this particular scenario. If you
want to use Kerberos Authenticatin then you will have to register an SPN for
the SQL Server using NETBIOS name.
Generally SPN should be registered in the following format
MSSQLSvc/sqlmachine.domain.net:1433 sqlserviceact
But to enable Kerberos protocol in this inter domain scenario, you will also
need to register an SPN using the NETBIOS name
MSSQLSvc/sqlmachine:1433 sqlserviceact
Thanks,
Bala.
This posting is provided "AS IS" with no warranties, and confers no
rights.
"ALLEN" <anonymous@.discussions.microsoft.com> wrote in message
news:3F57F4DF-7BB7-4C66-A362-5C112F850ABE@.microsoft.com...
> HI ALL
> I have tow domains, in the same forest. From one domain, which has a SQL
Server A , I want to use the Enterprise manager or the Query Analyzer to
connect the SQL Server B in the other domain and vise versa. Could any one
elaborate all the method to do that.
> thank you very much.
Sunday, 11 March 2012
connect error with Windows Security
My Windows2000\SQL2000 server uses Windows Only security from a NT 4 domain.
My Win2000 client logs in to AD, not the NT4 domain. I am getting sql conne
ct errors 123 and 53 when I try to create a DSN and add my NT4 domain creden
tials. Does anyone know how
to create a DSN using credentials other than the one I am logged in as?
Thanks.Could you post the exact error messages you get?
If you are creating a DSN to use Windows authentication, you
don't specify a user name and password. You just select NT
authentication for the login info. The login must exist on
the server and if you selected a database for the DSN, the
user must exist in the database.
-Sue
On Mon, 24 May 2004 13:36:07 -0700, "Jon S"
<anonymous@.discussions.microsoft.com> wrote:
>My Windows2000\SQL2000 server uses Windows Only security from a NT 4 domain. My Win
2000 client logs in to AD, not the NT4 domain. I am getting sql connect errors 123 a
nd 53 when I try to create a DSN and add my NT4 domain credentials. Does anyone know
ho
w to create a DSN using credentials other than the one I am logged in as?
>Thanks.|||I am trying to create a user DSN and specify server name on the first screen
. On the security screen, it defaults to my AD login credentials, so I click
sql security, enter my NT4 domain credentials, then click Windows security.
The error I get is " SQLSt
ate 2800, error 18452, Login failed for user'(null)'.Reason:Not associated w
ith a trusted SQL Server connection"|||The error means you are attempting to login to SQL Server
using windows authentication and the login was not able to
be validated. On the SQL Server end, make sure that the
login exists on the server.If the login exists, try dropping
and recreating and see if that makes a difference for that
login. But if the login is fine then it's likely a Windows
authentication issue. You can check the event logs for
network related issues, problems contacting a domain
controller, that type of thing. You can also try to force
the client to connect through named pipes by creating a
named pipe alias using the Client Network Utility.
-Sue
On Tue, 25 May 2004 07:06:03 -0700, "Jon S"
<anonymous@.discussions.microsoft.com> wrote:
>I am trying to create a user DSN and specify server name on the first screen. On th
e security screen, it defaults to my AD login credentials, so I click sql security,
enter my NT4 domain credentials, then click Windows security. The error I get is " S
QLS
tate 2800, error 18452, Login failed for user'(null)'.Reason:Not associated with a trusted S
QL Server connection"
>
>
My Win2000 client logs in to AD, not the NT4 domain. I am getting sql conne
ct errors 123 and 53 when I try to create a DSN and add my NT4 domain creden
tials. Does anyone know how
to create a DSN using credentials other than the one I am logged in as?
Thanks.Could you post the exact error messages you get?
If you are creating a DSN to use Windows authentication, you
don't specify a user name and password. You just select NT
authentication for the login info. The login must exist on
the server and if you selected a database for the DSN, the
user must exist in the database.
-Sue
On Mon, 24 May 2004 13:36:07 -0700, "Jon S"
<anonymous@.discussions.microsoft.com> wrote:
>My Windows2000\SQL2000 server uses Windows Only security from a NT 4 domain. My Win
2000 client logs in to AD, not the NT4 domain. I am getting sql connect errors 123 a
nd 53 when I try to create a DSN and add my NT4 domain credentials. Does anyone know
ho
w to create a DSN using credentials other than the one I am logged in as?
>Thanks.|||I am trying to create a user DSN and specify server name on the first screen
. On the security screen, it defaults to my AD login credentials, so I click
sql security, enter my NT4 domain credentials, then click Windows security.
The error I get is " SQLSt
ate 2800, error 18452, Login failed for user'(null)'.Reason:Not associated w
ith a trusted SQL Server connection"|||The error means you are attempting to login to SQL Server
using windows authentication and the login was not able to
be validated. On the SQL Server end, make sure that the
login exists on the server.If the login exists, try dropping
and recreating and see if that makes a difference for that
login. But if the login is fine then it's likely a Windows
authentication issue. You can check the event logs for
network related issues, problems contacting a domain
controller, that type of thing. You can also try to force
the client to connect through named pipes by creating a
named pipe alias using the Client Network Utility.
-Sue
On Tue, 25 May 2004 07:06:03 -0700, "Jon S"
<anonymous@.discussions.microsoft.com> wrote:
>I am trying to create a user DSN and specify server name on the first screen. On th
e security screen, it defaults to my AD login credentials, so I click sql security,
enter my NT4 domain credentials, then click Windows security. The error I get is " S
QLS
tate 2800, error 18452, Login failed for user'(null)'.Reason:Not associated with a trusted S
QL Server connection"
>
>
connect error with Windows Security
My Windows2000\SQL2000 server uses Windows Only security from a NT 4 domain. My Win2000 client logs in to AD, not the NT4 domain. I am getting sql connect errors 123 and 53 when I try to create a DSN and add my NT4 domain credentials. Does anyone know how
to create a DSN using credentials other than the one I am logged in as?
Thanks.
Could you post the exact error messages you get?
If you are creating a DSN to use Windows authentication, you
don't specify a user name and password. You just select NT
authentication for the login info. The login must exist on
the server and if you selected a database for the DSN, the
user must exist in the database.
-Sue
On Mon, 24 May 2004 13:36:07 -0700, "Jon S"
<anonymous@.discussions.microsoft.com> wrote:
>My Windows2000\SQL2000 server uses Windows Only security from a NT 4 domain. My Win2000 client logs in to AD, not the NT4 domain. I am getting sql connect errors 123 and 53 when I try to create a DSN and add my NT4 domain credentials. Does anyone know ho
w to create a DSN using credentials other than the one I am logged in as?
>Thanks.
|||I am trying to create a user DSN and specify server name on the first screen. On the security screen, it defaults to my AD login credentials, so I click sql security, enter my NT4 domain credentials, then click Windows security. The error I get is " SQLSt
ate 2800, error 18452, Login failed for user'(null)'.Reason:Not associated with a trusted SQL Server connection"
|||The error means you are attempting to login to SQL Server
using windows authentication and the login was not able to
be validated. On the SQL Server end, make sure that the
login exists on the server.If the login exists, try dropping
and recreating and see if that makes a difference for that
login. But if the login is fine then it's likely a Windows
authentication issue. You can check the event logs for
network related issues, problems contacting a domain
controller, that type of thing. You can also try to force
the client to connect through named pipes by creating a
named pipe alias using the Client Network Utility.
-Sue
On Tue, 25 May 2004 07:06:03 -0700, "Jon S"
<anonymous@.discussions.microsoft.com> wrote:
>I am trying to create a user DSN and specify server name on the first screen. On the security screen, it defaults to my AD login credentials, so I click sql security, enter my NT4 domain credentials, then click Windows security. The error I get is " SQLS
tate 2800, error 18452, Login failed for user'(null)'.Reason:Not associated with a trusted SQL Server connection"
>
>
to create a DSN using credentials other than the one I am logged in as?
Thanks.
Could you post the exact error messages you get?
If you are creating a DSN to use Windows authentication, you
don't specify a user name and password. You just select NT
authentication for the login info. The login must exist on
the server and if you selected a database for the DSN, the
user must exist in the database.
-Sue
On Mon, 24 May 2004 13:36:07 -0700, "Jon S"
<anonymous@.discussions.microsoft.com> wrote:
>My Windows2000\SQL2000 server uses Windows Only security from a NT 4 domain. My Win2000 client logs in to AD, not the NT4 domain. I am getting sql connect errors 123 and 53 when I try to create a DSN and add my NT4 domain credentials. Does anyone know ho
w to create a DSN using credentials other than the one I am logged in as?
>Thanks.
|||I am trying to create a user DSN and specify server name on the first screen. On the security screen, it defaults to my AD login credentials, so I click sql security, enter my NT4 domain credentials, then click Windows security. The error I get is " SQLSt
ate 2800, error 18452, Login failed for user'(null)'.Reason:Not associated with a trusted SQL Server connection"
|||The error means you are attempting to login to SQL Server
using windows authentication and the login was not able to
be validated. On the SQL Server end, make sure that the
login exists on the server.If the login exists, try dropping
and recreating and see if that makes a difference for that
login. But if the login is fine then it's likely a Windows
authentication issue. You can check the event logs for
network related issues, problems contacting a domain
controller, that type of thing. You can also try to force
the client to connect through named pipes by creating a
named pipe alias using the Client Network Utility.
-Sue
On Tue, 25 May 2004 07:06:03 -0700, "Jon S"
<anonymous@.discussions.microsoft.com> wrote:
>I am trying to create a user DSN and specify server name on the first screen. On the security screen, it defaults to my AD login credentials, so I click sql security, enter my NT4 domain credentials, then click Windows security. The error I get is " SQLS
tate 2800, error 18452, Login failed for user'(null)'.Reason:Not associated with a trusted SQL Server connection"
>
>
Thursday, 8 March 2012
Conncting to SQL Server 2005 database
Hi,
I have SQL Server 2000 Client installed on Windows XP and SQL Server
2005 Database on Windows 2003 which is not on domain. I want to access
SQL Server 2005 database from SQL Server2000 Client. When i am trying
to connect it, i get access denied error. Is it possible to connect...?When you say sql server client do you mean query analyser / enterprise
manager. If so no they cant connect to sql 2005.
If you are linking servers then it is possible.
If you have sql 2005 tools and are going to server that is not on the domain
you may need to enable sql authentication on the sql server and connect usin
g
a sql username and password.
Chris
"saurabh.sarode@.gmail.com" wrote:
> Hi,
> I have SQL Server 2000 Client installed on Windows XP and SQL Server
> 2005 Database on Windows 2003 which is not on domain. I want to access
> SQL Server 2005 database from SQL Server2000 Client. When i am trying
> to connect it, i get access denied error. Is it possible to connect...?
>
I have SQL Server 2000 Client installed on Windows XP and SQL Server
2005 Database on Windows 2003 which is not on domain. I want to access
SQL Server 2005 database from SQL Server2000 Client. When i am trying
to connect it, i get access denied error. Is it possible to connect...?When you say sql server client do you mean query analyser / enterprise
manager. If so no they cant connect to sql 2005.
If you are linking servers then it is possible.
If you have sql 2005 tools and are going to server that is not on the domain
you may need to enable sql authentication on the sql server and connect usin
g
a sql username and password.
Chris
"saurabh.sarode@.gmail.com" wrote:
> Hi,
> I have SQL Server 2000 Client installed on Windows XP and SQL Server
> 2005 Database on Windows 2003 which is not on domain. I want to access
> SQL Server 2005 database from SQL Server2000 Client. When i am trying
> to connect it, i get access denied error. Is it possible to connect...?
>
Wednesday, 7 March 2012
Confused with FQDNs
Hi NG,
if i call a report with
http://servername/report everything works fine.
If i call the report with
http://servername.domain.com/report the report failed because he couldn't
find the datasource to the olap-cube.
I use win-auth on iis.
Any suggests?
FrankFrank Matthiesen wrote:
> Any suggests?
Solved...
frank
if i call a report with
http://servername/report everything works fine.
If i call the report with
http://servername.domain.com/report the report failed because he couldn't
find the datasource to the olap-cube.
I use win-auth on iis.
Any suggests?
FrankFrank Matthiesen wrote:
> Any suggests?
Solved...
frank
Friday, 17 February 2012
Configuring SQL MAIL
Hi All,
My question is that can I configure SQL MAIL, if my EXCHANGE
SERVER is on different domain and my SQL is running on different
domain.Can anyone guide me for this because I googled a lot
without any result.
I am using SQL SERVER 2000 Enterprise Edition with service pack 3.
and MICROSOFT EXCHANGE SERVER 2000.
Thanks
T.VIf the SQL Server service account is a domain account which can connect
to Exchange, then it should be fine, but that really depends on your
domain configuration. See Q12 here:
http://support.microsoft.com/defaul...kb;en-us;311231
And also this article:
http://support.microsoft.com/defaul...kb;en-us;263556
Simon
Sunday, 12 February 2012
Configuring Database mail with SMTP authentication
I try to configure database mail on SQL Server 2005 (June CTP)
All the services are running under the same domain account which has been also added to corporate Exchange server. When creating a database mail account on SQL Server, I check the "SMTP server requires authentication" check box and enter the account name and paassword. When trying to apply the changes I get the following error:
"An error occured during decryption (Microsoft SQL Server, Error 15466)"
All the services are running under the same domain account which has been also added to corporate Exchange server. When creating a database mail account on SQL Server, I check the "SMTP server requires authentication" check box and enter the account name and paassword. When trying to apply the changes I get the following error:
"An error occured during decryption (Microsoft SQL Server, Error 15466)"
Is there any workaround on this error?
Thanks.
Artem
Check this thread:
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1905071&SiteID=17
Configuring Database mail with SMTP authentication
I try to configure database mail on SQL Server 2005 (June CTP)
All the services are running under the same domain account which has been also added to corporate Exchange server. When creating a database mail account on SQL Server, I check the "SMTP server requires authentication" check box and enter the account name and paassword. When trying to apply the changes I get the following error:
"An error occured during decryption (Microsoft SQL Server, Error 15466)"
All the services are running under the same domain account which has been also added to corporate Exchange server. When creating a database mail account on SQL Server, I check the "SMTP server requires authentication" check box and enter the account name and paassword. When trying to apply the changes I get the following error:
"An error occured during decryption (Microsoft SQL Server, Error 15466)"
Is there any workaround on this error?
Thanks.
Artem
Check this thread:
http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1905071&SiteID=17
Configuring access
How can I let all domain users run reports without adding them one by one
into Report Manager?
ThanksAdd <DOMAIN>\Domain Users and grant Browse Rights.
Or better yet, create a security group that is allowed to view reports and
add this group to the list of users. I.e. if your group was called
"ReportUsers" and the name of my domain is WORKHERE then you would add:
WORKHERE\ReportUsers
=-Chris
"Mark Goldin" <mgoldin@.ufandd.com> wrote in message
news:evt7ufc%23GHA.3352@.TK2MSFTNGP03.phx.gbl...
> How can I let all domain users run reports without adding them one by one
> into Report Manager?
> Thanks
>
into Report Manager?
ThanksAdd <DOMAIN>\Domain Users and grant Browse Rights.
Or better yet, create a security group that is allowed to view reports and
add this group to the list of users. I.e. if your group was called
"ReportUsers" and the name of my domain is WORKHERE then you would add:
WORKHERE\ReportUsers
=-Chris
"Mark Goldin" <mgoldin@.ufandd.com> wrote in message
news:evt7ufc%23GHA.3352@.TK2MSFTNGP03.phx.gbl...
> How can I let all domain users run reports without adding them one by one
> into Report Manager?
> Thanks
>
Configuring a domain & SQL SERVER 2005 to work.
Attempting to link Access 2003 to SQL 2005, there is something keeping from doing so.
1 I setup the instance as sqlexpress.
2 I have a database shell there also.
3 It connects when I start the instance service.
4 My remote connections are configured to handle TCP/IP & Named Pipes.
Not in this order, but you get the idea. Now that I have these in place, I went first to the Access 2003 database to link the tables to this. When I came accross trouble in the form of need for a DSN to the domain for the things I created above.
In attempting to create one that looked functional, I came back to the same step. But, unsuccessful to link the tables again because browsing to that domain does not even show that particular file. This is the problem.
I do believe that once I am able to select a DSN, I will have a "healthy baby connection". I will then be the proud father of my first Server-side database setup!!!! But I am trying to get over these labor pains.
If you can′t use Windows authentication you will probably have to use SQL Server authentication. In addition you could try to set the network credentials of the user (Under the User account settings) to the domain which you want to connect to.HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
Configuring a domain & SQL SERVER 2005 to connection to another pc on another domain.
Attempting to link Access 2003 to SQL 2005, there is something keeping from doing so.
1 I setup the instance as sqlexpress.
2 I have a database shell there also.
3 It connects when I start the instance service.
4 My remote connections are configured to handle TCP/IP & Named Pipes.
Not in this order, but you get the idea. Now that I have these in place, I went first to the Access 2003 database to link the tables to this. When I came accross trouble in the form of need for a DSN to the domain for the things I created above.
In attempting to create one that looked functional, I came back to the same step. But, unsuccessful to link the tables again because browsing to that domain does not even show that particular file. This is the problem.
I do believe that once I am able to select a DSN, I will have a "healthy baby connection". I will then be the proud father of my first Server-side database setup!!!! But I am trying to get over these labor pains.
If you can′t use Windows authentication you will probably have to use SQL Server authentication. In addition you could try to set the network credentials of the user (Under the User account settings) to the domain which you want to connect to.HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
Subscribe to:
Posts (Atom)