Connecting to SQL across Non-Trusted Domains

The problem I am having is this :
SQL Servers in a non -trusted Windows 2000 Domain (Test domain) do not show
as being alive in Enterprise Manager unless you map a drive to a server in t
he non-trusted domain.
Has anyone seem this problem before? Not sure whether this is related to Act
ive Directory.
Also all our SQL Instances use specific port numbers.
Thanks
CPNZSounds like the Agent polling is not able to contact the other servers
unless you map a drive allowing your server
to communicate with the others. This is more of a problem with disjoined
domains that SQL Server.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||You can do the following.
Your SQL Server instances must be running as a LOCAL or Domain account. If
you configure a LOCAL account on the server you are trying to connect to
with the same username and password it will log in using this account.
Barry McAuslin
Look inside your SQL Server files with SQL File Explorer.
Go to http://www.sqlfe.com for more information.
"CPNZ" <anonymous@.discussions.microsoft.com> wrote in message
news:72C261EE-AB91-45D1-BA20-EE1F805E3FD0@.microsoft.com...
> The problem I am having is this :
> SQL Servers in a non -trusted Windows 2000 Domain (Test domain) do not
show as being alive in Enterprise Manager unless you map a drive to a server
in the non-trusted domain.
> Has anyone seem this problem before? Not sure whether this is related to
Active Directory.
> Also all our SQL Instances use specific port numbers.
> Thanks
> CPNZ|||Okay. We have clients using Enterprise Manager, and they used to be able to
connect accross these domains using SQL authentication.
Kevin could there be an Active Directory issue stopping these services being
seen accross the domains? My server people say nothing has changed in AD,
but you never know. Also could you give a little more info on the Polling A
gent.
Thanks
Clint|||Hi Clint,
The SQL Server state polling is controlled in Enterprise Manager.
Go to the server you registered. Then Select from the menu, Tools ,
Options.
By default we poll servers every 10 seconds.
Check to see if you're clients connect using Named Pipes or TCP/IP sockets.
You'll be unable to connect to a remote server in an untrusted domain
using Named Pipes. Use the SQL Client network utility to specify tcp/ip as
the protocol to connect to the remote server.
Hope this helps.
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Connecting to SQL across Non-Trusted Domains

The problem I am having is this :
SQL Servers in a non -trusted Windows 2000 Domain (Test domain) do not show
as being alive in Enterprise Manager unless you map a drive to a server in t
he non-trusted domain.
Has anyone seem this problem before? Not sure whether this is related to Act
ive Directory.
Also all our SQL Instances use specific port numbers.
ThanksClint,
That's called "working as designed" I'm afraif - it's expecting there to be
an underlying NT authentication.

> The problem I am having is this :
> SQL Servers in a non -trusted Windows 2000 Domain (Test domain) do not sho
w as being alive in Enterprise Manager unless you map a drive to a server in
the non-trusted domain.
> Has anyone seem this problem before? Not sure whether this is related to A
ctive Directory.
> Also all our SQL Instances use specific port numbers.
> Thanks
>
Neil Pike MVP/MCSE. Protech Computing Ltd
Reply here - no email
SQL FAQ (484 entries) see
http://forumsb.compuserve.com/gvfor...p?SRV=MSDevApps
(faqxxx.zip in lib 7)
or www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
or www.sqlserverfaq.com
or www.mssqlserver.com/faq

Connecting to MS SQL server 2000 from the different domains using asp.net

Hi,

My problem is somewhat like this that, i want to connect my all applications (developed in asp.net) to one database. In other words i want to make a centralised database that can be accessible from the application running at the different domains. When i did so by using the same username, password, database and server...i recieve an error that,"connection cannot be establised".

If any body have the solution for this problem. then please do write the "connection string" for me that can be efficiantly used on the applications running on differnt domains.

Thanks and Regards,

Steve Dcosta

Considering the domains trust each other and that you have the proper rights for accessing the database server from each of the different domains you can try the following connectionString replacing the correct values for the variables:

data source=putIPHereIncaseNameResolutionFails;user id=user;password=yourPassword;initial catalog=databaseName;persist security info=True

Connect to SQL named instance from another domain

Hi,

I have two domains setup with two way trust in place. SQL server 2005 is installed in domain A.

Is it possible to log in to SQL server using machine account of a machine in domain B?

I have been told that you cannot access SQL server from another domain using machine account. But I cannot find any resource or references about it.

If this isn't the right MSDN forum for this I apologize, but any advice would be greatly appreciated.

Thanks in advance.

Hi,

You can achive this by creating the same machine account of the one in domain B on the machine in domain A, and grant login to it.

HTH.

Ming.

|||

Hi

I am facing the same issue ... I have reporting servcies in domain A and Analysis Server on domain B , but there are no trust principles between domains. I need the reports to query the AS but my datasources are not able to establish a connection with the Analysis Server becuase its lying on another domain.

Is there a work around .

Jayanth

Connect to SQL named instance from another domain

Hi,

I have two domains setup with two way trust in place. SQL server 2005 is installed in domain A.

Is it possible to log in to SQL server using machine account of a machine in domain B?

I have been told that you cannot access SQL server from another domain using machine account. But I cannot find any resource or references about it.

If this isn't the right MSDN forum for this I apologize, but any advice would be greatly appreciated.

Thanks in advance.

Hi,

You can achive this by creating the same machine account of the one in domain B on the machine in domain A, and grant login to it.

HTH.

Ming.

|||

Hi

I am facing the same issue ... I have reporting servcies in domain A and Analysis Server on domain B , but there are no trust principles between domains. I need the reports to query the AS but my datasources are not able to establish a connection with the Analysis Server becuase its lying on another domain.

Is there a work around .

Jayanth