Replied: Sat, 08 Feb 2003 14:36:20 -0500 Replied: "John Yin" Return-Path: johnyin@earthlink.net Delivery-Date: Sat Feb 8 14:29:17 2003 Return-Path: Received: from albatross.mail.pas.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by grids.ucs.indiana.edu (8.10.2+Sun/8.10.2) with ESMTP id h18JTGN13386 for ; Sat, 8 Feb 2003 14:29:16 -0500 (EST) Received: from h-66-167-205-190.snvacaid.covad.net ([66.167.205.190] helo=JOHNYINTOSHIBA) by albatross.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 18hahf-0001xB-00; Sat, 08 Feb 2003 11:31:55 -0800 From: "John Yin" To: "'alex ho'" Cc: "'Geoffrey Fox'" Subject: RE: summary demo report Date: Sat, 8 Feb 2003 11:31:42 -0800 Message-ID: <003601c2cfa8$b8d509e0$03fea8c0@JOHNYINTOSHIBA> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0037_01C2CF65.AAB1C9E0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: <002d01c2cfa5$53a0b630$8a00a8c0@anabasdellcpx> Content-Length: 11118 This is a multi-part message in MIME format. ------=_NextPart_000_0037_01C2CF65.AAB1C9E0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit * Last week, we have continued to try to use and show Impromptu to our > customers, which include TO DATE: > Park Nicollet Hospital (1st PC OK, 2nd time PC has Sun > JVM, no Admin right) * This is a known issue. > Kaiser Permanente (Does not allow port > 8080 access) * For production, you need 2 servers. This was the same issue with Avery. So you run web server on 1 machine on port 80. Then HTTP tunneling on the 3rd server on port 80. In this case, audio most likely will work through SSL ports so no need for 3rd server. > Loanet (after openning 8080 in > firewall, still have Error: Cannot Connect to Server) > Pape Group (OK) > West Telemarketing (OK) These are probably HTTP Tunneling related. It would be useful to note whether or not the client sees a IMPORTANT do not close this window . I suspect many large corporations do not allow port 8080 so it could cause these problems. If you do it in the production setup, probably some or all of these will go away. > Material Services (Error: Cannot Connect > to Server) > Lehigh Valley Hospital (Error: Cannot Connect to > Server) > Pitney Bowes (Error: Cannot Connect to > Server) > St. Vincent Hospital (OK) > Western Union (Error: Cannot Connect to > Server) > > * in all of the above cases, I made sure Sun JVM is not configured > ------=_NextPart_000_0037_01C2CF65.AAB1C9E0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Ø      Last week, we have = continued to try to use and show Impromptu to our
> customers, which include TO DATE:
> Park Nicollet Hospital (1st PC OK, 2nd time PC has Sun
> JVM, no Admin right)

Ø      This is a known issue.
> Kaiser Permanente (Does not allow port
> 8080 access)

Ø       For production, you need 2 servers.  = This was the same issue with Avery.   = So you run web server on 1 machine on port 80.  Then HTTP tunneling on the 3rd server on port 80.  In this case, audio most likely = will work through SSL ports so no need for 3rd = server.


> Loanet (after openning 8080 in
> firewall, still have Error: Cannot Connect to Server)
> Pape Group (OK)
> West Telemarketing (OK)

 

        = ;     These are probably HTTP Tunneling related.  It would be useful to note whether or not the client sees a IMPORTANT do = not close this window …  I suspect many large corporations do not allow port 8080 so it could cause = these problems.  If you do it in = the production setup, probably some or all of these will go = away.


> Material Services (Error: Cannot Connect
> to Server)
> Lehigh = Valley Hospital (Error: Cannot = Connect to
> Server)
> Pitney Bowes (Error: Cannot Connect to
> Server)
> St. Vincent = Hospital (OK)
> Western Union (Error: Cannot Connect to
> Server)
>
> * in all of the above cases, I made sure Sun JVM is not = configured
>

 

------=_NextPart_000_0037_01C2CF65.AAB1C9E0--