By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,220 Members | 1,091 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,220 IT Pros & Developers. It's quick & easy.

Setting Source IP address of WebService Call

P: n/a
I have an interesting problem...and its one of those where I know what I
want but don't know how to ask it =)

I have an eCommerce application that uses Paypal for its payment gateway.
It is an XML webservice that my eComm app makes the request to.

Well, It has to do so over a SSL link. Well...I have multiple SSL sites on
my Win2003 machine. Each IIS site has its own IP address so I can bind the
SSL Cert to each site. Well, the site that is using the webservice is NOT
using the default IP address of the machine.

Here is the IP scheme of my machine...

IP addresses: (Has an SSL site) (Has an SSL site)

Well, I think my problem is when I make the webservice call to Paypal from
the IIS site that is bound to, it is using as
the source to make the request (verified by my firewall logs). Well, the
connection gets dropped since the application is not bound to

I don't think its anything special as far as the consumption of the
webservice is concerned. In fact, it pulled in nicely to 05 for me.

If I set this up on a test server that does not have multiple IP addresses,
it works fine.

Is there anyway to set the source IP address of the application that is
consuming the webservice.

FYI: I can't really make any changes to the IP scheme

Any help would be great!


May 14 '06 #1
Share this Question
Share on Google+
1 Reply

P: n/a
Hi Eric,

Thank you for posting.

From your description, I understand that you have a webserver which has
multiple ipendpoint addresses bound to multiple IIS sites on the server.
And in each IIS site, there exists web application that will make
webservice call to another remote server. However, you found that the
source ip address of the service client is always a certain fixed one which
is unexpected from you, correct?

Based on my understanding, webservices calls are just normal network
operation and generally they're over http protocol. So when making
webservice call, .net framework use webrequest component to send http
message, and it internally use socket API to establish tcp connection. And
for raw SOCKET api (or the System.Net.Socket namespace's Socket component),
we can choose to bind a specific local ip endpoint. However, the .net's
webservice proxy or httpwebrequest component encapsulate the underlying
socket work, and automatically choose a most appropriate local ipendpoint
and port, and so far we haven't control on this at webservice layer. Also,
this is not related to IIS site's IP address setting.


Steven Cheng
Microsoft Online Community Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

This posting is provided "AS IS" with no warranties, and confers no rights.

Get Secure!
(This posting is provided "AS IS", with no warranties, and confers no

May 15 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.