I have multiple IP addresses configured to a NIC in Windows 2003/2008 Servers. This is done to get unique internal IPs to IIS websites, and there is a static NAT from each of these internal website addresses to corresponding public addresses. Each internal IP has a unique public IP.
Windows cmd and other applications use primary IP as a source IP by default.
But now I have a problem in that I would need to initiate HTTP/HTTPS requests from one of the secondary addresses to an external website that has allowed incoming traffic from only this secondary address.
Is it possible to assign source IPs to windows applications in a less intrusive way than setting the secondary IP as a primary IP in Windows, or switching public addresses in the NAT configuration? I don't want to hassle with NAT or IP settings in a production server with remote connections only.
What I'm looking for is an easier way to test this external url than developing and deploying a web application running on the site with this secondary IP assigned.