Isa Error 0x80
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > ISA 2004 (Error Code 64: Host not available) gives intermittent and random error. Want to Advertise Here? Solved ISA 2004 (Error Code 64: Host not available) gives intermittent and random error. Posted on 2006-03-22 Software Firewalls 1 Verified Solution 30 Comments 37,065 Views Last Modified: 2013-11-16 Dear Experts!! Before I start, I would like to mention that I tried the solution from an expert article "Q_21483635.html", but no luck. We have even opened a case with Microsoft PSS, and its been 10days now without any breakthrough. We have an ISA 2004 Server with Service Pack 2 running on Windows Server 2003. The problem is explained below.......... When user browse the Web Page. It will open for two or three pages. Intermittently, it will not open, and we need to click refresh for browsing. This happen very often. While checking in ISA logging Query we can see the Allowed user (By checking PC’s IP) as anonymous User and access was denied. If the same User when refreshes the browser they can able to browse and in ISA logging Monitor we are able to see the particular user's login name. Error Message: Technical Information (for support personnel) · Error Code 64: Host not available · Background: The gateway or proxy server lost connection to the Web server. · Date: 3/11/2006 8:12:21 AM · Server: prxycity1.internal.com · Source: Remote server Just to eliminate doubts on network side, we tried accessing the internet directly without the Proxy server, and things work normal, but with ISA the error keeps coming randomly. Please help. 0 Question by:imkazi Facebook Twitter LinkedIn Google LVL 51 Best Solution byKeith Alabaster Lets look at this from a different angle. On the ISA server, if you click start programs isa server performance counters, it will start with a standard set of counters specific to ISA. you can also Go to Solution 30 Comments LVL 51 Overa
the webproxy for http traffic works fine, however, I've noticed that I'm having troubles accessing some https websites via the proxy... Most https sites work, but some don't... When I bypass the proxy (turn of proxy in IE on my client), I can access the https website just fine. And when I access the https website from the proxy itself (without using the ISA engine), I can access the https website as well... (https://webmail.telenet.be) The ISA server log show the following entries : HTTP Status CodeCache InformationError InformationLog Record TypeDestination PortProtocolActionHTTP https://www.experts-exchange.com/questions/21784015/ISA-2004-Error-Code-64-Host-not-available-gives-intermittent-and-random-error.html MethodURL 4070x00x800Web Proxy Filter443SSL-tunnelAllowed Connectionwebmail.telenet.be:443 4070x00x800Web Proxy Filter443SSL-tunnelAllowed Connectionwebmail.telenet.be:443 12210 An Internet Server API (ISAPI) filter has finished handling the request. Contact your system administrator. 0x00x80Web Proxy Filter443SSL-tunnelFailed Connection AttemptCONNECT 4070x00x800Web Proxy Filter443SSL-tunnelAllowed Connectionwebmail.telenet.be:443 4070x00x800Web Proxy Filter443SSL-tunnelAllowed Connectionwebmail.telenet.be:443 4070x00x800Web Proxy Filter443SSL-tunnelAllowed Connectionwebmail.telenet.be:443 4070x00x800Web Proxy Filter443SSL-tunnelAllowed Connectionwebmail.telenet.be:443 12210 An Internet Server API (ISAPI) filter has finished handling the request. Contact your system administrator. 0x00x80Web Proxy Filter443SSL-tunnelFailed Connection AttemptCONNECT http://forums.isaserver.org/m_2002049012/printable.htm Any suggestions ? thanks c0d3r -> RE: HTTPS via ISA 2006 WebProxy (16.Jul.2007 3:35:47 AM) Update : I'm using Websense Web Security(6.3.1) on the same server as well ... I've turned of the Websense Isapi filter, and access is restored... I'll open a ticket with Websense, but maybe someone has had the same problem and can already point me into the right direction ? tx ferrix -> RE: HTTPS via ISA 2006 WebProxy (16.Jul.2007 11:20:05 AM) It looks like websense is blocking the CONNECT requests. I don't know whether that's a configuration problem or a bug... When you're connecting from the proxy itself, it is likely that you're using Secure-NAT instead of IE "proxy settings", and the SSL requests are handled slightly differently by the proxy and CONNECT req's are not used (perhaps bypassing whatever is causing you trouble). In my experience, outbound filters and SSL don't mix unless you are inspecting the SSL traffic. Websense can only look at the CONNECT lines and make a decision that way, it can't see inside the encrypted https traffic. (If you want that feature you need to add another third party filter to your ISA to enable it) Page: [1]
this is happening. On my ISA Server, I am unable to get to the internet. This happens wether I have the connection settings to use itself for the proxy http://www.yqcomputer.com/146_1082_1.htm server or not in IE Options. When I do enable the proxy settings, I see http://www.chicagotech.net/msapps/isa1.htm ISA Denying access to the User account, using the Default Rule. I have 1 rule that I made that allows access to several specific user accounts on my domain INCLUDING the administrator account. On any other server, I have no problem to the internet. When I enable the proxy settings on the ISA Server, I see Error 0x80 The ISA Server isa error denied the specific URL. Im reading thru the help file in ISA Server and ISAServer.org but as of yet, no luck. Thanks! Top 1. ISA 2004 - Unable to connect to ISA Server from desktop using ISA Console - RPC Error 2. Unable to get SQL working from Web Server to SQL server through ISA server. We are using ISA Server 2004. We are also using SQL Server 2000 with the latest SP on isa error 0x80 a seperate server internally. We are tring to connect to SQL server from an outside location but can't. I tried the directions from Microsoft here http://www.yqcomputer.com/ I can connect internally if I use the IP address of the ISA server. So I know ISA is routing it correctly. When I try the ISA IP address externally though I'm not getting communication. I did make sure under the networks tab I had external selected. Any help would be appreciated. Thank you. 3. Isa Server 2004 - 2 ISA servers each a vpn to 1 target ISA 4. testing server behind one isa server needs to be seen behind another isa server 5. Unable to synchronize SUS Server throw ISA server 6. Unable to publish RDP Server with ISA Server 2000 7. Must ISA Server be installed in the same Server that is connected to Internet? 8. how come my isa server can't sync its time with internet server? 9. Reboot ISA server causes lost connection to the internet/2003 Server 10. how come my isa server can't sync its time with internet server? 11. Unable to access Internet from ISA Console 12. Unable to upload with FTP from internet to network with ISA 2004 - Error 550 13. New ISA Appliance - Internal clients unable to browse internet 14. Unable to upload with FTP from internet to network with ISA 2004
502 Proxy Error Whenever an ISA or TMG server throws a 502 Proxy Error your way, you know you are probably in for a real hurdle. But with a little familiarity with what a 502 error means, and how it can be fixed, you will be back in business in little time. First, let’s take a look at the definition of 502 HTTP response code: 502 Bad Gateway The server was acting as a gateway or proxy and received an invalid response from the upstream server. Pay close attention to what that is saying. The proxy (meaning your ISA or TMG server) received an invalid response from the upstream server (implying that the internal webserver that you are publishing!). Unfortunately that is not always the case as ISA and TMG can throw that error when they are unhappy about something that a normal browser would readily accept. They can also throw one of several different kinds of 502 depending on the circumstances. Understanding is critical to a quick resolution. Don’t just stop reading at 502, check the rest of the response. Here is how to determine whether the problem is with your ISA/TMG, or on the internal server: 1. Open a browser on the internal network. 2. Access the URL in question. 3. If you can view the content successfully, the problem is with your ISA/TMG. If not, the problem is with your webserver. Since this post is about ISA and TMG, let’s assume you are able to view the content internally just fine, so we’ll keep discussing ISA/TMG. 4. Go to your log viewer. In ISA that is Monitoring, or in TMG that is in Logs & Reports. 5. Edit the filter to look at live logs and have the user try again, or filter on the time range to see the error. Add the “Filter by” criteria for HTTP Status Code, and set it equal to 502. 6. Run the query, and examine the results. Some of the frequent causes of ISA/TMG generating 502s are: • A 502 can be thrown by the ISA/TMG when content filtering is enabled and something in the response is being blocked. Disable content filtering and see if you are then able to access the resource. If you are, look at the header in one of the logged errors (in your log, click the more information link on the error) and see what content type is being returned by the published server. Authorize that in your content filter. • If you are using ISA/TMG as a client proxy, and the destination server is running on a non-standard port, you can enc