Hello Francois and all,
Is there any chance that THttpCli doesn't work on dialup connections?
In one of our (remote) environment, the user has a dialup connection.
While he can browse with no problems with IE, httptst sample returns
an error of Failed: 404 Connection timed out (Error #10060) with
Hmm. But windows firewall does not really block any outbound
requests. It only blocks servers ... correct me if I'm wrong.
Thursday, April 13, 2006, 10:14:59 AM, you wrote:
Is there any chance that THttpCli doesn't work on dialup connections?
In one of our (remote) environment, the user has a
Oh yes, you're right -- what was I thinking? I remember
having a problem like this a while back, and I think it
was some sort of outbound firewall that was active on
only the dialup. Maybe ZoneAlarm?
Hmm. But windows firewall does not really block any outbound
requests. It only blocks servers
Is there any chance that THttpCli doesn't work on dialup connections?
No, it works on any physical layer supported by winsock and not blocked by
any security software or device.
In one of our (remote) environment, the user has a dialup connection.
While he can browse with no problems with
Hello Jack,
try a telnet session in port 80 with the host to test the connection. If
it connect then the route is OK.
---
Rgds, Wilfried [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
http://www.mestdagh.biz
--
To unsubscribe or change your settings for TWSocket mailing list
please
