connecting to sql server 2000 from sql server 2005 management studio

My web site is hosted by a third party, and the back-end is a sql server 2000 database. I was routinely running queries over the internet against the database using Query Analyzer. I just installed sql server 2005. Is it possible to run a sql query against a table in the sql server 2000 database from within sql server 2005 management studio? I haven't found anything in the docs explaining how to connect to sql server 2000. Any help would be appreciated.

You can just connect to the SQL Server 200 as you connected before and are connecting now with your Business Management Studio. Its downwards compatible.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||Hi there,

If all you want to do is access your SQL Server 2000 database using SQL Server 2005 Management Studio then you just need to add another connection in your Object Explorer. I believe the steps are:

1) Go File > Connect Object Explorer (NB. alternately you can click on the "Connect Object Explorer" button in the Object Explorer window

2) A dialog will appear where you specify the server name, auth type (SQL Server, Windows), username and password.

Enter the server name (should be the same as the name of the server you connect to in Query Analyzer) and other details as appropriate (the same config you used in Query Analyzer should apply here).

3) A node for your SQL Server 2000 server should appear in the Object Explorer. To query against the database, an easy way is to click on the database (you'll need to expand a few nodes in Obejct Explorer) and then click the "New Query" button (or go File > New > Query With Current Connection).

If your intent is to have your SQL Server 2005 database and define queries for that database that reference the SQL Server 2000 database then you'll need to define a linked server from the SQL Server 2005 instance to the SQL Server 2000 instance. There should be details on how to do this in Books Online.

Hope that helps a bit but sorry if it doesn't & I've missed the mark completely.

Connecting to SQL in ASP.net 20

I have a database that is currently connected and working properly in My SQL Server Management Studio. The problem I am havings is when I open My ASP.net 20 and Look in my Server Solutions I can not find the database to connect to it . It seems to be trying to use SLQ Express and not my SLQ Server Management Studio. How do I get my database to connect in my application? All I can see from within the Server solutions in ASP is the database .bak file which is the backup of the database. I thank you in advance.

Are you saying that, when you are trying to connect to the Server in the Server Explorer, that the server does not show up in the list?

Is the server 2000 or 2005 or.....?

|||Yes and no . I think I dono have my SQL Server Manager Studio (Dev ed) is not set as my primary and the SQL Express is . I think I need to configure my SQL Server Manager Studioas primary but am not sure how to do this. and help would be get.|||My question was concerning inside Visual Web Developer - the Server Explorer window|||Inside the designer in the server explorer the sever shows up ok but the database does not|||Inside the designer in the server explorer the sever shows up ok but the database does not

Connecting to SQL 2005 Server via VPN

Hi all,
I am unable to connect to SQL2005 server using the Management Studio. i can
however connect to SQL2000 using EM. Has anyone else encoutered this issue?
if so could you please share the solution? what is ti that i need to enable
on the firewall?
Thanks
JoresIs SQL Server 2005 enabled for remote connections?
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"joresm" <joresm@.hotmail.com> wrote in message
news:ODgXkoKaGHA.1220@.TK2MSFTNGP02.phx.gbl...
> Hi all,
> I am unable to connect to SQL2005 server using the Management Studio. i
> can however connect to SQL2000 using EM. Has anyone else encoutered this
> issue? if so could you please share the solution? what is ti that i need
> to enable on the firewall?
> Thanks
> Jores
>|||Yes, it is enabled and the Browser sevice is also running. i canconnect to
it using the query analyzer. the only problem is with Management studio.
Thanks
Jores
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uBvNIgLaGHA.1348@.TK2MSFTNGP05.phx.gbl...
> Is SQL Server 2005 enabled for remote connections?
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "joresm" <joresm@.hotmail.com> wrote in message
> news:ODgXkoKaGHA.1220@.TK2MSFTNGP02.phx.gbl...
>|||Hi I have experienced this problem also. Spent best part of a day trying to
resolve this to no avail. We have a VPN connection to our data center. The
database server has an instance of SQL 2000 which runs fine locally and
remotely from my desk. Recently we installed SQL 2005 and want to migrate
stuff to this new named instance. I can connect to the database fine locally
(on the database server itself and from other colocated machines (via
ADO.net). However I cannot access SQL 2005 over the VPN connection using
either ADO.net test app or SQL Management Studio. Is there some kind of port
blocking going on?
I don't know anything about Named Pipes, but I've tried the SQL
Configuration tool as suggested in some articles and have tried setting the
port to 1433 and turning of SQL 2000 to no avail. Would the VPN somehow be
blocking some ports - it appears that way, but my administrator assures me
that I should have full spectrum of ports available. WHATS GOING ON' Is the
SQL browser getting blocked or what? What button do I need to push to get
access to my database server from my development machine located over the
VPN?
Thanks Rob
"joresm" wrote:

> Yes, it is enabled and the Browser sevice is also running. i canconnect to
> it using the query analyzer. the only problem is with Management studio.
> Thanks
> Jores
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:uBvNIgLaGHA.1348@.TK2MSFTNGP05.phx.gbl...
>
>

Connecting to SQL 2005 Server via VPN

Hi all,
I am unable to connect to SQL2005 server using the Management Studio. i can
however connect to SQL2000 using EM. Has anyone else encoutered this issue?
if so could you please share the solution? what is ti that i need to enable
on the firewall?
Thanks
JoresIs SQL Server 2005 enabled for remote connections?
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"joresm" <joresm@.hotmail.com> wrote in message
news:ODgXkoKaGHA.1220@.TK2MSFTNGP02.phx.gbl...
> Hi all,
> I am unable to connect to SQL2005 server using the Management Studio. i
> can however connect to SQL2000 using EM. Has anyone else encoutered this
> issue? if so could you please share the solution? what is ti that i need
> to enable on the firewall?
> Thanks
> Jores
>|||Yes, it is enabled and the Browser sevice is also running. i canconnect to
it using the query analyzer. the only problem is with Management studio.
Thanks
Jores
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uBvNIgLaGHA.1348@.TK2MSFTNGP05.phx.gbl...
> Is SQL Server 2005 enabled for remote connections?
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "joresm" <joresm@.hotmail.com> wrote in message
> news:ODgXkoKaGHA.1220@.TK2MSFTNGP02.phx.gbl...
>> Hi all,
>> I am unable to connect to SQL2005 server using the Management Studio. i
>> can however connect to SQL2000 using EM. Has anyone else encoutered this
>> issue? if so could you please share the solution? what is ti that i need
>> to enable on the firewall?
>> Thanks
>> Jores
>|||Hi I have experienced this problem also. Spent best part of a day trying to
resolve this to no avail. We have a VPN connection to our data center. The
database server has an instance of SQL 2000 which runs fine locally and
remotely from my desk. Recently we installed SQL 2005 and want to migrate
stuff to this new named instance. I can connect to the database fine locally
(on the database server itself and from other colocated machines (via
ADO.net). However I cannot access SQL 2005 over the VPN connection using
either ADO.net test app or SQL Management Studio. Is there some kind of port
blocking going on?
I don't know anything about Named Pipes, but I've tried the SQL
Configuration tool as suggested in some articles and have tried setting the
port to 1433 and turning of SQL 2000 to no avail. Would the VPN somehow be
blocking some ports - it appears that way, but my administrator assures me
that I should have full spectrum of ports available. WHATS GOING ON' Is the
SQL browser getting blocked or what? What button do I need to push to get
access to my database server from my development machine located over the
VPN?
Thanks Rob
"joresm" wrote:
> Yes, it is enabled and the Browser sevice is also running. i canconnect to
> it using the query analyzer. the only problem is with Management studio.
> Thanks
> Jores
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:uBvNIgLaGHA.1348@.TK2MSFTNGP05.phx.gbl...
> > Is SQL Server 2005 enabled for remote connections?
> >
> > --
> > Hilary Cotter
> > Director of Text Mining and Database Strategy
> > RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> >
> > This posting is my own and doesn't necessarily represent RelevantNoise's
> > positions, strategies or opinions.
> >
> > Looking for a SQL Server replication book?
> > http://www.nwsu.com/0974973602.html
> >
> > Looking for a FAQ on Indexing Services/SQL FTS
> > http://www.indexserverfaq.com
> >
> >
> >
> > "joresm" <joresm@.hotmail.com> wrote in message
> > news:ODgXkoKaGHA.1220@.TK2MSFTNGP02.phx.gbl...
> >> Hi all,
> >> I am unable to connect to SQL2005 server using the Management Studio. i
> >> can however connect to SQL2000 using EM. Has anyone else encoutered this
> >> issue? if so could you please share the solution? what is ti that i need
> >> to enable on the firewall?
> >>
> >> Thanks
> >> Jores
> >>
> >
> >
>
>sqlsql

Connecting to some remote Sql Server

Hi

I've got a desktop and a notebook and both are connected to the router. On both I've got Sql Server Express and Sql Server Management Studio Express installed. I need to connect to a remote Sql Server (using user ID and password) which works fine on my desktop, but fails on my notebook: Error:0 and Error: 10060.

I checked all router settings and notebook settings, but I don't know what I am doing wrong. I got myself another notebook and installed Sql Server Express plus Management Studio, which did not work either.

Hopefully someone can help.

Thank you.

The error code is of Socket error. It seems you are not able to get connected to your SQL server.

following should help you.

http://www.dameware.com/support/kb/article.aspx?ID=300060

|||

Hi, I am able to connect to the local Sql Server Express (running on the notebook) - only remote connections (at least the one I am trying) fail.

Thanks!

|||

The remote connection may be failing because of socket error. You might like to have a look at remote connection. You might also like to look at the SQL server to check if it allows remote connections.

connecting to server from SQL Server Management Studio

Hi,

I have 2 servers (test ,preprod ) with sql2005 and reporting services

Using SQL Server Management Studio I can connect on reporting services on test server

specifying server name http://smcanSQL10-tst/reportserver or smcanSQL10-tst

but for preprod server I have to specify

http://smcanSQL10-ppd/reportserver

if I simply put smcanSQL10-ppd application raise error

The machine could not be found (Microsoft.SqlServer.Management.UI.RSClient)

Is any setting missiing in my server configuration?

Alex,

Have you checked in your SQL 2005 Reporting Service Configuration manager under the "Report Server Virtual Directory" to make sure that the name is corrected?

Ham

|||

yes,

on both servers it is

name: ReportServer

Website: Defaut Web Site

sqlsql

Connecting to Reporting Services in Management Studio

I get the following error in connectig to RS in Management Studio - what do I
need to do to fix this - thanks.
Paddy
--
The report server has encountered a configuration error. See the report
server log files for more information. (rsServerConfigurationError)
Access to the path 'C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
Services\ReportServer\RSReportServer.config' is denied.Go to the NTFS Permissions of C:\Program Files\Microsoft SQL
Server\MSSQL.3\Reporting Services\ReportServer\RSReportServer.config'
and make sure that ASPNET computer account has read access to this file.
or if the ReportServer directory has the correct permissions then just check
the inherit permission from parent checkbox.
"Paddy" wrote:
> I get the following error in connectig to RS in Management Studio - what do I
> need to do to fix this - thanks.
> Paddy
> --
> The report server has encountered a configuration error. See the report
> server log files for more information. (rsServerConfigurationError)
> Access to the path 'C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
> Services\ReportServer\RSReportServer.config' is denied.

Connecting To Remote MSDE With Server Management Studio

Hello,
I am having issues connecting to an MSDE instance on a remote machine
using MSSQL 9's Server Management Studio.
I am also have issues connecting to a remote instance of MSSQL v7 using
Server Management Studio. Later, I will have to connect to MSSQL v8.
If there is a step-by-step guide somewhere, I would like a URL for it.
Otherwise, I would just like to have input regarding what I should be
checking.
The MSDE was installed without an instance name, so I believe the
instance name is the name of the machine. I believe that I need to
specify the machine and the instance name in the Server Management
Studio connection dialog. I believe the format is
MachineName\InstanceName
In all cases I am using TCP/IP to connect.
All authentication is SQL Auth. The MSDE machine is configured to use
SQL Auth. The MSSQL v7 machine is too.
I was a bit surprised to see the requests on port 1434 instead of 1433.
I'll learn about the reason(s) for this later. Right now, I want to
know if there are any considerations regarding this.
There are firewalls involved, they have been configured to allow
access. This is confirmed by being able to use the MSSQL v7 tools to
connect to both the MSDE and the v7 servers.
The error I receive when connecting to the MSDE machine is:
(provider: SQL Network Interfaces, error: 26 - Error Locating
Server/Instance Specified) (Microsoft SQL Server, Error: -1)
The error I use when connecting to the v7 machine is:
(provider: TCP Provider, error: 0 - A socket operation encountered a
dead network.) (Microsoft SQL Server, Error: 10050)
Any thoughts or ideas?
hi,
> The MSDE was installed without an instance name, so I believe the
> instance name is the name of the machine. I believe that I need to
> specify the machine and the instance name in the Server Management
> Studio connection dialog. I believe the format is
> MachineName\InstanceName
as long as you did not install a named instance, you only have to provide
the MachineName..

> In all cases I am using TCP/IP to connect.
obviously the relative network protocol has been enabled on the remote
server..

> All authentication is SQL Auth. The MSDE machine is configured to use
> SQL Auth. The MSSQL v7 machine is too.
> I was a bit surprised to see the requests on port 1434 instead of
> 1433. I'll learn about the reason(s) for this later. Right now, I
> want to know if there are any considerations regarding this.
TCP/IP 1433 is the IANA assigned port to Microsoft SQL Server, and is the
default port for default instances of SQL Server... named instances usually
adopt the dynamic allocation of a port, so another service is involved,
running on UDP 1434 port, which resolves the connection enquiry redirecting
to the appropriate named instace's used TCP port..

> There are firewalls involved, they have been configured to allow
> access. This is confirmed by being able to use the MSSQL v7 tools to
> connect to both the MSDE and the v7 servers.
> The error I receive when connecting to the MSDE machine is:
> (provider: SQL Network Interfaces, error: 26 - Error Locating
> Server/Instance Specified) (Microsoft SQL Server, Error: -1)
> The error I use when connecting to the v7 machine is:
> (provider: TCP Provider, error: 0 - A socket operation encountered a
> dead network.) (Microsoft SQL Server, Error: 10050)
>
> Any thoughts or ideas?
try having a look at
http://support.microsoft.com/default...b;en-us;905618 ...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Connecting to named instance in Management Studio fails

I have a remote server with a default instance of Sql 2000 and a named
instance of Sql 2005. Whenever I try to connect to the named instance
in Management Studio, it ALWAYS connects to the default instance. I am
specifying the connection as ServerName\InstanceName. It seems like it
is ignoring the instance name in the connection request. I have tried
creating an alias, but it does not change the behavior. One special
note - due to our network structure we must use fully qualified domain
names when connecting to remote servers. The my local server and my
remote server are in different sub-domains:
local server = ServerA.HQ.domain.com
remote server = ServerX.Remote.domain.com
One interesting observation is that I am able to connect to the remote
server from a different db server in the same sub-domain without any
problems. i.e. ServerY.remote.domain.com can connect to
ServerX.remote.domain.com.
I know there was a bug in MDAC that was similar to this, but it was
supposedly fixed in MDAC 2.8 SP1. I wonder if the same bug crept into
the SQLNI code?check with your network admin. it seems there is firewall rule on udp 1434.
also, try to specify the tcp as part of your connection string.
e.g.
sqlcmd -S"ServerX.Remote.domain.com,tcp#"
-oj
"kmart" <kevmart@.gmail.com> wrote in message
news:1146849746.958318.194980@.v46g2000cwv.googlegroups.com...
>I have a remote server with a default instance of Sql 2000 and a named
> instance of Sql 2005. Whenever I try to connect to the named instance
> in Management Studio, it ALWAYS connects to the default instance. I am
> specifying the connection as ServerName\InstanceName. It seems like it
> is ignoring the instance name in the connection request. I have tried
> creating an alias, but it does not change the behavior. One special
> note - due to our network structure we must use fully qualified domain
> names when connecting to remote servers. The my local server and my
> remote server are in different sub-domains:
> local server = ServerA.HQ.domain.com
> remote server = ServerX.Remote.domain.com
> One interesting observation is that I am able to connect to the remote
> server from a different db server in the same sub-domain without any
> problems. i.e. ServerY.remote.domain.com can connect to
> ServerX.remote.domain.com.
> I know there was a bug in MDAC that was similar to this, but it was
> supposedly fixed in MDAC 2.8 SP1. I wonder if the same bug crept into
> the SQLNI code?
>

Connecting to named instance in Management Studio fails

I have a remote server with a default instance of Sql 2000 and a named
instance of Sql 2005. Whenever I try to connect to the named instance
in Management Studio, it ALWAYS connects to the default instance. I am
specifying the connection as ServerName\InstanceName. It seems like it
is ignoring the instance name in the connection request. I have tried
creating an alias, but it does not change the behavior. One special
note - due to our network structure we must use fully qualified domain
names when connecting to remote servers. The my local server and my
remote server are in different sub-domains:
local server = ServerA.HQ.domain.com
remote server = ServerX.Remote.domain.com
One interesting observation is that I am able to connect to the remote
server from a different db server in the same sub-domain without any
problems. i.e. ServerY.remote.domain.com can connect to
ServerX.remote.domain.com.
I know there was a bug in MDAC that was similar to this, but it was
supposedly fixed in MDAC 2.8 SP1. I wonder if the same bug crept into
the SQLNI code?check with your network admin. it seems there is firewall rule on udp 1434.
also, try to specify the tcp as part of your connection string.
e.g.
sqlcmd -S"ServerX.Remote.domain.com,tcp#"
-oj
"kmart" <kevmart@.gmail.com> wrote in message
news:1146849746.958318.194980@.v46g2000cwv.googlegroups.com...
>I have a remote server with a default instance of Sql 2000 and a named
> instance of Sql 2005. Whenever I try to connect to the named instance
> in Management Studio, it ALWAYS connects to the default instance. I am
> specifying the connection as ServerName\InstanceName. It seems like it
> is ignoring the instance name in the connection request. I have tried
> creating an alias, but it does not change the behavior. One special
> note - due to our network structure we must use fully qualified domain
> names when connecting to remote servers. The my local server and my
> remote server are in different sub-domains:
> local server = ServerA.HQ.domain.com
> remote server = ServerX.Remote.domain.com
> One interesting observation is that I am able to connect to the remote
> server from a different db server in the same sub-domain without any
> problems. i.e. ServerY.remote.domain.com can connect to
> ServerX.remote.domain.com.
> I know there was a bug in MDAC that was similar to this, but it was
> supposedly fixed in MDAC 2.8 SP1. I wonder if the same bug crept into
> the SQLNI code?
>

Connecting to MDF file over Workgroup

Hi

I've build a client management (Windows) application in VS2005 which works fine on the local development machine but falls over when trying to connect to the SQL Server Express file located on a second machine on the same Workgroup. Several of the apllications will connect to the database file from networked computers.

The error I get when testing the connection or trying to connect via the App is:

-------------------
The file "Z:\BushBreaks.MDF" is on a network path that is not supported for database files.
An attempt to attach and auto-named database for file z:\bushbreaks.mdf failed. A database with the same name exists, or specified file cannot be opened or it is on a UNC share.
-------------------

How can I configure this database and/or connection to be able to allow connections to the MDF file? Please note that security is not an issue if that is at all relevant.

Many Thanks
John

Current you can't use remote database file in your SQL connection. Here is a instruction about AttachDBFileName property in connection string from MSDN:

The name of the primary database file, including the full path name of an attachable database. The path may be absolute or relative by using the DataDirectory substitution string. If DataDirectory is used, the database file must exist within a subdirectory of the directory pointed to by the substitution string.

Note:

Remote server, HTTP, and UNC path names are not supported.

For more information, you can refer to:

http://msdn2.microsoft.com/en-us/library/system.data.sqlclient.sqlconnection.connectionstring.aspx

Connecting to an instance in a cluster

Hello, I just setup a few instances on a cluster. But somehow I cannot
conntect to the instances remotely using SQL Server Management Studio. I can
connect to them locally. I can also connect to the default instance fine. Any
idea?
Thanks!
is the virtual server enabled for remote connections?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Yuhong" <Yuhong@.discussions.microsoft.com> wrote in message
news:065C8B43-891D-41CC-8602-04FB551CFE34@.microsoft.com...
> Hello, I just setup a few instances on a cluster. But somehow I cannot
> conntect to the instances remotely using SQL Server Management Studio. I
> can
> connect to them locally. I can also connect to the default instance fine.
> Any
> idea?
> Thanks!
|||Yes.
"Hilary Cotter" wrote:

> is the virtual server enabled for remote connections?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Yuhong" <Yuhong@.discussions.microsoft.com> wrote in message
> news:065C8B43-891D-41CC-8602-04FB551CFE34@.microsoft.com...
>
>
|||Did you try to connect to the instance using its IP and port directly?
Linchi
"Yuhong" wrote:

> Hello, I just setup a few instances on a cluster. But somehow I cannot
> conntect to the instances remotely using SQL Server Management Studio. I can
> connect to them locally. I can also connect to the default instance fine. Any
> idea?
> Thanks!
|||Did you configure static or dynamic ports? Is the Browser service running
on all cluster nodes?
Anthony Thomas

"Yuhong" <Yuhong@.discussions.microsoft.com> wrote in message
news:05184BB4-026E-4FBF-AD14-8684B121A86F@.microsoft.com...[vbcol=seagreen]
> Yes.
> "Hilary Cotter" wrote:
I[vbcol=seagreen]
fine.[vbcol=seagreen]
|||Browser Service is running on all nodes. Dynamic ports are used by default
and I did not change it. The servers are behind a firewall. I opened port
1434. And port 1433 is open too. I can connect to the default instance fine
remotely and can connect any instances locally.
"Anthony Thomas" wrote:

> Did you configure static or dynamic ports? Is the Browser service running
> on all cluster nodes?
>
> Anthony Thomas
>
> --
> "Yuhong" <Yuhong@.discussions.microsoft.com> wrote in message
> news:05184BB4-026E-4FBF-AD14-8684B121A86F@.microsoft.com...
> I
> fine.
>
>
|||No, I did not try to connect using its IP and port. I did not open the
specific port for the named instances. The cluster is behind the firewall and
only Port 1433 and 1434 are open.
Thanks!
"Linchi Shea" wrote:
[vbcol=seagreen]
> Did you try to connect to the instance using its IP and port directly?
> Linchi
> "Yuhong" wrote:
|||You will need to use the SQL Server Configuration Manager to set a static
port for each named instance. You only need to set it once or each
instance on the cluster. You cannot use port 1434 or 1433. Then you open
the firewall for those ports. Note that you will have to restart each SQL
instance after setting the ports so SQL can bind correctly.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Yuhong" <Yuhong@.discussions.microsoft.com> wrote in message
news:54E0E94E-FAD2-4EDE-86A3-5D63C4E6E5E4@.microsoft.com...[vbcol=seagreen]
> Browser Service is running on all nodes. Dynamic ports are used by default
> and I did not change it. The servers are behind a firewall. I opened port
> 1434. And port 1433 is open too. I can connect to the default instance
> fine
> remotely and can connect any instances locally.
> "Anthony Thomas" wrote:
|||Hi Geoff,
Thanks for your information. There are many IPs in the TCP/IP properties
window in SQL Server Configuration Manager. Which one should I use? Should I
do the lookback adapter IP or do them all? Sorry I am really confused about
this part. The online help is not very clear about this. Thanks again!
"Geoff N. Hiten" wrote:

> You will need to use the SQL Server Configuration Manager to set a static
> port for each named instance. You only need to set it once or each
> instance on the cluster. You cannot use port 1434 or 1433. Then you open
> the firewall for those ports. Note that you will have to restart each SQL
> instance after setting the ports so SQL can bind correctly.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Yuhong" <Yuhong@.discussions.microsoft.com> wrote in message
> news:54E0E94E-FAD2-4EDE-86A3-5D63C4E6E5E4@.microsoft.com...
>

Connecting to a SQL Server 2005 over SSH using PuTTY

I'm having a problem connecting to my remote db from Management Studio, but I
am able to create an ODBC connection from the Data Sources applet in the
Control Panel.
PuTTY is setup to convert localhost:21433 to 192.168.100.242:1433 (the
address of my remote db server).
When I specify localhost:21433, provide the username, password, and catalog
to the Data Sources applet it connects fine. I then can use that DSN in
Visual Studio 2005 as a connection to the db.
However, when I try localhost,21433 in Management Studio, it gives me the
default connection error which talks about not having remote access enabled.
Please give me a hand with this as it is very important that I be able to
use the Management Studio tools for my app development.
Thanks in advance.
Trevor Murphy wrote:
> I'm having a problem connecting to my remote db from Management Studio, but I
> am able to create an ODBC connection from the Data Sources applet in the
> Control Panel.
> PuTTY is setup to convert localhost:21433 to 192.168.100.242:1433 (the
> address of my remote db server).
> When I specify localhost:21433, provide the username, password, and catalog
> to the Data Sources applet it connects fine. I then can use that DSN in
> Visual Studio 2005 as a connection to the db.
> However, when I try localhost,21433 in Management Studio, it gives me the
> default connection error which talks about not having remote access enabled.
> Please give me a hand with this as it is very important that I be able to
> use the Management Studio tools for my app development.
> Thanks in advance.
Does the connection error mention Named Pipes? If so, in the connection
dialog, click on Options, and under Connection Properties, make sure the
protocol explicitly states "TCP/IP".
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||I had gone to options>>connection properties and I set he network protocol to
tcp/ip. I couldn't set the connect to database b/c it wasn't connecting with
the server.
Anything else?
"Tracy McKibben" wrote:

> Trevor Murphy wrote:
> Does the connection error mention Named Pipes? If so, in the connection
> dialog, click on Options, and under Connection Properties, make sure the
> protocol explicitly states "TCP/IP".
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>

Connecting to a SQL Server 2005 over SSH using PuTTY

I'm having a problem connecting to my remote db from Management Studio, but
I
am able to create an ODBC connection from the Data Sources applet in the
Control Panel.
PuTTY is setup to convert localhost:21433 to 192.168.100.242:1433 (the
address of my remote db server).
When I specify localhost:21433, provide the username, password, and catalog
to the Data Sources applet it connects fine. I then can use that DSN in
Visual Studio 2005 as a connection to the db.
However, when I try localhost,21433 in Management Studio, it gives me the
default connection error which talks about not having remote access enabled.
Please give me a hand with this as it is very important that I be able to
use the Management Studio tools for my app development.
Thanks in advance.Trevor Murphy wrote:
> I'm having a problem connecting to my remote db from Management Studio, bu
t I
> am able to create an ODBC connection from the Data Sources applet in the
> Control Panel.
> PuTTY is setup to convert localhost:21433 to 192.168.100.242:1433 (the
> address of my remote db server).
> When I specify localhost:21433, provide the username, password, and catalo
g
> to the Data Sources applet it connects fine. I then can use that DSN in
> Visual Studio 2005 as a connection to the db.
> However, when I try localhost,21433 in Management Studio, it gives me the
> default connection error which talks about not having remote access enable
d.
> Please give me a hand with this as it is very important that I be able to
> use the Management Studio tools for my app development.
> Thanks in advance.
Does the connection error mention Named Pipes? If so, in the connection
dialog, click on Options, and under Connection Properties, make sure the
protocol explicitly states "TCP/IP".
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I had gone to options>>connection properties and I set he network protocol t
o
tcp/ip. I couldn't set the connect to database b/c it wasn't connecting with
the server.
Anything else?
"Tracy McKibben" wrote:

> Trevor Murphy wrote:
> Does the connection error mention Named Pipes? If so, in the connection
> dialog, click on Options, and under Connection Properties, make sure the
> protocol explicitly states "TCP/IP".
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||Trevor Murphy wrote:
> I had gone to options>>connection properties and I set he network protocol
to
> tcp/ip. I couldn't set the connect to database b/c it wasn't connecting wi
th
> the server.
> Anything else?
>
What happens if you telnet to localhost:21433 ?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Hi Tracy,
This is what I got. Forgive my ignorance, but I haven't used telnet in
decades.
Microsoft Telnet> open localhost:21433
Connecting To localhost:21433...Could not open connection to the host, on
port 23: Connect failed
Microsoft Telnet>
"Tracy McKibben" wrote:

> Trevor Murphy wrote:
> What happens if you telnet to localhost:21433 ?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
>|||Trevor Murphy wrote:
> Hi Tracy,
> This is what I got. Forgive my ignorance, but I haven't used telnet in
> decades.
> Microsoft Telnet> open localhost:21433
> Connecting To localhost:21433...Could not open connection to the host, on
> port 23: Connect failed
> Microsoft Telnet>
>
Try this at the command line:
telnet localhost 21433
If it connects, you should get a blank DOS window with a blinking
cursor. Otherwise, you'll get some sort of error message - I'm curious
what that error message will be.
Tracy McKibben
MCDBA
http://www.realsqlguy.com

Connecting to a Remote Server with SQL Management Studio Express

I installed a copy of SQL 2005 Express on another computer here using the
automatic download and install from Microsoft supported by the setup
toolkit.
I can't access this server from another machine on the LAN using SQL
Management Studio Express. I can 'see' the server but cannot connect. Both
machines are running XP, mine is trying to log in as 'Guest'.
Do I need to configure SQL 2005 on the remote machine to use mixed-mode
authentication and try to log in using an SQL password, or is there a way to
make a remote user work with Windows Authentication?
How should I go about this?
Thanks.
You will have to disable the simple filesharhing in XP, otherweise the
client will try to logon using the guest account.
Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||If you haven't done so yet - enable TCP/IP via the SQL Server Surface Area
Configuration tool / Remote Connections on the destination SQL Server. SQL
Server 2005 Express doesn't enable this by default. Also turn on the SQL
Browser service.
M a M
"Jens" wrote:

> You will have to disable the simple filesharhing in XP, otherweise the
> client will try to logon using the guest account.
>
> Jens K. Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
>
|||Thanks. I have done that but apparently have to enable mixed mode
authentication on the server in order to authenticate. How do I do this?
regards.
"M a M" <MaM@.discussions.microsoft.com> wrote in message
news:6045D19B-3B4F-4B27-B3CD-F82DD325E7DA@.microsoft.com...[vbcol=seagreen]
> If you haven't done so yet - enable TCP/IP via the SQL Server Surface Area
> Configuration tool / Remote Connections on the destination SQL Server. SQL
> Server 2005 Express doesn't enable this by default. Also turn on the SQL
> Browser service.
> M a M
> "Jens" wrote:
|||You could simply add the Windows NT account via the Security / Logins of the
Server in question. You have to log into the server locally obviously to make
this change. Either add the NT account or (your request) change the "Server
authentication" to SQL Server and Windows Authentication mode via the
Security tab of the SQL Server properties.
M a M
"Andrew Chalk" wrote:

> Thanks. I have done that but apparently have to enable mixed mode
> authentication on the server in order to authenticate. How do I do this?
> regards.
> "M a M" <MaM@.discussions.microsoft.com> wrote in message
> news:6045D19B-3B4F-4B27-B3CD-F82DD325E7DA@.microsoft.com...
>
>
|||> this change. Either add the NT account or (your request) change the
> "Server
> authentication" to SQL Server and Windows Authentication mode via the ...
How? This is XP with no SQL Management Studio Express. I have to connect
first before I can access the database with SQL MSE. That is the object of
this exercise.
Thanks.
"M a M" <MaM@.discussions.microsoft.com> wrote in message
news:96E18316-203F-46F1-A01D-FDEBE024CCBB@.microsoft.com...[vbcol=seagreen]
> You could simply add the Windows NT account via the Security / Logins of
> the
> Server in question. You have to log into the server locally obviously to
> make
> this change. Either add the NT account or (your request) change the
> "Server
> authentication" to SQL Server and Windows Authentication mode via the
> Security tab of the SQL Server properties.
> M a M
> "Andrew Chalk" wrote:
|||I loaded MSE on the remote machine and changed the logi mode to mixed. After
that, I was able to connect remotely with MSE.
So, my question boils down to this: How do I set the login mode of SQL
Server 2005 Express to mixed WITHOUT Manaagement Studio Express?
Thanks.
"M a M" <MaM@.discussions.microsoft.com> wrote in message
news:96E18316-203F-46F1-A01D-FDEBE024CCBB@.microsoft.com...[vbcol=seagreen]
> You could simply add the Windows NT account via the Security / Logins of
> the
> Server in question. You have to log into the server locally obviously to
> make
> this change. Either add the NT account or (your request) change the
> "Server
> authentication" to SQL Server and Windows Authentication mode via the
> Security tab of the SQL Server properties.
> M a M
> "Andrew Chalk" wrote:
|||HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\MSSQL.1\MSSQLServer change LoginMode from 1 to 2 and restart SQL
Server services.
"Andrew Chalk" wrote:

> I loaded MSE on the remote machine and changed the logi mode to mixed. After
> that, I was able to connect remotely with MSE.
> So, my question boils down to this: How do I set the login mode of SQL
> Server 2005 Express to mixed WITHOUT Manaagement Studio Express?
> Thanks.
> "M a M" <MaM@.discussions.microsoft.com> wrote in message
> news:96E18316-203F-46F1-A01D-FDEBE024CCBB@.microsoft.com...
>
>
|||Thanks!
"M a M" <MaM@.discussions.microsoft.com> wrote in message
news:6DBDB113-6DDE-4FAC-A09E-74FAAECAE75A@.microsoft.com...[vbcol=seagreen]
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
> Server\MSSQL.1\MSSQLServer change LoginMode from 1 to 2 and restart SQL
> Server services.
> "Andrew Chalk" wrote:

Connecting to a Remote Server with SQL Management Studio Express

I installed a copy of SQL 2005 Express on another computer here using the
automatic download and install from Microsoft supported by the setup
toolkit.
I can't access this server from another machine on the LAN using SQL
Management Studio Express. I can 'see' the server but cannot connect. Both
machines are running XP, mine is trying to log in as 'Guest'.
Do I need to configure SQL 2005 on the remote machine to use mixed-mode
authentication and try to log in using an SQL password, or is there a way to
make a remote user work with Windows Authentication?
How should I go about this?
Thanks.You will have to disable the simple filesharhing in XP, otherweise the
client will try to logon using the guest account.
Jens K. Suessmeyer.
http://www.sqlserver2005.de
--

connecting to a linked server using VS2005

hi,

i've currently created a linked server using sql server management studio express (it connects to an oracle database to draw data), i can query it all fine using the query analyzer with sql server etc.

how can i start using the linked server data with visual studio 2005? i can't seem to find the linked server anywhere inside the server explorer, am i suppose to import it / connect to it any specific way so i can start using the data retreived from the linked server?

thanks in advance!

create a view in SQL that reads from this linked server, and in ur server explorer, browse ur view,

Hope this helps

|||

Ramzi.Aynati:

create a view in SQL that reads from this linked server, and in ur server explorer, browse ur view,

Hope this helps

thanks, but how do i create a view?

|||

if you would like to hit linked server in you code just add database name to each object your would like to access. You can run query on server to which you are connected and server will forward your query to linked server. for example if your SQLServer2 is linked server in SQlServer1 you can run query like this om SQLServer1 ( if user you used to link servers have rights to objects in your query)

select * from [SQLserver2].[database].dbo.[tablename]

you can connect results from multiple servers

select * from [SQLserver2].[database].dbo.[tablename]
left join [SQLserver1].[database1].dbo.[tablename1]
ON tablename.aa=tablename1.bb

If you only use linked server in your query you can use OpenQuery which will process data on the linked server and returns only results to you.

SELECT * from OPENQUERY([SQLServer2,' select * from [database].dbo.[tablename]')

Thanks

|||

In your SQL, go to ur query analyzer

and type

Create View View_name as

SELECT *
FROM TEST1.Northwind.dbo.Orders

//where test is ur linked server

This is it, u got urself a view accessible from ur server explorer

|||

I would not recommend to create view like this because it will work very slow. To create view SQL server will try to load all data required to generate view from linked server to your server so it will generate very heavy network traffic and will be very slow. The better way is to get exactly what you need from your linked server or create view on linked server and access it from your main server.

Best solution will be to use Stored procedure to do this or table returned function (but not everything will work in function)

Thanks

|||

jpazgier:

I would not recommend to create view like this because it will work very slow. To create view SQL server will try to load all data required to generate view from linked server to your server so it will generate very heavy network traffic and will be very slow. The better way is to get exactly what you need from your linked server or create view on linked server and access it from your main server.

Best solution will be to use Stored procedure to do this or table returned function (but not everything will work in function)

Thanks

thanks, i might try both options.. would you happen to know of any tutorials that would put me to the right direction in creating a stored procedure to do this? thanks

|||

Dear Frank

As long as the table ur querying is less than 10000 records, u wont feel a pinch, the difference will be in milli seconds,

The topic jpazgier is raising is for really advanced SQL programming and for huge amount of records over 1 million

|||

thanks, have given it a go and i get this error message, any idea what i'm doing wrong?

OLE DB error trace [Non-interface error].

Msg 7312, Level 16, State 1, Procedure OracleComDir, Line 3

Invalid use of schema and/or catalog for OLE DB provider 'MSDAORA'. A four-part name was supplied, but the provider does not expose the necessary interfaces to use a catalog and/or schema.

|||nevermind, worked it out, thanks :)|||

Dear Frank

Please dont forget to mark the post that helped u the most as answered for sake of future readers

Glad to be of help my friend

|||

jpazgier:

I would not recommend to create view like this because it will work very slow. To create view SQL server will try to load all data required to generate view from linked server to your server so it will generate very heavy network traffic and will be very slow. The better way is to get exactly what you need from your linked server or create view on linked server and access it from your main server.

Best solution will be to use Stored procedure to do this or table returned function (but not everything will work in function)

Thanks

turns out there's about 500,000 records in the database, so results are generating really slow.

i've been attempting to create a stored procedure, but it's still taking 20 odd seconds to bring up the results, here's a basic summary of my stored procedure:

ALTER PROCEDURE GetOracleData
AS

SELECT
oracle_table1.field1,
oracle_table1.field2,
oracle_table2.field1,
oracle_table2.field2

from
OracleCD..oracle_database1.table1,
OracleCD..oracle_database2.table2

WHERE
(oracle_table1.field1 = oracle_table2.field1) AND
(oracle_table1.field2 = oracle_table2.field2)

OracleCD = name of the linked server i created, i'm thinking the fact that i'm calling the data from the linked server is the reason why it's taking soo long for the data to load? what's the best way to call upon data from different databases in a stored procedure?

thanks in advance!

connecting to a distant SQL server installed on VISTA

Hi,
I'm running an SQL server 2005 on a VISTA based machine.
When I use the management studio from the local machine everything
looks fine.
When I try to connect to that server using a managment tool from a
distant machine I'm able to do so but whan I connect to the server I
do not see the 'green play icon' but a white empty circle nor can I
stop\start that instance.
I'm able to connect to that server and use it from distant but the
connection is quite slow and has many unexplained delays.
tcp 1433 and udp 1434 are opened and both named pipes and TCP\IP are
enabled.
Am I missing something ?
thnak you for your response.
Gilad.
Gilad,
Can you give us more detail about what you mean when you say a distant
server? Are you connecting to a network through a VPN and connecting to a
server?
Can you connect to a distant server that has access to the SQL Server but
through its own local network? (for example with a remote desktop connection)
The connection is solid and if something happens to the connection, you can
log back into the machine on the local network and continue where you left
off.
A slow VPN that can be disconnected in the middle of a query is a shaky
method for doing remote work.
Regards,
Jamie
"Gilad" wrote:

> Hi,
> I'm running an SQL server 2005 on a VISTA based machine.
> When I use the management studio from the local machine everything
> looks fine.
> When I try to connect to that server using a managment tool from a
> distant machine I'm able to do so but whan I connect to the server I
> do not see the 'green play icon' but a white empty circle nor can I
> stop\start that instance.
> I'm able to connect to that server and use it from distant but the
> connection is quite slow and has many unexplained delays.
> tcp 1433 and udp 1434 are opened and both named pipes and TCP\IP are
> enabled.
> Am I missing something ?
> thnak you for your response.
> Gilad.
>

connecting to a distant SQL server installed on VISTA

Hi,
I'm running an SQL server 2005 on a VISTA based machine.
When I use the management studio from the local machine everything
looks fine.
When I try to connect to that server using a managment tool from a
distant machine I'm able to do so but whan I connect to the server I
do not see the 'green play icon' but a white empty circle nor can I
stop\start that instance.
I'm able to connect to that server and use it from distant but the
connection is quite slow and has many unexplained delays.
tcp 1433 and udp 1434 are opened and both named pipes and TCP\IP are
enabled.
Am I missing something ?
thnak you for your response.
Gilad.Gilad,
Can you give us more detail about what you mean when you say a distant
server? Are you connecting to a network through a VPN and connecting to a
server?
Can you connect to a distant server that has access to the SQL Server but
through its own local network? (for example with a remote desktop connection)
The connection is solid and if something happens to the connection, you can
log back into the machine on the local network and continue where you left
off.
A slow VPN that can be disconnected in the middle of a query is a shaky
method for doing remote work.
--
Regards,
Jamie
"Gilad" wrote:
> Hi,
> I'm running an SQL server 2005 on a VISTA based machine.
> When I use the management studio from the local machine everything
> looks fine.
> When I try to connect to that server using a managment tool from a
> distant machine I'm able to do so but whan I connect to the server I
> do not see the 'green play icon' but a white empty circle nor can I
> stop\start that instance.
> I'm able to connect to that server and use it from distant but the
> connection is quite slow and has many unexplained delays.
> tcp 1433 and udp 1434 are opened and both named pipes and TCP\IP are
> enabled.
> Am I missing something ?
> thnak you for your response.
> Gilad.
>

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
>
>