Search EggHeadCafe's Job Board
EggHeadCafe Silverlight WPF ASP.NET VB.NET C# Excel SQL Server SharePoint
search
ISA Server GroupsView
Isa
Isa Configuration
Isaserver

Group SummariesView
.NET Framework
Access
BizTalk
Certifications
CRM
DDK
Exchange Server
FoxPro
French
French .NET
Games
German
German .NET
Graphic Design
IIS
Internet
ISA Server
Italian
Italian .NET
Maps
MCIS
Miscellaneous
Mobile Apps
Money
MSN
Networking
Office
Ops Mgr
Publisher
Security
SharePoint
Small Business
Spanish
Spanish .NET
SQL Server
Systems Management Server
Transaction Server
Virtual PC / Virtual Server
Visual Studio
Win32
Windows 2000
Windows 2003 Server
Windows 7
Windows Live
Windows Media
Windows Update
Windows Vista
Windows XP
 

View All Microsoft Isa Posts  Ask A New Question 

configuring ISA 2004 on live network

JiminClevelan posted on Tuesday, July 24, 2007 3:06 PM

We currently have a 2000 server running ISA 2000 on our network.  I just
installed a 2003 server and want to load ISA2004 on this server.  Since our
internal addressing scheme is 192.168.0.X, when I configure the internal
addressing of the ISA 2004 server, can I also put this on the 192.168.0.X
network without it trying to "take control" of the ISA role on the network?
reply

 

Hi Jim,don't worry, you can configure the ISA 2004 also on the 192.168.0.

Mariu posted on Tuesday, July 24, 2007 4:44 PM

Hi Jim,

don't worry, you can configure the ISA 2004 also on the 192.168.0.x network.
Just make sure it does not has the same IP as the ISA 2000 Server.
Do you want to replace the old ISA Server, or why do you want to have both
on the same subnet?

Regards
Marius
reply

Marius,Thanks for the reply.

JiminClevelan posted on Tuesday, July 24, 2007 5:20 PM

Marius,

Thanks for the reply.  The ISA 2000 server is going to be replaced by the
ISA 2004 server.  They are two, separate physical boxes.  I'm just trying to
get the 2004 server configured as close to the 2000 server as possible.  My
networking skills are not the greatest so I'm not sure of how to do this, i.e
put them on separate subnets.  If you have any other info that can help me
out, I'd really appreciate it.

Thanks,

Jim
reply

Jim, just give the new ISA a differnet IP# on the same subnet (maybe one

Phillip Windell posted on Tuesday, July 24, 2007 8:51 PM

Jim, just give the new ISA a differnet IP# on the same subnet (maybe one
number higher or lower).  Do the same on the public side if you have more
public IP#s. All the rest of the TCP/IP specs stay the same.

If you set your network up to use Proxy autodetection then the users can
seelessly move to the new server when ready and they won't know the
difference.  This is especially true if you get the WPAD Proxy Autodetection
working with the old ISA first.  Then when you are ready to make the switch
just change the "A Record" in DNS that the WPAD Alias points (from old
server to new server) and give it about 3 days and most of the user will be
silently and transparently moved to the new ISA.

I just got done yesterday doing exactly the same thing with ours going from
ISA2004 to ISA2006.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Troubleshooting Client Authentication on Access Rules in ISA Server 2004
http://download.microsoft.com/download/9/1/8/918ed2d3-71d0-40ed-8e6d-fd6eeb6cfa07/ts_rules.doc

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp

Microsoft ISA Server Partners: Partner Hardware Solutions
http://www.microsoft.com/forefront/edgesecurity/partners/hardwarepartners.mspx
-----------------------------------------------------
reply

 
 

Previous Microsoft Isa conversation.