We are having all kinds of issues with named instances for SQL 2000.
I am trying to connect to a SQL Server 2000 named instance on a different subnet and get an error. I cannot connect with ODBC or our web app.
I am using the port number for the alias that I created in the SQL Client Utility. We can connect to default instances without a problem, but not the named instances.
The SQL Server is 2000 build 2040 (Service pack 4 with a hot fix.) The server is listening on port 1223. In the ODBC connection I click on the Network Config and create an alias with the named instance such as SQLVSN\SQLNI and specify port 1223. I have also tried adding the port to the connection string in the ASP include file (SQLVSN\SQLNI,1223). If I do the same thing with a default instance on the network, both the app and ODBC work fine. It is only when I use a named instance.
Very frustrated. Thanks for any help you can provideIt shouldn't be much different. Here is a connection string in ASP which I use for our internal webpage.
Set objConn = Server.CreateObject("ADODB.Connection")
Set objrs = Server.CreateObject("ADODB.Recordset")
objConn.Open "Driver={SQL Server};" & _
"Server=SERVERNAME\INSTANCENAME;" & _
"Database=DATABASENAME;" & _
"Network=NETWORKNAME;" & _
"Uid=USERNAME;" & _
"Pwd=PASSWORD"
str = "SELECT bla bla FROM bla bla WHERE bla bla;"
set objrs=objConn.execute(str)
I know all about security and dynamic SQL queries; this is just a proof of concept|||That's what we have. The app works on one of the servers that are on the same subnet, but not the one on a different subnet.
The one that is on the other subnet can't connect when I try to create an ODBC connection as a test. This goes for all named instances in the company, for which we have quite a few because we have several SQL Server Cluster Groups setup. However, I can create an ODBC connection to a default instance with no problem what so ever.
I have to be overlooking something when it comes to named instances.
Showing posts with label instances. Show all posts
Showing posts with label instances. Show all posts
Tuesday, March 27, 2012
Connecting to SQL Server 2000 Named Instances
I have the following problem;
I fully understand that to connect to a named instance of SQL Server you need to use the ServerName\SQLInstanceName. The problem I have is that I have a SQL Server in a different zone. I can connect to the Default instance by IP Address or the ServerName.zone.domain.org. (e.g. MySQLServer.zone1.mydomain.org).
However, the same thing does not work for the Named Instance. It seems to be named instance or nothing.
How can I connect to this named instance across network zones?:Suse the instance name with the ip address, like 1.2.3.4\myInstance and you ought to be fine.
-PatP|||That did it. Thanks!!! :beer:
I fully understand that to connect to a named instance of SQL Server you need to use the ServerName\SQLInstanceName. The problem I have is that I have a SQL Server in a different zone. I can connect to the Default instance by IP Address or the ServerName.zone.domain.org. (e.g. MySQLServer.zone1.mydomain.org).
However, the same thing does not work for the Named Instance. It seems to be named instance or nothing.
How can I connect to this named instance across network zones?:Suse the instance name with the ip address, like 1.2.3.4\myInstance and you ought to be fine.
-PatP|||That did it. Thanks!!! :beer:
Tuesday, March 20, 2012
Connecting to remote Express instance using SSMS
I have a server running SQL Server 2005 Ent. Ed. SP2 and locally, I can see
the default instance and two SQLExpress instances named 'sqlexpress' and
'officeservers', all withing SSMS, and can connect and manage them.
From my workstation, running SQL 2005 Dev, SP2, I can connect to the default
instance on that server, but cannot connect to the express instances. They
both have TCP/IP protocol enabled, along with "Allow Remote COnnections".
I have done the following:
Made myself a member of the local Admin group
Tried using the sa account to connect
nothing seems to work. What am I missing?
TIA
Todd Chittenden
Is the SQLBrowser Service enabled and started?
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:15C51BF6-FF25-435E-B26B-3863344FB81D@.microsoft.com...
>I have a server running SQL Server 2005 Ent. Ed. SP2 and locally, I can see
> the default instance and two SQLExpress instances named 'sqlexpress' and
> 'officeservers', all withing SSMS, and can connect and manage them.
> From my workstation, running SQL 2005 Dev, SP2, I can connect to the
> default
> instance on that server, but cannot connect to the express instances. They
> both have TCP/IP protocol enabled, along with "Allow Remote COnnections".
> I have done the following:
> Made myself a member of the local Admin group
> Tried using the sa account to connect
> nothing seems to work. What am I missing?
> TIA
> --
> Todd Chittenden
>
|||I found it not long after posting the original question:
No, the Browser service was not running. Starting that up enabled me to
connect to it. So that was the answer.
But even before the Enterprise instance was installed, (which includes the
browser service) I was not able to connect. I know I have other machines in
my domain that are running SQL Express. Should I not be able to connect to
them using my SSMS? What do I need to do to make that happen?
I assume that I need membership in the group on the local machine that bears
the SQL Express instance name?
What else? I can't rely on the Browser service in those instances.
Thanks
Todd Chittenden
"Roger Wolter[MSFT]" wrote:
> Is the SQLBrowser Service enabled and started?
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Todd C" <ToddC@.discussions.microsoft.com> wrote in message
> news:15C51BF6-FF25-435E-B26B-3863344FB81D@.microsoft.com...
>
|||SQL Express by default installs as a named instance. Unless you specify the
TCP/IP port in the connection string, you need the sqlbrowser service to
connect to a named instance.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:F4B981A2-4B9A-443E-855B-D53B89FCE511@.microsoft.com...[vbcol=seagreen]
>I found it not long after posting the original question:
> No, the Browser service was not running. Starting that up enabled me to
> connect to it. So that was the answer.
> But even before the Enterprise instance was installed, (which includes the
> browser service) I was not able to connect. I know I have other machines
> in
> my domain that are running SQL Express. Should I not be able to connect to
> them using my SSMS? What do I need to do to make that happen?
> I assume that I need membership in the group on the local machine that
> bears
> the SQL Express instance name?
> What else? I can't rely on the Browser service in those instances.
> Thanks
> --
> Todd Chittenden
>
> "Roger Wolter[MSFT]" wrote:
the default instance and two SQLExpress instances named 'sqlexpress' and
'officeservers', all withing SSMS, and can connect and manage them.
From my workstation, running SQL 2005 Dev, SP2, I can connect to the default
instance on that server, but cannot connect to the express instances. They
both have TCP/IP protocol enabled, along with "Allow Remote COnnections".
I have done the following:
Made myself a member of the local Admin group
Tried using the sa account to connect
nothing seems to work. What am I missing?
TIA
Todd Chittenden
Is the SQLBrowser Service enabled and started?
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:15C51BF6-FF25-435E-B26B-3863344FB81D@.microsoft.com...
>I have a server running SQL Server 2005 Ent. Ed. SP2 and locally, I can see
> the default instance and two SQLExpress instances named 'sqlexpress' and
> 'officeservers', all withing SSMS, and can connect and manage them.
> From my workstation, running SQL 2005 Dev, SP2, I can connect to the
> default
> instance on that server, but cannot connect to the express instances. They
> both have TCP/IP protocol enabled, along with "Allow Remote COnnections".
> I have done the following:
> Made myself a member of the local Admin group
> Tried using the sa account to connect
> nothing seems to work. What am I missing?
> TIA
> --
> Todd Chittenden
>
|||I found it not long after posting the original question:
No, the Browser service was not running. Starting that up enabled me to
connect to it. So that was the answer.
But even before the Enterprise instance was installed, (which includes the
browser service) I was not able to connect. I know I have other machines in
my domain that are running SQL Express. Should I not be able to connect to
them using my SSMS? What do I need to do to make that happen?
I assume that I need membership in the group on the local machine that bears
the SQL Express instance name?
What else? I can't rely on the Browser service in those instances.
Thanks
Todd Chittenden
"Roger Wolter[MSFT]" wrote:
> Is the SQLBrowser Service enabled and started?
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Todd C" <ToddC@.discussions.microsoft.com> wrote in message
> news:15C51BF6-FF25-435E-B26B-3863344FB81D@.microsoft.com...
>
|||SQL Express by default installs as a named instance. Unless you specify the
TCP/IP port in the connection string, you need the sqlbrowser service to
connect to a named instance.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:F4B981A2-4B9A-443E-855B-D53B89FCE511@.microsoft.com...[vbcol=seagreen]
>I found it not long after posting the original question:
> No, the Browser service was not running. Starting that up enabled me to
> connect to it. So that was the answer.
> But even before the Enterprise instance was installed, (which includes the
> browser service) I was not able to connect. I know I have other machines
> in
> my domain that are running SQL Express. Should I not be able to connect to
> them using my SSMS? What do I need to do to make that happen?
> I assume that I need membership in the group on the local machine that
> bears
> the SQL Express instance name?
> What else? I can't rely on the Browser service in those instances.
> Thanks
> --
> Todd Chittenden
>
> "Roger Wolter[MSFT]" wrote:
Connecting to remote Express instance using SSMS
I have a server running SQL Server 2005 Ent. Ed. SP2 and locally, I can see
the default instance and two SQLExpress instances named 'sqlexpress' and
'officeservers', all withing SSMS, and can connect and manage them.
From my workstation, running SQL 2005 Dev, SP2, I can connect to the default
instance on that server, but cannot connect to the express instances. They
both have TCP/IP protocol enabled, along with "Allow Remote COnnections".
I have done the following:
Made myself a member of the local Admin group
Tried using the sa account to connect
nothing seems to work. What am I missing?
TIA
--
Todd ChittendenIs the SQLBrowser Service enabled and started?
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:15C51BF6-FF25-435E-B26B-3863344FB81D@.microsoft.com...
>I have a server running SQL Server 2005 Ent. Ed. SP2 and locally, I can see
> the default instance and two SQLExpress instances named 'sqlexpress' and
> 'officeservers', all withing SSMS, and can connect and manage them.
> From my workstation, running SQL 2005 Dev, SP2, I can connect to the
> default
> instance on that server, but cannot connect to the express instances. They
> both have TCP/IP protocol enabled, along with "Allow Remote COnnections".
> I have done the following:
> Made myself a member of the local Admin group
> Tried using the sa account to connect
> nothing seems to work. What am I missing?
> TIA
> --
> Todd Chittenden
>|||I found it not long after posting the original question:
No, the Browser service was not running. Starting that up enabled me to
connect to it. So that was the answer.
But even before the Enterprise instance was installed, (which includes the
browser service) I was not able to connect. I know I have other machines in
my domain that are running SQL Express. Should I not be able to connect to
them using my SSMS? What do I need to do to make that happen?
I assume that I need membership in the group on the local machine that bears
the SQL Express instance name?
What else? I can't rely on the Browser service in those instances.
Thanks
--
Todd Chittenden
"Roger Wolter[MSFT]" wrote:
> Is the SQLBrowser Service enabled and started?
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Todd C" <ToddC@.discussions.microsoft.com> wrote in message
> news:15C51BF6-FF25-435E-B26B-3863344FB81D@.microsoft.com...
>|||SQL Express by default installs as a named instance. Unless you specify the
TCP/IP port in the connection string, you need the sqlbrowser service to
connect to a named instance.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:F4B981A2-4B9A-443E-855B-D53B89FCE511@.microsoft.com...[vbcol=seagreen]
>I found it not long after posting the original question:
> No, the Browser service was not running. Starting that up enabled me to
> connect to it. So that was the answer.
> But even before the Enterprise instance was installed, (which includes the
> browser service) I was not able to connect. I know I have other machines
> in
> my domain that are running SQL Express. Should I not be able to connect to
> them using my SSMS? What do I need to do to make that happen?
> I assume that I need membership in the group on the local machine that
> bears
> the SQL Express instance name?
> What else? I can't rely on the Browser service in those instances.
> Thanks
> --
> Todd Chittenden
>
> "Roger Wolter[MSFT]" wrote:
>
the default instance and two SQLExpress instances named 'sqlexpress' and
'officeservers', all withing SSMS, and can connect and manage them.
From my workstation, running SQL 2005 Dev, SP2, I can connect to the default
instance on that server, but cannot connect to the express instances. They
both have TCP/IP protocol enabled, along with "Allow Remote COnnections".
I have done the following:
Made myself a member of the local Admin group
Tried using the sa account to connect
nothing seems to work. What am I missing?
TIA
--
Todd ChittendenIs the SQLBrowser Service enabled and started?
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:15C51BF6-FF25-435E-B26B-3863344FB81D@.microsoft.com...
>I have a server running SQL Server 2005 Ent. Ed. SP2 and locally, I can see
> the default instance and two SQLExpress instances named 'sqlexpress' and
> 'officeservers', all withing SSMS, and can connect and manage them.
> From my workstation, running SQL 2005 Dev, SP2, I can connect to the
> default
> instance on that server, but cannot connect to the express instances. They
> both have TCP/IP protocol enabled, along with "Allow Remote COnnections".
> I have done the following:
> Made myself a member of the local Admin group
> Tried using the sa account to connect
> nothing seems to work. What am I missing?
> TIA
> --
> Todd Chittenden
>|||I found it not long after posting the original question:
No, the Browser service was not running. Starting that up enabled me to
connect to it. So that was the answer.
But even before the Enterprise instance was installed, (which includes the
browser service) I was not able to connect. I know I have other machines in
my domain that are running SQL Express. Should I not be able to connect to
them using my SSMS? What do I need to do to make that happen?
I assume that I need membership in the group on the local machine that bears
the SQL Express instance name?
What else? I can't rely on the Browser service in those instances.
Thanks
--
Todd Chittenden
"Roger Wolter[MSFT]" wrote:
> Is the SQLBrowser Service enabled and started?
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Todd C" <ToddC@.discussions.microsoft.com> wrote in message
> news:15C51BF6-FF25-435E-B26B-3863344FB81D@.microsoft.com...
>|||SQL Express by default installs as a named instance. Unless you specify the
TCP/IP port in the connection string, you need the sqlbrowser service to
connect to a named instance.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:F4B981A2-4B9A-443E-855B-D53B89FCE511@.microsoft.com...[vbcol=seagreen]
>I found it not long after posting the original question:
> No, the Browser service was not running. Starting that up enabled me to
> connect to it. So that was the answer.
> But even before the Enterprise instance was installed, (which includes the
> browser service) I was not able to connect. I know I have other machines
> in
> my domain that are running SQL Express. Should I not be able to connect to
> them using my SSMS? What do I need to do to make that happen?
> I assume that I need membership in the group on the local machine that
> bears
> the SQL Express instance name?
> What else? I can't rely on the Browser service in those instances.
> Thanks
> --
> Todd Chittenden
>
> "Roger Wolter[MSFT]" wrote:
>
Connecting to Named Instances
We have a few servers with named instances, 2003 Server w/ SQL 2000 SP3a
running Named Pipes only.
Our users primarily use IIS 5, 5.1, and 6 to connect to these servers with
ColdFusion and ASP .NET applications. Right now the ASP .NET applications
aren't able to connect to the server, here is an example of the connection
string:
user id=myuser;data source="SQLserver\SQLinstance";initial
catalog=mydatabase;password=mypassword
This doesn't work, and we're not quite sure why. Does any one also have
some good resources on managing multiple instances of SQL server from a SQL
admin and SQL developer point of view?
Thanks,
Trevor
These articles will help you troubleshoot.
265808 INF: How to Connect to an SQL Server 2000 Named Instance with the
http://support.microsoft.com/?id=265808
286303 INF: Behavior of SQL Server 2000 Network Library During Dynamic Port
http://support.microsoft.com/?id=286303
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
running Named Pipes only.
Our users primarily use IIS 5, 5.1, and 6 to connect to these servers with
ColdFusion and ASP .NET applications. Right now the ASP .NET applications
aren't able to connect to the server, here is an example of the connection
string:
user id=myuser;data source="SQLserver\SQLinstance";initial
catalog=mydatabase;password=mypassword
This doesn't work, and we're not quite sure why. Does any one also have
some good resources on managing multiple instances of SQL server from a SQL
admin and SQL developer point of view?
Thanks,
Trevor
These articles will help you troubleshoot.
265808 INF: How to Connect to an SQL Server 2000 Named Instance with the
http://support.microsoft.com/?id=265808
286303 INF: Behavior of SQL Server 2000 Network Library During Dynamic Port
http://support.microsoft.com/?id=286303
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
Monday, March 19, 2012
Connecting to Named Instances
We have a few servers with named instances, 2003 Server w/ SQL 2000 SP3a
running Named Pipes only.
Our users primarily use IIS 5, 5.1, and 6 to connect to these servers with
ColdFusion and ASP .NET applications. Right now the ASP .NET applications
aren't able to connect to the server, here is an example of the connection
string:
user id=myuser;data source="SQLserver\SQLinstance";initial
catalog=mydatabase;password=mypassword
This doesn't work, and we're not quite sure why. Does any one also have
some good resources on managing multiple instances of SQL server from a SQL
admin and SQL developer point of view?
Thanks,
TrevorThese articles will help you troubleshoot.
265808 INF: How to Connect to an SQL Server 2000 Named Instance with the
http://support.microsoft.com/?id=265808
286303 INF: Behavior of SQL Server 2000 Network Library During Dynamic Port
http://support.microsoft.com/?id=286303
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
running Named Pipes only.
Our users primarily use IIS 5, 5.1, and 6 to connect to these servers with
ColdFusion and ASP .NET applications. Right now the ASP .NET applications
aren't able to connect to the server, here is an example of the connection
string:
user id=myuser;data source="SQLserver\SQLinstance";initial
catalog=mydatabase;password=mypassword
This doesn't work, and we're not quite sure why. Does any one also have
some good resources on managing multiple instances of SQL server from a SQL
admin and SQL developer point of view?
Thanks,
TrevorThese articles will help you troubleshoot.
265808 INF: How to Connect to an SQL Server 2000 Named Instance with the
http://support.microsoft.com/?id=265808
286303 INF: Behavior of SQL Server 2000 Network Library During Dynamic Port
http://support.microsoft.com/?id=286303
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
connecting to MSDE on Windows 2003 SBS Server
I have an application (Point of Sale System) that utilizes a MSDE
database. The server came loaded with MSDE instances already and I
installed one for the POS System. The client PCs can see the other 3
MSDE instances, but cannot see the one I installed. Any ideas on how
the new instance can appear on the network. The new instance was not
named. The other three were named instances of MSDE.
hi,
auschnet@.gmail.com wrote:
> I have an application (Point of Sale System) that utilizes a MSDE
> database. The server came loaded with MSDE instances already and I
> installed one for the POS System. The client PCs can see the other 3
> MSDE instances, but cannot see the one I installed. Any ideas on how
> the new instance can appear on the network. The new instance was not
> named. The other three were named instances of MSDE.
please verify the required/desired network protocols are enabled... MSDE
installs by default disabling them and you can override this behavior
providing the
DISABLENETWORKPROTOCOLS=0
parameter to the setup.exe boostrap installer, or later, at run time, using
the Server Network Utility (svrnetcn.exe) and enabling the preferred network
protocol..
additionally, WinXP sp2 ships with a built-in Firewall that's enabled by
default, preventing network connections to... if this is a case, you have to
specify an exception for the service or for the MSDE used port, usually
specifying a subnet or individual remot IP addreses to restrict
connections...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
database. The server came loaded with MSDE instances already and I
installed one for the POS System. The client PCs can see the other 3
MSDE instances, but cannot see the one I installed. Any ideas on how
the new instance can appear on the network. The new instance was not
named. The other three were named instances of MSDE.
hi,
auschnet@.gmail.com wrote:
> I have an application (Point of Sale System) that utilizes a MSDE
> database. The server came loaded with MSDE instances already and I
> installed one for the POS System. The client PCs can see the other 3
> MSDE instances, but cannot see the one I installed. Any ideas on how
> the new instance can appear on the network. The new instance was not
> named. The other three were named instances of MSDE.
please verify the required/desired network protocols are enabled... MSDE
installs by default disabling them and you can override this behavior
providing the
DISABLENETWORKPROTOCOLS=0
parameter to the setup.exe boostrap installer, or later, at run time, using
the Server Network Utility (svrnetcn.exe) and enabling the preferred network
protocol..
additionally, WinXP sp2 ships with a built-in Firewall that's enabled by
default, preventing network connections to... if this is a case, you have to
specify an exception for the service or for the MSDE used port, usually
specifying a subnet or individual remot IP addreses to restrict
connections...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Thursday, March 8, 2012
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...
>
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...
>
Wednesday, March 7, 2012
Connecting to a second instance via VPN
Hi,
I have two SQL SERVER Instances on the computer I am trying to connect to via VPN:
1) TEST
2. TEST/INST2
I can connect to the first with no problems.
When I am trying to connect to the second (with the Enterprise Manager/Query Analyzer and even with isql) - I get the following message:
"SQL SERVER does not exists or access denied".
I use the SQL SERVER user and password to connect (as login sa).
How can I connect to the second instance?
Thanks in advance.you have to make sure that tcp/it is enabled on the server. can you use remote desktop or some other remote access tool to connect to the box? check to see if the service for the named instance is running (this should have been the first suggestion)|||Sorry, I had the instance name wrong...
Thanks for your answer anyway!
I have two SQL SERVER Instances on the computer I am trying to connect to via VPN:
1) TEST
2. TEST/INST2
I can connect to the first with no problems.
When I am trying to connect to the second (with the Enterprise Manager/Query Analyzer and even with isql) - I get the following message:
"SQL SERVER does not exists or access denied".
I use the SQL SERVER user and password to connect (as login sa).
How can I connect to the second instance?
Thanks in advance.you have to make sure that tcp/it is enabled on the server. can you use remote desktop or some other remote access tool to connect to the box? check to see if the service for the named instance is running (this should have been the first suggestion)|||Sorry, I had the instance name wrong...
Thanks for your answer anyway!
Subscribe to:
Posts (Atom)