Cache mode with a single NIC was the correct choice. You have to identify the upstream route to ISA in Network Configuration. The ISA help covers this quite well. Jim Harrison MCP(NT4, W2K), A+, Network+, PCG http://isaserver.org/authors/harrison/ Read the book! ----- Original Message ----- From: "Alan Kaplan" <alan@xxxxxxxxxxx> To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx> Sent: Wednesday, December 12, 2001 05:23 Subject: [isalist] Cache to upstream server within LAN http://www.ISAserver.org I am working in a large enterprise which wants to setup ISA to reduce the load on internet gateways that are available only across the WAN. There is no need for a firewall, as the server does not have (and cannot have)an outside address. It does have two NICs that I would like to take advantage of. The server OS is Windows 2000 Advanced Server, not Datacenter. The domain is still NT 4, so ISA must be loaded in stand-alone mode. I tried to setup in Cache mode only, but ISA in this configuration had only dial-up to the internet. I rebuilt, setting up ISA in integrated mode. I got the server working, but all of the traffic was on one NIC only. I attempted to exclude the second NIC from the LAT -- which did not help. In a display of poor judgement I attempted to use Compaq's teaming of the NICS. That hosed the server. I plan to rebuild to have a clean configuration. My goal is caching internet requests, utilizing both NICS, maintaining the capablity of filtering ports, and having the ability to later monitor/filter content. I am Proxy certified, this is my first attempt at deploying ISA. It has not gone quite as easily as expected... Thanks. Alan Kaplan ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: jim@xxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')