none
SQL Server Management Studio Error 64

    Question

  • Hi!<o:p></o:p>

    I am experiencing some difficulties with SQL
    management studio for some users in a domain:<o:p></o:p>

    User DomainA\Joe is granted SQL login rights on a
    SQL2008 SP2 instance, and can log into the instance from a domain member
    laptop. Joe can also log into the same instance from the SQL server(when using
    rdp).<o:p></o:p>

    User DomainA\Johnny is granted the same SQL login rights
    on the same SQL2008 SP2 instance as DomainA\Joe, and cannot login to the
    instance from the same domain member laptop as Joe.

    If Johnny tries to login to SQL management studio to the same SQL instance from
    the server(using rdp) it works out fine.<o:p></o:p>

    The error DomainA\Johnny receive:

    A connection was
    successfully established with the server, but then an error during the login
    process.(provider TCP Provider, error: 0 - The specified network name is no longer
    available.)(Microsoft SQL Server, Error: 64)
    <o:p></o:p>

    SQL Server edition: SQL Server 2008 SP2(10.0.4064.0)
    Enterprise

    Windows OS: Windows 2008 R2 Enterprise(SP1 not installed)

    Domain information: Windows 2008 R2 Domain level

    Forrest level: Windows 2008 R2 <o:p></o:p>

    The computer, server and users are all in the same
    domain and IP subnet (so no firewall is blocking). Windows firewall is disabled
    on both server and computer and there are no IPsec communication requirements.<o:p></o:p>

    The question is: Why is a user denied login using SQL
    management studio on a domain laptop, but is granted login on the server - when
    another user with the same level of permission is granted login using SQL
    management studio on the same domain laptop(and is also granted login on the
    SQL server)?<o:p></o:p>



    ---------------------------------------------------------- Please use Mark as Answer if my post solved your problem and use Vote As Helpful if a post was useful. http://www.havardkristiansen.com

    Wednesday, October 03, 2012 11:32 AM

Answers

  • Hi,

    thank you all for the replies. Due to a domain migration a lot of the users kept their old Active Directory Groups from the parrent domain causing Kerberos to fail.
    I wrote a blogg post for this, for more information see: http://havardkristiansen.com/?p=315

    Best regards,

    Håvard


    ---------------------------------------------------------- Please use Mark as Answer if my post solved your problem and use Vote As Helpful if a post was useful. http://www.havardkristiansen.com

    Monday, October 08, 2012 8:29 PM

All replies

  • Can you check & share the sql server error log for login failure details?

    Regards,
    Rohit Garg
    (My Blog)
    This posting is provided with no warranties and confers no rights.
    Please remember to click Mark as Answer and Vote as Helpful on posts that help you. This can be beneficial to other community members reading the thread.

    Wednesday, October 03, 2012 1:12 PM
  • Hi Havard,

    Make sure the issues below and try to connect it again remotely.
    1) SQL Server should be up and running.
    2) Enable TCP/IP in SQL Server Configuration
    3) Open Port in Windows Firewall
    4) Enable Remote Connection
    5) Enable SQL Server Browser Service
    6) Create exception of sqlbrowser.exe in Firewall

    For more information, refer to:
    http://relyonsoft.com/techsupport/?p=143
    http://www.escapekeys.com/blog/index.cfm/2011/1/26/Microsoft-SQL-Server-Error-64-A-connection-was-successfully-established-with-the-server.

    TechNet Subscriber Support
    If you are
    TechNet Subscription user and have any feedback on our support quality, please send your feedback here.


    Thanks,
    Maggie


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. This can be beneficial to other community members reading the thread.

    Thursday, October 04, 2012 2:57 AM
    Moderator
  • Hi,

    thank you all for the replies. Due to a domain migration a lot of the users kept their old Active Directory Groups from the parrent domain causing Kerberos to fail.
    I wrote a blogg post for this, for more information see: http://havardkristiansen.com/?p=315

    Best regards,

    Håvard


    ---------------------------------------------------------- Please use Mark as Answer if my post solved your problem and use Vote As Helpful if a post was useful. http://www.havardkristiansen.com

    Monday, October 08, 2012 8:29 PM