Welcome to ISAserver.org

Forums | Register | Login | My Profile | Inbox | RSS RSS icon | My Subscription | My Forums | Address Book | Member List | Search | FAQ | Ticket List | Log Out

Web Publishing Error Code 64 Host not available

Users viewing this topic: none

Logged in as: Guest
  Printable Version
All Forums >> [ISA 2006 Publishing] >> Web Publishing >> Web Publishing Error Code 64 Host not available Page: [1]
Login
Message << Older Topic   Newer Topic >>
Web Publishing Error Code 64 Host not available - 18.Nov.2008 12:51:36 PM   
onesquin

 

Posts: 3
Joined: 18.Aug.2005
Status: offline
I just recently swapped out hardware for our ISA Server.  Technically everything in our environment is the same except The ISA Server with the fundamental difference being the old server was 2006 SP0 and the new server is ISA 2006 SP1.

All of the rules were imported.  Before we did not have any problems publishing a web server that serves out several applications.  Here are the details on the server

Windows Server 2003 R2
It is using an IIS Connector to serve Apache Tomcat(v5) based applications.  The applications are Atlassian Confluence and Atlassian Jira.

Basically after clicking around for a while after logging in there will be an
Error Code 64 Host not available on the browser.
The corresponding error on the ISA server log is a Failed Connection Attempt with status
Status: 64 The specified network name is no longer available.

This is 100% repeatable for both of the applications.
There is zero problem with the applications internally.
I have created new publishing rules and the same has happened
I have changed the keepalives for IIS and nothing.
I have tried all four combinations of the Forward Orig Host header and Proxy requests to published site under the TO tab of the publish rule with no luck.

There are some errors in the ISAPI connector log, but it is not consistent with the errors.

Any help would be greatly appreciated.  I might have forgotten some info, let me know if you need anything else.
Post #: 1
RE: Web Publishing Error Code 64 Host not available - 21.Nov.2008 10:33:23 AM   
tshinder

 

Posts: 47669
Joined: 10.Jan.2001
From: Texas
Status: online
Did you install the fix for the RSS bug on the Windows 2003 SP2 machine?

Tom

_____________________________

Thomas W Shinder, M.D.
Sr. Consultant/Technical Writer
Prowess Consulting http://www.prowessconsulting.com/
Blog: http://blogs.isaserver.org/shinder/

GET THE NEW ISA 2006 Book!: http://tinyurl.com/2gpoo8

(in reply to onesquin)
Post #: 2
RE: Web Publishing Error Code 64 Host not available - 21.Nov.2008 11:18:21 AM   
preeves

 

Posts: 24
Joined: 2.Dec.2004
Status: offline
Hmmmm, I have a similar problem, with a site that has multiple images on 1 page, only 1 or two of the thumbnails will load, the rest show as broken links along with the status 64 error in the isa log.
Reloading the page (not refreshing the page) causes another couple of the thumbnails to load.
There is also a similar problem a few below this post.

I do have EnableRSS = 0 in the registry (on ISA), and I do have other sites which as far as I know do not have this problem, although on other IIS servers.

Paul

(in reply to tshinder)
Post #: 3
RE: Web Publishing Error Code 64 Host not available - 21.Nov.2008 11:36:06 AM   
onesquin

 

Posts: 3
Joined: 18.Aug.2005
Status: offline
I am pretty sure we have it narrowed down to the NTLM authentication.  We are working through it right now.  Will update you if a definitive answer is found.

(in reply to preeves)
Post #: 4
RE: Web Publishing Error Code 64 Host not available - 21.Nov.2008 5:01:38 PM   
jhood

 

Posts: 18
Joined: 6.Jun.2006
Status: offline
I been working with onesquin on this problem and tried the rss fix but no love.

Breakdown..

If the published rule is set to all users, then the site comes through without a problem.

If the published rule is set to authenticated users using the HTML form based authentication, then the site comes through, BUT gives a host not found error on the 2nd or 3rd link you click on.

We have other sites working like exchange owa, it is just the websites using the Tomcat java server that are having problems. However it was working perfectly for months till we upgraded the hardware, along with sp1 for isa 2006.

The "test run" button of the rule comes back positive, as expected since it takes 2 or 3 clicks on the site to break.

-isa server SSL listener using forms based authentication
-web server - iis redirecting to Tomcat that redirects back iis.

exact error code is : 64 Host not available, the connection to the web server was lost.

(in reply to onesquin)
Post #: 5
RE: Web Publishing Error Code 64 Host not available - 25.Nov.2008 7:53:05 AM   
tshinder

 

Posts: 47669
Joined: 10.Jan.2001
From: Texas
Status: online
Hi J,

It might be related to the Java app and changes make with SP1. You might want to check and see if it works if you remove SP1 -- that way you can isolate that vairable and let PSS know that it's a SP1 issue. If removing SP1 doesn't fix it, then it might be a bug in the Web site.

