Q288396 doesn't; it deals with a single-NIC ISA scenario Q288236 does; it suggests that you create an internal DNS record for the published destination set and use an internal IP to reach it. http://support.microsoft.com/support/kb/articles/Q288/2/36.ASP Jim Harrison MCP(2K), A+, Network+, PCG ----- Original Message ----- From: "Raji Arulambalam" <rajia@xxxxxxxxxxxxxx> To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx> Sent: Wednesday, September 26, 2001 10:03 PM Subject: [isalist] Event 14120 http://www.ISAserver.org Hi How does the fix in Q288396 fix this problem when you WEB Publish to an internal IIS server. Using the same IP # of the IIS server but mapping different ports to the various external domains that you host. We publish 10 external IP # to 10 Web sites all hosted on the one internal IIS server with one IP # and using different ports. Any comments are welcome. --------------------------------------------- Raji Arulambalam Systems Administrator Bay of Plenty REGIONAL Council P O Box 364 Whakatane. NEW ZEALAND -------------------------------------------- ****************************************************** This e-mail has been checked for viruses and no viruses were detected. ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: jim@xxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')