Hi,

I am the only one whos ISEE logfile is getting full with "connection
refused" messages and "timeout"? It seems ISEE clients try to connect
the HP server every 30 seconds by default, but the server does only
respond to about every 10th attempt.

IMHO I'd would have been more clever to make the client call HP only
when necessary and then do not use MS IIS 5.0 as web server (this is
what the server announces).

Also initial configuration with the entitlement check is just a
pain. I failed to fill in the requeired data, because the additional
input fields just did not appear. Maybe that happens when the HP
server cannot be reached, and the latter happens most of the time.

The other thing is the use of Java with some 5 second timeout that
older machines just seem to be unable to handle in time (e.g a
D270/2).

If this is the solution, can I have Predictive back? ;-)

Regards,
Ulrich

Hi Ulrich,

I have few questions about your ISEE installation:

1. what are your versions of HPUX and ISEE client?
2. have you tried CheckCon.class and what is an output?
3. does network resolution work?
4. who did first installation?
5. have you tried to reinstall ISEE client? Sometimes it helps ).
6. do you have other servers with correct installation?

Regards,
Mario.

"Ulrich Windl" <Ulrich.Windl@RZ.Uni-Regensburg.DE> wrote in message
news:m3k706oiv6.fsf@pc5234.klinik.uni-regensburg.de...
> Hi,
>
> I am the only one whos ISEE logfile is getting full with "connection
> refused" messages and "timeout"? It seems ISEE clients try to connect
> the HP server every 30 seconds by default, but the server does only
> respond to about every 10th attempt.
>
> IMHO I'd would have been more clever to make the client call HP only
> when necessary and then do not use MS IIS 5.0 as web server (this is
> what the server announces).
>
> Also initial configuration with the entitlement check is just a
> pain. I failed to fill in the requeired data, because the additional
> input fields just did not appear. Maybe that happens when the HP
> server cannot be reached, and the latter happens most of the time.
>
> The other thing is the use of Java with some 5 second timeout that
> older machines just seem to be unable to handle in time (e.g a
> D270/2).
>
> If this is the solution, can I have Predictive back? ;-)
>
> Regards,
> Ulrich

"Mario" <mario.jaksic@zg.tel.hr> writes:

> Hi Ulrich,
>
> I have few questions about your ISEE installation:
>
> 1. what are your versions of HPUX and ISEE client?

HP-UX 11i (11.11) and ISEE 3.50 (previously 3.0).

> 2. have you tried CheckCon.class and what is an output?

I don't have that, but a "telnet isee.europe.hp.com http" was refused
most of the time, and when a connection was established, the server
was quite slow to respond. Together with the default timeout of 15
seconds, this was most likely too short.

> 3. does network resolution work?

Vie /etc/nsswitch and local /etc/hosts, yes.

> 4. who did first installation?

The specialist (I) ;-)

> 5. have you tried to reinstall ISEE client? Sometimes it helps ).

Once, but how does it help against a slow remote server?

> 6. do you have other servers with correct installation?

I think my installations are all correct, but is the software that I
installed? ;-)

Regards,
Ulrich

>
> Regards,
> Mario.
>
> "Ulrich Windl" <Ulrich.Windl@RZ.Uni-Regensburg.DE> wrote in message
> news:m3k706oiv6.fsf@pc5234.klinik.uni-regensburg.de...
> > Hi,
> >
> > I am the only one whos ISEE logfile is getting full with "connection
> > refused" messages and "timeout"? It seems ISEE clients try to connect
> > the HP server every 30 seconds by default, but the server does only
> > respond to about every 10th attempt.
> >
> > IMHO I'd would have been more clever to make the client call HP only
> > when necessary and then do not use MS IIS 5.0 as web server (this is
> > what the server announces).
> >
> > Also initial configuration with the entitlement check is just a
> > pain. I failed to fill in the requeired data, because the additional
> > input fields just did not appear. Maybe that happens when the HP
> > server cannot be reached, and the latter happens most of the time.
> >
> > The other thing is the use of Java with some 5 second timeout that
> > older machines just seem to be unable to handle in time (e.g a
> > D270/2).
> >
> > If this is the solution, can I have Predictive back? ;-)
> >
> > Regards,
> > Ulrich