Remotely Register SQL Server 2005 Express in Enterprise Manager

I have SQL Server 2005 Express installed on a windows server 2003 standard edition. I have configured the windows firewall to allow exceptions for sqlservr.exe and sqlbrowser.exe. I have enabled remote and local connections using tcp/ip & Named Pipes through the Sql Server Surface Area Connection utility. I am able to telnet into the server with: telnet <server ip> <1433>.

Here is the strange part: I am able to connect to the Sql Server remotely from a development machine via Sql Server Management Studio Express, but I am unable to connect to the Sql Server from the same development machine by registering it in Sql Server Enterprise Manager...Is it possible to register SQL Express through Enterprise Manager?

When registering the SQL Express DB in Enterprise Manager I tried both just the (IP Address) of the server and the (IP Address\SQLExpress) as the server/host but I am getting the following errors from enterprise manager:

Just the (IP Address) as the server/host:

Invalid Connection.

ConnectionOpen( Invalid Instance())

(IP Address\SQLEXPRESS) as the server/host:

Sql Server does not exist or access denied. ConnectOpen(Connect()).

Any idea why I can’t register/mount the instance remotely in Enterprise Manager

but I can in Sql Server Management Studio Express?

Thanks,

Greg

You can not use the Enterprise management tools with sql 2005, it is only for sql 2000 and below. The connection layer and management objects are different, but the SQL 2005 Management tools can read the lower version systems. Doing this you will notice that some functions can not be completed on the lower versions due to the differences in connections. For example you can not create a new maintenance plan in the sql 2005 tools to work on sql 2000, but you can edit it after it has been created using the old sql enterprise manager.

Remotely Register SQL Server 2005 Express in Enterprise Manager

I have SQL Server 2005 Express installed on a windows server 2003 standard edition. I have configured the windows firewall to allow exceptions for sqlservr.exe and sqlbrowser.exe. I have enabled remote and local connections using tcp/ip & Named Pipes through the Sql Server Surface Area Connection utility. I am able to telnet into the server with: telnet <server ip> <1433>.

Here is the strange part: I am able to connect to the Sql Server remotely from a development machine via Sql Server Management Studio Express, but I am unable to connect to the Sql Server from the same development machine by registering it in Sql Server Enterprise Manager...Is it possible to register SQL Express through Enterprise Manager?

When registering the SQL Express DB in Enterprise Manager I tried both just the (IP Address) of the server and the (IP Address\SQLExpress) as the server/host but I am getting the following errors from enterprise manager:

Just the (IP Address) as the server/host:

Invalid Connection.

ConnectionOpen( Invalid Instance())

(IP Address\SQLEXPRESS) as the server/host:

Sql Server does not exist or access denied. ConnectOpen(Connect()).

Any idea why I can’t register/mount the instance remotely in Enterprise Manager

but I can in Sql Server Management Studio Express?

Thanks,

Greg

You will not be able to register a sql2k5 on EM. EM uses sql2k dmo which can't be used to manage sql2k5.

You will have to use sql2k5 mgmt tool to manage sqlexpress/sql2k5 instances.|||

Hi OJ,

Thanks for the reply, I was afraid this was going to be the case. Well so here is the follow up to my question.

I am using Sql Server Management Studio Express (SSMSE)...so will I be able to connect/register a sql2k server to SSMSE?

Basically I want to export the data from my sql2K DB into my sql2k5 express DB so will I be able to do that with SSMSE or will I need the full version of Sql Server Management Studio?

Thanks,

Greg

|||I haven't explicitly looked at ssmse. However, I believe it uses smo. Thus, it's capable to connecting to sql2k and manage it.sql

Remotely connecting

I am kinda new to this.

Question:
I am trying to set up server.
I have installed SQL 2005 standard.

And now I am trying to log in through TCP/IP..
I went to SQL Server Config Mgmt and Enabled TCP/IP
Double checked IP address and made it Active and enabled it.

Now I tried to connect Management Studio using that IP and it doesnt log in.

Does anyone knows good links to guidelines on how to set up server, login etc.

Thank you very muchDid you restart the service ? See my screencast on www.sqlserver2005.de . You have to restart to make changes effective.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de|||

check your surface area configuration for connection. check the ooption that says you want to accept connection from a remote connection. The only connection allowed by default is local

start>programs>micrsoft sql server 2005>configuration tools>surface area configuration>configuration for services and connection>remote connection>local and remote connection

from there you'll know what to do

Remote User Connection to SQL Server 7 Standard Edition

Is it possible to connect a remote user (in a wide area network) to a
database running on SQL Server 7 Standard Edition.
Do I need the Enterprise Edition to accomplish this?
Yes (to the first)
and
No (to the second)
Mike John
"guez" <guez@.discussions.microsoft.com> wrote in message
news:C4A2552E-74CA-4DDF-A1D1-4A1E05FB773C@.microsoft.com...
> Is it possible to connect a remote user (in a wide area network) to a
> database running on SQL Server 7 Standard Edition.
> Do I need the Enterprise Edition to accomplish this?

