Hi,
We have just had a 64-bit SQL Server 2000 cluster installed in our
network and I am having difficulties connecting to it.
The named instance I am trying to access is 192.168.0.108\DX
I can connect to it from a machine on the same subnet using Enterprise
Manager, but not from a machine on another subnet (192.168.14.0), when
attempiting EM just stops responding. The weird thing is that I can
connect using Query Analyzer, but not EM (obviously using the same
connection details).
Does anybody have any suggestions to what might be causing this
behaviour?
The client computer I use is a Windows XP Professional with SP2 and
client connectivity tools for SQL Server 2000. I have tried disabling
the firewall, which didn't help. I can connect to another SQL Server
(default instance, 32-bit, non-clustered) on the other network with
EM.
Regards,
Ville Tuomola
Have you tried pinging the server when you can't connect?
Have you checked the registration/connection properties for
the server in Enterprise Manager? Are you sure you aren't
just getting a login timeout? You can increase the login
timeout from the menu go to Tools then Options. On the
Advanced tab, increase the login timeout to a value higher
than the default 4 seconds.
-Sue
On 7 Oct 2004 01:11:35 -0700, vtuomola@.gmail.com (Ville
Tuomola) wrote:
>Hi,
>We have just had a 64-bit SQL Server 2000 cluster installed in our
>network and I am having difficulties connecting to it.
>The named instance I am trying to access is 192.168.0.108\DX
>I can connect to it from a machine on the same subnet using Enterprise
>Manager, but not from a machine on another subnet (192.168.14.0), when
>attempiting EM just stops responding. The weird thing is that I can
>connect using Query Analyzer, but not EM (obviously using the same
>connection details).
>Does anybody have any suggestions to what might be causing this
>behaviour?
>The client computer I use is a Windows XP Professional with SP2 and
>client connectivity tools for SQL Server 2000. I have tried disabling
>the firewall, which didn't help. I can connect to another SQL Server
>(default instance, 32-bit, non-clustered) on the other network with
>EM.
>Regards,
>Ville Tuomola
Showing posts with label cluster. Show all posts
Showing posts with label cluster. Show all posts
Monday, March 19, 2012
Sunday, March 11, 2012
Connecting to cluster instance from .NET
Hi
Apologies if this isn't the right forum.
I have an instance of sql (2005) setup called SQL1\SQL1
I am trying to connect to a database (hm1) using the following connection
string in my web.config:
server=SQL1\SQL1;database=hm1;uid=hm1;pwd=hm1;
...but it can't find it. I need to know if this is the correct way to
address an instance in the connection string - I've tried
server=10.0.0.8\SQL1;
and
server=10.0.0.8;database=SQL1\hm1;
But neither work. On the SQL server itself, apart from naming the instance,
are there any other configuration settings I might be missing? (Unfortunately
I didn't set the server up and I know next to nothing about SQL clustering)
I feel like this a bit of a dumb question but any help really appreciated.
Ed
Will this help:
http://www.connectionstrings.com/?carrier=sqlserver
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
..
"edwaldo" <edwaldo@.discussions.microsoft.com> wrote in message
news:C37E6C7F-DC56-46F1-9001-32104E89F9D0@.microsoft.com...
Hi
Apologies if this isn't the right forum.
I have an instance of sql (2005) setup called SQL1\SQL1
I am trying to connect to a database (hm1) using the following connection
string in my web.config:
server=SQL1\SQL1;database=hm1;uid=hm1;pwd=hm1;
...but it can't find it. I need to know if this is the correct way to
address an instance in the connection string - I've tried
server=10.0.0.8\SQL1;
and
server=10.0.0.8;database=SQL1\hm1;
But neither work. On the SQL server itself, apart from naming the instance,
are there any other configuration settings I might be missing?
(Unfortunately
I didn't set the server up and I know next to nothing about SQL clustering)
I feel like this a bit of a dumb question but any help really appreciated.
Ed
|||And take a look at http://support.microsoft.com/kb/328306. Connecting to a
clustered instance is not that different from connecting to a standalone
instance.
By the way, when you said "it can't find it", what was it, the server or the
database?
Linchi
"edwaldo" wrote:
> Hi
> Apologies if this isn't the right forum.
> I have an instance of sql (2005) setup called SQL1\SQL1
> I am trying to connect to a database (hm1) using the following connection
> string in my web.config:
> server=SQL1\SQL1;database=hm1;uid=hm1;pwd=hm1;
> ..but it can't find it. I need to know if this is the correct way to
> address an instance in the connection string - I've tried
> server=10.0.0.8\SQL1;
> and
> server=10.0.0.8;database=SQL1\hm1;
> But neither work. On the SQL server itself, apart from naming the instance,
> are there any other configuration settings I might be missing? (Unfortunately
> I didn't set the server up and I know next to nothing about SQL clustering)
> I feel like this a bit of a dumb question but any help really appreciated.
> Ed
|||Thanks for your help - I'll take a look at that article.
I'm getting the message 'SQL Server does not exist or access is denied" in
my .NET app. Not sure if it's the server or the database that I can't
connect to, I can ping the server but that's it. Is there a simple way to
test database connectivity to the instance from my web server?
Thanks again.
"Linchi Shea" wrote:
[vbcol=seagreen]
> And take a look at http://support.microsoft.com/kb/328306. Connecting to a
> clustered instance is not that different from connecting to a standalone
> instance.
> By the way, when you said "it can't find it", what was it, the server or the
> database?
> Linchi
> "edwaldo" wrote:
|||> I'm getting the message 'SQL Server does not exist or access is denied" in
Then that KB article will definitely help. At least, it would get you close
to what may have caused it. If not, post back with what you have tried.
Linchi
"edwaldo" wrote:
[vbcol=seagreen]
> Thanks for your help - I'll take a look at that article.
> I'm getting the message 'SQL Server does not exist or access is denied" in
> my .NET app. Not sure if it's the server or the database that I can't
> connect to, I can ping the server but that's it. Is there a simple way to
> test database connectivity to the instance from my web server?
> Thanks again.
>
> "Linchi Shea" wrote:
|||Can you connect to it through SSIS or SQLCMD?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
..
"edwaldo" <edwaldo@.discussions.microsoft.com> wrote in message
news:5EB601E4-CE5D-4A52-BCFE-B8C599CFEF89@.microsoft.com...
Thanks for your help - I'll take a look at that article.
I'm getting the message 'SQL Server does not exist or access is denied" in
my .NET app. Not sure if it's the server or the database that I can't
connect to, I can ping the server but that's it. Is there a simple way to
test database connectivity to the instance from my web server?
Thanks again.
"Linchi Shea" wrote:
[vbcol=seagreen]
> And take a look at http://support.microsoft.com/kb/328306. Connecting to a
> clustered instance is not that different from connecting to a standalone
> instance.
> By the way, when you said "it can't find it", what was it, the server or
> the
> database?
> Linchi
> "edwaldo" wrote:
|||Thanks to both of you for your help.
Is SQLCMD for Sql Express only? I am running Server 2005. The machine I'm
trying to connect FROM is not running SQL.
I hadn't heard of SSIS - do you know the syntax I should be using to test
connectivity?
Thanks,
Ed
"Tom Moreau" wrote:
> Can you connect to it through SSIS or SQLCMD?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> ..
> "edwaldo" <edwaldo@.discussions.microsoft.com> wrote in message
> news:5EB601E4-CE5D-4A52-BCFE-B8C599CFEF89@.microsoft.com...
> Thanks for your help - I'll take a look at that article.
> I'm getting the message 'SQL Server does not exist or access is denied" in
> my .NET app. Not sure if it's the server or the database that I can't
> connect to, I can ping the server but that's it. Is there a simple way to
> test database connectivity to the instance from my web server?
> Thanks again.
>
> "Linchi Shea" wrote:
>
>
|||I should have said SSMS, not SSIS. (Too many acronyms to remember in SQL
2005!) SSMS = SQL Server Management Studio. Both it and SQLCMD (a command
line utility) are part of the SQL Server client tools. You should have
those on the server. If not, get the install disk and install them there.
At that point, you can log onto SQL Server locally. If you can't, then
there is probably a security issue - i.e. wrong login/password.
If that all works, then install the client tools on another machine and see
if you can connect to the server from them, using the same credentials as
you did previously. Let us know what happens and we can take it further.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
..
"edwaldo" <edwaldo@.discussions.microsoft.com> wrote in message
news:3B0450DF-DA21-4686-9B0C-E8EC65570459@.microsoft.com...
Thanks to both of you for your help.
Is SQLCMD for Sql Express only? I am running Server 2005. The machine I'm
trying to connect FROM is not running SQL.
I hadn't heard of SSIS - do you know the syntax I should be using to test
connectivity?
Thanks,
Ed
"Tom Moreau" wrote:
> Can you connect to it through SSIS or SQLCMD?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> ..
> "edwaldo" <edwaldo@.discussions.microsoft.com> wrote in message
> news:5EB601E4-CE5D-4A52-BCFE-B8C599CFEF89@.microsoft.com...
> Thanks for your help - I'll take a look at that article.
> I'm getting the message 'SQL Server does not exist or access is denied" in
> my .NET app. Not sure if it's the server or the database that I can't
> connect to, I can ping the server but that's it. Is there a simple way to
> test database connectivity to the instance from my web server?
> Thanks again.
>
> "Linchi Shea" wrote:
>
>
|||Can you TELNET to the assigned service port? Say, for example, that SQL
Server is listening on TCP 1433. Then if you TELNET <ip address or server
name> <port number>, you should get a black screen, which means it
successfully connected. If it can't find the server or port, then you have
a server configuration issue. If you connect successfully, then you have a
client configuration issue.
Sincerely,
Anthony Thomas
"edwaldo" <edwaldo@.discussions.microsoft.com> wrote in message
news:5EB601E4-CE5D-4A52-BCFE-B8C599CFEF89@.microsoft.com...[vbcol=seagreen]
> Thanks for your help - I'll take a look at that article.
> I'm getting the message 'SQL Server does not exist or access is denied" in
> my .NET app. Not sure if it's the server or the database that I can't
> connect to, I can ping the server but that's it. Is there a simple way to
> test database connectivity to the instance from my web server?
> Thanks again.
>
> "Linchi Shea" wrote:
a[vbcol=seagreen]
the[vbcol=seagreen]
connection[vbcol=seagreen]
instance,[vbcol=seagreen]
(Unfortunately[vbcol=seagreen]
clustering)[vbcol=seagreen]
appreciated.[vbcol=seagreen]
|||Hello
I am working on this issue with Edwaldo
The problem comes when i try and add the SQL instance within the Enterprise
Manager or even if i try to TELNET to the server.
Any ideas? I have been thinking that this is something to do with the way
that the one to one NAT is configured on the firewall. As it is set for a
value of one at the Coventry end and the start ip address is 10.0.0.10 (which
is the old server and is working) So in the firewall rules they are showing
as being outside the NAT pool.
The issue i have is that changing the NAT pool size with alter the external
IP addresses of other servers which i can not really do. I can make the
change for a couple of seconds and test but then need to change it back.
Any help is greatfully received
Thanks for this
Gareth Collins
"Anthony Thomas" wrote:
> Can you TELNET to the assigned service port? Say, for example, that SQL
> Server is listening on TCP 1433. Then if you TELNET <ip address or server
> name> <port number>, you should get a black screen, which means it
> successfully connected. If it can't find the server or port, then you have
> a server configuration issue. If you connect successfully, then you have a
> client configuration issue.
> Sincerely,
>
> Anthony Thomas
>
> --
> "edwaldo" <edwaldo@.discussions.microsoft.com> wrote in message
> news:5EB601E4-CE5D-4A52-BCFE-B8C599CFEF89@.microsoft.com...
> a
> the
> connection
> instance,
> (Unfortunately
> clustering)
> appreciated.
>
>
Apologies if this isn't the right forum.
I have an instance of sql (2005) setup called SQL1\SQL1
I am trying to connect to a database (hm1) using the following connection
string in my web.config:
server=SQL1\SQL1;database=hm1;uid=hm1;pwd=hm1;
...but it can't find it. I need to know if this is the correct way to
address an instance in the connection string - I've tried
server=10.0.0.8\SQL1;
and
server=10.0.0.8;database=SQL1\hm1;
But neither work. On the SQL server itself, apart from naming the instance,
are there any other configuration settings I might be missing? (Unfortunately
I didn't set the server up and I know next to nothing about SQL clustering)
I feel like this a bit of a dumb question but any help really appreciated.
Ed
Will this help:
http://www.connectionstrings.com/?carrier=sqlserver
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
..
"edwaldo" <edwaldo@.discussions.microsoft.com> wrote in message
news:C37E6C7F-DC56-46F1-9001-32104E89F9D0@.microsoft.com...
Hi
Apologies if this isn't the right forum.
I have an instance of sql (2005) setup called SQL1\SQL1
I am trying to connect to a database (hm1) using the following connection
string in my web.config:
server=SQL1\SQL1;database=hm1;uid=hm1;pwd=hm1;
...but it can't find it. I need to know if this is the correct way to
address an instance in the connection string - I've tried
server=10.0.0.8\SQL1;
and
server=10.0.0.8;database=SQL1\hm1;
But neither work. On the SQL server itself, apart from naming the instance,
are there any other configuration settings I might be missing?
(Unfortunately
I didn't set the server up and I know next to nothing about SQL clustering)
I feel like this a bit of a dumb question but any help really appreciated.
Ed
|||And take a look at http://support.microsoft.com/kb/328306. Connecting to a
clustered instance is not that different from connecting to a standalone
instance.
By the way, when you said "it can't find it", what was it, the server or the
database?
Linchi
"edwaldo" wrote:
> Hi
> Apologies if this isn't the right forum.
> I have an instance of sql (2005) setup called SQL1\SQL1
> I am trying to connect to a database (hm1) using the following connection
> string in my web.config:
> server=SQL1\SQL1;database=hm1;uid=hm1;pwd=hm1;
> ..but it can't find it. I need to know if this is the correct way to
> address an instance in the connection string - I've tried
> server=10.0.0.8\SQL1;
> and
> server=10.0.0.8;database=SQL1\hm1;
> But neither work. On the SQL server itself, apart from naming the instance,
> are there any other configuration settings I might be missing? (Unfortunately
> I didn't set the server up and I know next to nothing about SQL clustering)
> I feel like this a bit of a dumb question but any help really appreciated.
> Ed
|||Thanks for your help - I'll take a look at that article.
I'm getting the message 'SQL Server does not exist or access is denied" in
my .NET app. Not sure if it's the server or the database that I can't
connect to, I can ping the server but that's it. Is there a simple way to
test database connectivity to the instance from my web server?
Thanks again.
"Linchi Shea" wrote:
[vbcol=seagreen]
> And take a look at http://support.microsoft.com/kb/328306. Connecting to a
> clustered instance is not that different from connecting to a standalone
> instance.
> By the way, when you said "it can't find it", what was it, the server or the
> database?
> Linchi
> "edwaldo" wrote:
|||> I'm getting the message 'SQL Server does not exist or access is denied" in
Then that KB article will definitely help. At least, it would get you close
to what may have caused it. If not, post back with what you have tried.
Linchi
"edwaldo" wrote:
[vbcol=seagreen]
> Thanks for your help - I'll take a look at that article.
> I'm getting the message 'SQL Server does not exist or access is denied" in
> my .NET app. Not sure if it's the server or the database that I can't
> connect to, I can ping the server but that's it. Is there a simple way to
> test database connectivity to the instance from my web server?
> Thanks again.
>
> "Linchi Shea" wrote:
|||Can you connect to it through SSIS or SQLCMD?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
..
"edwaldo" <edwaldo@.discussions.microsoft.com> wrote in message
news:5EB601E4-CE5D-4A52-BCFE-B8C599CFEF89@.microsoft.com...
Thanks for your help - I'll take a look at that article.
I'm getting the message 'SQL Server does not exist or access is denied" in
my .NET app. Not sure if it's the server or the database that I can't
connect to, I can ping the server but that's it. Is there a simple way to
test database connectivity to the instance from my web server?
Thanks again.
"Linchi Shea" wrote:
[vbcol=seagreen]
> And take a look at http://support.microsoft.com/kb/328306. Connecting to a
> clustered instance is not that different from connecting to a standalone
> instance.
> By the way, when you said "it can't find it", what was it, the server or
> the
> database?
> Linchi
> "edwaldo" wrote:
|||Thanks to both of you for your help.
Is SQLCMD for Sql Express only? I am running Server 2005. The machine I'm
trying to connect FROM is not running SQL.
I hadn't heard of SSIS - do you know the syntax I should be using to test
connectivity?
Thanks,
Ed
"Tom Moreau" wrote:
> Can you connect to it through SSIS or SQLCMD?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> ..
> "edwaldo" <edwaldo@.discussions.microsoft.com> wrote in message
> news:5EB601E4-CE5D-4A52-BCFE-B8C599CFEF89@.microsoft.com...
> Thanks for your help - I'll take a look at that article.
> I'm getting the message 'SQL Server does not exist or access is denied" in
> my .NET app. Not sure if it's the server or the database that I can't
> connect to, I can ping the server but that's it. Is there a simple way to
> test database connectivity to the instance from my web server?
> Thanks again.
>
> "Linchi Shea" wrote:
>
>
|||I should have said SSMS, not SSIS. (Too many acronyms to remember in SQL
2005!) SSMS = SQL Server Management Studio. Both it and SQLCMD (a command
line utility) are part of the SQL Server client tools. You should have
those on the server. If not, get the install disk and install them there.
At that point, you can log onto SQL Server locally. If you can't, then
there is probably a security issue - i.e. wrong login/password.
If that all works, then install the client tools on another machine and see
if you can connect to the server from them, using the same credentials as
you did previously. Let us know what happens and we can take it further.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
..
"edwaldo" <edwaldo@.discussions.microsoft.com> wrote in message
news:3B0450DF-DA21-4686-9B0C-E8EC65570459@.microsoft.com...
Thanks to both of you for your help.
Is SQLCMD for Sql Express only? I am running Server 2005. The machine I'm
trying to connect FROM is not running SQL.
I hadn't heard of SSIS - do you know the syntax I should be using to test
connectivity?
Thanks,
Ed
"Tom Moreau" wrote:
> Can you connect to it through SSIS or SQLCMD?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
> SQL Server MVP
> Toronto, ON Canada
> ..
> "edwaldo" <edwaldo@.discussions.microsoft.com> wrote in message
> news:5EB601E4-CE5D-4A52-BCFE-B8C599CFEF89@.microsoft.com...
> Thanks for your help - I'll take a look at that article.
> I'm getting the message 'SQL Server does not exist or access is denied" in
> my .NET app. Not sure if it's the server or the database that I can't
> connect to, I can ping the server but that's it. Is there a simple way to
> test database connectivity to the instance from my web server?
> Thanks again.
>
> "Linchi Shea" wrote:
>
>
|||Can you TELNET to the assigned service port? Say, for example, that SQL
Server is listening on TCP 1433. Then if you TELNET <ip address or server
name> <port number>, you should get a black screen, which means it
successfully connected. If it can't find the server or port, then you have
a server configuration issue. If you connect successfully, then you have a
client configuration issue.
Sincerely,
Anthony Thomas
"edwaldo" <edwaldo@.discussions.microsoft.com> wrote in message
news:5EB601E4-CE5D-4A52-BCFE-B8C599CFEF89@.microsoft.com...[vbcol=seagreen]
> Thanks for your help - I'll take a look at that article.
> I'm getting the message 'SQL Server does not exist or access is denied" in
> my .NET app. Not sure if it's the server or the database that I can't
> connect to, I can ping the server but that's it. Is there a simple way to
> test database connectivity to the instance from my web server?
> Thanks again.
>
> "Linchi Shea" wrote:
a[vbcol=seagreen]
the[vbcol=seagreen]
connection[vbcol=seagreen]
instance,[vbcol=seagreen]
(Unfortunately[vbcol=seagreen]
clustering)[vbcol=seagreen]
appreciated.[vbcol=seagreen]
|||Hello
I am working on this issue with Edwaldo
The problem comes when i try and add the SQL instance within the Enterprise
Manager or even if i try to TELNET to the server.
Any ideas? I have been thinking that this is something to do with the way
that the one to one NAT is configured on the firewall. As it is set for a
value of one at the Coventry end and the start ip address is 10.0.0.10 (which
is the old server and is working) So in the firewall rules they are showing
as being outside the NAT pool.
The issue i have is that changing the NAT pool size with alter the external
IP addresses of other servers which i can not really do. I can make the
change for a couple of seconds and test but then need to change it back.
Any help is greatfully received
Thanks for this
Gareth Collins
"Anthony Thomas" wrote:
> Can you TELNET to the assigned service port? Say, for example, that SQL
> Server is listening on TCP 1433. Then if you TELNET <ip address or server
> name> <port number>, you should get a black screen, which means it
> successfully connected. If it can't find the server or port, then you have
> a server configuration issue. If you connect successfully, then you have a
> client configuration issue.
> Sincerely,
>
> Anthony Thomas
>
> --
> "edwaldo" <edwaldo@.discussions.microsoft.com> wrote in message
> news:5EB601E4-CE5D-4A52-BCFE-B8C599CFEF89@.microsoft.com...
> a
> the
> connection
> instance,
> (Unfortunately
> clustering)
> appreciated.
>
>
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 Named Instance of SQL Server from ASP.Net
Hi,
I have a named instance of SQL Server 2000 called VTMS on a server called
VTMS which resides on a cluster.
I am trying to connect to a database on VTMS from a webapp (URL
http://reports) hosted on a server called RPT (ASP.Net 2.0) using Windows
Authentication.
When I publish this site locally and access it through http://localhost or
publish it on RPT and remote in to RPT and access it through http://reports,
it is able to connect to the database on VTMS. However, if I try to access it
through http://reports from my local machine, it comes up with the error:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server)
I have the same problem trying to connect to a Reporting Services 2005
report deployed to RPT, but accessing data on VTMS.
My connection strings are as follows:
Data Source:
Data Source=VTMS\VTMS;Initial Catalog=Timesheets
Web.Config:
<add name="HomeDepotON" connectionString="Data Source=VTMS\VTMS;Initial
Catalog=Timesheets;Integrated Security=True"
providerName="System.Data.SqlClient" />
Please help.
You need to enable TCP/IP on MS SQL side.
Right click on SQL server in SQL Server enterprise manager. Tab "General".
Button "Network Configuration"
Make sure you have TCP/IP in enabled protocols.
Also make sure that if there is any firewall between Web server and SQL then
it's open. Also try to ping the SQL server from Web server. Sometimes web
server can not resolve the name of the SQL server due to the network
configuration. Fix it or use IP address.
I have a named instance of SQL Server 2000 called VTMS on a server called
VTMS which resides on a cluster.
I am trying to connect to a database on VTMS from a webapp (URL
http://reports) hosted on a server called RPT (ASP.Net 2.0) using Windows
Authentication.
When I publish this site locally and access it through http://localhost or
publish it on RPT and remote in to RPT and access it through http://reports,
it is able to connect to the database on VTMS. However, if I try to access it
through http://reports from my local machine, it comes up with the error:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server)
I have the same problem trying to connect to a Reporting Services 2005
report deployed to RPT, but accessing data on VTMS.
My connection strings are as follows:
Data Source:
Data Source=VTMS\VTMS;Initial Catalog=Timesheets
Web.Config:
<add name="HomeDepotON" connectionString="Data Source=VTMS\VTMS;Initial
Catalog=Timesheets;Integrated Security=True"
providerName="System.Data.SqlClient" />
Please help.
You need to enable TCP/IP on MS SQL side.
Right click on SQL server in SQL Server enterprise manager. Tab "General".
Button "Network Configuration"
Make sure you have TCP/IP in enabled protocols.
Also make sure that if there is any firewall between Web server and SQL then
it's open. Also try to ping the SQL server from Web server. Sometimes web
server can not resolve the name of the SQL server due to the network
configuration. Fix it or use IP address.
Connecting to a Named Instance of SQL Server from ASP.Net
Hi,
I have a named instance of SQL Server 2000 called VTMS on a server called
VTMS which resides on a cluster.
I am trying to connect to a database on VTMS from a webapp (URL
http://reports) hosted on a server called RPT (ASP.Net 2.0) using Windows
Authentication.
When I publish this site locally and access it through http://localhost or
publish it on RPT and remote in to RPT and access it through http://reports,
it is able to connect to the database on VTMS. However, if I try to access i
t
through http://reports from my local machine, it comes up with the error:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server)
I have the same problem trying to connect to a Reporting Services 2005
report deployed to RPT, but accessing data on VTMS.
My connection strings are as follows:
Data Source:
Data Source=VTMS\VTMS;Initial Catalog=Timesheets
Web.Config:
<add name="HomeDepotON" connectionString="Data Source=VTMS\VTMS;Initial
Catalog=Timesheets;Integrated Security=True"
providerName="System.Data.SqlClient" />
Please help.You need to enable TCP/IP on MS SQL side.
Right click on SQL server in SQL Server enterprise manager. Tab "General".
Button "Network Configuration"
Make sure you have TCP/IP in enabled protocols.
Also make sure that if there is any firewall between Web server and SQL then
it's open. Also try to ping the SQL server from Web server. Sometimes web
server can not resolve the name of the SQL server due to the network
configuration. Fix it or use IP address.
I have a named instance of SQL Server 2000 called VTMS on a server called
VTMS which resides on a cluster.
I am trying to connect to a database on VTMS from a webapp (URL
http://reports) hosted on a server called RPT (ASP.Net 2.0) using Windows
Authentication.
When I publish this site locally and access it through http://localhost or
publish it on RPT and remote in to RPT and access it through http://reports,
it is able to connect to the database on VTMS. However, if I try to access i
t
through http://reports from my local machine, it comes up with the error:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server)
I have the same problem trying to connect to a Reporting Services 2005
report deployed to RPT, but accessing data on VTMS.
My connection strings are as follows:
Data Source:
Data Source=VTMS\VTMS;Initial Catalog=Timesheets
Web.Config:
<add name="HomeDepotON" connectionString="Data Source=VTMS\VTMS;Initial
Catalog=Timesheets;Integrated Security=True"
providerName="System.Data.SqlClient" />
Please help.You need to enable TCP/IP on MS SQL side.
Right click on SQL server in SQL Server enterprise manager. Tab "General".
Button "Network Configuration"
Make sure you have TCP/IP in enabled protocols.
Also make sure that if there is any firewall between Web server and SQL then
it's open. Also try to ping the SQL server from Web server. Sometimes web
server can not resolve the name of the SQL server due to the network
configuration. Fix it or use IP address.
Saturday, February 25, 2012
Connecting Surface Area Configuration to server on Clustered Server
I've run into a problem after upgrading production servers running under Microsoft Cluster Server, Windows Enterprise Server 2003 SP1, and SQL Server 2005 SP1 Enterprise Edition.
Once I completed the upgrade and applied the patch, I needed to examine the values set in the Features component of the Surface Area Configuration tool. The tool attempts to connect to localhost\instancename, but reports the following error:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error:26 - Error Locating Server/Instance Specified)(Microsoft SQL Server)
I'm logged into the virtual server via Remote Desktop, but the SAC tool thinks I'm logged into the physical server supporting the virtual server. I seem to be caught between a rock and a hard place here, as I can't enable remote connections without first gaining access on the server itself.
Any help will be greatly appreciated.
Can anyone give me a little help here - I can't make configuration changes on production servers.
Thanks.
|||Well, after a lucky break I found the answer.
sp_configure 'remote admin connections', 1
go
reconfigure
go
Once this was executed on the server I was able to go into Surface Area Configuration, enter the virtual server name, and connect successfully and make the other changes necessary. A simple solution to a scary problem. (Even though I'd used sp_configure for years on both Sybase and MSSQL servers it's easy to forget about the simple solutions.)
Connecting Surface Area Configuration to server on Clustered Server
I've run into a problem after upgrading production servers running under Microsoft Cluster Server, Windows Enterprise Server 2003 SP1, and SQL Server 2005 SP1 Enterprise Edition.
Once I completed the upgrade and applied the patch, I needed to examine the values set in the Features component of the Surface Area Configuration tool. The tool attempts to connect to localhost\instancename, but reports the following error:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error:26 - Error Locating Server/Instance Specified)(Microsoft SQL Server)
I'm logged into the virtual server via Remote Desktop, but the SAC tool thinks I'm logged into the physical server supporting the virtual server. I seem to be caught between a rock and a hard place here, as I can't enable remote connections without first gaining access on the server itself.
Any help will be greatly appreciated.
Can anyone give me a little help here - I can't make configuration changes on production servers.
Thanks.
|||Well, after a lucky break I found the answer.
sp_configure 'remote admin connections', 1
go
reconfigure
go
Once this was executed on the server I was able to go into Surface Area Configuration, enter the virtual server name, and connect successfully and make the other changes necessary. A simple solution to a scary problem. (Even though I'd used sp_configure for years on both Sybase and MSSQL servers it's easy to forget about the simple solutions.)
|||thx a lotFriday, February 17, 2012
Connecting a node in cluster
I have 2-node cluster. I can connect to the cluster from
enterprise manager. However, due to some reason, the
administrator wants to run enterprise manager connecting
to an instance on a node rather than cluster. How do we do
it?
I am not usre what you are asking. If you want to connect to the virtual
SQL Server from a machine other than the nodes of the cluster, you just
specify the virtual SQL Server name when registering the SQL Server.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Inform the Administrator that you need to connect to the Virtual Server,
not the node itself.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
enterprise manager. However, due to some reason, the
administrator wants to run enterprise manager connecting
to an instance on a node rather than cluster. How do we do
it?
I am not usre what you are asking. If you want to connect to the virtual
SQL Server from a machine other than the nodes of the cluster, you just
specify the virtual SQL Server name when registering the SQL Server.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Inform the Administrator that you need to connect to the Virtual Server,
not the node itself.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
Connecting a node in cluster
I have 2-node cluster. I can connect to the cluster from
enterprise manager. However, due to some reason, the
administrator wants to run enterprise manager connecting
to an instance on a node rather than cluster. How do we do
it?I am not usre what you are asking. If you want to connect to the virtual
SQL Server from a machine other than the nodes of the cluster, you just
specify the virtual SQL Server name when registering the SQL Server.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Inform the Administrator that you need to connect to the Virtual Server,
not the node itself.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
enterprise manager. However, due to some reason, the
administrator wants to run enterprise manager connecting
to an instance on a node rather than cluster. How do we do
it?I am not usre what you are asking. If you want to connect to the virtual
SQL Server from a machine other than the nodes of the cluster, you just
specify the virtual SQL Server name when registering the SQL Server.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Inform the Administrator that you need to connect to the Virtual Server,
not the node itself.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
Subscribe to:
Posts (Atom)