Right, DNS maps the address to the FQDN configured in the destination set. I believe this is a bug with ISA server because a number of people are having this problem and everything checks out yet OWA does not work through ISA but it works fine internally. All other web publishing rules work except OWA. ----- Original Message ----- From: Jim Harrison To: [ISAserver.org Discussion List] Sent: Thursday, September 06, 2001 10:26 PM Subject: [isalist] Re: OWA http://www.ISAserver.org I think you're referring to a publishing rule. Destination sets don't map anything. They provide comparative data for ISA to use in determining how to handle a request. ISA will use multiple IP addresses just fine (within certain combinations; see Q288247 for details). It's a matter of whether or not the name you use resolves to an IP that ISA recognizes (as you pointed out) and that the request is understood and allowed. Jim Harrison MCP(2K), A+, Network+, PCG ----- Original Message ----- From: Colin Bondi To: [ISAserver.org Discussion List] Sent: Thursday, September 06, 2001 9:23 PM Subject: [isalist] Re: OWA http://www.ISAserver.org Don't know about Kirk but I have a destination set created that maps through external DNS to an IP address on my external NIC. This IP address is not being used for any other web sites although it is being used for other protocols. The IP address I'm using for OWA is not the default IP on the external NIC, but an additional one that was added. The ISA server does recognize this IP and is using it successfully for other protocols. Colin Bondi Information Systems Manager Communi(k), Inc. 503.431.7800 cbondi@xxxxxxxxxxxx ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: cbondi@xxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')