Add NT users

After adding NT users as SQL Server logins, I tried to set
them up on their PC using ODBC connections but get the
message:
SQL Server error: 18452
Login failed for user (null). Reason: not associated with
a trusted SQL Server connection
Can someone advise on basic checks?
(Our SQL Server is setup for MIXED MODE and I myself can
use the NT Authentication since I belong to the SQL ADMIN
group via the main DOMAIN server setup)
thks!what's the connection string look like? This error typically means SQL
Server thought you were coming in with a standard security connection...
Richard Waymire, MCSE, MCDBA
This posting is provided "AS IS" with no warranties, and confers no rights.
"wayne" <anonymous@.discussions.microsoft.com> wrote in message
news:ecb201c40c36$87a17810$a301280a@.phx.gbl...
> After adding NT users as SQL Server logins, I tried to set
> them up on their PC using ODBC connections but get the
> message:
> SQL Server error: 18452
> Login failed for user (null). Reason: not associated with
> a trusted SQL Server connection
> Can someone advise on basic checks?
> (Our SQL Server is setup for MIXED MODE and I myself can
> use the NT Authentication since I belong to the SQL ADMIN
> group via the main DOMAIN server setup)
> thks!|||Good point - Can't remember where I last checked for this
info - can't find it in the Profiler or Performance
Logs/Alerts....any hints?

>--Original Message--
>what's the connection string look like? This error
typically means SQL
>Server thought you were coming in with a standard
security connection...
>--
>Richard Waymire, MCSE, MCDBA
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>"wayne" <anonymous@.discussions.microsoft.com> wrote in
message
>news:ecb201c40c36$87a17810$a301280a@.phx.gbl...
set
with
ADMIN
>
>.
>|||it'd be in the application code.
Richard Waymire, MCSE, MCDBA
This posting is provided "AS IS" with no warranties, and confers no rights.
"Wayne" <anonymous@.discussions.microsoft.com> wrote in message
news:c10501c40c3f$eb6ae260$a601280a@.phx.gbl...
> Good point - Can't remember where I last checked for this
> info - can't find it in the Profiler or Performance
> Logs/Alerts....any hints?
>
> typically means SQL
> security connection...
> confers no rights.
> message
> set
> with
> ADMIN|||We are not using any development tools - just settingup
the ODBC connection to enabled Access/Excel to make
connections to the SQL Server!
It is where the ODBC Admin tool (setting-up a DSN) that
has failed - any idea?
Cheers!
>--Original Message--
>it'd be in the application code.
>--
>Richard Waymire, MCSE, MCDBA
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>"Wayne" <anonymous@.discussions.microsoft.com> wrote in
message
>news:c10501c40c3f$eb6ae260$a601280a@.phx.gbl...
this
and
to
the
can
>
>.
>|||ODBC administrator is in the Control Panel
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||when you configure the data source in ODBC as a type for SQL Server,
clicking next on the config will bring you to the page where it asks if you
want to "With Windows NT authentication..." or "With SQL Server
authentication..." - make sure the top option is selected.
Richard Waymire, MCSE, MCDBA
This posting is provided "AS IS" with no warranties, and confers no rights.
"Wayne" <anonymous@.discussions.microsoft.com> wrote in message
news:c7f301c40cca$be4c1200$a601280a@.phx.gbl...
> We are not using any development tools - just settingup
> the ODBC connection to enabled Access/Excel to make
> connections to the SQL Server!
> It is where the ODBC Admin tool (setting-up a DSN) that
> has failed - any idea?
> Cheers!
> confers no rights.
> message
> this
> and
> to
> the
> can|||Wayne,
It may be easier to troubleshoot if you open up a case with a SQL
Support Engineer.
Login failed user 'null' could indicate problems with the DC or even DNS.
There's a utility called netdiag.exe that you can get from the WIndows
Resource kit, to validate communication with the DC and your DNS servers.
Run the following test:
isql -Snp:sqlserverNameHere -E -Q"Select @.@.version"
and
isql -Stcp:sqlserverNameHere -E -Q"Select @.@.version"
and post the results.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Thks Kevin!

>--Original Message--
>Wayne,
> It may be easier to troubleshoot if you open up a case
with a SQL
>Support Engineer.
>Login failed user 'null' could indicate problems with the
DC or even DNS.
>There's a utility called netdiag.exe that you can get
from the WIndows
>Resource kit, to validate communication with the DC and
your DNS servers.
>
>Run the following test:
>isql -Snp:sqlserverNameHere -E -Q"Select @.@.version"
>and
>isql -Stcp:sqlserverNameHere -E -Q"Select @.@.version"
>and post the results.
>
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and
confers no rights.
>
>.
>