Similar Threads
1. Unexpected client authentication popup when using IE and Web Proxy
2. Direct connect instead of going through firewall/proxy
ISA Server 2000 rookie could do with some help!
Recently I have noticed that my XP clients can only access the web via
a direct connection to the internet instead of going through the
installed firewall client, which points to the proxy on our SBS
server. As far as I am aware I have not (knowingly) made any changes
to our ISA Server 2000 setup apart from installing updates via
Microsoft Update.
Can anyone point me to areas where I can begin troubleshooting this
problem? Obviously I want all of our clients to access the web via our
proxy.
Any help would be greatly appreciated.
3. firewall client/proxy settings in IE
4. Web Proxy client access to IP Address instead of FQDN
Hi,
I found a strange problem I'm not sure if it's related to ISA2004 or IE6. I
have some WebProxy clients that access external Web sites, through ISA2004,
using destination IP Address instead of FQDN name typed in the IE Address
field. I see this in ISA logs: for some clients I notice that all the URL
begins with IP address and all the Destination Host Names are IP Addresses.
This cause failures accessing sites where the IP address is not among the
public names.
What may cause this problem ? Anyone already experienced this.
Thanks.
Massimo Piceni.
5. Not Using Proxy but clients are having thier IE settings Changed
6. Using IE proxy server settings in a web service client
I can not make proxy server settings in Internet Explorer work for my web
service client. When the proxy is defined manually, all is well.
But, when I import settings from Internet Explorer, the IsBypassed attribyte
becomes true and the address returned from GetProxy(url) is the same as the
Url I am entering in the call.
I do not know how the proxy server is configured, perhaps someone have an
advice for me or for the administrator of the proxy server?
When connecting to the network, from my office, through VPN, all is also
well in both cases. IsBypassed=false and GetProxy returns the address to the
actual proxy server.
And when I start IE and try the address of the web service server, I can
connect to it!
Reading about proxy servers, it seems it would work automatially, I have
also tried to run the program without setting the proxy, with same
dissapointing result.
I have spent days trying to make IE settings work in my program, but with
little success, and is wery greatful for any help in this matter.
Regards,
Kenneth Jonsson
public void SetServerProxy(SoapHttpClientProtocol service)
{
if (...)
{
// Install user proxy settings
WebProxy userProxy = new WebProxy(ProxyServer);
NetworkCredential credential = new NetworkCredential(ProxyUser,
ProxyPassword, ProxyDomain);
userProxy.Credentials = credential;
service.Proxy = userProxy;
}
else
{
// Install default IE proxy settings
service.Proxy = WebRequest.GetSystemWebProxy();
service.Proxy.Credentials = CredentialCache.DefaultNetworkCredentials;
bool isBypassed = service.Proxy.IsBypassed(new Uri(service.Url)); <--
becomes true
Uri proxy = service.Proxy.GetProxy(new Uri(service.Url)); <-- is not
the proxy server defined in Internet Explorer (instead it is the Url entered
in the call)
}
}
7. ISA firewall client vs Proxy client
8. Compatibility between Winsock Proxy Client 2.0, Firewall Client 20
Hi friends, my question is there is some compatibility issue with the
earliers versions o Firewall Client ISA Server 2004 and Winsock Proxy Client
2.0 and Firewall Client ISA 2000?
Could those earliers versions configure the web browser automatically too?
and
What are their limitations?
Really I was searching all the web for information in Internet but I
couldn't find anything about compatibility between ISA Server 2004 and
earlier versions of Firewall Client, I will apreciate any help or link.
thanks in advance,
Felipe C.