Hello there,
I'm currently building up a SQL 2005 Active/Standby cluster in a DMZ. I have three NIC's in each server.
Each NIC is connected to a different network:
192.168.100.1 is the public NIC
10.0.0.1 is the NIC used for communication betwen the cluster nodes (heartbeat)
192.168.200.1 is the admin NIC
I have installed my cluster using the 192.168.100.0 network for public access. This means that my SQL virtual ip is 192.168.100.10
Each server can be administered over the 192.168.200.0 network (admin) and the cluster/sql sever ip is available from the 192.168.100.0 (public) network.
Now for my question: How can I assign a ip address from my admin network (e.g.192.168.200.10) to the existing SQL server cluster to make it available from my admin network while keeping the public ip.
Thanx in advance!
Chris
From http://www.developmentnow.com/g/99_2004_12_1_0_0/sql-server-clustering.htm
Posted via DevelopmentNow.com Groups
http://www.developmentnow.com
"chrismk" <Multiple IP's (from 2 different networks) on a single SQL 2005
Cluster> wrote in message
news:59d2db33-7eb3-4b9e-af0f-fd54c5d3d72b@.developmentnow.com...
> I'm currently building up a SQL 2005 Active/Standby cluster in a DMZ. I
> have three NIC's in each server.
BTW, I am not trying to be a pain, but some of the issues here have me
extremely curious. First, why are you putting it in the perimeter network?
You should have it behind the internal firewall so the data is fully
protected and have anything that runs in the perimeter network to make its
calls through the internal firewall using a non-standard port. Data needs to
be protected.
> Each NIC is connected to a different network:
> 192.168.100.1 is the public NIC
> 10.0.0.1 is the NIC used for communication betwen the cluster nodes
> (heartbeat)
> 192.168.200.1 is the admin NIC
Why do you need an admin NIC. There is this concept of IP routing that
should make this requirement go away. <G>
> I have installed my cluster using the 192.168.100.0 network for public
> access. This means that my SQL virtual ip is 192.168.100.10
> Each server can be administered over the 192.168.200.0 network (admin) and
> the cluster/sql sever ip is available from the 192.168.100.0 (public)
> network.
> Now for my question: How can I assign a ip address from my admin network
> (e.g.192.168.200.10) to the existing SQL server cluster to make it
> available from my admin network while keeping the public ip.
It should work. Add the new IP Address resource and set the dependencies on
all the other resources as needed.
However, just because it should work does not mean it is your best
alternative.
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp
The next ClusterHelp classes are:
Dec 10 - 13 in Denver
Jan 18 - 31 in Denver
|||Check out the following KB articles:
http://msdn2.microsoft.com/en-us/library/ms190460.aspx
http://msdn2.microsoft.com/en-us/library/ms177447.aspx
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
"chrismk" <Multiple IP's (from 2 different networks) on a single SQL 2005
Cluster> wrote in message
news:59d2db33-7eb3-4b9e-af0f-fd54c5d3d72b@.developmentnow.com...
Hello there,
I'm currently building up a SQL 2005 Active/Standby cluster in a DMZ. I have
three NIC's in each server.
Each NIC is connected to a different network:
192.168.100.1 is the public NIC
10.0.0.1 is the NIC used for communication betwen the cluster nodes
(heartbeat)
192.168.200.1 is the admin NIC
I have installed my cluster using the 192.168.100.0 network for public
access. This means that my SQL virtual ip is 192.168.100.10
Each server can be administered over the 192.168.200.0 network (admin) and
the cluster/sql sever ip is available from the 192.168.100.0 (public)
network.
Now for my question: How can I assign a ip address from my admin network
(e.g.192.168.200.10) to the existing SQL server cluster to make it
available from my admin network while keeping the public ip.
Thanx in advance!
Chris
From
http://www.developmentnow.com/g/99_2004_12_1_0_0/sql-server-clustering.htm
Posted via DevelopmentNow.com Groups
http://www.developmentnow.com
Showing posts with label dmz. Show all posts
Showing posts with label dmz. Show all posts
Friday, March 30, 2012
Friday, March 9, 2012
Multiple connections from IIS on 1433 causing problems
I have SQL2000 with 8 databases running on the LAN. In our DMZ we have
a web server [IIS5] which connects to the SQL on 1433 through the
DMZ/LAN port. Up until last Tuesday everything seemed OK with approx 10
connections form DMZ>>LAN on port 1433 whenever the site was opened.
However now I am seeing 50-60 connections even though there are only a
max of 10 users connected.
As a test I closed the website to the WAN [0 connections] and opened
one occurrence of the website . It immediately, created 2 IIS
connections and 10 SQL connections. After 20-30 seconds the SQL dropped
to 2 connections until I clicked an internal link, & then it rose back
to 10 again.
Does this make sense, I dont know what the developers may have done to
trigger this and not sure where to go next. Connection pooling is
enabled & we use DSNs to make the IIS>>>SQL connections.
Thanx for your time
G> Does this make sense, I dont know what the developers may have done to
> trigger this and not sure where to go next. Connection pooling is
> enabled & we use DSNs to make the IIS>>>SQL connections.
Basically, the high-water mark should reflect the number of concurrent open
connections needed by the application. Keep in mind that when concurrent
queries are executed, each requires a separate connection and ADO will
dynamically create additional connection objects as needed. You might try a
Profiler Trace including Batch Starting, RPC Starting, Batch Completed and
RPC Completed events to help identify the cause.
Hope this helps.
Dan Guzman
SQL Server MVP
"gstar" <gary.brett@.gmail.com> wrote in message
news:1168856615.584379.217420@.l53g2000cwa.googlegroups.com...
>I have SQL2000 with 8 databases running on the LAN. In our DMZ we have
> a web server [IIS5] which connects to the SQL on 1433 through the
> DMZ/LAN port. Up until last Tuesday everything seemed OK with approx 10
> connections form DMZ>>LAN on port 1433 whenever the site was opened.
> However now I am seeing 50-60 connections even though there are only a
> max of 10 users connected.
> As a test I closed the website to the WAN [0 connections] and opened
> one occurrence of the website . It immediately, created 2 IIS
> connections and 10 SQL connections. After 20-30 seconds the SQL dropped
> to 2 connections until I clicked an internal link, & then it rose back
> to 10 again.
> Does this make sense, I dont know what the developers may have done to
> trigger this and not sure where to go next. Connection pooling is
> enabled & we use DSNs to make the IIS>>>SQL connections.
> Thanx for your time
> G
>|||I have see this problem before. If you are running IIS, I am assuming
asp or aspx (.net). If you have more connections than users, it is
probably that the application is not closing connections properly. In
"classic ASP" you had a command to open the connection - often at the
top of the web page, ran your query and then closed it at the bottom of
the page as the code was interpreted. Maybe this will help give the
developers some ideas. Same sort of concept can happen with .NET.
KR
Dan Guzman wrote:[vbcol=seagreen]
> Basically, the high-water mark should reflect the number of concurrent ope
n
> connections needed by the application. Keep in mind that when concurrent
> queries are executed, each requires a separate connection and ADO will
> dynamically create additional connection objects as needed. You might try
a
> Profiler Trace including Batch Starting, RPC Starting, Batch Completed and
> RPC Completed events to help identify the cause.
>
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "gstar" <gary.brett@.gmail.com> wrote in message
> news:1168856615.584379.217420@.l53g2000cwa.googlegroups.com...
a web server [IIS5] which connects to the SQL on 1433 through the
DMZ/LAN port. Up until last Tuesday everything seemed OK with approx 10
connections form DMZ>>LAN on port 1433 whenever the site was opened.
However now I am seeing 50-60 connections even though there are only a
max of 10 users connected.
As a test I closed the website to the WAN [0 connections] and opened
one occurrence of the website . It immediately, created 2 IIS
connections and 10 SQL connections. After 20-30 seconds the SQL dropped
to 2 connections until I clicked an internal link, & then it rose back
to 10 again.
Does this make sense, I dont know what the developers may have done to
trigger this and not sure where to go next. Connection pooling is
enabled & we use DSNs to make the IIS>>>SQL connections.
Thanx for your time
G> Does this make sense, I dont know what the developers may have done to
> trigger this and not sure where to go next. Connection pooling is
> enabled & we use DSNs to make the IIS>>>SQL connections.
Basically, the high-water mark should reflect the number of concurrent open
connections needed by the application. Keep in mind that when concurrent
queries are executed, each requires a separate connection and ADO will
dynamically create additional connection objects as needed. You might try a
Profiler Trace including Batch Starting, RPC Starting, Batch Completed and
RPC Completed events to help identify the cause.
Hope this helps.
Dan Guzman
SQL Server MVP
"gstar" <gary.brett@.gmail.com> wrote in message
news:1168856615.584379.217420@.l53g2000cwa.googlegroups.com...
>I have SQL2000 with 8 databases running on the LAN. In our DMZ we have
> a web server [IIS5] which connects to the SQL on 1433 through the
> DMZ/LAN port. Up until last Tuesday everything seemed OK with approx 10
> connections form DMZ>>LAN on port 1433 whenever the site was opened.
> However now I am seeing 50-60 connections even though there are only a
> max of 10 users connected.
> As a test I closed the website to the WAN [0 connections] and opened
> one occurrence of the website . It immediately, created 2 IIS
> connections and 10 SQL connections. After 20-30 seconds the SQL dropped
> to 2 connections until I clicked an internal link, & then it rose back
> to 10 again.
> Does this make sense, I dont know what the developers may have done to
> trigger this and not sure where to go next. Connection pooling is
> enabled & we use DSNs to make the IIS>>>SQL connections.
> Thanx for your time
> G
>|||I have see this problem before. If you are running IIS, I am assuming
asp or aspx (.net). If you have more connections than users, it is
probably that the application is not closing connections properly. In
"classic ASP" you had a command to open the connection - often at the
top of the web page, ran your query and then closed it at the bottom of
the page as the code was interpreted. Maybe this will help give the
developers some ideas. Same sort of concept can happen with .NET.
KR
Dan Guzman wrote:[vbcol=seagreen]
> Basically, the high-water mark should reflect the number of concurrent ope
n
> connections needed by the application. Keep in mind that when concurrent
> queries are executed, each requires a separate connection and ADO will
> dynamically create additional connection objects as needed. You might try
a
> Profiler Trace including Batch Starting, RPC Starting, Batch Completed and
> RPC Completed events to help identify the cause.
>
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "gstar" <gary.brett@.gmail.com> wrote in message
> news:1168856615.584379.217420@.l53g2000cwa.googlegroups.com...
Multiple connections from IIS on 1433 causing problems
I have SQL2000 with 8 databases running on the LAN. In our DMZ we have
a web server [IIS5] which connects to the SQL on 1433 through the
DMZ/LAN port. Up until last Tuesday everything seemed OK with approx 10
connections form DMZ>>LAN on port 1433 whenever the site was opened.
However now I am seeing 50-60 connections even though there are only a
max of 10 users connected.
As a test I closed the website to the WAN [0 connections] and opened
one occurrence of the website . It immediately, created 2 IIS
connections and 10 SQL connections. After 20-30 seconds the SQL dropped
to 2 connections until I clicked an internal link, & then it rose back
to 10 again.
Does this make sense, I dont know what the developers may have done to
trigger this and not sure where to go next. Connection pooling is
enabled & we use DSNs to make the IIS>>SQL connections.
Thanx for your time
G> Does this make sense, I dont know what the developers may have done to
> trigger this and not sure where to go next. Connection pooling is
> enabled & we use DSNs to make the IIS>>SQL connections.
Basically, the high-water mark should reflect the number of concurrent open
connections needed by the application. Keep in mind that when concurrent
queries are executed, each requires a separate connection and ADO will
dynamically create additional connection objects as needed. You might try a
Profiler Trace including Batch Starting, RPC Starting, Batch Completed and
RPC Completed events to help identify the cause.
Hope this helps.
Dan Guzman
SQL Server MVP
"gstar" <gary.brett@.gmail.com> wrote in message
news:1168856615.584379.217420@.l53g2000cwa.googlegroups.com...
>I have SQL2000 with 8 databases running on the LAN. In our DMZ we have
> a web server [IIS5] which connects to the SQL on 1433 through the
> DMZ/LAN port. Up until last Tuesday everything seemed OK with approx 10
> connections form DMZ>>LAN on port 1433 whenever the site was opened.
> However now I am seeing 50-60 connections even though there are only a
> max of 10 users connected.
> As a test I closed the website to the WAN [0 connections] and opened
> one occurrence of the website . It immediately, created 2 IIS
> connections and 10 SQL connections. After 20-30 seconds the SQL dropped
> to 2 connections until I clicked an internal link, & then it rose back
> to 10 again.
> Does this make sense, I dont know what the developers may have done to
> trigger this and not sure where to go next. Connection pooling is
> enabled & we use DSNs to make the IIS>>SQL connections.
> Thanx for your time
> G
>|||I have see this problem before. If you are running IIS, I am assuming
asp or aspx (.net). If you have more connections than users, it is
probably that the application is not closing connections properly. In
"classic ASP" you had a command to open the connection - often at the
top of the web page, ran your query and then closed it at the bottom of
the page as the code was interpreted. Maybe this will help give the
developers some ideas. Same sort of concept can happen with .NET.
KR
Dan Guzman wrote:
> > Does this make sense, I dont know what the developers may have done to
> > trigger this and not sure where to go next. Connection pooling is
> > enabled & we use DSNs to make the IIS>>SQL connections.
> Basically, the high-water mark should reflect the number of concurrent open
> connections needed by the application. Keep in mind that when concurrent
> queries are executed, each requires a separate connection and ADO will
> dynamically create additional connection objects as needed. You might try a
> Profiler Trace including Batch Starting, RPC Starting, Batch Completed and
> RPC Completed events to help identify the cause.
>
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "gstar" <gary.brett@.gmail.com> wrote in message
> news:1168856615.584379.217420@.l53g2000cwa.googlegroups.com...
> >I have SQL2000 with 8 databases running on the LAN. In our DMZ we have
> > a web server [IIS5] which connects to the SQL on 1433 through the
> > DMZ/LAN port. Up until last Tuesday everything seemed OK with approx 10
> > connections form DMZ>>LAN on port 1433 whenever the site was opened.
> > However now I am seeing 50-60 connections even though there are only a
> > max of 10 users connected.
> >
> > As a test I closed the website to the WAN [0 connections] and opened
> > one occurrence of the website . It immediately, created 2 IIS
> > connections and 10 SQL connections. After 20-30 seconds the SQL dropped
> > to 2 connections until I clicked an internal link, & then it rose back
> > to 10 again.
> >
> > Does this make sense, I dont know what the developers may have done to
> > trigger this and not sure where to go next. Connection pooling is
> > enabled & we use DSNs to make the IIS>>SQL connections.
> >
> > Thanx for your time
> >
> > G
> >
a web server [IIS5] which connects to the SQL on 1433 through the
DMZ/LAN port. Up until last Tuesday everything seemed OK with approx 10
connections form DMZ>>LAN on port 1433 whenever the site was opened.
However now I am seeing 50-60 connections even though there are only a
max of 10 users connected.
As a test I closed the website to the WAN [0 connections] and opened
one occurrence of the website . It immediately, created 2 IIS
connections and 10 SQL connections. After 20-30 seconds the SQL dropped
to 2 connections until I clicked an internal link, & then it rose back
to 10 again.
Does this make sense, I dont know what the developers may have done to
trigger this and not sure where to go next. Connection pooling is
enabled & we use DSNs to make the IIS>>SQL connections.
Thanx for your time
G> Does this make sense, I dont know what the developers may have done to
> trigger this and not sure where to go next. Connection pooling is
> enabled & we use DSNs to make the IIS>>SQL connections.
Basically, the high-water mark should reflect the number of concurrent open
connections needed by the application. Keep in mind that when concurrent
queries are executed, each requires a separate connection and ADO will
dynamically create additional connection objects as needed. You might try a
Profiler Trace including Batch Starting, RPC Starting, Batch Completed and
RPC Completed events to help identify the cause.
Hope this helps.
Dan Guzman
SQL Server MVP
"gstar" <gary.brett@.gmail.com> wrote in message
news:1168856615.584379.217420@.l53g2000cwa.googlegroups.com...
>I have SQL2000 with 8 databases running on the LAN. In our DMZ we have
> a web server [IIS5] which connects to the SQL on 1433 through the
> DMZ/LAN port. Up until last Tuesday everything seemed OK with approx 10
> connections form DMZ>>LAN on port 1433 whenever the site was opened.
> However now I am seeing 50-60 connections even though there are only a
> max of 10 users connected.
> As a test I closed the website to the WAN [0 connections] and opened
> one occurrence of the website . It immediately, created 2 IIS
> connections and 10 SQL connections. After 20-30 seconds the SQL dropped
> to 2 connections until I clicked an internal link, & then it rose back
> to 10 again.
> Does this make sense, I dont know what the developers may have done to
> trigger this and not sure where to go next. Connection pooling is
> enabled & we use DSNs to make the IIS>>SQL connections.
> Thanx for your time
> G
>|||I have see this problem before. If you are running IIS, I am assuming
asp or aspx (.net). If you have more connections than users, it is
probably that the application is not closing connections properly. In
"classic ASP" you had a command to open the connection - often at the
top of the web page, ran your query and then closed it at the bottom of
the page as the code was interpreted. Maybe this will help give the
developers some ideas. Same sort of concept can happen with .NET.
KR
Dan Guzman wrote:
> > Does this make sense, I dont know what the developers may have done to
> > trigger this and not sure where to go next. Connection pooling is
> > enabled & we use DSNs to make the IIS>>SQL connections.
> Basically, the high-water mark should reflect the number of concurrent open
> connections needed by the application. Keep in mind that when concurrent
> queries are executed, each requires a separate connection and ADO will
> dynamically create additional connection objects as needed. You might try a
> Profiler Trace including Batch Starting, RPC Starting, Batch Completed and
> RPC Completed events to help identify the cause.
>
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "gstar" <gary.brett@.gmail.com> wrote in message
> news:1168856615.584379.217420@.l53g2000cwa.googlegroups.com...
> >I have SQL2000 with 8 databases running on the LAN. In our DMZ we have
> > a web server [IIS5] which connects to the SQL on 1433 through the
> > DMZ/LAN port. Up until last Tuesday everything seemed OK with approx 10
> > connections form DMZ>>LAN on port 1433 whenever the site was opened.
> > However now I am seeing 50-60 connections even though there are only a
> > max of 10 users connected.
> >
> > As a test I closed the website to the WAN [0 connections] and opened
> > one occurrence of the website . It immediately, created 2 IIS
> > connections and 10 SQL connections. After 20-30 seconds the SQL dropped
> > to 2 connections until I clicked an internal link, & then it rose back
> > to 10 again.
> >
> > Does this make sense, I dont know what the developers may have done to
> > trigger this and not sure where to go next. Connection pooling is
> > enabled & we use DSNs to make the IIS>>SQL connections.
> >
> > Thanx for your time
> >
> > G
> >
Subscribe to:
Posts (Atom)