SQL Server Error 18456

  • I'm running an Access 2000 Database on Windows 2000.  The Access Database links to SQL Server 2000 tables.   The error occurs when the users login through our terminal server and open the database to open the tables or forms. The connection will fail with the following:

    Connection failed:

      SQLState '28000'

                SQL Server Error 18456

                [Microsoft][ODBC SQLServer Driver][SQL Server]Login failed for

    user 'xy'.

    When these same users connect to the database through their workstations they are able to logon successfully and use the linked tables and forms.

    I used in the Data Source set up and tested the connection and I have as WindowsNt authentication using the network login ID.   All these users are in added to sql server as users for these database using windows authentication.

    But if I add in the sql server box, administrator rights to the user then they could access the sql server database through terminal server, I don't want to have to give these administrators rights to all users, what can I do?

    Is there anything else to check for?

    Thanks in advance.

  • This was removed by the editor as SPAM

  • Are the SQL Server and the Terminal Server in the same Domain? It sounds like a trust issue. You say however you setup the accunts as administrator and they can get in. Do you mean as a member Domain Admin or Local Admin group? Do you hav a group you put them into to give access that is local to the SQL Server or i it a domain group?

  • yes it is in the same domain, I am setting them as a local/administrator. and then they get no error message if the stay only with user rights then they get that error message, i also tried to add the poweruser access but same thing.

  • Is this an Active Directory setup? Thre was a similar post in th past few weeks if it is.

    http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=6&messageid=271375#bm272890

    And see if it helps.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply