Hi, Vicky.
"Trusted" refers to your domain based login that this protocol
expects. You might temporarily delete your SQL-based login and re-add
your "trusted" ID or the group it is a member of in the domain to test
this functionality.
You can troubleshoot this by putting a trace (SQL Profiler) on to see
where the authentication fails and what exact message is responsible
for the failure.
Is it possible that you have different passwords between your SQL
account and your domain-based account? If not, try setting them to the
same code.
If you enable more TCP/IP and Named Pipes for both the client and
server and try again, it will probably allow you to pass the check by
authenticating somewhere. I only suggest this if you are stuck.
Hope this helps or gives you some options.
--Steve
st***@strategic-pc.com