Welcome to ISAserver.org

Web Publishing worked on Beta , Not on full release

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2004 General ] >> Web Publishing >> Web Publishing worked on Beta , Not on full release

Page: [1]

Message

<< Older Topic Newer Topic >>

Web Publishing worked on Beta , Not on full release - 21.Jul.2004 4:11:00 PM

TonyR

Posts: 13
Joined: 28.Jan.2003
Status: offline

I've been running ISA 2004 Beta for a while wth many websites published and working fine. I decided to remove the beta and install the full trial version until ours arrived.
I uninstalled the beta. removed the directory , rebooted and installed the trila version.
Now I cannot publish any web sites. I can see the requests getting denied in the live log.

I follow the web publishing 'wizard' with the following settings

Browse and select the webserver
Check the Forward Host header box
Path: Empty
Accept requests for: The domain name below
Public Name: www.xxx.com
Path: Empty
Web Listerner: Web Listerner1
User Set: All Users

Apply the rule and the requests get denied
I've also tried setting
Accept requests for: All Domain Names.

It still denies the connections.

I'm so frustrated. I wish'd left the beta alone & working.

I've rebooted but that did not help.

Any suggestions ?

thanks in advance

PS the weblistener
Networks: External ,Internal, Local host

Other arrears like inbound smtp are working fine
I can reach the websites from an internal connection.

Post #: 1

Featured Links*

RE: Web Publishing worked on Beta , Not on full release - 21.Jul.2004 5:45:00 PM

TonyR

Posts: 13
Joined: 28.Jan.2003
Status: offline

FWIW: ftp publishing is working fine

(in reply to TonyR)

Post #: 2

RE: Web Publishing worked on Beta , Not on full release - 21.Jul.2004 8:19:00 PM

TonyR

Posts: 13
Joined: 28.Jan.2003
Status: offline

Never mind. Fixed it.
I forgot that I put iis on this box to test Paessler Router Traffic Grapher a while back and it was causing ISA to fail to bind to port 80.

Alert Information
Description: The Web Proxy filter failed to bind its socket to 66.xxx.xxx.xx port 80. This may have been caused by another service that is already using the same port or by a network adapter that is not functional. To resolve this issue, restart the Microsoft Firewall service. The error code specified in the data area of the event properties indicates the cause of the failure. The failure is due to error: 0x80072740

(in reply to TonyR)

Post #: 3