THe dreaded 14120 error; it's caused much grief in the ISA Server community. What is it and what can be done about it? All theses and more will be answered in tomorrow's Jerry Springer show, but for now, you can read this article…
Designing An ISA Server Solution on a Complex Network.
This article deals with the specifics of ISA and client configuration for the Firewall Client-enabled host.
This article discusses the particulars of ISA configuration to support each client type; SecureNAT, Web Proxy And Firewall.
This article deals with the setup and configuration of SecureNAT and Web Proxy clients
Want some more fun? Let’s look at the ISA scenario. What many folks will do is place DNS resolver IPs in both NICs, ISP in the external, local in the internal. While this seems to make sense, it’s actually very inefficient and you can actually cause huge timeouts this way. Remember that TCP/IP will choose the route for a given packet based on its destination, not where it found the data. This means that DNS entries are not really NIC-specific, it’s just more meaningful to the person entering them.
Using ISA over a dial-up connection is fraught with pitfalls, mainly because the dial-up connection is fundamentally different from a permanent connection.
Before you install ISA, you have to properly set up the networking properties for that machine. Mistakes made either during or after installing ISA server can render your once proud server unresponsive.