login failed in different domains

  • Hi,

    I run the same application on 2 machines on 2 different domains. Both apps send data to 1 SQL Server. Both instances use the same login name. The apps run for a long time with no problems. For 3 days now,the one of the sides start erroring: SQL Server does not exist or access is denited. Today the error changed to "login request failed to open database for login...". The problem is that I did not changed anything on SQL side - somebody else makes changes and do not have a way to know who is it...

    Please, advise, what I have to look first in this case ? I did check the SQL logins, the 2 apps logins... Both domains are admin for SQL server...Is it possible the problem to arise if somebody changed the trusted logins for the domains itselves?

    Thanks a lot for the help.

  • That is something you may want to check with whoever administers your NT domain...

    Mike

  • In Enterprise Manager, right click on the Server, select properties and that should tell you what type of authentication is being used.

    -SQLBill

  • NT admin said there's nothing changed! And the SQl Server uses the right auth.

    My questions is principle:

    In situations like this what will be the steps to look at.Like: first-I checked the login on the SQl server, then I checked the apps login and the connection string, etc. Is there something on line to give good troubleshooting directions for login and access issues?

    Thanks a lot.

  • make sure you can reach the server from that machine! it sounds like the client lost configuration info


    * Noel

  • I found the problem - it was the corrupted ini file - no paths inside, just crap...

    But I still would like to know if somebody have seen a good troubleshooting materials for connections and SQL/windows security/user rights.

    Thanks you, guys, a lot for the help.

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

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