No. When the application generates its own outbound traffic (as opposed to
traffic that's a reply to an inbound request) it simply creates data and
drops it on the stack. The stack divides the data into packets and consults
the routing table to see which interface can route the data to its destination.
If more than one interface is capable, then the stack chooses the interface
with the lowest metric (lower numbers mean higher priority). If both metrics
are the same, the stack chooses the interface that's bound first.
There are ways you can code an application to use a specific interface; how
to do that is buried somewhere deep within MSDN but I don't know where. If
your application B is packaged software, there's nothing you can do other
than contact the vendor and ask for a modification.
Steve Riley
(E-Mail Removed)
> Good day.
>
> I have configured two IP's of the same network on a network card,
> because each application needs to bind to ports 80 and 443.
>
> IP A is binded to IIS.
> IP B is binded to application B.
> So, far everything works, except for when application B uses IP A to
> access an internal server.
>
> Is there any way to configure the server to use IP B when application
> B is accessing the internal server?
>
> thanks.
>