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.
Showing posts with label non-trusted. Show all posts
Showing posts with label non-trusted. Show all posts
Sunday, March 25, 2012
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
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
Wednesday, March 7, 2012
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
>
>
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
>
>
Friday, February 24, 2012
Connecting MS, or EM to a server on a non-trusted domain
We have just put a new SQL Server 2000 (on Windows Server 2003 R2) in a
non-trusted Windows domain.
I can rdp to the machine just fine, but I can't get MS to connect.
My machine (and most servers) are in the HOME domain and the new server is
in the non-trusted QA domain.
I've tried several combinations, including creating a SQL Server login for
my use on the server - no joy.
I'm fairly certain this can work, but I'm out of idea's as to how ...
Thanks,
Jay
Make sure that you configured the SQL in Mixed mode authentication.
Regards,
Mohammad Daoud | Technical Development Manager | Mobile +962 79 999 65 85
Tel. +962 6 554 3721 | daoudm@.greatpbs.com
http://www.greatpbs.com| http://www.facebook.com/group.php?gid=18895609248/
"Jay" wrote:
> We have just put a new SQL Server 2000 (on Windows Server 2003 R2) in a
> non-trusted Windows domain.
> I can rdp to the machine just fine, but I can't get MS to connect.
> My machine (and most servers) are in the HOME domain and the new server is
> in the non-trusted QA domain.
> I've tried several combinations, including creating a SQL Server login for
> my use on the server - no joy.
> I'm fairly certain this can work, but I'm out of idea's as to how ...
> Thanks,
> Jay
>
>
|||Ya, thanks. I had already checked that. Actually, I found that port 1433 was
blocked and that it was by design.
Jay
"Mohammad Daoud" <MohammadDaoud@.discussions.microsoft.com> wrote in message
news:CC64BC8A-BE8C-4BBC-BB84-AC45FA5BFBB7@.microsoft.com...[vbcol=seagreen]
> Make sure that you configured the SQL in Mixed mode authentication.
> Regards,
> Mohammad Daoud | Technical Development Manager | Mobile +962 79 999 65 85
> Tel. +962 6 554 3721 | daoudm@.greatpbs.com
> http://www.greatpbs.com|
> http://www.facebook.com/group.php?gid=18895609248/
> "Jay" wrote:
non-trusted Windows domain.
I can rdp to the machine just fine, but I can't get MS to connect.
My machine (and most servers) are in the HOME domain and the new server is
in the non-trusted QA domain.
I've tried several combinations, including creating a SQL Server login for
my use on the server - no joy.
I'm fairly certain this can work, but I'm out of idea's as to how ...
Thanks,
Jay
Make sure that you configured the SQL in Mixed mode authentication.
Regards,
Mohammad Daoud | Technical Development Manager | Mobile +962 79 999 65 85
Tel. +962 6 554 3721 | daoudm@.greatpbs.com
http://www.greatpbs.com| http://www.facebook.com/group.php?gid=18895609248/
"Jay" wrote:
> We have just put a new SQL Server 2000 (on Windows Server 2003 R2) in a
> non-trusted Windows domain.
> I can rdp to the machine just fine, but I can't get MS to connect.
> My machine (and most servers) are in the HOME domain and the new server is
> in the non-trusted QA domain.
> I've tried several combinations, including creating a SQL Server login for
> my use on the server - no joy.
> I'm fairly certain this can work, but I'm out of idea's as to how ...
> Thanks,
> Jay
>
>
|||Ya, thanks. I had already checked that. Actually, I found that port 1433 was
blocked and that it was by design.
Jay
"Mohammad Daoud" <MohammadDaoud@.discussions.microsoft.com> wrote in message
news:CC64BC8A-BE8C-4BBC-BB84-AC45FA5BFBB7@.microsoft.com...[vbcol=seagreen]
> Make sure that you configured the SQL in Mixed mode authentication.
> Regards,
> Mohammad Daoud | Technical Development Manager | Mobile +962 79 999 65 85
> Tel. +962 6 554 3721 | daoudm@.greatpbs.com
> http://www.greatpbs.com|
> http://www.facebook.com/group.php?gid=18895609248/
> "Jay" wrote:
Connecting MS, or EM to a server on a non-trusted domain
We have just put a new SQL Server 2000 (on Windows Server 2003 R2) in a
non-trusted Windows domain.
I can rdp to the machine just fine, but I can't get MS to connect.
My machine (and most servers) are in the HOME domain and the new server is
in the non-trusted QA domain.
I've tried several combinations, including creating a SQL Server login for
my use on the server - no joy.
I'm fairly certain this can work, but I'm out of idea's as to how ...
Thanks,
JayMake sure that you configured the SQL in Mixed mode authentication.
Regards,
Mohammad Daoud | Technical Development Manager | Mobile +962 79 999 65 85
Tel. +962 6 554 3721 | daoudm@.greatpbs.com
http://www.greatpbs.com|http://www.facebook.com/group.php?gid=18895609248/
"Jay" wrote:
> We have just put a new SQL Server 2000 (on Windows Server 2003 R2) in a
> non-trusted Windows domain.
> I can rdp to the machine just fine, but I can't get MS to connect.
> My machine (and most servers) are in the HOME domain and the new server is
> in the non-trusted QA domain.
> I've tried several combinations, including creating a SQL Server login for
> my use on the server - no joy.
> I'm fairly certain this can work, but I'm out of idea's as to how ...
> Thanks,
> Jay
>
>|||Ya, thanks. I had already checked that. Actually, I found that port 1433 was
blocked and that it was by design.
Jay
"Mohammad Daoud" <MohammadDaoud@.discussions.microsoft.com> wrote in message
news:CC64BC8A-BE8C-4BBC-BB84-AC45FA5BFBB7@.microsoft.com...
> Make sure that you configured the SQL in Mixed mode authentication.
> Regards,
> Mohammad Daoud | Technical Development Manager | Mobile +962 79 999 65 85
> Tel. +962 6 554 3721 | daoudm@.greatpbs.com
> http://www.greatpbs.com|
> http://www.facebook.com/group.php?gid=18895609248/
> "Jay" wrote:
>> We have just put a new SQL Server 2000 (on Windows Server 2003 R2) in a
>> non-trusted Windows domain.
>> I can rdp to the machine just fine, but I can't get MS to connect.
>> My machine (and most servers) are in the HOME domain and the new server
>> is
>> in the non-trusted QA domain.
>> I've tried several combinations, including creating a SQL Server login
>> for
>> my use on the server - no joy.
>> I'm fairly certain this can work, but I'm out of idea's as to how ...
>> Thanks,
>> Jay
>>
non-trusted Windows domain.
I can rdp to the machine just fine, but I can't get MS to connect.
My machine (and most servers) are in the HOME domain and the new server is
in the non-trusted QA domain.
I've tried several combinations, including creating a SQL Server login for
my use on the server - no joy.
I'm fairly certain this can work, but I'm out of idea's as to how ...
Thanks,
JayMake sure that you configured the SQL in Mixed mode authentication.
Regards,
Mohammad Daoud | Technical Development Manager | Mobile +962 79 999 65 85
Tel. +962 6 554 3721 | daoudm@.greatpbs.com
http://www.greatpbs.com|http://www.facebook.com/group.php?gid=18895609248/
"Jay" wrote:
> We have just put a new SQL Server 2000 (on Windows Server 2003 R2) in a
> non-trusted Windows domain.
> I can rdp to the machine just fine, but I can't get MS to connect.
> My machine (and most servers) are in the HOME domain and the new server is
> in the non-trusted QA domain.
> I've tried several combinations, including creating a SQL Server login for
> my use on the server - no joy.
> I'm fairly certain this can work, but I'm out of idea's as to how ...
> Thanks,
> Jay
>
>|||Ya, thanks. I had already checked that. Actually, I found that port 1433 was
blocked and that it was by design.
Jay
"Mohammad Daoud" <MohammadDaoud@.discussions.microsoft.com> wrote in message
news:CC64BC8A-BE8C-4BBC-BB84-AC45FA5BFBB7@.microsoft.com...
> Make sure that you configured the SQL in Mixed mode authentication.
> Regards,
> Mohammad Daoud | Technical Development Manager | Mobile +962 79 999 65 85
> Tel. +962 6 554 3721 | daoudm@.greatpbs.com
> http://www.greatpbs.com|
> http://www.facebook.com/group.php?gid=18895609248/
> "Jay" wrote:
>> We have just put a new SQL Server 2000 (on Windows Server 2003 R2) in a
>> non-trusted Windows domain.
>> I can rdp to the machine just fine, but I can't get MS to connect.
>> My machine (and most servers) are in the HOME domain and the new server
>> is
>> in the non-trusted QA domain.
>> I've tried several combinations, including creating a SQL Server login
>> for
>> my use on the server - no joy.
>> I'm fairly certain this can work, but I'm out of idea's as to how ...
>> Thanks,
>> Jay
>>
Connecting MS, or EM to a server on a non-trusted domain
We have just put a new SQL Server 2000 (on Windows Server 2003 R2) in a
non-trusted Windows domain.
I can rdp to the machine just fine, but I can't get MS to connect.
My machine (and most servers) are in the HOME domain and the new server is
in the non-trusted QA domain.
I've tried several combinations, including creating a SQL Server login for
my use on the server - no joy.
I'm fairly certain this can work, but I'm out of idea's as to how ...
Thanks,
JayMake sure that you configured the SQL in Mixed mode authentication.
Regards,
Mohammad Daoud | Technical Development Manager | Mobile +962 79 999 65 85
Tel. +962 6 554 3721 | daoudm@.greatpbs.com
http://www.greatpbs.com| http://www.facebook.com/group.php?gid=18895609248/
"Jay" wrote:
> We have just put a new SQL Server 2000 (on Windows Server 2003 R2) in a
> non-trusted Windows domain.
> I can rdp to the machine just fine, but I can't get MS to connect.
> My machine (and most servers) are in the HOME domain and the new server is
> in the non-trusted QA domain.
> I've tried several combinations, including creating a SQL Server login for
> my use on the server - no joy.
> I'm fairly certain this can work, but I'm out of idea's as to how ...
> Thanks,
> Jay
>
>|||Ya, thanks. I had already checked that. Actually, I found that port 1433 was
blocked and that it was by design.
Jay
"Mohammad Daoud" <MohammadDaoud@.discussions.microsoft.com> wrote in message
news:CC64BC8A-BE8C-4BBC-BB84-AC45FA5BFBB7@.microsoft.com...[vbcol=seagreen]
> Make sure that you configured the SQL in Mixed mode authentication.
> Regards,
> Mohammad Daoud | Technical Development Manager | Mobile +962 79 999 65 85
> Tel. +962 6 554 3721 | daoudm@.greatpbs.com
> http://www.greatpbs.com|
> http://www.facebook.com/group.php?gid=18895609248/
> "Jay" wrote:
>
non-trusted Windows domain.
I can rdp to the machine just fine, but I can't get MS to connect.
My machine (and most servers) are in the HOME domain and the new server is
in the non-trusted QA domain.
I've tried several combinations, including creating a SQL Server login for
my use on the server - no joy.
I'm fairly certain this can work, but I'm out of idea's as to how ...
Thanks,
JayMake sure that you configured the SQL in Mixed mode authentication.
Regards,
Mohammad Daoud | Technical Development Manager | Mobile +962 79 999 65 85
Tel. +962 6 554 3721 | daoudm@.greatpbs.com
http://www.greatpbs.com| http://www.facebook.com/group.php?gid=18895609248/
"Jay" wrote:
> We have just put a new SQL Server 2000 (on Windows Server 2003 R2) in a
> non-trusted Windows domain.
> I can rdp to the machine just fine, but I can't get MS to connect.
> My machine (and most servers) are in the HOME domain and the new server is
> in the non-trusted QA domain.
> I've tried several combinations, including creating a SQL Server login for
> my use on the server - no joy.
> I'm fairly certain this can work, but I'm out of idea's as to how ...
> Thanks,
> Jay
>
>|||Ya, thanks. I had already checked that. Actually, I found that port 1433 was
blocked and that it was by design.
Jay
"Mohammad Daoud" <MohammadDaoud@.discussions.microsoft.com> wrote in message
news:CC64BC8A-BE8C-4BBC-BB84-AC45FA5BFBB7@.microsoft.com...[vbcol=seagreen]
> Make sure that you configured the SQL in Mixed mode authentication.
> Regards,
> Mohammad Daoud | Technical Development Manager | Mobile +962 79 999 65 85
> Tel. +962 6 554 3721 | daoudm@.greatpbs.com
> http://www.greatpbs.com|
> http://www.facebook.com/group.php?gid=18895609248/
> "Jay" wrote:
>
Subscribe to:
Posts (Atom)