Trusted Connection failing

16 Mar 2006 9:18 PM

jfission23

My VB.net app running on 6 local computers and failing on another two,
and I am stumped. The message I receive the two failing computers is:

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

I have a short program to test 2 different types of connections:
- server name and trusted connection
- server name and user name and password
....and of course the trusted connection fails on the two machines.

Now here's the kicker; all machines are setup similar and nothing that
I can find would indicated why a trusted connection won't work on the
two.

The connection string is contained in a 'config' file and is the
following:

server='Comp1'; Database=db2; Trusted_Connection=True

It appears to be an obvious problem with each client machine. What am I
missing? Thanks.

16 Mar 2006 11:36 PM

Jéjé

does the user can access the server after he made a connection to it?
(connect to a shared folder)

does the users and computers are on the same domain?
does the firewall is on?

<jfissio***@hotmail.com> wrote in message
Show quoteHide quote

news:1142543938.383604.17400@z34g2000cwc.googlegroups.com...
> My VB.net app running on 6 local computers and failing on another two,
> and I am stumped. The message I receive the two failing computers is:
>
> Login failed for user '(null)'. Reason: Not associated with a trusted
> SQL Server connection.
>
> I have a short program to test 2 different types of connections:
> - server name and trusted connection
> - server name and user name and password
> ...and of course the trusted connection fails on the two machines.
>
> Now here's the kicker; all machines are setup similar and nothing that
> I can find would indicated why a trusted connection won't work on the
> two.
>
> The connection string is contained in a 'config' file and is the
> following:
>
> server='Comp1'; Database=db2; Trusted_Connection=True
>
> It appears to be an obvious problem with each client machine. What am I
> missing? Thanks.
>

16 Mar 2006 11:52 PM

jfission23

All users are part of a WORKGROUP, and not a domain. All connections
are direct by LAN to the server. If a non-working computer is moved to
LAN connection of a working computer, the non-working computer can
still not connect by way of trusted connection.

These non-working computers can connect to the server using user name
and password, but that is temporary and incomplete.

Jéjé wrote:
Show quoteHide quote

> does the user can access the server after he made a connection to it?
> (connect to a shared folder)
>
> does the users and computers are on the same domain?
> does the firewall is on?

17 Mar 2006 12:23 AM

Jéjé

can you access the SQL server AFTER you made a connection to this server
using a shared folder?

connect a letter to a shared folder, and after try to access SQL Server
sometimes this generates the right security token for the user.

<jfissio***@hotmail.com> wrote in message

news:1142553171.265069.61210@z34g2000cwc.googlegroups.com...

All users are part of a WORKGROUP, and not a domain. All connections
are direct by LAN to the server. If a non-working computer is moved to
LAN connection of a working computer, the non-working computer can
still not connect by way of trusted connection.

These non-working computers can connect to the server using user name
and password, but that is temporary and incomplete.

Jéjé wrote:
Show quoteHide quote

> does the user can access the server after he made a connection to it?
> (connect to a shared folder)
>
> does the users and computers are on the same domain?
> does the firewall is on?

17 Mar 2006 3:47 PM

jfission23

I'll try that next time I am on-site, and re-post if it does work.
Thanks.

Jéjé wrote:
Show quoteHide quote

> can you access the SQL server AFTER you made a connection to this server
> using a shared folder?
>
> connect a letter to a shared folder, and after try to access SQL Server
> sometimes this generates the right security token for the user.