FWIW, I have seen the opposite happen. I used server publishing (rather than web publishing) to publish a site, but forgot to turn off the web listener, and the error was that the web listener could not initialize because the port was already in use... Obviously it will cause contention, but the web listener does not always win (in my experience, anyway). AD ----- Original Message ----- From: "Jim Harrison" <jim@xxxxxxxxxxxx> To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx> Sent: Thursday, August 23, 2001 10:29 AM Subject: [isalist] Re: Server and Web Publishing on port 80 > http://www.ISAserver.org > > > That is a very true statement. The web proxy incoming listener will get > priority over any server publishing rule. BTW, packet filters override web > publishing functionality. > > Jim Harrison > MCP(2K), A+, Network+, PCG > > ----- Original Message ----- > From: "Tom Soulsby" <tom@xxxxxxxxxxxxx> > To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx> > Sent: Thursday, August 23, 2001 8:33 AM > Subject: [isalist] Server and Web Publishing on port 80 > > > http://www.ISAserver.org > > > Would you agree that you cannot have Web and Server rules on port 80 ? > > Cheers, > Tom. > > ------------------------------------------------------ > You are currently subscribed to this ISAserver.org Discussion List as: > jim@xxxxxxxxxxxx > To unsubscribe send a blank email to $subst('Email.Unsub') > > > > ------------------------------------------------------ > You are currently subscribed to this ISAserver.org Discussion List as: thor@xxxxxxxxxxxxxxx > To unsubscribe send a blank email to $subst('Email.Unsub')