I've received a few responses since my last post for the reflectionX
problem we are having.
Thanks for the replies. It was suggested the desktop or reflectionX was
running
out of tcp sockets. We checked this by clicking on help about in
reflection X, then clicking
on network stats. The max tcp sockets were 32 which the users were
maxing out. I just wasn't
sure how to check this at the time of post.
original post follows.
thanks,
Allan
>----------
>From: SIMEONE, Allan J.
>Sent: Monday, December 01, 1997 10:22AM
>To: 'alpha-osf-managers_at_ornl.gov'
>Subject: SUMMARY: reflection X question (no fix)
>
>
>No responses on this one. If I find a fix, I'll update.
>
>thanks,
>Allan
>----------
>From: SIMEONE, Allan J.
>Sent: Tuesday, November 25, 1997 2:35PM
>To: 'alpha-osf-managers_at_ornl.org'
>Subject: reflection X question
>
>hello,
>
>A few users are having problems with reflection X to a DU 4.0b system.
>I'm not sure if it is the system side or the reflection X side at this time
>that is the
>problem.
>
>The error is...
>
>Connectoin refused (RX2443) TT_ERR_PROCID the process id passed is not
>valid...
>
>However, the user already has several processes up on the screen through
>Reflection X.
>I'm thinking it is a process limit on the unix box or in Reflection X.
>anyone know where I
>can check this?
>
>thanks,
>Allan
>
>
Received on Tue Dec 02 1997 - 15:38:28 NZDT