• Twitter
  • FaceBook

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 Farm for hosting websites

Users viewing this topic: none

Logged in as: Guest
  Printable Version
All Forums >> [ISA 2006 General] >> Installation and Planning >> Web Farm for hosting websites Page: [1]
Message << Older Topic   Newer Topic >>
Web Farm for hosting websites - 27.Jul.2009 6:14:01 AM   


Posts: 3
Joined: 23.Feb.2009
Status: offline
Hi Guys,

We have a new network coming online in a new location and we need a bit of advice.

On our old network when we tried to do web farms we kept seeing issues where we would see an issue 64 come up in the trace with the message:
Failed Connection Attempt R2002 7/27/2009 10:34:28 AM
Log type: Web Proxy (Reverse)
Status: 64 The specified network name is no longer available.

Now we couldn't trace this down to a server or network card issue so we assumed it was a network hub and assumed that the new infrastructure would be OK as this was going to have all new equipment.

We are now seeing this issue in our new network so this must be something in our set up.

We are the hosting company for several large companies and we need to get this fixed before we move too many of their websites to this new site.

So this is the setup we have.

External network port goes into isa server, routes through here and then on the second network card we have a hub which joins the ISA to the web servers. The second network card in the web servers is linked via a second hub to our file servers.

We are using Microsoft Windows Virtual Server to create the servers we need, (could the issue 64 be because of this?). And we have 1 test server and 2 live servers.

We do have a domain and dns server but we leave the dns server alone aside from when we add new servers and the domain server adds the record in here for us.

The rules in the ISA look like this:
from: anywhere

-webfarm: specified by IP address.
-internal site name: Customer_Live
-Cookie based
-Forward the original host header
-request came from the original client who sent the request

-Network specified IP address
-Connections: port 80
-Authentication: No Authentication
--Advanced:Allow Client authentication over http

Public names:
List of domains that the customer has the get routed to the servers.

Authentication delegation:
No delegation, but client may authenticate directly

Application Settings:
None editable


Web server: redirect over http port 80.

Users: All Users

Schedule Always

Link translations: Apply link translation to this rule.

If someone can come back to me and let me know how to avoid this issue 64 as it can have a detrimental effect on the speed of the website for users visiting the website.

Oh and the new site has a 1 Gbps connection both for the external and internal links.

Post #: 1
RE: Web Farm for hosting websites - 27.Jul.2009 7:50:38 AM   


Posts: 3
Joined: 23.Feb.2009
Status: offline
Here are all the other error codes that we are seeing in the ISA.

10022 An invalid argument was supplied.
10053 An Existing connection was aborted by the software in your host machine.
10054 An Existing connection was forcibly closed by the remote host
1232 The Network location cannot be reached. For more information about network troubleshooting, see Windows Help.
1460 This operation returned because the timeout period expired.
64 The specified network name is no longer available

We are seeing them in different proportions.

Hope this helps someone.


(in reply to teec_Michda)
Post #: 2

Page:   [1] << Older Topic    Newer Topic >>
All Forums >> [ISA 2006 General] >> Installation and Planning >> Web Farm for hosting websites 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