Like Aaron said, it looks like a trusted connection is being attempted
since the error messages shows the 'computername/inet_user' Windows
account rather than a SQL login. If the SQL Server shows it is
configured for mixed security, it may be that it was changed after SQL
Server was started and the service needs to be restarted for this to
take affect. Another possibility is that connection string is malformed
so a trusted connection is being attempted.
--
Hope this helps.
Dan Guzman
SQL Server MVP
-----------------------
SQL FAQ links (courtesy Neil Pike):
http://www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
http://www.sqlserverfaq.com
http://www.mssqlserver.com/faq
-----------------------
> I do have it in Mixed mode.
> I am thinking that I will also make the SQL user (which only has read
> rights), make that same name a Windows user as well.
> > Perhaps the new SQL installation is configured for only Windows
> > authentication. You can change it to SQL Server and Windows from
the
> > Enterprise Manager server properties security tab.
> > --
> > Hope this helps.
> > Dan Guzman
> > SQL Server MVP
> > -----------------------
> > SQL FAQ links (courtesy Neil Pike):
> > http://www.ntfaq.com/Articles/Index.cfm?DepartmentID=800
> > http://www.sqlserverfaq.com
> > http://www.mssqlserver.com/faq
> > -----------------------
> > > I have a new 2kserver that I am running as our company webserver.
I
> > have
> > > SQL 2k on it as well. My website will be displaying info from
the
> > SQL
> > > database.
> > > When I try to view a page that connects to the SQL, it tells me
that
> > there
> > > is a log in failure and that the username and password are not
> > recognized.
> > > All the pages are .ASP pages.
> > > The line of code that it fails on is the line where I am making my
SQL
> > > query, and I am including the user name and password that I made
for
> > the
> > > SQL. But what it is telling me is the computername/inet_user
name is
> > what
> > > is not working.
> > > What is the deal?
> > > I am not sure if this is a IIS issue or a SQL issue.
> > > Please let me know.
> > > Thanks!
by