Connecting to a DB in a non-trusted domain

SQL Server 2000 mainly, but also 2005 (Management Studio only)
We are restructuring our network and have created a new QA (clustered)
server in a new, non-trusted domain (named QA). To do the initial setup of
the server, I've been using rdp to login to the box and run EM there (the
server is 2000). The rdp login process is flawless.
When I attempt to create a New Server registration in EM, or MS I get the
error:
machine.qa.name.com - SQL Server does not exist access denied.
ConnectionOpen (Connect())
Checking the event log on the remote server, I see the attempted login with
the CORP domain, not the QA domain
So, I tried to create a local SQL Server login: QA\myname and when I check
the event log, I get the same CORP\myname "Unknown user, or bad password"
error. I've also tried entering the server as QA\machine.qa.name.com and
several other combinations.
I'm at a loss. I really need to register this server.
Thanks,
JayFWIW, I get two messages in the remote computers event log:
-- message #1 --
Event Type: Failure Audit
Event Source: Security
Event Category: Account Logon
Event ID: 680
Date: 11/6/2007
Time: 10:53:08 AM
User: NT AUTHORITY\SYSTEM
Computer: __QA_ClusterNode-A__
Description:
Logon attempt by: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
Logon account: __MyLoginName__
Source Workstation: __MyWorkstation__
Error Code: 0xC0000064
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
--
-- message #2
Event Type: Failure Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 529
Date: 11/6/2007
Time: 10:53:07 AM
User: NT AUTHORITY\SYSTEM
Computer: __QA_ClusterNode-A__
Description:
Logon Failure:
Reason: Unknown user name or bad password
User Name: MyLoginName
Domain: __MYDOMAIN__
Logon Type: 3
Logon Process: NtLmSsp
Authentication Package: NTLM
Workstation Name: __MyWorkStation__
Caller User Name: -
Caller Domain: -
Caller Logon ID: -
Caller Process ID: -
Transited Services: -
Source Network Address: __My_IP_Address__
Source Port: 0
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
--
"Jay" <nospan@.nospam.org> wrote in message
news:OymY1FKIIHA.4808@.TK2MSFTNGP05.phx.gbl...
> SQL Server 2000 mainly, but also 2005 (Management Studio only)
> We are restructuring our network and have created a new QA (clustered)
> server in a new, non-trusted domain (named QA). To do the initial setup of
> the server, I've been using rdp to login to the box and run EM there (the
> server is 2000). The rdp login process is flawless.
> When I attempt to create a New Server registration in EM, or MS I get the
> error:
> machine.qa.name.com - SQL Server does not exist access denied.
> ConnectionOpen (Connect())
> Checking the event log on the remote server, I see the attempted login
> with the CORP domain, not the QA domain
> So, I tried to create a local SQL Server login: QA\myname and when I check
> the event log, I get the same CORP\myname "Unknown user, or bad password"
> error. I've also tried entering the server as QA\machine.qa.name.com and
> several other combinations.
> I'm at a loss. I really need to register this server.
> Thanks,
> Jay
>
>|||I have completly uninstalled all of my SQL Server instances and reinstalled
the 2000 tools and am still getting the error.
The only thing I can think of that could have caused this was that I had
previously changed all of the login accounts in services to local to fix a
domain issue that prevented my local instances from starting when the domain
policy was updated. However, as I said, I've removed everything.
"Jay" <nospan@.nospam.org> wrote in message
news:OymY1FKIIHA.4808@.TK2MSFTNGP05.phx.gbl...
> SQL Server 2000 mainly, but also 2005 (Management Studio only)
> We are restructuring our network and have created a new QA (clustered)
> server in a new, non-trusted domain (named QA). To do the initial setup of
> the server, I've been using rdp to login to the box and run EM there (the
> server is 2000). The rdp login process is flawless.
> When I attempt to create a New Server registration in EM, or MS I get the
> error:
> machine.qa.name.com - SQL Server does not exist access denied.
> ConnectionOpen (Connect())
> Checking the event log on the remote server, I see the attempted login
> with the CORP domain, not the QA domain
> So, I tried to create a local SQL Server login: QA\myname and when I check
> the event log, I get the same CORP\myname "Unknown user, or bad password"
> error. I've also tried entering the server as QA\machine.qa.name.com and
> several other combinations.
> I'm at a loss. I really need to register this server.
> Thanks,
> Jay
>
>

Connecting Surface Area Configuration to server on Clustered Server

I've run into a problem after upgrading production servers running under Microsoft Cluster Server, Windows Enterprise Server 2003 SP1, and SQL Server 2005 SP1 Enterprise Edition.

Once I completed the upgrade and applied the patch, I needed to examine the values set in the Features component of the Surface Area Configuration tool. The tool attempts to connect to localhost\instancename, but reports the following error:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error:26 - Error Locating Server/Instance Specified)(Microsoft SQL Server)

I'm logged into the virtual server via Remote Desktop, but the SAC tool thinks I'm logged into the physical server supporting the virtual server. I seem to be caught between a rock and a hard place here, as I can't enable remote connections without first gaining access on the server itself.

Any help will be greatly appreciated.

Can anyone give me a little help here - I can't make configuration changes on production servers.

Thanks.

|||

Well, after a lucky break I found the answer.

sp_configure 'remote admin connections', 1
go
reconfigure
go

Once this was executed on the server I was able to go into Surface Area Configuration, enter the virtual server name, and connect successfully and make the other changes necessary. A simple solution to a scary problem. (Even though I'd used sp_configure for years on both Sybase and MSSQL servers it's easy to forget about the simple solutions.)

