RE: ISA 2004 on W2K3 DC...

  • From: "Thomas W Shinder" <tshinder@xxxxxxxxxxx>
  • To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
  • Date: Fri, 17 Sep 2004 21:32:38 -0500

Hi Steve,
 
It might be worth looking at my intradomain communciations in a trihomed
DMZ article I put up recently on www.isaserver.org too.
 
Thanks!
Tom

________________________________

From: Steve Moffat [mailto:steve@xxxxxxxxxxxxxxxxxxxxxxxxxx] 
Sent: Thursday, September 16, 2004 6:06 AM
To: [ISAserver.org Discussion List]
Subject: [isalist] RE: ISA 2004 on W2K3 DC...


http://www.ISAserver.org

I have the very same scenario up and running, no issues, the protocols
you have to  allow are wide and varied, but a starting point id Dr
Shiners fe/be exchange paper.
 
S

________________________________

From: Shawn P. Lemay [mailto:slemay2@xxxxxxxxx] 
Sent: Wednesday, September 15, 2004 10:23 PM
To: Isa Weblist
Subject: [isalist] ISA 2004 on W2K3 DC...


http://www.ISAserver.org

OK - I know the practice is bad... don't blame the tech here...
 
I have two offices that purchased W2K3 and ISA 2004.  Their intent is to
have one domain with a VPN tunnel between the two offices with AD
replication between the two servers.  Both servers will do DNS, DHCP,
SUS, and basic AD.  I'm pulling my hair out trying to figure out how to
do this with ISA 2004.  I know this is the "preferred" way to do it in
SBS (which I discouraged them from buying all together - as they'd only
get one DC out of it).  I have figured out how to get the DHCP to work
(again - all these services are on the same ISA 2004 box) - but can't
get the rest to work reliably.  Any suggestions?  Thanks,
Shawn
 
------------------------------------------------------
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:
steve@xxxxxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=isalist
Report abuse to listadmin@xxxxxxxxxxxxx
------------------------------------------------------
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 

________________________________

This E-Mail is confidential. It is not intended to be read, copied,
disclosed or used by any person other than the recipient named above. 

Unauthorised use, disclosure, or copying is strictly prohibited and may
be unlawful. Optimum IT Solutions disclaims any liability for any action
taken in connection of this E-Mail. The comments or statements expressed
in this E-Mail are not necessarily those of Optimum IT Solutions or its
subsidiaries or affiliates.

administrator@xxxxxxxxxxxxxxxxxxxxxxxxxx
<mailto:administrator@xxxxxxxxxxxxxxxxxxxxxxxxxx>  
________________________________


Other related posts: