spouseele
Posts: 12782
Joined: 1.Jun.2001
From: Belgium
Status: offline
|
Hi Yaroslav,
I have just redone the test of server publishing the outgoing web proxy listener and it worked as expected. I have used a open protocol and site&content rule and verified that in the firewall and web proxy log the requests where accepted. Here is an excerpt of the firewall and proxy log: code:
Firewall log ------------ 10.0.129.1, -, -, N, 11/4/2002, 22:34:42, fwsrv, ISA, -, -, 217.136.92.194, 1983, -, 0, 0, 8080, TCP, Accept, -, -, -, 0, 0, -, -, 2, 45 10.0.129.1, -, -, N, 11/4/2002, 22:34:42, fwsrv, ISA, -, -, 217.136.92.194, 1984, -, 0, 0, 8080, TCP, Accept, -, -, -, 0, 0, -, -, 2, 45 10.0.129.1, -, -, N, 11/4/2002, 22:34:42, fwsrv, ISA, -, -, 217.136.92.194, 1985, -, 0, 0, 8080, TCP, Accept, -, -, -, 0, 0, -, -, 2, 45 10.0.129.1, -, -, N, 11/4/2002, 22:34:42, fwsrv, ISA, -, -, 217.136.92.194, 1986, -, 0, 0, 8080, TCP, Accept, -, -, -, 0, 0, -, -, 2, 45 10.0.129.1, -, -, N, 11/4/2002, 22:34:42, fwsrv, ISA, -, -, 217.136.92.194, 1987, 16, 0, 0, 8080, TCP, Accept, -, -, -, 0, 0, -, -, 2, 45 10.0.129.1, -, -, N, 11/4/2002, 22:35:41, fwsrv, ISA, -, -, 217.136.92.194, 1984, 58687, 0, 0, 8080, TCP, Accept, -, -, -, 20000, 0, -, -, 2, 45 10.0.129.1, -, -, N, 11/4/2002, 22:35:41, fwsrv, ISA, -, -, 217.136.92.194, 1987, 58828, 0, 0, 8080, TCP, Accept, -, -, -, 20000, 0, -, -, 2, 45 10.0.129.1, -, -, N, 11/4/2002, 22:35:41, fwsrv, ISA, -, -, 217.136.92.194, 1986, 58875, 0, 0, 8080, TCP, Accept, -, -, -, 20000, 0, -, -, 2, 45 10.0.129.1, -, -, N, 11/4/2002, 22:35:41, fwsrv, ISA, -, -, 217.136.92.194, 1983, 59531, 0, 0, 8080, TCP, Accept, -, -, -, 20000, 0, -, -, 2, 45 10.0.129.1, -, -, N, 11/4/2002, 22:35:55, fwsrv, ISA, -, -, 217.136.92.194, 1985, 71828, 0, 0, 8080, TCP, Accept, -, -, -, 20000, 0, -, -, 2, 45 1
Web proxy log ------------- 127.0.0.1, anonymous, Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0), N, 11/4/2002, 22:35:35, w3proxy, ISA, -, www.google.be, 216.239.53.101, 80, 203, 295, 4378, http, TCP, GET, http://www.google.be/, text/html, Inet, 200, 0x40020005, PR-SPECIAL, SCR-INTERNET 127.0.0.1, anonymous, Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0), N, 11/4/2002, 22:35:35, w3proxy, ISA, -, www.google.be, 216.239.53.101, 80, 188, 391, 195, http, TCP, GET, http://www.google.be/images/hp0.gif, text/html, Inet, 304, 0x40000006, PR-SPECIAL, SCR-INTERNET 127.0.0.1, anonymous, Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0), N, 11/4/2002, 22:35:35, w3proxy, ISA, -, www.google.be, 216.239.53.101, 80, 188, 391, 195, http, TCP, GET, http://www.google.be/images/hp1.gif, text/html, Inet, 304, 0x40000006, PR-SPECIAL, SCR-INTERNET 127.0.0.1, anonymous, Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0), N, 11/4/2002, 22:35:35, w3proxy, ISA, -, www.google.be, 216.239.53.101, 80, 172, 391, 195, http, TCP, GET, http://www.google.be/images/hp2.gif, text/html, Inet, 304, 0x40000006, PR-SPECIAL, SCR-INTERNET 127.0.0.1, anonymous, Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0), N, 11/4/2002, 22:35:35, w3proxy, ISA, -, www.google.be, 216.239.53.101, 80, 171, 391, 195, http, TCP, GET, http://www.google.be/images/hp3.gif, text/html, Inet, 304, 0x40000006, PR-SPECIAL, SCR-INTERNET
So, it sounds more like a authorization problem in your case.
HTH, Stefaan
|