Connecting Surface Area Configuration to server on Clustered Server

I've run into a problem after upgrading production servers running under Microsoft Cluster Server, Windows Enterprise Server 2003 SP1, and SQL Server 2005 SP1 Enterprise Edition.

Once I completed the upgrade and applied the patch, I needed to examine the values set in the Features component of the Surface Area Configuration tool. The tool attempts to connect to localhost\instancename, but reports the following error:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error:26 - Error Locating Server/Instance Specified)(Microsoft SQL Server)

I'm logged into the virtual server via Remote Desktop, but the SAC tool thinks I'm logged into the physical server supporting the virtual server. I seem to be caught between a rock and a hard place here, as I can't enable remote connections without first gaining access on the server itself.

Any help will be greatly appreciated.

Can anyone give me a little help here - I can't make configuration changes on production servers.

Thanks.

|||

Well, after a lucky break I found the answer.

sp_configure 'remote admin connections', 1
go
reconfigure
go

Once this was executed on the server I was able to go into Surface Area Configuration, enter the virtual server name, and connect successfully and make the other changes necessary. A simple solution to a scary problem. (Even though I'd used sp_configure for years on both Sybase and MSSQL servers it's easy to forget about the simple solutions.)

|||thx a lot

Connect to SSIS Service on machine "Servername" failed: Error loading type library/DLL

Got above error on clustered sql2k5 x86 when connect to SSIS, any solution?

Check the article on "How to: Configure Integration Services on a Cluster" @. http://msdn2.microsoft.com/en-us/library/ms345193.aspx

Thanks,
Loonysan

|||Thanks for the info, but it's not related to my problem. SSIS installation is fine, the issue is I got above error when register SSIS in SSMS on active node. I can register same SSIS remotely on passive node without error.

Connect to SSIS Service on machine "Servername" failed: Error loading type library

Got above error on clustered sql2k5 x86 when connect to SSIS, any solution?

Check the article on "How to: Configure Integration Services on a Cluster" @. http://msdn2.microsoft.com/en-us/library/ms345193.aspx

Thanks,
Loonysan

|||Thanks for the info, but it's not related to my problem. SSIS installation is fine, the issue is I got above error when register SSIS in SSMS on active node. I can register same SSIS remotely on passive node without error.

Connect to SSIS on clustered sql2k5

I got following error when try to expand msdb under SSIS in SSMS, the SSIS I connected to is on clustered server. The windows account used is member of local admin on both nodes in the cluster and sysadmin in sql. I tried with host name that SSIS runs on and virtual sql server name for connection, tried connect from remote client machine and server itself, got same error:

Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)

Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Named Pipes Provider: Could not open a connection to SQL Server [2]. (Microsoft SQL Native Client)

Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Named Pipes Provider: Could not open a connection to SQL Server [2]. (Microsoft SQL Native Client)

Anyone knows what's happen? Thanks.

I solve the problem by changing <ServerName>.</ServerName> to <ServerName>virtual_sql_server_name</ServerName> in %ms sql server%\90\dts\binn\MsDtsSrvr.ini.xml file on each node.|||

I have configured SSIS on the cluster after clustered DB installation. I have followed the directions on 'How to: Configure Integration Services on a Cluster' doc on msdn (http://msdn2.microsoft.com/en-us/library/ms345193.aspx) but I am still not able to connect and I get this error message (very similar to the message on beginning of this post)

TITLE: Microsoft SQL Server Management Studio

Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

ADDITIONAL INFORMATION:

The SQL server specified in SSIS service configuration is not present or is not available. This might occur when there is no default instance of SQL Server on the computer. For more information, see the topic "Configuring the Integration Services Service" in Server 2005 Books Online.

Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Named Pipes Provider: Could not open a connection to SQL Server [2]. (MsDtsSrvr)

BUTTONS:

OK

Appreciate any help you can provide.

Thanks!

Connect to SSIS on clustered sql2k5

I got following error when try to expand msdb under SSIS in SSMS, the SSIS I connected to is on clustered server. The windows account used is member of local admin on both nodes in the cluster and sysadmin in sql. I tried with host name that SSIS runs on and virtual sql server name for connection, tried connect from remote client machine and server itself, got same error:

Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)

Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Named Pipes Provider: Could not open a connection to SQL Server [2]. (Microsoft SQL Native Client)

Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Named Pipes Provider: Could not open a connection to SQL Server [2]. (Microsoft SQL Native Client)

Anyone knows what's happen? Thanks.

I solve the problem by changing <ServerName>.</ServerName> to <ServerName>virtual_sql_server_name</ServerName> in %ms sql server%\90\dts\binn\MsDtsSrvr.ini.xml file on each node.|||

I have configured SSIS on the cluster after clustered DB installation. I have followed the directions on 'How to: Configure Integration Services on a Cluster' doc on msdn (http://msdn2.microsoft.com/en-us/library/ms345193.aspx) but I am still not able to connect and I get this error message (very similar to the message on beginning of this post)

TITLE: Microsoft SQL Server Management Studio

Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

ADDITIONAL INFORMATION:

The SQL server specified in SSIS service configuration is not present or is not available. This might occur when there is no default instance of SQL Server on the computer. For more information, see the topic "Configuring the Integration Services Service" in Server 2005 Books Online.

Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Named Pipes Provider: Could not open a connection to SQL Server [2]. (MsDtsSrvr)

BUTTONS:

OK

Appreciate any help you can provide.

Thanks!