Re: Communication issue
- From: "Phillip Windell" <philwindell@xxxxxxxxxxx>
- Date: Tue, 31 Jul 2007 14:54:42 -0500
You're welcomed, Jim!
--
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
-----------------------------------------------------
"Jim in Cleveland" <JiminCleveland@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:04041699-28A8-40F1-A577-67642B3F0859@xxxxxxxxxxxxxxxx
Phillip,
Once again, thank you for educating me on this topic. I have a feeling
I
will be bouncing more question off of you in the near future!! Again,
thanks!!
Jim
"Phillip Windell" wrote:
"Jim in Cleveland" <JiminCleveland@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:5B9A5E23-9F8B-4294-B394-07C70E77996C@xxxxxxxxxxxxxxxx
Regarding the internal NIC card then, leave the default gateway blank?
Yes, that is correct.
Also, during installation, I came upon a page that asks to configure
the
internal network address range. On our 2000 server, this looks like
you
entered a range that then made up the LAT table. The entry on it was
192.168.0.0 to 192.168.0.255. On the 2004 machine, I have the option
of
choosing a range (I did same as above) or to select the network
adapter.
Since we have a single, internal domain (192.168.0.x and no other), can
I
populate the Internal Network Address range as 192.168.0.0 to
192.168.0.255?
Yes, this replaces what you once knew as the LAT, and the range of
192.168.0.0 to 192.168.0.255 looks fine. But I recommend never going
lower
than "10" on the third Octet because the low numbers are heavily over
used.
Unfortuneately it means you'd have to readdress your LAN so it is
probably
too late for that now.
You may also notice that there is a "Domains Tab" in the Properties of
the
Internal Network Definition (Networks node of the MMC Tree),...this
replaces
what you once knew as the LDT (Local Doman Table) and it should include
the
FQDN of the AD Domain.
--
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
-----------------------------------------------------
.
- References:
- Re: Communication issue
- From: Phillip Windell
- Re: Communication issue
- From: Jim in Cleveland
- Re: Communication issue
- From: Phillip Windell
- Re: Communication issue
- Prev by Date: Re: Communication issue
- Next by Date: Re: Reverse Proxy issues
- Previous by thread: Re: Communication issue
- Next by thread: ISA 2006 and internal routing...
- Index(es):
Relevant Pages
|
Loading