PDA

View Full Version : Q811493 Problem


WInson Smith
April 17th 03, 05:10 PM
Since installing Q811493 on several Windows 2000
workstations yesterday, we can no longer change
permissions on folders on remote servers using peer to peer
(non-Active Directory) networking (don't know about other
networking). After being prompted for and supplying your
username and password, you get a "The credentials supplied
conflict with an existing set of credentials". After
installing the update on another PC to confirm that it is
Q811493 that makes the difference, we called Microsoft
about it and they said that they were unaware of the
problem.

Matthew Mucker [MSFT]
April 17th 03, 05:15 PM
"The credentials supplied conflict with an existing set of credentials"
means that you're trying to connect to a remote machine using a
username/password, but you've already got a connection to that machine with
a different username/password.

You can't connect to the same remote machine with two sets of credentials at
the same time. Disconnect the first session first and you should be good to
go. (Perhaps you were deploying these fixes remotely and that tool created a
connection as a different user?)


"WInson Smith" > wrote in message
...
> Since installing Q811493 on several Windows 2000
> workstations yesterday, we can no longer change
> permissions on folders on remote servers using peer to peer
> (non-Active Directory) networking (don't know about other
> networking). After being prompted for and supplying your
> username and password, you get a "The credentials supplied
> conflict with an existing set of credentials". After
> installing the update on another PC to confirm that it is
> Q811493 that makes the difference, we called Microsoft
> about it and they said that they were unaware of the
> problem.

Winston_Q_Smith
April 17th 03, 05:37 PM
>Subject: Re: Q811493 Problem
>From: "Matthew Mucker [MSFT]"
> Sent: 4/17/2003 9:15:26 AM

I know what that message is supposed to mean! The problem
is NOT being caused by having an existing connection, it
is apparently caused by a bug in the patch. We tried it
on several computers in a variety of situations.

Google