Welcome to ISAserver.org

Web Publishing / Please Help I'm ready too....

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2000 General] >> Web Publishing >> Web Publishing / Please Help I'm ready too....

Page: [1]

Message

<< Older Topic Newer Topic >>

Web Publishing / Please Help I'm ready too.... - 13.Jun.2001 9:00:00 PM

rsnider

Posts: 2
Joined: 7.Jun.2001
From: Oxford, AL US
Status: offline

Here is what is up. I have isa running it works great except web publishing. I have tried to publish an internal web site and I have tried to publish owa for exchange 2000. I cannot get anything to come through. I get an error that says "The page you are looking for is currently unavailable. The Web site might be experiencing technical difficulties, or you may need to adjust your browser settings."

Ok here is the setup. I have isa running with two nics. One is connected into a cisco 3620 and has an ip address for my isp. The other nic has an internal ip address of 172.16.x.x. I am using nat for my network. I have published my internal exchange server for mail and it is working great. But when I try to redirect to any internal web site I get the error mentioned above. I have setup everything according to shinder's section. But to no avail nothing is working. I know that my dns is working because I can ping and resolve the fqdn that I am using for owa. The name is owc.mydomain.com. When I ping it returns the ip address of the external interface of isa. The isa dns server has two lookup zones one for interal address and one for external. I can see the website internally but not externally.

Any help would be appreciated.

Thanks,

rsnider

Post #: 1

Featured Links*

RE: Web Publishing / Please Help I'm ready too.... - 14.Jun.2001 3:48:00 AM

Ultraman

Posts: 182
Joined: 20.Apr.2001
Status: offline

rsnider,

Have you read about the problems in destination sets having to do with FQDN's vs. IP addresses? If not, MAKE SURE that the destination sets contain FQDN's pointing to the OWA boxes and the web publishing rules contain IP addresses (not the standard FQDN that ISA throws in there for you). This is an actual bug in ISA that will cause this type of behavior.

------------------
Eric Jansen
Independent Software, Inc.
MCP (MCSE 2K pledge), ICE, ICA

(in reply to rsnider)

Post #: 2