?
Solved

Specify Outbound Network Interface in ODBC Connection

Posted on 2011-09-26
3
Medium Priority
?
285 Views
Last Modified: 2012-05-12
Background:
A client machine needs to be able to query a SQL Server over the network using an ODBC connection.  The server will only accept connections from a specific IP range, and the client machine is not in the range.

We've come up with the idea of adding a second network card to the client machine, and configuring the second network card with an IP address that is in the specific range.  With that done, we now need to make the ODBC connection use that second network interface.  That is, the client needs to be configured to always connect to the SQL server using the second network interface.  Is this possible?  How?

Please note I have read this post already.  That question is the same as mine, but neither of those answers addresses the question.
0
Comment
Question by:mactfines
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 83

Expert Comment

by:Dave Baldwin
ID: 36600481
I have dual NICs in several computers here.  Windows uses the one that connects to the IP range I ask for.  I have two networks using private IP address ranges, one in 10.202.xx.xx and the other is 172.23.xx.xx.  On two machines I have web servers with two IP addesses, one in each range, and it works fine.

How is your setup different?  And how are you connecting to the SQL server?
0
 

Author Comment

by:mactfines
ID: 36600568
The difference here is that the SQL Server we are connecting to is not in the IP range of either of the network interfaces.  It is actually at another company altogether.  All connections to it need to come from a specific range of addresses, so I need to make the client always tries to connect using the new, second interface.  The logic Windows uses results in it always using the first--which makes sense to me, given they both have the same path through the Internet to the SQL server...

However, now that I write all that out, we should be able to just use the route command to specify that the route to the SQL server's IP always uses the second network interface.
0
 
LVL 42

Accepted Solution

by:
kevinhsieh earned 1500 total points
ID: 36600764
I was going to suggest using the route command to route traffic for the SQL server out to a gateway available to the second NIC.
0

Featured Post

Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Background Information Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
This article will inform Clients about common and important expectations from the freelancers (Experts) who are looking at your Gig.
Michael from AdRem Software outlines event notifications and Automatic Corrective Actions in network monitoring. Automatic Corrective Actions are scripts, which can automatically run upon discovery of a certain undesirable condition in your network.…
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…
Suggested Courses

800 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question