Issues with Admin account 'locking'

[ourspt]

Hi,

I am working on a VB6.0 application where we use server side COM+ components and some client side DLLs. Our application needs the administrator to be logged in on the server on which the COM+ components are there. Until now, the administrators used to log on to this server and then when they need to go out temporarily, used to 'lock' the server (using CTRL+ALT+DEL) and go and we did not have any problem with this. But since a few days, when the admin locks the server terminal like this, no users are able to run the applicaiton there after.

(The exe on the client machine is not able to execute the server side components when the desktop of the server is 'locked' when the administrator is logged in ( by using CTRL+ALT+DEL) and hence the application is trying to install the client proxy again. This is because client side application's proxy acts as 'stub' and the server side COM+ components act as skeleton and since there is no response from skeleton, stub is trying to reinstall application proxy again)

Hence the administrators are being forced to leave the terminal accessible when they are logged on and have to go out temporarily and this is causing security threats to us.

Any help in solving this problem is greatly appreciated.

Thanks

ourspt

[Pino]

Hi,

I am working on a VB6.0 application where we use server side COM+ components and some client side DLLs. Our application needs the administrator to be logged in on the server on which the COM+ components are there. Until now, the administrators used to log on to this server and then when they need to go out temporarily, used to 'lock' the server (using CTRL+ALT+DEL) and go and we did not have any problem with this. But since a few days, when the admin locks the server terminal like this, no users are able to run the applicaiton there after.

(The exe on the client machine is not able to execute the server side components when the desktop of the server is 'locked' when the administrator is logged in ( by using CTRL+ALT+DEL) and hence the application is trying to install the client proxy again. This is because client side application's proxy acts as 'stub' and the server side COM+ components act as skeleton and since there is no response from skeleton, stub is trying to reinstall application proxy again)

Hence the administrators are being forced to leave the terminal accessible when they are logged on and have to go out temporarily and this is causing security threats to us.

Any help in solving this problem is greatly appreciated.

Thanks

ourspt

did this just happen or did you upgrade or somthing?

[Dave Sell]

This smells alot like XP SP2...