Bruce
April 17th 03, 08:04 PM
Unaware of the problem? Don't they read their own
newsgroups?
After the fiasco I had yesterday with 811493, and seeing,
on this newsgroup, that others have experienced the same
problems, I'm not going to just plain accept that updates
and install them. I'll especially not install any that
are not uninstallable.
What's especially annoying is that MSFT says they aren't
aware of any problems. I guess they'll just issue an
update to fix 811493.
Will SP2 include the 811493 anymore?
Geezzzz
>-----Original 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.
>.
>
newsgroups?
After the fiasco I had yesterday with 811493, and seeing,
on this newsgroup, that others have experienced the same
problems, I'm not going to just plain accept that updates
and install them. I'll especially not install any that
are not uninstallable.
What's especially annoying is that MSFT says they aren't
aware of any problems. I guess they'll just issue an
update to fix 811493.
Will SP2 include the 811493 anymore?
Geezzzz
>-----Original 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.
>.
>