Not associated with a trusted SQL Server connection

I have two dev boxes, a Dell and an HP and I develop asp.net apps on both
and run sql server on both.  For some time now I have been accessing the
database on the opposite machine from which I develop (runs better that
way).

All of a sudden, however, I'm getting "Logon failed for user "sa" Reason:
Not associated with a trusted SQL Server connection" when I run on the Dell
and use the HP for a server.  My connection string hasen't changed and both
servers are configured for Mixed Mode (the registry login parameter is set
to 2).  Still, Query Analyzer and EM can access the HPmachine just fine from
the Dell.  My connection string has always been the same ......

Connect  Timeout=40;workstati
on id=HPBox;packet size=4096;user id=sa;data
 source=HPBox;persist
 security info=True;initial
 catalog=DataBaseOne;
password=xxxxxx
-- Any idea what could be causing this - all of a sudden?
Regards,
Gary

Gary,

Can you connected to the server using "sa" from Query Analyzer?  Also, as a
side note, I wouldn't recommend developing your aps using the sa password.

HTH

Jerry
"Gary Blakely" <seemywebsite@nospam.com> wrote in message
news:%23VXd0q7wFHA.720@TK2MSFTNGP10.phx.gbl...
>I have two dev boxes, a Dell and an HP and I develop asp.net apps on both
>and run sql server on both.  For some time now I have been accessing the
>database on the opposite machine from which I develop (runs better that
>way).
>
> All of a sudden, however, I'm getting "Logon failed for user "sa" Reason:
> Not associated with a trusted SQL Server connection" when I run on the
> Dell and use the HP for a server.  My connection string hasen't changed
> and both servers are configured for Mixed Mode (the registry login
> parameter is set to 2).  Still, Query Analyzer and EM can access the
> HPmachine just fine from the Dell.  My connection string has always been
> the same ......
>
> Connect  Timeout=40;workstati
on id=HPBox;packet size=4096;user id=sa;data
>  source=HPBox;persist
 security info=True;initial
>  catalog=DataBaseOne;
password=xxxxxx
> -- Any idea what could be causing this - all of a sudden?
> Regards,
> Gary
>
>

Yes, as I said in my message, I can connect with Query analyzer.  That is
what is very puzzling but my connectstring has not  changed.

we just use sa for testing.

--
Regards,
Gary Blakely
Dean Blakely & Associates
www.deanblakely.com
"Jerry Spivey" <jspivey@vestas-awt.com> wrote in message
news:e1mXQ67wFHA.3644@TK2MSFTNGP11.phx.gbl...
> Gary,
>
> Can you connected to the server using "sa" from Query Analyzer?  Also, as
> a side note, I wouldn't recommend developing your aps using the sa
> password.
>
> HTH
>
> Jerry
> "Gary Blakely" <seemywebsite@nospam.com> wrote in message
> news:%23VXd0q7wFHA.720@TK2MSFTNGP10.phx.gbl... 
>
>

This is an authentication issue.
Please check the time for both the machine logging in, the server and the
domain controller. If they are more than 5 minutes apart authentication will
fail.

--
Nik Marshall-Blank MCSD/MCDBA

"Gary Blakely" <seemywebsite@nospam.com> wrote in message
news:%23VXd0q7wFHA.720@TK2MSFTNGP10.phx.gbl...
>I have two dev boxes, a Dell and an HP and I develop asp.net apps on both
>and run sql server on both.  For some time now I have been accessing the
>database on the opposite machine from which I develop (runs better that
>way).
>
> All of a sudden, however, I'm getting "Logon failed for user "sa" Reason:
> Not associated with a trusted SQL Server connection" when I run on the
> Dell and use the HP for a server.  My connection string hasen't changed
> and both servers are configured for Mixed Mode (the registry login
> parameter is set to 2).  Still, Query Analyzer and EM can access the
> HPmachine just fine from the Dell.  My connection string has always been
> the same ......
>
> Connect  Timeout=40;workstati
on id=HPBox;packet size=4096;user id=sa;data
>  source=HPBox;persist
 security info=True;initial
>  catalog=DataBaseOne;
password=xxxxxx
> -- Any idea what could be causing this - all of a sudden?
> Regards,
> Gary
>
>

my two machines are in a workgroup not a domain.  The clocks are identical
on the two systems.


--
Regards,
Gary Blakely
Dean Blakely & Associates
www.deanblakely.com
"Nik Marshall-Blank (delete fcom for my email address)"
<NikMB@fcomiNodefcom.afcomt> wrote in message
news:WCr_e.15919$o11.5329@fe01.news.easynews.com...
> This is an authentication issue.
> Please check the time for both the machine logging in, the server and the
> domain controller. If they are more than 5 minutes apart authentication
> will fail.
>
> --
> Nik Marshall-Blank MCSD/MCDBA
>
> "Gary Blakely" <seemywebsite@nospam.com> wrote in message
> news:%23VXd0q7wFHA.720@TK2MSFTNGP10.phx.gbl... 
>
>