Force network traffic through a specific nic

  • Thread starter Thread starter Nick
  • Start date Start date
N

Nick

I have an application that runs on three servers, two web
and one database. In an effort to speed transactions and
reduce network traffic, I want to use a crossover cable
between the main app server and the database server on
secondary nics and use netbeui as the communication
protocol. When I set this up I'm seeing no activity on the
netbeui nics.

I have changed the odbc on the main app server to use
named pipes in an effort to force traffic down this path
but that didn't work. I can't disconnect the tcpip nic on
the database server because the second app server still
has to communicate with the database server.

Is there some way to assign administrative cost to the
nics or to ensure that when the application uses the odbc
traffic defaults to netbeui?

TIA,
Nick Harley
 
Nick said:
I have an application that runs on three servers, two web
and one database. In an effort to speed transactions and
reduce network traffic, I want to use a crossover cable
between the main app server and the database server on
secondary nics and use netbeui as the communication
protocol. When I set this up I'm seeing no activity on the
netbeui nics.

I have changed the odbc on the main app server to use
named pipes in an effort to force traffic down this path
but that didn't work. I can't disconnect the tcpip nic on
the database server because the second app server still
has to communicate with the database server.

Is there some way to assign administrative cost to the
nics or to ensure that when the application uses the odbc
traffic defaults to netbeui?

TIA,
Nick Harley
Click to expand...
Hello,

AFAIK, it isn't possible to tell an application to use a specific
NIC.

When you enabled NETBEUI on the secondary NICs, did you disable
NETBEUI on the primary NICs?

You can create a "private IP network" using a crossover cable on the
secondary NICs of the servers. Assign 10.1.1.1 and 10.1.1.2 to the
secondary NICs, and tell your DB and App server to talk to each other
via the 10. network rather than the regular one. This may be a
viable solution in your scenario.

regards,

SteveC
======
If at first you don't succeed, forget skydiving
 
Back
Top