Remote User Connection to SQL Server 7 Standard Edition

Is it possible to connect a remote user (in a wide area network) to a
database running on SQL Server 7 Standard Edition.
Do I need the Enterprise Edition to accomplish this?Yes (to the first)
and
No (to the second)
Mike John
"guez" <guez@.discussions.microsoft.com> wrote in message
news:C4A2552E-74CA-4DDF-A1D1-4A1E05FB773C@.microsoft.com...
> Is it possible to connect a remote user (in a wide area network) to a
> database running on SQL Server 7 Standard Edition.
> Do I need the Enterprise Edition to accomplish this?

Remote User Connection to SQL Server 7 Standard Edition

Is it possible to connect a remote user (in a wide area network) to a
database running on SQL Server 7 Standard Edition.
Do I need the Enterprise Edition to accomplish this?Yes (to the first)
and
No (to the second)
Mike John
"guez" <guez@.discussions.microsoft.com> wrote in message
news:C4A2552E-74CA-4DDF-A1D1-4A1E05FB773C@.microsoft.com...
> Is it possible to connect a remote user (in a wide area network) to a
> database running on SQL Server 7 Standard Edition.
> Do I need the Enterprise Edition to accomplish this?sql

Remote logins for SQL 2000?

Hi all,
A company recently came in and setup SQL 2000 standard edition on our
Windows 2003 server. I've noticed that the password they setup for the SQL
user they created is not very secure. I am new to SQL, and I was wondering
if there is a way to remotely login to it? If not, I'll probably keep the
password the same, but if there is a way to log in remotely, I will
definately have to change it.
The user they created can be found under the Users section of the database
they setup and has the following access:
public
db_datareader
db_datawriterHi
Is it Window Authetntication or Mixed?

> Windows 2003 server. I've noticed that the password they setup for the
> SQL
> user they created is not very secure.
They created logins first to SQL Server and then added them to the database
"supersonic_oasis" <supersonicoasis@.discussions.microsoft.com> wrote in
message news:C9FE03CC-EF5A-414E-A103-B14F50EB13AB@.microsoft.com...
> Hi all,
> A company recently came in and setup SQL 2000 standard edition on our
> Windows 2003 server. I've noticed that the password they setup for the
> SQL
> user they created is not very secure. I am new to SQL, and I was
> wondering
> if there is a way to remotely login to it? If not, I'll probably keep the
> password the same, but if there is a way to log in remotely, I will
> definately have to change it.
> The user they created can be found under the Users section of the database
> they setup and has the following access:
> public
> db_datareader
> db_datawriter|||Yes you can remotely log into it, subject to various network security
issues of course.
J.
On Mon, 1 May 2006 04:22:01 -0700, supersonic_oasis
<supersonicoasis@.discussions.microsoft.com> wrote:

>Hi all,
>A company recently came in and setup SQL 2000 standard edition on our
>Windows 2003 server. I've noticed that the password they setup for the SQL
>user they created is not very secure. I am new to SQL, and I was wondering
>if there is a way to remotely login to it? If not, I'll probably keep the
>password the same, but if there is a way to log in remotely, I will
>definately have to change it.
>The user they created can be found under the Users section of the database
>they setup and has the following access:
>public
>db_datareader
>db_datawriter

Remote logins for SQL 2000?

Hi all,
A company recently came in and setup SQL 2000 standard edition on our
Windows 2003 server. I've noticed that the password they setup for the SQL
user they created is not very secure. I am new to SQL, and I was wondering
if there is a way to remotely login to it? If not, I'll probably keep the
password the same, but if there is a way to log in remotely, I will
definately have to change it.
The user they created can be found under the Users section of the database
they setup and has the following access:
public
db_datareader
db_datawriterHi
Is it Window Authetntication or Mixed?
> Windows 2003 server. I've noticed that the password they setup for the
> SQL
> user they created is not very secure.
They created logins first to SQL Server and then added them to the database
"supersonic_oasis" <supersonicoasis@.discussions.microsoft.com> wrote in
message news:C9FE03CC-EF5A-414E-A103-B14F50EB13AB@.microsoft.com...
> Hi all,
> A company recently came in and setup SQL 2000 standard edition on our
> Windows 2003 server. I've noticed that the password they setup for the
> SQL
> user they created is not very secure. I am new to SQL, and I was
> wondering
> if there is a way to remotely login to it? If not, I'll probably keep the
> password the same, but if there is a way to log in remotely, I will
> definately have to change it.
> The user they created can be found under the Users section of the database
> they setup and has the following access:
> public
> db_datareader
> db_datawriter|||Yes you can remotely log into it, subject to various network security
issues of course.
J.
On Mon, 1 May 2006 04:22:01 -0700, supersonic_oasis
<supersonicoasis@.discussions.microsoft.com> wrote:
>Hi all,
>A company recently came in and setup SQL 2000 standard edition on our
>Windows 2003 server. I've noticed that the password they setup for the SQL
>user they created is not very secure. I am new to SQL, and I was wondering
>if there is a way to remotely login to it? If not, I'll probably keep the
>password the same, but if there is a way to log in remotely, I will
>definately have to change it.
>The user they created can be found under the Users section of the database
>they setup and has the following access:
>public
>db_datareader
>db_datawriter

