L 2000 on it. Yesterday. users began having read-only access to a database
that clearly states they have read/write access. At around the same time th
at this occured, I noticed
in the security log that the Kerberos account experienced logon failure with
Event ID 537. This error code just states unable to logon for unknown reas
on. Any help/suggestions is greatly appreciated.
DaveNot sure I understand the question - what do you mean by read-only access?
If you look at sp_protects or something similar in the database are the
user's permissions changed?
Richard Waymire, MCSE, MCDBA
This posting is provided "AS IS" with no warranties, and confers no rights.
"Dave" <anonymous@.discussions.microsoft.com> wrote in message
news:6AAC7FF7-98A2-4E3A-872A-C84594EF887D@.microsoft.com...
quote:
> I recently started receiveing an error message on a Win2K server that has
SQL 2000 on it. Yesterday. users began having read-only access to a
database that clearly states they have read/write access. At around the
same time that this occured, I noticed in the security log that the Kerberos
account experienced logon failure with Event ID 537. This error code just
states unable to logon for unknown reason. Any help/suggestions is greatly
appreciated.
quote:|||The kerberos error could be caused by duplicate Netbios names. This could
> Dave
be due to parent child/domains.
This would happen if the machine with same netbios name exists in the
parent
domain. So when a user in parent domain gets authenticated, he accesses the
machine
account listed in AD users and computers for the machine account in parent
domain.
However the child domain user will access the machine in child domain.
Also, when
using the IP or FQDN, the duplicate netbios names are not causing problems
and
hence would work.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
No comments:
Post a Comment