Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
KHeon
Posting Yak Master
135 Posts |
 Posted - 2002-06-10 : 14:27:23
|
Hello everyone!quote:
multihomed -An adjective used to describe a host that is connected to two or more networks or has two or more network addresses. For example, a network server may be connected to a serial line and a LAN or to multiple LANs.definition courtesy of [url]www.webopedia.com[/url]
We've got a strange issue with one of our webservers communicating to our SQL Server [7].Here's the deal, we have a webserver that has dual nics (multihomed) that for some reason when communicating with our SQL Server is dreadfully slow, takig anywheres from 4-6 seconds per insert (round-trip) but when we remove the second nic and test it's right where I'd expect it, between 4-18 milliseconds. The SQL Server is located internally, the webserver is located externally (about 1/2 mile down the road). The is a firewall on both ends.Any thoughts?Kyle HeonPixelMEDIA, Inc.Senior Application Programmer, MCPkheon@pixelmedia.comEdited by - KHeon on 06/10/2002 14:28:35 |
|
|
efelito
Constraint Violating Yak Guru
478 Posts |
Posted - 2002-06-10 : 14:36:45
|
| Is anything else on the server slow when both NICs are in? Does the server run at normal speed no matter which NIC is left in? Do you have to pull the NIC or does disabling it do the trick? What OS and SP are you running?Jeff BanschbachConsultant, MCDBA |
 |
|
|
KHeon
Posting Yak Master
135 Posts |
Posted - 2002-06-10 : 14:49:14
|
| The card was disabled and it was the LAN side that was disabled. The server is NT4 w/SP6a + 7 roll-upThe IT guy is hoping that when we re-enable the second nic card that everything will be okay. The reason he thinks this will happen is because when the server was rebuilt (last month or so) the system was brought up with the LAN side nic first, which mapped all bindings to the improper card and then when the second nic was placed in, which is the acting WAN nic the mappings never got rebound to the proper card.I'm not a network guru unfortunately so I don't know if that makes sense or not. Since the rebuld, when we'd ping the server by it's name, on the server we'd get the IP for the LAN nic, not the WAN nic, that is not the case now when we ping the server by name from itself.Thanks!Kyle HeonPixelMEDIA, Inc.Senior Application Programmer, MCPkheon@pixelmedia.com |
|
|
|
setbasedisthetruepath
Used SQL Salesman
992 Posts |
Posted - 2002-06-10 : 15:22:46
|
| I would suspect that the webserver is lacking a static route which forces communication through one of the two NIC's. More than likely the webserver is broadcasting those packets across both NIC's.A traceroute or pathping will tell you for sure.setBasedIsTheTruepath<O> |
|
|
|
KHeon
Posting Yak Master
135 Posts |
Posted - 2002-06-10 : 15:35:44
|
| We've done both pings and tracert and they look okay. We've done them from both the SQL Server side and the webserver side. Generally response time is about 10ms. Tracert is only a few hops max.Thanks!Kyle HeonPixelMEDIA, Inc.Senior Application Programmer, MCPkheon@pixelmedia.com |
|
|
|
|
|
|
|
|
Multihomed SQL Server Issues