RE: 2004 Enterprise Array setup

  • From: "Thomas W Shinder" <tshinder@xxxxxxxxxxx>
  • To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
  • Date: Tue, 26 Apr 2005 15:02:04 -0500

Hi Nathan,

Might work, but I highly recommend a common switch between them (just in
case).

HTH, 


Tom
www.isaserver.org/shinder
Tom and Deb Shinder's Configuring ISA Server 2004
http://tinyurl.com/3xqb7
MVP -- ISA Firewalls


-----Original Message-----
From: nathan [mailto:ncasey@xxxxxxxxxxxxxxxxx] 
Sent: Tuesday, April 26, 2005 2:49 PM
To: [ISAserver.org Discussion List]
Subject: [isalist] 2004 Enterprise Array setup

http://www.ISAserver.org

I am in the process of building an ISA 2004 array to replace out current
ISA 2000 array. The new array consists of two 2003 Enterprise Servers
with
SP1. Each server has three NIC's: One for LAN (Internal), one for DMZ
(External) and one for intra-array communications.
My question is regarding the NIC's for intra-array communications. Can
they be connected via a crossover cable?
I am using Rainwall for network load balancing. 

Thanks
Nathan 

------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist
ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp
ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
World of Windows Networking: http://www.windowsnetworking.com
Leading Network Software Directory: http://www.serverfiles.com
No.1 Exchange Server Resource Site: http://www.msexchange.org
Windows Security Resource Site: http://www.windowsecurity.com/
Network Security Library: http://www.secinf.net/
Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
tshinder@xxxxxxxxxxxxxxxxxx
To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=isalist
Report abuse to listadmin@xxxxxxxxxxxxx




Other related posts: