Okay, thanks Barry.

Unfortunately I do have the users set up on the standalone server, and am
still getting the error;

"18452: Login failed for user '(null)'. Reason: not associated with a
trusted SQL server connection."

Specifically this is an error message appearing in a MS Access 97 front end
with ODBC tables connected to SQL Server 2000 running an an NT 4.0 box. All
the latest NT/SQL patches installed, latest MDAC, etc. Only TCP/IP and IPX
enabled, and security mode set to "Mixed". The connection works properly on
about half our workstations, doesn't work on the other half (all different
user names, all Win98 boxes).

Any ideas?

Thanks
Sam T

"Barry McAuslin" <barry_mcauslin@yahoo.com.nospam> wrote in message
news:egqoogEiDHA.4024@TK2MSFTNGP11.phx.gbl...
> Yes you can. You just have to make sure the username and password exists
on
> the server. I.e. if you are connecting from a domain or standalone with
the
> user name of Joe and password of pass, you must have a user called Joe
with
> a password of pass on you standalone SQL Server.
>
> This is just basic windows workgroup security.
>
> ----------
>
> Barry McAuslin
>
> Look inside your SQL Server files with SQL File Explorer.
> Go to http://www.sqlfe.com for more information.
>
> "Sam T" <NOritSPAM9001@nyp.org> wrote in message
> news:udNVFPDiDHA.3700@TK2MSFTNGP11.phx.gbl...
> > Greetings,
> >
> > Is it possible to use the Windows Authentication option on a server
which
> is
> > configured as "stand-alone" and not as a domain controller or member of
a
> > domain? I would prefer not to have to use the SQL Server authentication
> > option.
> >
> > Thank you,
> >
> > Sam T
> >
> >
>
>

Try just TCPIP. Go to a WS not working and run cliconfg.exe. Create an
alias to the SQL server using TCPIP or change the default network library to
TCP/IP.

----------

Barry McAuslin

Look inside your SQL Server files with SQL File Explorer.
Go to http://www.sqlfe.com for more information.

"Sam T" <NOritSPAM9001@nyp.org> wrote in message
news:eGOVesOiDHA.752@TK2MSFTNGP12.phx.gbl...
> Okay, thanks Barry.
>
> Unfortunately I do have the users set up on the standalone server, and am
> still getting the error;
>
> "18452: Login failed for user '(null)'. Reason: not associated with a
> trusted SQL server connection."
>
> Specifically this is an error message appearing in a MS Access 97 front
end
> with ODBC tables connected to SQL Server 2000 running an an NT 4.0 box.
All
> the latest NT/SQL patches installed, latest MDAC, etc. Only TCP/IP and
IPX
> enabled, and security mode set to "Mixed". The connection works properly
on
> about half our workstations, doesn't work on the other half (all different
> user names, all Win98 boxes).
>
> Any ideas?
>
> Thanks
> Sam T
>
> "Barry McAuslin" <barry_mcauslin@yahoo.com.nospam> wrote in message
> news:egqoogEiDHA.4024@TK2MSFTNGP11.phx.gbl...
> > Yes you can. You just have to make sure the username and password
exists
> on
> > the server. I.e. if you are connecting from a domain or standalone with
> the
> > user name of Joe and password of pass, you must have a user called Joe
> with
> > a password of pass on you standalone SQL Server.
> >
> > This is just basic windows workgroup security.
> >
> > ----------
> >
> > Barry McAuslin
> >
> > Look inside your SQL Server files with SQL File Explorer.
> > Go to http://www.sqlfe.com for more information.
> >
> > "Sam T" <NOritSPAM9001@nyp.org> wrote in message
> > news:udNVFPDiDHA.3700@TK2MSFTNGP11.phx.gbl...
> > > Greetings,
> > >
> > > Is it possible to use the Windows Authentication option on a server
> which
> > is
> > > configured as "stand-alone" and not as a domain controller or member
of
> a
> > > domain? I would prefer not to have to use the SQL Server
authentication
> > > option.
> > >
> > > Thank you,
> > >
> > > Sam T
> > >
> > >
> >
> >
>
>