server via Db-Library and TCP/IP without problem. However,
this same machine can ONLY connect to a SQL 2000 via DB-
Library using named pipes. If TCP/IP is used the
following messages is returned ......
SQL SERVER MESSAGE 18452, state1, severity 14:What is the SQL 2000 server's security model as compared to SQL 7? Maybe
one is listening for Windows authentication only, and another for mixed?
SQL 2000 SP 3a forces Win authentication if you don't pay attention.
You can run server network utility on the SQL servers from the SQL program
group and compare it to your SQL client network utility's protocols, but I
don't think that'll yield as much info as figuring out the security models.
Heck, you should even turn on auditing (SQL Server properties from
Enterprise Manager | Security) so you can see what is happening in the SQL
error log.
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"Julie" <anonymous@.discussions.microsoft.com> wrote in message
news:6d9001c3e67e$626cc870$a601280a@.phx.gbl...
quote:|||Both servers are running in a mixed mode and we use NT
> I have Windows 2000 client that can connect to a Sql 7
> server via Db-Library and TCP/IP without problem. However,
> this same machine can ONLY connect to a SQL 2000 via DB-
> Library using named pipes. If TCP/IP is used the
> following messages is returned ......
> SQL SERVER MESSAGE 18452, state1, severity 14:
>
authentication the majority of the time. 90% of our
clients are running Windows NT and we did not see this
problem until we started to introduce W2K machines.
quote:
>--Original Message--
>What is the SQL 2000 server's security model as compared
to SQL 7? Maybe
quote:
>one is listening for Windows authentication only, and
another for mixed?
quote:
>SQL 2000 SP 3a forces Win authentication if you don't pay
attention.
quote:
>You can run server network utility on the SQL servers
from the SQL program
quote:
>group and compare it to your SQL client network utility's
protocols, but I
quote:
>don't think that'll yield as much info as figuring out
the security models.
quote:
>Heck, you should even turn on auditing (SQL Server
properties from
quote:
>Enterprise Manager | Security) so you can see what is
happening in the SQL
quote:
>error log.
>--
> ****************************************
******************
*********
quote:
>Andy S.
>MCSE NT/2000, MCDBA SQL 7/2000
>andymcdba1@.NOMORESPAM.yahoo.com
>Please remove NOMORESPAM before replying.
>Always keep your antivirus and Microsoft software
>up to date with the latest definitions and product
updates.
quote:
>Be suspicious of every email attachment, I will never send
>or post anything other than the text of a http:// link nor
>post the link directly to a file for downloading.
>This posting is provided "as is" with no warranties
>and confers no rights.
> ****************************************
******************
*********
quote:
>"Julie" <anonymous@.discussions.microsoft.com> wrote in
message
quote:|||Hi Julie,
>news:6d9001c3e67e$626cc870$a601280a@.phx.gbl...
However,[QUOTE]
>
>.
>
To make Trusted Connections over TCP requires more effort than with Named
Pipes. The problem may lie with communication to the DC. Make a network
trace from the client when it fails. This will show a 3 way tcp handshake
with both SQL and the DC. Then work with the network team to isolation
issues with this DC. Or it may even be a problem with DNS.
You may also want to try using a utility called netdiag.exe This tool
will flush out common DNS and DC problems.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||I think I've run into the same problem in the past. Are your servers running
on NT4 and are you using trusted connections, i.e. NT authentication? I
could not get a W2K client to connect to an NT4 server using TCP/IP and
trusted connections with DB-Library. I'm pretty sure it worked OK with ODBC
and OLEDB.
I only had the problem with this combination, W2K on the client, NT4 on the
server and NT authentication using DB-Library and TCP/IP. When we upgraded
our servers to W2K the problem went away.
I've seen a few other people run into the same problem, but couldn't get MS
to acknowledge that this was a problem.
HTH,
Mike Kruchten
"Julie" <anonymous@.discussions.microsoft.com> wrote in message
news:6d9001c3e67e$626cc870$a601280a@.phx.gbl...
quote:|||Mike,
> I have Windows 2000 client that can connect to a Sql 7
> server via Db-Library and TCP/IP without problem. However,
> this same machine can ONLY connect to a SQL 2000 via DB-
> Library using named pipes. If TCP/IP is used the
> following messages is returned ......
> SQL SERVER MESSAGE 18452, state1, severity 14:
>
Thanks for the response, I thought I was going crazy.
We have the same situation here and ODBC does work fine.
Julie
>--Original Message--
>I think I've run into the same problem in the past. Are
your servers running
>on NT4 and are you using trusted connections, i.e. NT
authentication? I
>could not get a W2K client to connect to an NT4 server
using TCP/IP and
>trusted connections with DB-Library. I'm pretty sure it
worked OK with ODBC
>and OLEDB.
>I only had the problem with this combination, W2K on the
client, NT4 on the
>server and NT authentication using DB-Library and TCP/IP.
When we upgraded
>our servers to W2K the problem went away.
>I've seen a few other people run into the same problem,
but couldn't get MS
>to acknowledge that this was a problem.
>HTH,
>Mike Kruchten
>
>"Julie" <anonymous@.discussions.microsoft.com> wrote in
message
>news:6d9001c3e67e$626cc870$a601280a@.phx.gbl...
However,
>
>.
>
No comments:
Post a Comment