Authentication issue and cached credentials

I have a user with an XP SP2 machine who logs in over a VPN connection
frequently. Occasionally he has a network blip and momentarily looses
network connectivity. When this happens, and he tries to access the network
shares he was previously working on he receives a bad user name or password
type error and can't access the shares. It goes away in about 30 minutes. I
have checked and during that time his account is not locked out nor does he
reenter credentials. He is getting kerberos error Event 14 on his machine
saying to check the credentials manager locally on XP, which we did, however
there are no cached credentials on his box showing up. If he opens a command
prompt and newly enters credentials with the runas command and then accesses
the network shares, same shares, same credentials from the command prompt
using net use, he is successful, meanwhile under the gui he can not access
the network shares. Has anyone seen this behaviour and have a fix? If his
credentials showed up in credential manager, it would be easy, but they
aren't there.
--
Beckyibop

--
Beckyibop


"Becky" wrote:

I have a user with an XP SP2 machine who logs in over a VPN connection
frequently. Occasionally he has a network blip and momentarily looses
network connectivity. When this happens, and he tries to access the network
shares he was previously working on he receives a bad user name or password
type error and can't access the shares. It goes away in about 30 minutes. I
have checked and during that time his account is not locked out nor does he
reenter credentials. He is getting kerberos error Event 14 on his machine
saying to check the credentials manager locally on XP, which we did, however
there are no cached credentials on his box showing up. If he opens a command
prompt and newly enters credentials with the runas command and then accesses
the network shares, same shares, same credentials from the command prompt
using net use, he is successful, meanwhile under the gui he can not access
the network shares. Has anyone seen this behaviour and have a fix? If his
credentials showed up in credential manager, it would be easy, but they
aren't there.

Oh there are no scheduled tasks or services running with his user account.
--
Beckyibop

Not an answer to your problem, but shares created under RunAs won't work in
the GUI because they were created in a different user-space.

I understand that, but with the same credentials under the command prompt, it
works and doesn't work with the GUI, I'm trying to understand why the GUI
doesn't work when the credentials you logged in with in both places are the
same.
--
Beckyibop


"Ian" wrote:


Not an answer to your problem, but shares created under RunAs won't work in
the GUI because they were created in a different user-space.

"Becky" wrote in message
...
I have a user with an XP SP2 machine who logs in over a VPN connection
frequently. Occasionally he has a network blip and momentarily looses
network connectivity. When this happens, and he tries to access the
network
shares he was previously working on he receives a bad user name or
password
type error and can't access the shares. It goes away in about 30 minutes.
I
have checked and during that time his account is not locked out nor does
he
reenter credentials. He is getting kerberos error Event 14 on his machine
saying to check the credentials manager locally on XP, which we did,
however
there are no cached credentials on his box showing up. If he opens a
command
prompt and newly enters credentials with the runas command and then
accesses
the network shares, same shares, same credentials from the command prompt
using net use, he is successful, meanwhile under the gui he can not access
the network shares. Has anyone seen this behaviour and have a fix? If
his
credentials showed up in credential manager, it would be easy, but they
aren't there.
--
Beckyibop
I saw a similar ? problem with a VPN user. After logging into his VPN and
exiting, he no longer had network access. The only thing we could have him
do was "release and renew" his IP settings which was inconvenient, but
worked.