Hi C, Using the IP address should work fine, although I always use a split DNS or HOSTS file entry so that the same FQDN used by the external network client is entered into the redirect. Then the ISA Server resolves the same FQDN to the internal IP address of the server. It makes the log files a little cleaner and always solves issues with host header problems. HTH, Tom Thomas W Shinder www.isaserver.org/shinder ISA Server and Beyond: http://tinyurl.com/1jq1 Configuring ISA Server: http://tinyurl.com/1llp -----Original Message----- From: cdawkins [mailto:cdawkins@xxxxxxxxxxxxx] Sent: Sunday, April 20, 2003 1:22 PM To: [ISAserver.org Discussion List] Subject: [isalist] RE: OWA again this time HTTP 404 page not found http://www.ISAserver.org I actually use the IP address which is 192.168.1.2. > Hi C, > > In the Action Tab, what IP addrss does that entry resolve to? That > sounds like a major problem, although there may be others. > > HTH, > Tom > > Thomas W Shinder=20 > www.isaserver.org/shinder=20 > ISA Server and Beyond: http://tinyurl.com/1jq1=20 > Configuring ISA Server: http://tinyurl.com/1llp=20 > > > > -----Original Message----- > From: cdawkins [mailto:cdawkins@xxxxxxxxxxxxx]=20 > Sent: Tuesday, April 15, 2003 5:16 AM > To: [ISAserver.org Discussion List] > Subject: [isalist] RE: OWA again this time HTTP 404 page not found > > > http://www.ISAserver.org > > > The OWA rule and destination set were created by the OWA wizard. > The internal company Active Directory name is companyname.LOCAL. The > external DNS name is servername.companyname.COM. > > The Action Tab has servername.companyname.com. The destination sets have > servername.companyname.COM as I said automatically created. There is a > host entry on the Firewall server pointing servername.companyname.COM to > the internal IP address which is on the exchange server (also a Domain > controller) All this is without SSL as I just want to see it working > first!!! > > Also my second question was why when using the default set of packet > filters does ISA block any attempt to access IIS. So when I disable > (actually I enable all protcols) it works? Shouldnt the publishing rule > take care of this? I dont want to place and port 80 rule on the packet > filters. ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Exchange Server Resource Site: http://www.msexchange.org/ Windows Security Resource Site: http://www.windowsecurity.com/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: tshinder@xxxxxxxxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')