views:

68

answers:

2
Q: 

IP Routing

I have a WinForms application that our customer install locally and it is accessing our webservers through a leased/private network. All WS calls is getting routed properly when adressing our web server, but when the application is trying to access some other external resource (RSS) that is on the WWW - .Net/Windows is sending this request via the leased line which, ofcourse, is unable to handle this request.

If the RSS adress is opened with an ordinary web browser, everything works as expected.

Our web servers are also available via the www, and if the application is configured to use this public adress the RSS traffic works fine.

Anyone got an idea on whats going on.

Regards Lars Krog-Jensen

A: 

Is your application configured to use a proxy to access all resources?

It shouldn't otherwise be possible for requests from your app to use different IP routing to requests from a standalone browser.

You can double check what the real routing table looks like by running

> route print

from a cmd.exe window

Alnitak
Yes, the application is configured with the .exe.config to use a specified proxy.
and is the proxy perhaps at the other end of the private leased line?
Alnitak
A: 

It sounds like you have to go through a proxy.

Brian Rasmussen