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.