|
Here is a solution that worked for someone on the msnews groups a couple of months ago: 1. Set up the Exchange 2000 Server as a secureNAT client. (Exchange 2000 system configured with its default gateway as the ISA internal IP address) 2. Enable IP forwarding on the ISA Server. (This will allow the Exchange 2000 box to ping external IPs through the ISA Server). 3. Create a protocol rule alowing all protocols to move thorugh the ISA Server.(Alternatively you might want to create a protocol rule for only HTTP) 4. Create a packet filter for HTTP on the external ISA interface. (Keep the default of port 80) 5. Create a record in your DNS that is published externally with the name of the Exchange 2000 Server. (This IP address should point to the ISA Server's external IP address). 6. Create a destination set that includes the entire FQDN of your Exchange 2000 server (ie: exchange2000.domain.com) 7. Create a web publishing rule that uses the destination set exchange2000.domain.com) and forwards downsteam to the Exchange 2000 server. 8. Configure a listener for "Incoming Web requests" that uses the "Integrated or Basic" methods of authenication. (This is what Exchange 2000 sets up on the /exchange folder). Also, be sure to enable passing of the host header information in the Web Publishing rules. HTH, Tom quote: Originally posted by McHarvest: Hi,i would like to create simple publishing scenario with an internal Exchnage 2000 Server and a ISA Server running integrated mode. First, a destination set are created. At second i had used the webpublishing wizzard to configure the OWA. (The destinationset are based on a enterprise-policy with the internal FQDN of the Exchg.) When i am try to reach the Server on the external IP (second NIC) of ISA Server, nothing is happend. A Portscan shows that a Port 80 not thems to be exist. Than i have tryed to creat a dest.set with array and server policy. The same thing. When i create Serverpublishing rule i can connect the Exchg. What cause can it be ? Thank's at all, Frank.
|