HTH,
Tom

_____________________________

Thomas W Shinder, M.D.
Sr. Consultant/Technical Writer
Prowess Consulting http://www.prowessconsulting.com/
Blog: http://blogs.isaserver.org/shinder/

GET THE NEW ISA 2006 Book!: http://tinyurl.com/2gpoo8

(in reply to jhood)
Post #: 6
RE: Web Publishing Error Code 64 Host not available - 25.Nov.2008 9:03:09 AM   
onesquin

 

Posts: 3
Joined: 18.Aug.2005
Status: offline
Actually it was the NTLM authentication.  We removed the NTLM authentication from the publishing rule and changed it to No authentication.  We simply set the listener to do the authentication.

Something must have slightly changed in SP1 to cause it to work a little differently.

(in reply to tshinder)
Post #: 7
RE: Web Publishing Error Code 64 Host not available - 28.Nov.2008 10:09:19 AM   
tshinder

 

Posts: 47669
Joined: 10.Jan.2001
From: Texas
Status: online
Just so that I have this striaght -- NTLM auth was enabled on the listener.

We're you forcing authentication at the listener or on the Web Publshing Rule?

Thanks!
Tom

_____________________________

Thomas W Shinder, M.D.
Sr. Consultant/Technical Writer
Prowess Consulting http://www.prowessconsulting.com/
Blog: http://blogs.isaserver.org/shinder/

GET THE NEW ISA 2006 Book!: http://tinyurl.com/2gpoo8

(in reply to onesquin)
Post #: 8
RE: Web Publishing Error Code 64 Host not available - 5.Dec.2008 10:23:18 AM   
yeskaygee1

 

Posts: 14
Joined: 5.Dec.2008
Status: offline
Hello,

I am new to this forum and I would like to report a similar problem on this with a different settings

1 - The listener is configured without SSL and with no authentication
2 - The access is restricted to a specific group of hosts
3 - The connection works for all but few (3 to 4) hosts.

The error messages returned from the ISA logs are either or both of the below
Status: 64 The specified network name is no longer available
Status: 1460 This operation returned because the timeout period expired

I am really not sure if it is related to what you are already checking. But any pointers would really help.

Regards,
Karthigeyan

(in reply to tshinder)
Post #: 9
RE: Web Publishing Error Code 64 Host not available - 7.Dec.2008 9:24:40 PM   
tshinder

 

Posts: 47669
Joined: 10.Jan.2001
From: Texas
Status: online
Sounds like yours is an outbound access issue while the original post is an inbound access issue.

Tom

_____________________________

Thomas W Shinder, M.D.
Sr. Consultant/Technical Writer
Prowess Consulting http://www.prowessconsulting.com/
Blog: http://blogs.isaserver.org/shinder/

GET THE NEW ISA 2006 Book!: http://tinyurl.com/2gpoo8

(in reply to yeskaygee1)
Post #: 10
RE: Web Publishing Error Code 64 Host not available - 8.Dec.2008 9:24:34 AM   
jhood

 

Posts: 18
Joined: 6.Jun.2006
Status: offline
Yes, the web publishing rule had NTLM enabled, but it was never doing anything  since the webserver didnt have NTLM enabled.

However, we didnt want to rely on the java server(Tomcat) for security(it has a login page too), so leaving NTLM on the listener got us what we wanted.


What appears to happen, if you have NTLM on the publishing rule, but not on the webserver, ISA will show you 2 or 3 pages. Then ISA will kill the connection, but erroneously tell you connection was lost to the webserver.

Before sp1, ISA would allow this behaviour

(in reply to tshinder)
Post #: 11
RE: Web Publishing Error Code 64 Host not available - 8.Dec.2008 11:42:25 AM   
yeskaygee1

 

Posts: 14
Joined: 5.Dec.2008
Status: offline
This error is reported on an inbound access. To be more clear on the scenario below are the details and problem description

1 - The internal server has got multiple portals (portal1:80, portal2:8080, portal3:8081) published on different ports.

2 - Connection from external hosts (access restricted to hosts H1, H2, H3 ) works fine on all portals. Connection from host H4 does not work for portal:8080 but works for other published portals

3 - The ISA error logs matches the traffic from external host to the portal2 on port 8080 but throws out this error (ISA error 64). I also see unsually high processing time (in the range of 1000000 ms)

4 - I am using a single listener (non https) for publishing all the portals through multiple rules.

It would be really helpful if some one can throw light on this error.

Regards,
Karthigeyan Sankar

(in reply to tshinder)
Post #: 12

Page:   [1] << Older Topic    Newer Topic >>
All Forums >> [ISA 2006 Publishing] >> Web Publishing >> Web Publishing Error Code 64 Host not available Page: [1]
Jump to:

New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts