Sunday, March 25, 2012

Authentification problem with SQL Server 2000

Hello !
We use SQL Server 2000 (standard edition) under Windows 2003 Server.
Due to a hardware failure, we have fully set up the server after having
formating the hard drives. After having installed Windows Server 2003, we
have installed SQL Server 2000, then we have restored the databases from our
last night SQL backup.
Curiously : all our Windows XP users can connect to the server, but not our
Windows 2000 users! We have tried to create an ODBC data source with Windows
authentication : failure. With SQL authentication : failure.
But the same user, with his same userid, on another PC under Windows XP : no
problem.
And it was working well before the crash. Can anybody give us an explanation
? a solution ? a help ?
Thank you,
GilbertDo you have TCP/IP enabled on the SQL Server as an allowed connection type?
/*
Warren Brunk - MCITP,MCTS,MCDBA
www.techintsolutions.com
*/
"Gilbert Tordeur" <gilbert.tordeur@.jci.com> wrote in message
news:O56wq5lQIHA.4476@.TK2MSFTNGP06.phx.gbl...
> Hello !
> We use SQL Server 2000 (standard edition) under Windows 2003 Server.
> Due to a hardware failure, we have fully set up the server after having
> formating the hard drives. After having installed Windows Server 2003, we
> have installed SQL Server 2000, then we have restored the databases from
> our last night SQL backup.
> Curiously : all our Windows XP users can connect to the server, but not
> our Windows 2000 users! We have tried to create an ODBC data source with
> Windows authentication : failure. With SQL authentication : failure.
> But the same user, with his same userid, on another PC under Windows XP :
> no problem.
> And it was working well before the crash. Can anybody give us an
> explanation ? a solution ? a help ?
> Thank you,
> Gilbert
>|||Hi Warren,
Thank you for your answer. Could you tell us where to look at, to answer
your question ?
Gilbert
"Warren Brunk" <wbrunk@.techintsolutions.com> a crit dans le message de
news: eUKerPpQIHA.5980@.TK2MSFTNGP04.phx.gbl...
> Do you have TCP/IP enabled on the SQL Server as an allowed connection
> type?
> --
> /*
> Warren Brunk - MCITP,MCTS,MCDBA
> www.techintsolutions.com
> */
> "Gilbert Tordeur" <gilbert.tordeur@.jci.com> wrote in message
> news:O56wq5lQIHA.4476@.TK2MSFTNGP06.phx.gbl...
>|||http://technet.microsoft.com/en-us/...y/ms174212.aspx
You need to use the SQL Server configuration manager which has an option for
viewing which connections are allowed...
Its under your start menu programs in the same group as SQL Server...
/*
Warren Brunk - MCITP,MCTS,MCDBA
www.techintsolutions.com
*/
"Gilbert Tordeur" <gilbert.tordeur@.jci.com> wrote in message
news:uiXkOQvQIHA.2208@.TK2MSFTNGP06.phx.gbl...
> Hi Warren,
> Thank you for your answer. Could you tell us where to look at, to answer
> your question ?
> Gilbert
> "Warren Brunk" <wbrunk@.techintsolutions.com> a crit dans le message de
> news: eUKerPpQIHA.5980@.TK2MSFTNGP04.phx.gbl...
>|||Hi Warren,
Sorry to be a bit late, but : Thank you !
And a Happy New Year,
Gilbert
"Warren Brunk" <wbrunk@.techintsolutions.com> a crit dans le message de
news: OJDKPu5QIHA.5288@.TK2MSFTNGP04.phx.gbl...
> http://technet.microsoft.com/en-us/...y/ms174212.aspx
> You need to use the SQL Server configuration manager which has an option
> for viewing which connections are allowed...
> Its under your start menu programs in the same group as SQL Server...
> --
> /*
> Warren Brunk - MCITP,MCTS,MCDBA
> www.techintsolutions.com
> */
>
> "Gilbert Tordeur" <gilbert.tordeur@.jci.com> wrote in message
> news:uiXkOQvQIHA.2208@.TK2MSFTNGP06.phx.gbl...
>

No comments:

Post a Comment