Connecting to SQL across Non-Trusted Domains

From: Clint P (anonymous_at_discussions.microsoft.com)
Date: 04/23/04 

Date: Thu, 22 Apr 2004 20:11:02 -0700

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

Relevant Pages

  • Connecting to SQL across Non-Trusted Domains
    ... 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. ...
    (microsoft.public.sqlserver.security)
  • List SQL servers in a network
    ... Most of the solutions use SQLDMO to list all sql servers in the network like ... public static string[] GetAvailableSQLServers ... - this does not work with Windows XP (see SQLDMO documentation: ...
    (microsoft.public.dotnet.general)
  • Re: RWW and Sql Enterprise Manager
    ... If you are simply looking at managing these SQL Servers ... It's just like running secure RDP on the remote machine. ... MCP MCDBA MCAD MCSD MCT MCTS MCITP:DBA ... Have you tried using ASP Enterprise Manager? ...
    (microsoft.public.windows.server.sbs)
  • MS03-031 Problems
    ... I manage several SQL Servers (2000 Enterprise Edition ... default instance and two or more named instances ... These servers run in a Windows NT4 ... I have found that if I configure the service accounts to ...
    (microsoft.public.sqlserver.security)
  • RE: Cross domain authentication in SQL 2005
    ... SQL Server Windows authentication works fine when the two domains trust each ... My concern is that if we add the SQL servers to domain B, ...
    (microsoft.public.sqlserver.setup)