can't register server in enterprise manager

I have a SQL 2000 Server that I just recently moved into an AD domain from
an NT domain. We created new windows authentication accounts for all users
and things have worked fine except for a couple of people. Three people
can't access any databases.
On my PC, if I login as myself and go to EM I can register this server with
no problems. If I login as one of these users, I get the following when
trying to register the server:
A connection could not be established to <servername>
Reason: Login failed for user <domain>\<user>
Please verify SQL Server is running and check your SQL Server registration
properties and try again.
SQL is definitely running and it is not a password problem since I logged in
just fine to the PC. Also, the user has local Administrator access to the
PC. I don't understand why 3 out of 30 login accounts are doing this. Can
anyone help?
Thanks.Hello,
You may want to first create a new domain user and then add it as a SQL
login to test the sitaution. If the issue does not occur, it seems to be
some issue with the specific user accounts. You may want to try following
steps for a problemtic domain login.
1. Remove all SQL logins with similar name from SQL logins
2. Remove the domain user from the AD
3. Try to create a new domain user with the same name, and add it again as
a SQL login.
4. Test if the issue still occurs at this time.
If the issue perists, you may try the following steps to isolate the issue:
1. Add the following registry keys:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
DisableStrictNameChecking DWORD Value=1
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
DisableLoopbackCheck DWORD
Value=1
2. Edit the Local Security policy and set ?Network Security: LAN Manager
authentication level? to ?Send LM and NTLM responses?
3. Test if the issue occurs at this time.
926642 Error message when you try to access a server locally by using its
FQDN or its CNAME alias after you install Windows Server 2003 Service Pack
1: "Access denied" or "No network provider accepted the given network path"
http://support.microsoft.com/default.aspx?scid=kb;EN-US;926642
If you have any update on the issue, please feel free to let's know. Thank
you.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||r
Take a look into ERROR.LOG , what is says?
When you create a login for one of those people what default database you
granted for them? Does it exist? Perhaps it is in suspect mode?
"r" <none@.none.com> wrote in message
news:uqolHls%23HHA.3900@.TK2MSFTNGP02.phx.gbl...
>I have a SQL 2000 Server that I just recently moved into an AD domain from
>an NT domain. We created new windows authentication accounts for all users
>and things have worked fine except for a couple of people. Three people
>can't access any databases.
> On my PC, if I login as myself and go to EM I can register this server
> with no problems. If I login as one of these users, I get the following
> when trying to register the server:
> A connection could not be established to <servername>
> Reason: Login failed for user <domain>\<user>
> Please verify SQL Server is running and check your SQL Server
> registration properties and try again.
> SQL is definitely running and it is not a password problem since I logged
> in just fine to the PC. Also, the user has local Administrator access to
> the PC. I don't understand why 3 out of 30 login accounts are doing this.
> Can anyone help?
> Thanks.
>