Hi there!
We are experiencing a very strange problem with our VB.NET application.
The application is using .NET Framework v1.1.4322 and the problem is
experienced only by Windows XP users.
When our application starts, it retrieves all required core assemblies
from a network path \\SERVER\DIRECTORY\ and copy them locally using standard
System.IO classes. It then load those core assemblies through reflection
and get some other "modules" assemblies on a per-request basis from the
network, in the same way. All this process works really fine, except when
user changes it's password while the application is running.
When the password change occur, the application can no more reach the
network path used by the application because user is no more authenticated
to this server. To re-authenticate to the share, we need to manually
navigate to the network path through windows explorer and supply an
"administrative" user credentials when asked by windows, user's new
credentials are no more accepted.
What is weirder is that only the network path used by the application is
losing it's credentials, we can navigate anywhere else without
re-authenticating user.
Please note that our networking department have been working closely
with Microsoft people to diagnose the problem and the tests are now pointing
at our application as they found nothing wrong on the network side.
Anyone is having an idea of what may be going wrong here? Any help
would be appreciated.
Thanks,
--
Sylvain Audet MCP+SB - Senior programmer
Hartco Corporation (http://www.hartco.com/)
