What is causing intermittent connections problems from web server to sql server 2008 r2?SQL Server 2008 Remote AccessNetwork Load Balancing, intermittent port problem on Windows Server 2008Connecting SQL 2008 and Web server 2008 using directly connected Ethernet cable on 2nd network cardsSynch SQL 2008 with failover server?Double hop problem with sql server 2008Implementing Automatic failover with SQL Server 2008 R2 Web EditionSQL Server 2008 Web edition - access from another IIS?.NET + Connection to SQL Server 2008 R2How do you begin to diagnose intermittent SQL Server connection errors?
Print the new site header
Is a sequel allowed to start before the end of the first book?
Does cooling a potato change the nature of its carbohydrates?
Checking if argument is a floating point without breaking on control sequences in argument
How much steel armor can you wear and still be able to swim?
Boundaries and Buddhism
Harmonic Series Phase Difference?
How to prevent cables getting intertwined
Co-worker is now managing my team. Does this mean that I'm being demoted?
...and then she held the gun
How did the European Union reach the figure of 3% as a maximum allowed deficit?
How can I detect if I'm in a subshell?
How to address players struggling with simple controls?
How can caller ID be faked?
Should I email my professor to clear up a (possibly very irrelevant) awkward misunderstanding?
Justifying Affordable Bespoke Spaceships
Would a 7805 5v regulator drain a 9v battery?
Having some issue with notation in a Hilbert space
How useful is the GRE Exam?
You may find me... puzzling
What is "dot" sign in •NO?
Is the infant mortality rate among African-American babies in Youngstown, Ohio greater than that of babies in Iran?
Basic power tool set for Home repair and simple projects
Bash function: Execute $@ command with each argument in sequence executed separately
What is causing intermittent connections problems from web server to sql server 2008 r2?
SQL Server 2008 Remote AccessNetwork Load Balancing, intermittent port problem on Windows Server 2008Connecting SQL 2008 and Web server 2008 using directly connected Ethernet cable on 2nd network cardsSynch SQL 2008 with failover server?Double hop problem with sql server 2008Implementing Automatic failover with SQL Server 2008 R2 Web EditionSQL Server 2008 Web edition - access from another IIS?.NET + Connection to SQL Server 2008 R2How do you begin to diagnose intermittent SQL Server connection errors?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
We have 4 API servers and 2 web servers that connect to a SQL 2008 R2 server. Recently we've noticed that the web servers sometimes can't find the SQL server. This doesn't happen for every connection, but it does happen several times per minute. All the servers are on Windows 2008 R2, and connect to the DB via TCP. We've verified that the DB is reachable, and in fact, the API servers don't have any problems connecting to the DB.
Because the connection problems are intermittent it is proving difficult to troubleshoot. We've verified that the firewall is not blocking the connection, and that the maximum number of connections is not being reached (max is the default of 32767, and our average connection count at any given time is around 1000).
What might be causing these irregular connection problems?
windows-server-2008 sql-server web-server sql-server-2008
add a comment |
We have 4 API servers and 2 web servers that connect to a SQL 2008 R2 server. Recently we've noticed that the web servers sometimes can't find the SQL server. This doesn't happen for every connection, but it does happen several times per minute. All the servers are on Windows 2008 R2, and connect to the DB via TCP. We've verified that the DB is reachable, and in fact, the API servers don't have any problems connecting to the DB.
Because the connection problems are intermittent it is proving difficult to troubleshoot. We've verified that the firewall is not blocking the connection, and that the maximum number of connections is not being reached (max is the default of 32767, and our average connection count at any given time is around 1000).
What might be causing these irregular connection problems?
windows-server-2008 sql-server web-server sql-server-2008
add a comment |
We have 4 API servers and 2 web servers that connect to a SQL 2008 R2 server. Recently we've noticed that the web servers sometimes can't find the SQL server. This doesn't happen for every connection, but it does happen several times per minute. All the servers are on Windows 2008 R2, and connect to the DB via TCP. We've verified that the DB is reachable, and in fact, the API servers don't have any problems connecting to the DB.
Because the connection problems are intermittent it is proving difficult to troubleshoot. We've verified that the firewall is not blocking the connection, and that the maximum number of connections is not being reached (max is the default of 32767, and our average connection count at any given time is around 1000).
What might be causing these irregular connection problems?
windows-server-2008 sql-server web-server sql-server-2008
We have 4 API servers and 2 web servers that connect to a SQL 2008 R2 server. Recently we've noticed that the web servers sometimes can't find the SQL server. This doesn't happen for every connection, but it does happen several times per minute. All the servers are on Windows 2008 R2, and connect to the DB via TCP. We've verified that the DB is reachable, and in fact, the API servers don't have any problems connecting to the DB.
Because the connection problems are intermittent it is proving difficult to troubleshoot. We've verified that the firewall is not blocking the connection, and that the maximum number of connections is not being reached (max is the default of 32767, and our average connection count at any given time is around 1000).
What might be causing these irregular connection problems?
windows-server-2008 sql-server web-server sql-server-2008
windows-server-2008 sql-server web-server sql-server-2008
asked Aug 18 '10 at 22:07
Aaron Lewis
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
So these DB servers are on another network (via the firewall)? If so take a look at the ARP cache on the web and DB servers at the time the problem occurs and look at the ARP table on the firewall when the problem occurs. The web servers should have the MAC address of the firewall for the DB server's ip address in their cache, the DB servers should have the MAC address of the firewall for the web server's ip address in their cache, and the firewall should have the MAC address for the DB server's ip address and the MAC address for the web server's ip address in it's cache. Make sure that the firewall ARP table shows the MAC adresses for the servers listed on the appropriate firewall interface that each server is "connected" to. If that gets you no where then check the ARP table on the switches between the web and DB servers.
You can also put a network sniffer on the web and DB servers and start a packet capture. When the problem occurs, look at the capture on both ends and see what's happening. You should see traffic from the web servers toward the DB servers (toward the firewall) and from the DB servers to the web servers (toward the firewall). If you do then it's a network problem, if you don't then it's a server problem.
EDIT
Also, you can look for any RST packets coming from either end of the connection in your network capture that might be coming from the firewall due to connection timeout settings on the firewall.
add a comment |
I'd suggest looking at the NIC statistics -- mainly error counts, whether there's any offloading to a TOE module happening, and whether the web servers' link to the switch (or another net device) is getting saturated. Also the output of 'netstat -ano' -- it's possible you'll get errors if the entire ephemeral port range (49152-65535 by default on Windows 2008) is in use on the web servers.
Being intermittently unable to connect to SQL can have myriad causes from hardware to connection pooling problems, so if you could post the error message that's being logged or displayed (assuming there is one), that might give people a better idea of what's wrong.
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f172089%2fwhat-is-causing-intermittent-connections-problems-from-web-server-to-sql-server%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
So these DB servers are on another network (via the firewall)? If so take a look at the ARP cache on the web and DB servers at the time the problem occurs and look at the ARP table on the firewall when the problem occurs. The web servers should have the MAC address of the firewall for the DB server's ip address in their cache, the DB servers should have the MAC address of the firewall for the web server's ip address in their cache, and the firewall should have the MAC address for the DB server's ip address and the MAC address for the web server's ip address in it's cache. Make sure that the firewall ARP table shows the MAC adresses for the servers listed on the appropriate firewall interface that each server is "connected" to. If that gets you no where then check the ARP table on the switches between the web and DB servers.
You can also put a network sniffer on the web and DB servers and start a packet capture. When the problem occurs, look at the capture on both ends and see what's happening. You should see traffic from the web servers toward the DB servers (toward the firewall) and from the DB servers to the web servers (toward the firewall). If you do then it's a network problem, if you don't then it's a server problem.
EDIT
Also, you can look for any RST packets coming from either end of the connection in your network capture that might be coming from the firewall due to connection timeout settings on the firewall.
add a comment |
So these DB servers are on another network (via the firewall)? If so take a look at the ARP cache on the web and DB servers at the time the problem occurs and look at the ARP table on the firewall when the problem occurs. The web servers should have the MAC address of the firewall for the DB server's ip address in their cache, the DB servers should have the MAC address of the firewall for the web server's ip address in their cache, and the firewall should have the MAC address for the DB server's ip address and the MAC address for the web server's ip address in it's cache. Make sure that the firewall ARP table shows the MAC adresses for the servers listed on the appropriate firewall interface that each server is "connected" to. If that gets you no where then check the ARP table on the switches between the web and DB servers.
You can also put a network sniffer on the web and DB servers and start a packet capture. When the problem occurs, look at the capture on both ends and see what's happening. You should see traffic from the web servers toward the DB servers (toward the firewall) and from the DB servers to the web servers (toward the firewall). If you do then it's a network problem, if you don't then it's a server problem.
EDIT
Also, you can look for any RST packets coming from either end of the connection in your network capture that might be coming from the firewall due to connection timeout settings on the firewall.
add a comment |
So these DB servers are on another network (via the firewall)? If so take a look at the ARP cache on the web and DB servers at the time the problem occurs and look at the ARP table on the firewall when the problem occurs. The web servers should have the MAC address of the firewall for the DB server's ip address in their cache, the DB servers should have the MAC address of the firewall for the web server's ip address in their cache, and the firewall should have the MAC address for the DB server's ip address and the MAC address for the web server's ip address in it's cache. Make sure that the firewall ARP table shows the MAC adresses for the servers listed on the appropriate firewall interface that each server is "connected" to. If that gets you no where then check the ARP table on the switches between the web and DB servers.
You can also put a network sniffer on the web and DB servers and start a packet capture. When the problem occurs, look at the capture on both ends and see what's happening. You should see traffic from the web servers toward the DB servers (toward the firewall) and from the DB servers to the web servers (toward the firewall). If you do then it's a network problem, if you don't then it's a server problem.
EDIT
Also, you can look for any RST packets coming from either end of the connection in your network capture that might be coming from the firewall due to connection timeout settings on the firewall.
So these DB servers are on another network (via the firewall)? If so take a look at the ARP cache on the web and DB servers at the time the problem occurs and look at the ARP table on the firewall when the problem occurs. The web servers should have the MAC address of the firewall for the DB server's ip address in their cache, the DB servers should have the MAC address of the firewall for the web server's ip address in their cache, and the firewall should have the MAC address for the DB server's ip address and the MAC address for the web server's ip address in it's cache. Make sure that the firewall ARP table shows the MAC adresses for the servers listed on the appropriate firewall interface that each server is "connected" to. If that gets you no where then check the ARP table on the switches between the web and DB servers.
You can also put a network sniffer on the web and DB servers and start a packet capture. When the problem occurs, look at the capture on both ends and see what's happening. You should see traffic from the web servers toward the DB servers (toward the firewall) and from the DB servers to the web servers (toward the firewall). If you do then it's a network problem, if you don't then it's a server problem.
EDIT
Also, you can look for any RST packets coming from either end of the connection in your network capture that might be coming from the firewall due to connection timeout settings on the firewall.
edited Aug 18 '10 at 23:08
answered Aug 18 '10 at 22:19
joeqwertyjoeqwerty
97.7k466149
97.7k466149
add a comment |
add a comment |
I'd suggest looking at the NIC statistics -- mainly error counts, whether there's any offloading to a TOE module happening, and whether the web servers' link to the switch (or another net device) is getting saturated. Also the output of 'netstat -ano' -- it's possible you'll get errors if the entire ephemeral port range (49152-65535 by default on Windows 2008) is in use on the web servers.
Being intermittently unable to connect to SQL can have myriad causes from hardware to connection pooling problems, so if you could post the error message that's being logged or displayed (assuming there is one), that might give people a better idea of what's wrong.
add a comment |
I'd suggest looking at the NIC statistics -- mainly error counts, whether there's any offloading to a TOE module happening, and whether the web servers' link to the switch (or another net device) is getting saturated. Also the output of 'netstat -ano' -- it's possible you'll get errors if the entire ephemeral port range (49152-65535 by default on Windows 2008) is in use on the web servers.
Being intermittently unable to connect to SQL can have myriad causes from hardware to connection pooling problems, so if you could post the error message that's being logged or displayed (assuming there is one), that might give people a better idea of what's wrong.
add a comment |
I'd suggest looking at the NIC statistics -- mainly error counts, whether there's any offloading to a TOE module happening, and whether the web servers' link to the switch (or another net device) is getting saturated. Also the output of 'netstat -ano' -- it's possible you'll get errors if the entire ephemeral port range (49152-65535 by default on Windows 2008) is in use on the web servers.
Being intermittently unable to connect to SQL can have myriad causes from hardware to connection pooling problems, so if you could post the error message that's being logged or displayed (assuming there is one), that might give people a better idea of what's wrong.
I'd suggest looking at the NIC statistics -- mainly error counts, whether there's any offloading to a TOE module happening, and whether the web servers' link to the switch (or another net device) is getting saturated. Also the output of 'netstat -ano' -- it's possible you'll get errors if the entire ephemeral port range (49152-65535 by default on Windows 2008) is in use on the web servers.
Being intermittently unable to connect to SQL can have myriad causes from hardware to connection pooling problems, so if you could post the error message that's being logged or displayed (assuming there is one), that might give people a better idea of what's wrong.
answered Jul 3 '11 at 12:15
James LJames L
3591518
3591518
add a comment |
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f172089%2fwhat-is-causing-intermittent-connections-problems-from-web-server-to-sql-server%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown