dual NIC cards SQL Server does not exist

[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access
denied
I have two NIC cards on my client machine.
NIC #1 is the corporate network where my SQLServer resides.
NIC #2 is for a local device accessed via TCP/IP.
When I try to open a connection to the corporate database I sometimes get
the error above.
If the other device on NIC #2 is powered off I always find the server.
I know the database is always on NIC card #1.
How can I force DBNETLIB to always connect to try a specific NIC card?
Does using named pipes affect this?
Eggle
Try connecting using the IP address for NIC 1.
-Sue
On Wed, 7 Mar 2007 07:22:03 -0800, RedBear
<RedBear@.discussions.microsoft.com> wrote:

>[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access
>denied
>I have two NIC cards on my client machine.
>NIC #1 is the corporate network where my SQLServer resides.
>NIC #2 is for a local device accessed via TCP/IP.
>When I try to open a connection to the corporate database I sometimes get
>the error above.
>If the other device on NIC #2 is powered off I always find the server.
>I know the database is always on NIC card #1.
>How can I force DBNETLIB to always connect to try a specific NIC card?
>Does using named pipes affect this?
|||I have tried IP Address and WINDS name.
The problem is intermittent - connect #1 works, #2 fails, more work more fail.
It seems like the connect is getting routed to NIC #2 where it fails as
expected but never tried on NIC #1 where it would have succeeded.
Can I force a connect onto a specifc NIC card?
The low level connect code should try all NIC cards and declare failure only
after all NIC cards have replied negative or timeed out.
Eggle
"Sue Hoegemeier" wrote:

> Try connecting using the IP address for NIC 1.
> -Sue
> On Wed, 7 Mar 2007 07:22:03 -0800, RedBear
> <RedBear@.discussions.microsoft.com> wrote:
>
>
|||The only way I know of to force it to a specific card is to use that
cards IP address.
Being that it's intermittent, it will be very difficult to
troubleshoot although it's more likely something on the hardware side
of the configuration - maybe something with how the dual NICs are set
up, if you have something like teaming enabled, etc.
And it could be that it's not related to the dual NICs - you could
possible have the intermittent connectivity errors with just one NIC.
The following article has a lot of troubleshooting steps:
http://support.microsoft.com/kb/328306
-Sue
On Mon, 12 Mar 2007 05:18:03 -0700, RedBear
<RedBear@.discussions.microsoft.com> wrote:

>I have tried IP Address and WINDS name.
>The problem is intermittent - connect #1 works, #2 fails, more work more fail.
>It seems like the connect is getting routed to NIC #2 where it fails as
>expected but never tried on NIC #1 where it would have succeeded.
>Can I force a connect onto a specifc NIC card?
>The low level connect code should try all NIC cards and declare failure only
>after all NIC cards have replied negative or timeed out.