Login failed for user ". The user is not associated with a trusted SQL Server connection

There are two servers:  db1 and db2.  They are remote to us and I'm sure a firewall is involved.  They also use a domain and windows authentication for us to connect to.  We also have an account that the web server uses, we can also try to connect with (username/password).  Several of us users are able to connect and work normally with db2.  However, all of us are having connection issues with db1.  

It's intermittent, though:

Sometimes I can connect to db1 and run a query (using Windows Authentication), or use the SQL Server Management Studio and explore the databases, but other times it hangs and I get the error (in the title).  It may switch within seconds.  When it does retrieve data, it is fast and doesn't skip like it would with packet loss.  (I do not believe packet loss is the issue here.)

To db1, I can never connect using the username/password, however the web server always can.  I can always connect both ways to db2 without issue.

The database administrator verifies that other people are able to connect OK, and that our accounts are not blocked or locked.  He can see in the logs where we attempt to connect (by our IP).  He says it does not appear to be anything on his end.  We think there is nothing that is on our end (since we can connect to db2 just fine, which is essentially in the same location).

What could be causing this?  Some closed obscure port on a firewall?
Who is Participating?
InkEyeConnect With a Mentor Author Commented:
The answer became somewhat clear(er).  After ruling out any firewall issues, the DBA was able to duplicate the problem.  After a hard reboot (which was not a simple matter), the problem was apparently solved.  However, the next day, the 2nd database server (which was fine) was now experiencing the problem.  After close examination, it was discovered that several services had not started.  (I don't know which ones, but possibly something having to do with a domain controller might have been involved.)  DBA started the necessary services, and everything works fine.
Vitor MontalvãoMSSQL Senior EngineerCommented:
There's a similar question with solution. Check if it applies to your problem:

Good luck
InkEyeAuthor Commented:
I think his situation is somewhat different:  In our case, there are other users in other remote locations that apparently are connecting without issue.  In my case, I can connect only sometimes, and even after I have connected it may randomly perform functions/queries (or not).

Yet, on the other server, it always works fine.

The thinking is that perhaps the firewall at their end has blocked a range of ports for the first db server, but not all the ports.  Thus, depending on what ports are available, I am able to connect.  But this doesn't explain everything.
Vitor MontalvãoMSSQL Senior EngineerCommented:
That's great :)

InkEyeAuthor Commented:
I really had nothing to do with the solution, though.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.