Welcome to ISAserver.org

Failed Connection Attempt - HTTP Status Code 13

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2004 Firewall] >> Firewall Client >> Failed Connection Attempt - HTTP Status Code 13

Page: [1]

Message

<< Older Topic Newer Topic >>

Failed Connection Attempt - HTTP Status Code 13 - 5.Apr.2005 5:22:00 PM

tjcarst

Posts: 171
Joined: 6.May2004
From: Lincoln, NE
Status: offline

I am pulling my hair out on this one. I have allowed all users access to this address. If I set my clients to bypass ISA and go through my external hardware firewall, it is successful. Any ideas here would help me save what's left of my hair.

--- Error ---
(received on Windows 2000 & Windows XP Web Proxy/Firewall/SecureNAT clients)

"Unable to establish secure socket, error = 336130315
error:1408F10B:SSL routines:SSL_3_GET_RECORD:wrong version number"

"Unable to establish connection with host. The SSL handshake failed."

--- ISA Log ---

Original Client IP: 0.0.0.0
Transport: TCP
Log Record Type: Firewall
Destination IP: 65.16.47.152
Destination IP: 80
Protocol:
Action: Donnection failed
Source Network: Internal
Destination Network: External

Firewall Client Application Settings:
Application: BZMD.PRO
Key: Disable Value: 0
Key: DisableEx Value: 0

[ April 05, 2005, 11:30 PM: Message edited by: tjcarst ]

Post #: 1

Featured Links*

RE: Failed Connection Attempt - HTTP Status Code 13 - 5.Apr.2005 9:55:00 PM

tjcarst

Posts: 171
Joined: 6.May2004
From: Lincoln, NE
Status: offline

The breakdown appears to happen here:

Original Client IP: 0.0.0.0
Bytes Sent: 2153
Bytes Rec: 102
Result code: 0x80074e24
HTTP Status Code: 13
Log Record: Web Proxy
Destination IP: 65.16.47.152
Destination Port: 80
Action: Failed Connection Attempt

Any ideas? My hair is thinning....

Thanks.

tjcarst

(in reply to tjcarst)

Post #: 2

RE: Failed Connection Attempt - HTTP Status Code 13 - 7.Apr.2005 5:43:00 PM

tjcarst

Posts: 171
Joined: 6.May2004
From: Lincoln, NE
Status: offline

I have spent hours on this and have made no progress.

Has anyone else any ideas?

(in reply to tjcarst)

Post #: 3

RE: Failed Connection Attempt - HTTP Status Code 13 - 13.Apr.2005 10:40:00 PM

Guest

Hello,

Any luck with this? I am running into a similar issue.

cwilliams@capcomfcu.org

(in reply to tjcarst)

Post #: 4

RE: Failed Connection Attempt - HTTP Status Code 13 - 15.Apr.2005 8:36:00 PM

tjcarst

Posts: 171
Joined: 6.May2004
From: Lincoln, NE
Status: offline

No luck yet. I'm completely bald now...

(in reply to tjcarst)

Post #: 5

RE: Failed Connection Attempt - HTTP Status Code 13 - 29.Apr.2005 6:15:00 PM

Guest

Try turning off the Web Proxy Filter in the HTTP protocol definition.

(in reply to tjcarst)

Post #: 6

RE: Failed Connection Attempt - HTTP Status Code 13 - 30.Jun.2005 3:57:00 PM

tjcarst

Posts: 171
Joined: 6.May2004
From: Lincoln, NE
Status: offline

I've given up. Disabling the HTTP Web Proxy Filter did not work either. I have a feeling this project will make it back on my project list someday soon. If anyone has any other ideas, they are appreciated.

tjcarst

[ June 30, 2005, 03:57 PM: Message edited by: tjcarst ]

(in reply to tjcarst)

Post #: 7

RE: Failed Connection Attempt - HTTP Status Code 13 - 6.Jul.2005 8:46:00 AM

netgoalie

Posts: 2
Joined: 6.Jul.2005
Status: offline

Have you tried enabling SSL over port 80? (I'm not sure why your app. is trying to do SSL over 80 as opposed to 443, but that's what your log seems to indicate.) If this is a home-grown app., can you change it to use port 443? If not, try saving the following script to a .vbs file and running it:

set isa=CreateObject("FPC.Root")
set tprange=isa.Arrays.GetContainingArray.ArrayPolicy.WebProxy.TunnelPortRanges
set tmp=tprange.AddRange("SSL 80", 80, 80)
tprange.Save

(in reply to tjcarst)

Post #: 8

RE: Failed Connection Attempt - HTTP Status Code 13 - 13.Jul.2005 2:39:00 PM

tjcarst

Posts: 171
Joined: 6.May2004
From: Lincoln, NE
Status: offline

I have not tried that yet.

(in reply to tjcarst)

Post #: 9

RE: Failed Connection Attempt - HTTP Status Code 13 - 13.Jul.2005 4:34:00 PM

tjcarst

Posts: 171
Joined: 6.May2004
From: Lincoln, NE
Status: offline

I can connect now that I enabled SSL on port 80. I still have some other errors, but I think they are specific to the third party connection software. I'll see if I can get them to assist now that I can connect.

Thanks for the suggestion. I had enabled tcp 80 to their site, but hadn't made it SSL.

tjcarst

(in reply to tjcarst)

Post #: 10

RE: Failed Connection Attempt - HTTP Status Code 13 - 11.Oct.2005 6:15:00 AM

whatech

Posts: 11
Joined: 8.Sep.2004
Status: offline

If you enable SSL over port 80, how does it affect those websites that uses 443?

I am having a similar problem accessing a citrix web application via proxy. Basically, when I log on to their website and click the application I need, it then downloads a file that is associated with the Citrix ICA Web client. The ICA Web client fires up a connection to a Citrix Metaframe server on TCP port 80. I have set an allow rule to the ip address range they have specified, but I am not able to access the application.

Can you please tell me, if I set SSL to port 80, does that mean we won't be able to access secure sites using SSL 443?

Also, according to the user guide of the website im trying to access, if using SOCKS & HTTPS Proxies, I need a dns/host entry for 'FTRL_PROXY' which corresponds to the ip address of their SOCKS.

Some help would be appreciated.

Thanks.

(in reply to tjcarst)

Post #: 11