Bind Application to network Adapter

Hi everyone:

I have a Windows 2008 R2 server with two network adapters, one is connected
to Administration VLAN and the other is connected to Production VLAN. I
would like to do some things for one adapter and another things for the
other. For example, I would like to do my backups through the network
adapter which is not in the Production VLAN, or when i copy files from a
server to this server i would like to use the the network adapter which is
not in the Production VLAN. How can I bind a network adapter with an
application or program???

Thanks in advance



Hola a todos:

Tengo un servidor con 2 tarjetas, una en una VLAN y la otra en otra VLAN. El
tema es que me gustaría hacer ciertas operaciones por una tarjeta y otras
por otra. Por ejemplo. Me gustaría que el backup se realizara usuando la
tarjeta de red de una VLAN distinta de la VLAN de Produccion, o que cuando
copio ficheros a ese servidor se utilice la tarjeta que no esta en
produccion. Como puedo determinar que el sistema operativo haga ciertas
cosas por una tarjeta y otras por otra???

Muchas Gracias por Adelantado

Un saludo

"Eduardo" <(E-Mail Removed)> wrote in message
news:48F788BA-0B91-4749-878E-(E-Mail Removed)...
> Hi everyone:
>
> I have a Windows 2008 R2 server with two network adapters, one is
> connected to Administration VLAN and the other is connected to Production
> VLAN. I would like to do some things for one adapter and another things
> for the other. For example, I would like to do my backups through the
> network adapter which is not in the Production VLAN, or when i copy files
> from a server to this server i would like to use the the network adapter
> which is not in the Production VLAN. How can I bind a network adapter with
> an application or program???

You don't. There is no such thing.

First,...what you are trying to do is just plain a bad idea.

The Nic used is based on the destination.
The destination is based on the destiantion IP# because name resolution
won't work like this.

......and you cannot run both Nics in the subnet (in case you wanted to
suggest that next).

--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
Technet Library
ISA2004

Yes but if I have my backup server with two nics too, one in Production Vlan
and the other in Administration how can i force backup traffic to use
administration nic???

Thanks in advance

"Phillip Windell" <(E-Mail Removed)> escribió en el mensaje de
noticias:(E-Mail Removed)...
>
> "Eduardo" <(E-Mail Removed)> wrote in message
> news:48F788BA-0B91-4749-878E-(E-Mail Removed)...
>> Hi everyone:
>>
>> I have a Windows 2008 R2 server with two network adapters, one is
>> connected to Administration VLAN and the other is connected to Production
>> VLAN. I would like to do some things for one adapter and another things
>> for the other. For example, I would like to do my backups through the
>> network adapter which is not in the Production VLAN, or when i copy files
>> from a server to this server i would like to use the the network adapter
>> which is not in the Production VLAN. How can I bind a network adapter
>> with an application or program???
>
> You don't. There is no such thing.
>
> First,...what you are trying to do is just plain a bad idea.
>
> The Nic used is based on the destination.
> The destination is based on the destiantion IP# because name resolution
> won't work like this.
>
> .....and you cannot run both Nics in the subnet (in case you wanted to
> suggest that next).
>
> --
> Phillip Windell
>
> The views expressed, are my own and not those of my employer, or
> Microsoft,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------
> Technet Library
> ISA2004
>
>

"Eduardo" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Yes but if I have my backup server with two nics too, one in Production
> Vlan and the other in Administration how can i force backup traffic to use
> administration nic???

I answered that already.

The path is determined by the destination, the destination is identified by
the IP#.

The destination is everything. The routing table chooses the route based on
the destiantion IP#,...the route chosen by the routing table defines the
source IP of the source interface used.

So the Backup Utility must choose the storage location by the IP#
only,...you cannot use a name unless you make special arrangments with a
fake name to be used for the second IP on the destiantion.

Usually when people do this they are trying to solve perceived imaginary
traffic problems that do not exist. I run my backups over the regular
LAN,...have for 10 years,...never had a traffic problem.

The modern movement toward Virtualization is making this stuff more and more
a thing of the past.

--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

Thank you very much, I'll try to build a manual solution



"Phillip Windell" <(E-Mail Removed)> escribió en el mensaje de
noticias:(E-Mail Removed)...
> "Eduardo" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> Yes but if I have my backup server with two nics too, one in Production
>> Vlan and the other in Administration how can i force backup traffic to
>> use administration nic???
>
> I answered that already.
>
> The path is determined by the destination, the destination is identified
> by the IP#.
>
> The destination is everything. The routing table chooses the route based
> on the destiantion IP#,...the route chosen by the routing table defines
> the source IP of the source interface used.
>
> So the Backup Utility must choose the storage location by the IP#
> only,...you cannot use a name unless you make special arrangments with a
> fake name to be used for the second IP on the destiantion.
>
> Usually when people do this they are trying to solve perceived imaginary
> traffic problems that do not exist. I run my backups over the regular
> LAN,...have for 10 years,...never had a traffic problem.
>
> The modern movement toward Virtualization is making this stuff more and
> more a thing of the past.
>
> --
> Phillip Windell
>
> The views expressed, are my own and not those of my employer, or
> Microsoft,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------
>
>