Forbidden unwanted swittching session between clients

[Frn]

I asked in this forum about concurent requests more clients at the same time. IMHO is this behaviour set up in this way :
ConnectPriority=3 (refuse all new connection)
LockSetting=2 (auto logoff on disconnect)

(more clients can connect, but only one of them can work and another must wait). I setup the server and all seems to be OK. But ...

I simulate this situation :

- client A is connected on server and works
- client B tries conenction, but it is not connected until session from A id live.

This is ideal situation. But what happens when network error occured ?

- communication channel between client A and server is down (due network error - I disconnect netork card
- client B is promptly connected
- user on PC with VNC server (WindowsNT) is logged off, but the client B can see on a short while screen from client A session.


How can I setup VNC server "when connection error detected, PC must be at first logoff and new connection can be established only after logoff process is finished" ? Or more simply - "after connection error the server ends session, but new connection can be established after timeout XX sec" ? Is this parameter configurable ?

And last question - is theoretic possible than client B "takes up" session from client A (whitch has communication problems) ? How can I forbid this situation ?

Thanks for any answer.

[ipsec]

I dont think there is a way to not allow someone who is being connected to a server no access to view. Otherwise that would defeat the point of giving them access.

Since you are sharing the console when they connect they see what is on the console at that time. I am unaware of any timeout option or automatic retry within the viewer program for connecting. But this could be a nice suggestion for the future..