Remote Connection to Analysis Services using VPN

Given that MS Analysis Services does not support standard SQL Server
Authentication (thus requiring windows user accounts), is it possible for a
remote client PC, connected to a network using a VPN, to be authenticated on
an Analysis Server if it is not part of the host domain? If so, how can this
be achieved?
Is there a way of using the anonymous login account?
If not, is this not a strange inconsistency with SQL server, and are there
plans to address this with Yukon?
Many Thanks
Simon Kirk
I am running into the same problem. Currently we are kludging this by
creating a "pass-thru" user on the server with the same uid/pwd as the
client. Also, the user has to be an admin on the Analysis Server box. I'd
love to know if anyone has found a more direct way to remotely register an
Analysis Server.
Ken Collier
"Simon Kirk" wrote:

> Given that MS Analysis Services does not support standard SQL Server
> Authentication (thus requiring windows user accounts), is it possible for a
> remote client PC, connected to a network using a VPN, to be authenticated on
> an Analysis Server if it is not part of the host domain? If so, how can this
> be achieved?
> Is there a way of using the anonymous login account?
> If not, is this not a strange inconsistency with SQL server, and are there
> plans to address this with Yukon?
> Many Thanks
> Simon Kirk
>

Remote Connection to Analysis Services using VPN

Given that MS Analysis Services does not support standard SQL Server
Authentication (thus requiring windows user accounts), is it possible for a
remote client PC, connected to a network using a VPN, to be authenticated on
an Analysis Server if it is not part of the host domain? If so, how can this
be achieved?
Is there a way of using the anonymous login account?
If not, is this not a strange inconsistency with SQL server, and are there
plans to address this with Yukon?
Many Thanks
Simon KirkI am running into the same problem. Currently we are kludging this by
creating a "pass-thru" user on the server with the same uid/pwd as the
client. Also, the user has to be an admin on the Analysis Server box. I'd
love to know if anyone has found a more direct way to remotely register an
Analysis Server.
Ken Collier
"Simon Kirk" wrote:

> Given that MS Analysis Services does not support standard SQL Server
> Authentication (thus requiring windows user accounts), is it possible for
a
> remote client PC, connected to a network using a VPN, to be authenticated
on
> an Analysis Server if it is not part of the host domain? If so, how can th
is
> be achieved?
> Is there a way of using the anonymous login account?
> If not, is this not a strange inconsistency with SQL server, and are there
> plans to address this with Yukon?
> Many Thanks
> Simon Kirk
>

Remote Connection problems, I've read many a thread on this and nothing has worked!

Hi, I am trying to enable remote access on a SQL Server 2005 standard edition instance. I have enabled it in the properties using the Management studio and have enabled it under Sql Server Surface Area Configuration under "Database engine".

But it didn't work. I know for a fact that my connection string is correct (I tested it on the actual machine)

So I checked everything again and I noticed in the Sql Server Surface Area under "Analysis Services" there is another "remote connection" checkbox to be enabled, however it won't let me enable it there because it says the "Sql Browser" is not started. I checked and the Sql Browser is started.

I'm thinking maybe the problem there is that I have an instance of SQL 2000 running and perhaps it is the sql browser for that (I can remotely connect ot my SQL 2000 instance).

I checked under Computer management -> services and their is no SQL Browser for the instance of SQL 2005. Not even a thing to enable. Just the Default instance SQL Browser, which is for my SQL 2000 instance. Am I missing something here?

Also there is no SQL Browser to enable in the management or Surface Area Configuration programs.

I have also tried to connect using the default port number (1433) and the IP (to bypass the need for the SQL Browser). It apparently finds my Server 2000 instance because it doesn't accept my user name and password and connot find the specific database (note: I verified the username and pswd are correct by testing the values on the SQL machine). How do I find what port number a specific instance of SQL Server is running on?

Hi,

the fact that you are using the default instance of SQL Server 2000 on your computer and that you can connect to the SQL Server 2k with the default settings (1433) indicates that SQL Server 2l5 is installed on another port than 1433, because ports can′t be shared. So try to see on which port you installed SQL Server 2k and on therefore on which port it is listening. Then specify the port within your connection string with the following syntax:

MachineName\instanceName,Portnumber

HTH; Jens Suessmeyer.

http://www.sqlserver2005.de
|||

I've tried figuring out what port the SQL 2005 is running on by running a port scan, but nothing really jumped out at me other than the 1433, which the SQL 2000 is running on.

What is a good way to find out what port the SQL 2005 is running on?

|||

Hi,

you can have a look at:

http://support.microsoft.com/default.aspx?scid=kb;en-us;823938

The port which SQL Server is listening to can be retrieved via looking in the eventlog or using the statement xp_readerrorlog which shows up something like "SQL Server listening on xxx.xxx.xxx.xxx:PortNumber"

HTH, Jens Suessmeyer.

http//www.sqlserver2005.de