Post reply

Connection issue

  • May 10, 2007 at 6:18 pm

    #172368

    Hi everyone,

    A user of mine has SQL 2005 client on his XP computer and is trying to connect to a SQL 2K SP4 running on Win 2K SP4. He gets the following error when he tries to connect from Management Studio:

    Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection. (Microsoft SQL Server, Error: 18452)

    I've been working on it all day and am exhausted, so I turn to you now. Thanks in advance for your help.

  • May 10, 2007 at 6:58 pm

    #705692

    Is your user using a DB account or Windows account? Sounds like you're using Windows auth. Try DB account and see if it works. Definitely a security issue.

  • May 10, 2007 at 9:43 pm

    #705710

    Is your SQL Server configured to use in "Mixed Mode authentication"?

    Is your server is in same domain?

    If it is in different domain, ask him to execute the following command on the command prompt from his work station.

    net use \\servername /userOMAINNAME\username

    then, he must add SERVERNAME in alias in CLIENT NETWORK UTILITY. or SQL Configuration manager.

    Ask him to try connecting to sql server now.

    See if it works.

  • May 11, 2007 at 9:25 am

    #705863

    Hi everyone,

    My user is using a domain account. The server is in the same domain too. The server is set to mixed mode auth.

    There are other users who use Management Studio to connect to the same database, so I am not sure why he is the only one that is having login problems.

    Edit: Thanks for your response and help.

  • May 11, 2007 at 9:29 am

    #705867

    can the user login using enterprise manager or the QA?

    Everything you can imagine is real.

  • May 11, 2007 at 9:58 am

    #705894

    I want to echo bledu's question and also ask if the user could ever login to the SQL 2000 instance.  If no, make sure his login has been added and that it has access to it's default database.

    Greg

    Greg

  • May 14, 2007 at 4:15 pm

    #706357

    Sorry for the very late response. The user tried to connect to the database using QA and he gets the same error message.

  • May 15, 2007 at 2:59 am

    #706430

    1. dumb question but did you check whether the user has is added to the sql users? what do you get if you run this command

    EXEC

    master..xp_logininfo 'domainName\userName'

    2. You could try specifying the sql port 1433 for the connection

    Everything you can imagine is real.

  • May 15, 2007 at 9:36 am

    #706552

    Yes, I have tried that. When I run xp_logininfo, I get:

    account name type privilege mapped login name permission path

    domain\user useruser domain\user NULL

    As far as port 1433 is concerned, how do I set it so that Management Studio uses that port. And can you explain your reasoning behind this approach?

    Thanks.

Viewing 9 posts - 1 through 8 (of 8 total)

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