LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Doug Wheeler <[log in to unmask]>
Mon, 9 Apr 2001 08:59:41 -0400
text/plain (67 lines)
Michael,
Yup, this happened to me as well. I have an intranet that runs on IIS and
its mail service for mailing forms. I tried the double IP approach as well.
No go. After much head pounding on the table, manual reading and list
reading, it was determined that Listserv really likes to be on it's own. So,
I put Listserv on another box along with its own IIS and everyone is happy.
Doug


Doug Wheeler
Server Analyst - Information Resources
Georgia-Pacific Corporation
Neenah Technical Center
email : mailto:[log in to unmask]
voice : 920.729.8178 fax : 920.729.8164




-----Original Message-----
From: Michael Shannon [mailto:[log in to unmask]]
Sent: Sunday, April 08, 2001 11:33 PM
To: [log in to unmask]
Subject: Update - Specifiying web port for wa.exe


>
> MS IIS provides Host Header Names support to Host Multiple
> Sites from One IP
> Address http://support.microsoft.com/support/kb/articles/Q190/0/08.ASP
>

Just a quick note to let you all know what's been done to resolve this.

Jim Walker's suggestion above didn't solve the problem.  IIS didn't seem to
want to know about the LISTSERV site and wouldn't resolve to it properly.
Might be something that can be fixed but I didn't have the time (or the
inclination) to muddle through and figure it out.

Ben Parker's suggestion of configuring LISTSERV so that the full URL is
specified in WWW_ARCHIVE_CGI= didn't work either.  When I entered
"listserv.machine:81/cgi-bin/wa.exe" it was accepted but when LISTSERV
generated a dyamic address back to itself (using &WA_URL;) it always dropped
the port number.  When I tried to set the configuration for NODE or MYDOMAIN
with the port specified LISTSERV wouldn't accept it as correct value.
Setting TCPGUI_IPADDR or TCPGUI_PORT had absolutely no effect.

So.....the end result was to kick off the offending web service on my
LISTSERV machine.  It was something of a guest to begin with and, as we all
know, NOTHING is as important as LISTSERV traffic.... ;~)

LISTSERV now has port 80 of the primary web service all to itself and it's
perfectly happy.

Chazzozz!!

Michael Shannon
Webmaster
[log in to unmask]

"Before you can grow old and wise you must first survive being young and
stupid." - Ancient Proverb

Note: Opinions expressed on this list are my own and do not reflect the
views, opinions or position of my employer.  If swallowed, seek medical
advice.

ATOM RSS1 RSS2