Skip to main content

[Migrated content. Thread originally posted on 08 November 2005]

I have the following problem with the thin client. I am connected via the internet with an atc file. When the session is inactive during a certain period, I get the following message.

The remote host is not responding.
Press OK to close this program.
Press Cancel to wait another %s seconds.

When I press OK. The thin client exits but the process on the server isn't killed.

I use QUIT_MODE 100 in my configfile en I haven't specified TC_QUIT_MODE so he should use the QUIT_MODE variable.
I haven't mentioned the TC_CHECK_ALIVE_INTERVAL.

Can someone tell me how I can get this process killed on the server.

[Migrated content. Thread originally posted on 08 November 2005]

I have the following problem with the thin client. I am connected via the internet with an atc file. When the session is inactive during a certain period, I get the following message.

The remote host is not responding.
Press OK to close this program.
Press Cancel to wait another %s seconds.

When I press OK. The thin client exits but the process on the server isn't killed.

I use QUIT_MODE 100 in my configfile en I haven't specified TC_QUIT_MODE so he should use the QUIT_MODE variable.
I haven't mentioned the TC_CHECK_ALIVE_INTERVAL.

Can someone tell me how I can get this process killed on the server.
The only way I have found to kill that process is to shut the thin client service down and re-start it.

[Migrated content. Thread originally posted on 08 November 2005]

I have the following problem with the thin client. I am connected via the internet with an atc file. When the session is inactive during a certain period, I get the following message.

The remote host is not responding.
Press OK to close this program.
Press Cancel to wait another %s seconds.

When I press OK. The thin client exits but the process on the server isn't killed.

I use QUIT_MODE 100 in my configfile en I haven't specified TC_QUIT_MODE so he should use the QUIT_MODE variable.
I haven't mentioned the TC_CHECK_ALIVE_INTERVAL.

Can someone tell me how I can get this process killed on the server.
If you are using a windows server, you can kill the acuthin tasks by using the AT command.

Search the Internet for a program called PSKILL.EXE. This allows you to kill a task based on the PID, which you can get using the ACURCL command.

At a command prompt on the server enter:
at {time} {c:\\...\\PSKILL.EXE PID}

{time} would be the current time plus a couple of minutes.

The AT command should execute at the time you specify.

The AT command allows the PSKILL command to execute as a service, it will not work if you just enter it from a command prompt.

[Migrated content. Thread originally posted on 08 November 2005]

I have the following problem with the thin client. I am connected via the internet with an atc file. When the session is inactive during a certain period, I get the following message.

The remote host is not responding.
Press OK to close this program.
Press Cancel to wait another %s seconds.

When I press OK. The thin client exits but the process on the server isn't killed.

I use QUIT_MODE 100 in my configfile en I haven't specified TC_QUIT_MODE so he should use the QUIT_MODE variable.
I haven't mentioned the TC_CHECK_ALIVE_INTERVAL.

Can someone tell me how I can get this process killed on the server.
I get the problem with a unix or a linux server. I get the message 'host not responding ...' but my process still exists on the server. When I press Ok to quit the process keeps running and often takes a lot of cpu time and slows down the system.

[Migrated content. Thread originally posted on 08 November 2005]

I have the following problem with the thin client. I am connected via the internet with an atc file. When the session is inactive during a certain period, I get the following message.

The remote host is not responding.
Press OK to close this program.
Press Cancel to wait another %s seconds.

When I press OK. The thin client exits but the process on the server isn't killed.

I use QUIT_MODE 100 in my configfile en I haven't specified TC_QUIT_MODE so he should use the QUIT_MODE variable.
I haven't mentioned the TC_CHECK_ALIVE_INTERVAL.

Can someone tell me how I can get this process killed on the server.
I'm not sure why the process doesn't go away, but I'm under the understanding that this could occur when the runtime is in a loop. That's not the only thing that would cause this, but one of them...

Rob

[Migrated content. Thread originally posted on 08 November 2005]

I have the following problem with the thin client. I am connected via the internet with an atc file. When the session is inactive during a certain period, I get the following message.

The remote host is not responding.
Press OK to close this program.
Press Cancel to wait another %s seconds.

When I press OK. The thin client exits but the process on the server isn't killed.

I use QUIT_MODE 100 in my configfile en I haven't specified TC_QUIT_MODE so he should use the QUIT_MODE variable.
I haven't mentioned the TC_CHECK_ALIVE_INTERVAL.

Can someone tell me how I can get this process killed on the server.
The problem occurs when i loose my internet connection. With acurcl -info I can get the client and username. Does anybody know how i can get the ip address of the client ?

I want to make a script where I ping the thin client every 10 seconds. When the connection is lost, i will kill the process.
Terms & ConditionsAccessibility statement