Effect of changing account password when already logged on

We have a distributed application set up as follows (all machines running
Windows Server 2003):

One machine 1, we are logged in to the console session with a
user-interactive process running.
One machines 2, 3, 4 and 5, we are logged in to the console session with a
user-interactive DCOM server process running.

We generally change our password with these sessions remaining open and
these processes still running.

Theoretically, I am thinking that once I have a token, it represents my user
and changing my account password does not invalidate that. As I would
expect, all processes continue to run as normal. But is that really true?
This does not always seem to be the case and recently, I think I see a
pattern. I try to keep the processes running but sometimes I must close one
of the DCOM server processes because it needs to restart. At that point, I
cannot launch another DCOM server process. The error is security related. I
think it might be E_ACCESSDENIED, but I am not certain. At this point, I
usually give up, close all process and log off all sessions, causing some
unwanted down time. BTW, it is configured to run as the interactive user and
all other settings are default.

Can anyone offer some advice? Thanks,

Paul


.