Welcome to ISAserver.org

"HTTPS Server" not recognised

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2004 General ] >> Web Publishing >> "HTTPS Server" not recognised

Page: [1]

Message

<< Older Topic Newer Topic >>

"HTTPS Server" not recognised - 23.Feb.2007 6:45:56 AM

tvbruwae

Posts: 57
Joined: 19.Jul.2005
Status: offline

Hi

We are trying to publish an HTTPS LAN application over 3 different ISA Servers in separated sites. Every site has a more or less similar setup, with an ISA Server and a local internet connection.

The "server publishing" rule uses the "HTTPS Server" protocol, listens on the external interface of the ISA Server and forwards requests to an IP on the LAN.

This works fine for 2 of the 3 ISA Servers. When launching a request from the internet to one of the published IP addresses, requests are picked up by the publishing rule and logged with the "HTTPS Server" protocol. The "destination" address in the ISA log file is the actual LAN address of the published server.

On the third server, incoming requests are detected as being "HTTPS". The destination IP in the ISA logs is the IP address of the ISA Server on which the site should be published. Action is "Denied connection - Default rule".. Opening up HTTPS obviously still fails as nothing is listening on that port on the ISA Server.

What could be the problem on the third server? Rules are exactly the same on all three ISA Servers. We used Ethereal to sniffer on the external (published) IP addresses and saw similar packets coming in on all three sites. Only in the third site, ISA is not able to respond properly by using the publishing rule..

Thanks for any tips!
Tim

Post #: 1

Featured Links*

RE: "HTTPS Server" not recognised - 27.Feb.2007 4:51:05 AM

tvbruwae

Posts: 57
Joined: 19.Jul.2005
Status: offline

Update: after checking every setting on the third ISA Server we found a difference with the others. Once corrected the publishing worked fine.

This is what happened:

On the failing ISA Server, we had two network rules: the default one and a "route from all networks to all networks" rule
On the other ISA Servers we had the default rule and "NAT from internal network to internal network & external"

Once we changed the ROUTE rule to NAT, the ISA Server successfully recongnised the packets to be "HTTPS Server". Information was found on http://www.microsoft.com/technet/isa/2004/help/M_P_C_PnatRule.mspx?mfr=true

< Message edited by tvbruwae -- 27.Feb.2007 4:53:20 AM >

(in reply to tvbruwae)

Post #: 2