microsoft.public.sqlserver.server - Trusted connection problems

Author

Trusted connection problems

Steve Hickle

2002-10-05, 9:10 pm

According to SQL2K BOL (Administriering SQL
Server/Managing Security/Security Levels/Authentication
Modes):
"If a user attempts to connect to an instance of SQL
Server providing a blank login name, SQL Server uses
Windows Authentication. Additionally, if a user attempts
to connect to an instance of SQL Server configured for
Windows Authentication Mode by using a specific login, the
login is ignored and Windows Authentication is used."

This isn't working for me. I have my SQL Server 2000
configured for Windows Authentication. When I use isqlw
to try and establish a "SQL Server Authentication"
connection with a blank userid and password, I get the
message:

Msg 18452, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][SQL Server]Login
failed for user ''. Reason: Not associated with a trusted
SQL Server connection.

I should be connected with a trusted connection in the
context of the userid I'm logged onto my workstation with
(if I read the BOL correctly). Can someone explain why
this isn't working?

Thanks,

Steve

Vikrant V Dalwale [MS]

2002-10-05, 9:10 pm

Hello Steve,

The Books On Line is correct.

- Have logged in to the Workstation which is in the same domain ?

- I assume that, you have setup the Windows Authentication Mode correctly.
You can verify using the
SEM, right click on SQL Server Name and Select Properties and go to
Security Tab. There the radiao button on
"Windows Only" should be selected under the authentication.

- IMP: Make sure that your NT Login Account has "access this computer from
the network" rights.
This can be added in the security policy. Use the domain policy for
Windows2000 and NT4 PDCs and BDCs.
Use the local policy for NT4 member servers.

- Try using both Tcp/ip and Named pipes as default net-lib using the
client-network utility and see if changing it makes the diff.

- Verify actual Net-Lib in registry at
" HKLM\Software\Microsoft\MSSQLS
erver\Client\ConnectTo"

Thanks,

Vikrant Dalwale

Microsoft SQL Server Support Professional

This posting is provided "AS IS" with no warranties, and confers no rights.
Get secure ! For info, please visit http://www.microsoft.com/security.
Please reply to Newsgroups only.

--------------------
>Content-Class: urn:content-classes:message
>From: "Steve Hickle" <steve.hickle@druryinn.com>
>Sender: "Steve Hickle" <steve.hickle@druryinn.com>
>Subject: Trusted connection problems
>Date: Wed, 18 Sep 2002 15:40:14 -0700
>Lines: 30
>Message-ID: < 190901c25f64$5a994e40$9de62ecf
@tkmsftngxs01>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="iso-8859-1"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
>Thread-Index: AcJfZFqZOpnjqZjRRPq48DwQJinR+Q
==
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: tkmsftngxs01 207.46.230.157
>Path: cpmsftngxa07!tkmsftngxs01
>Xref: cpmsftngxa07 microsoft.public.sqlserver.server:3788
>X-Tomcat-NG: microsoft.public.sqlserver.server
>
>According to SQL2K BOL (Administriering SQL
>Server/Managing Security/Security Levels/Authentication
>Modes):
>"If a user attempts to connect to an instance of SQL
>Server providing a blank login name, SQL Server uses
>Windows Authentication. Additionally, if a user attempts
>to connect to an instance of SQL Server configured for
>Windows Authentication Mode by using a specific login, the
>login is ignored and Windows Authentication is used."
>
>This isn't working for me. I have my SQL Server 2000
>configured for Windows Authentication. When I use isqlw
>to try and establish a "SQL Server Authentication"
>connection with a blank userid and password, I get the
>message:
>
>Msg 18452, Level 16, State 1
>[Microsoft][ODBC SQL Server Driver][SQL Server]Login
>failed for user ''. Reason: Not associated with a trusted
>SQL Server connection.
>
>I should be connected with a trusted connection in the
>context of the userid I'm logged onto my workstation with
>(if I read the BOL correctly). Can someone explain why
>this isn't working?
>
>Thanks,
>
>Steve
>
>

Steve Hickle

2002-10-05, 9:11 pm

Vikrant, thanks for responding. I've checked the issues
you mentioned and everything seems to be configured
properly. The only one that I wasn't quite sure about was
the net-lib registry entry. Mine is DBNETLIB, regardless
of what protocol I say to use. I need to get this to work
with just TCP/IP enabled (client and server), if
possible. Here's the behavior I've been experiencing as I
did more testing:

If I use named pipes I can establish a trusted connection
when I specifiy SQL Server authentication in the
connection dialog of isqlw. This works when connecting to
a remote server configured for named pipes. It only works
for a connection to the local server if the "Enabled
shared memory protocol" check box is un-checked in the SQL
Server Client Network Utility.

If I disable named pipes and enable TCP/IP using both the
client and the server network utility, I can't establish a
trusted connection when I specifiy SQL Server
authentication in the connection dialog of isqlw. This is
true for both a remote server connection and a local
server connection.

Please advise on what to do next.

Thanks,

Steve
>-----Original Message-----
>
>
>Hello Steve,
>
>The Books On Line is correct.
>
>
>- Have logged in to the Workstation which is in the same
domain ?
>
>- I assume that, you have setup the Windows
Authentication Mode correctly.
>You can verify using the
> SEM, right click on SQL Server Name and Select
Properties and go to
>Security Tab. There the radiao button on
> "Windows Only" should be selected under the
authentication.
>
>- IMP: Make sure that your NT Login Account has "access
this computer from
>the network" rights.
> This can be added in the security policy. Use the
domain policy for
>Windows2000 and NT4 PDCs and BDCs.
> Use the local policy for NT4 member servers.
>
>- Try using both Tcp/ip and Named pipes as default net-
lib using the
>client-network utility and see if changing it makes the
diff.
>
>- Verify actual Net-Lib in registry at
>" HKLM\Software\Microsoft\MSSQLS
erver\Client\ConnectTo"
>
>
>
>Thanks,
>
>Vikrant Dalwale
>
>Microsoft SQL Server Support Professional
>
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>Get secure ! For info, please visit
http://www.microsoft.com/security.
>Please reply to Newsgroups only.
>
>--------------------
>>Content-Class: urn:content-classes:message
>>From: "Steve Hickle" <steve.hickle@druryinn.com>
>>Sender: "Steve Hickle" <steve.hickle@druryinn.com>
>>Subject: Trusted connection problems
>>Date: Wed, 18 Sep 2002 15:40:14 -0700
>>Lines: 30
>>Message-ID: < 190901c25f64$5a994e40$9de62ecf
@tkmsftngxs01>
>>MIME-Version: 1.0
>>Content-Type: text/plain;
>> charset="iso-8859-1"
>>Content-Transfer-Encoding: 7bit
>>X-Newsreader: Microsoft CDO for Windows 2000
>>X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
>>Thread-Index: AcJfZFqZOpnjqZjRRPq48DwQJinR+Q
==
>>Newsgroups: microsoft.public.sqlserver.server
>>NNTP-Posting-Host: tkmsftngxs01 207.46.230.157
>>Path: cpmsftngxa07!tkmsftngxs01
>>Xref: cpmsftngxa07 microsoft.public.sqlserver.server:3788
>>X-Tomcat-NG: microsoft.public.sqlserver.server
>>
>>According to SQL2K BOL (Administriering SQL
>>Server/Managing Security/Security Levels/Authentication
>>Modes):
>>"If a user attempts to connect to an instance of SQL
>>Server providing a blank login name, SQL Server uses
>>Windows Authentication. Additionally, if a user attempts
>>to connect to an instance of SQL Server configured for
>>Windows Authentication Mode by using a specific login,
the
>>login is ignored and Windows Authentication is used."
>>
>>This isn't working for me. I have my SQL Server 2000
>>configured for Windows Authentication. When I use isqlw
>>to try and establish a "SQL Server Authentication"
>>connection with a blank userid and password, I get the
>>message:
>>
>>Msg 18452, Level 16, State 1
>>[Microsoft][ODBC SQL Server Driver][SQL Server]Login
>>failed for user ''. Reason: Not associated with a
trusted
>>SQL Server connection.
>>
>>I should be connected with a trusted connection in the
>>context of the userid I'm logged onto my workstation
with
>>(if I read the BOL correctly). Can someone explain why
>>this isn't working?
>>
>>Thanks,
>>
>>Steve
>>
>>
>
>.
>

Vikrant V Dalwale [MS]

2002-10-05, 9:11 pm

Hello Steve,

DBNETLIB is the right value of the Reg Key
HKLM\Software\Microsoft\MSSQLS
erver\Client\ConnectTo

Now the fact that you are connecting thru Named Pipes and having problems
with TCP/IP,
tells us that SQL Server and the client are not listening to the same port
#. Make sure, that
properties of TCP/IP shows 1433 as default port# (thru client and server
net utility ) on server as well as on client .

Also, make sure that the default system DSN for the SQL Server does have
1433 for the TCP/IP protocol. ( thru client-configuration button ).

Let me know whats the MDAC version on SQL Server and the Client.

Thanks,

Vikrant Dalwale

Microsoft SQL Server Support Professional

This posting is provided "AS IS" with no warranties, and confers no rights.
Get secure ! For info, please visit http://www.microsoft.com/security.
Please reply to Newsgroups only.

--------------------
>Content-Class: urn:content-classes:message
>From: "Steve Hickle" <steve.hickle@druryinn.com>
>Sender: "Steve Hickle" <steve.hickle@druryinn.com>
>References: < 190901c25f64$5a994e40$9de62ecf
@tkmsftngxs01>
<1bOkWA4XCHA.1576@cpmsftngxa07>
>Subject: RE: Trusted connection problems
>Date: Thu, 19 Sep 2002 09:50:29 -0700
>Lines: 137
>Message-ID: < 2cb001c25ffc$a915f120$37ef2ecf
@TKMSFTNGXA13>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="iso-8859-1"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
>Thread-Index: AcJf/KkVI09Ck7UoRhed2ejy8e0axw==
>Newsgroups: microsoft.public.sqlserver.server
>Path: cpmsftngxa08
>Xref: cpmsftngxa08 microsoft.public.sqlserver.server:229967
>NNTP-Posting-Host: TKMSFTNGXA13 10.201.226.41
>X-Tomcat-NG: microsoft.public.sqlserver.server
>
>Vikrant, thanks for responding. I've checked the issues
>you mentioned and everything seems to be configured
>properly. The only one that I wasn't quite sure about was
>the net-lib registry entry. Mine is DBNETLIB, regardless
>of what protocol I say to use. I need to get this to work
>with just TCP/IP enabled (client and server), if
>possible. Here's the behavior I've been experiencing as I
>did more testing:
>
>If I use named pipes I can establish a trusted connection
>when I specifiy SQL Server authentication in the
>connection dialog of isqlw. This works when connecting to
>a remote server configured for named pipes. It only works
>for a connection to the local server if the "Enabled
>shared memory protocol" check box is un-checked in the SQL
>Server Client Network Utility.
>
>If I disable named pipes and enable TCP/IP using both the
>client and the server network utility, I can't establish a
>trusted connection when I specifiy SQL Server
>authentication in the connection dialog of isqlw. This is
>true for both a remote server connection and a local
>server connection.
>
>Please advise on what to do next.
>
>Thanks,
>
>Steve
>>-----Original Message-----
>>
>>
>>Hello Steve,
>>
>>The Books On Line is correct.
>>
>>
>>- Have logged in to the Workstation which is in the same
>domain ?
>>
>>- I assume that, you have setup the Windows
>Authentication Mode correctly.
>>You can verify using the
>> SEM, right click on SQL Server Name and Select
>Properties and go to
>>Security Tab. There the radiao button on
>> "Windows Only" should be selected under the
>authentication.
>>
>>- IMP: Make sure that your NT Login Account has "access
>this computer from
>>the network" rights.
>> This can be added in the security policy. Use the
>domain policy for
>>Windows2000 and NT4 PDCs and BDCs.
>> Use the local policy for NT4 member servers.
>>
>>- Try using both Tcp/ip and Named pipes as default net-
>lib using the
>>client-network utility and see if changing it makes the
>diff.
>>
>>- Verify actual Net-Lib in registry at
>>" HKLM\Software\Microsoft\MSSQLS
erver\Client\ConnectTo"
>>
>>
>>
>>Thanks,
>>
>>Vikrant Dalwale
>>
>>Microsoft SQL Server Support Professional
>>
>>This posting is provided "AS IS" with no warranties, and
>confers no rights.
>>Get secure ! For info, please visit
>http://www.microsoft.com/security.
>>Please reply to Newsgroups only.
>>
>>--------------------
>>>Content-Class: urn:content-classes:message
>>>From: "Steve Hickle" <steve.hickle@druryinn.com>
>>>Sender: "Steve Hickle" <steve.hickle@druryinn.com>
>>>Subject: Trusted connection problems
>>>Date: Wed, 18 Sep 2002 15:40:14 -0700
>>>Lines: 30
>>>Message-ID: < 190901c25f64$5a994e40$9de62ecf
@tkmsftngxs01>
>>>MIME-Version: 1.0
>>>Content-Type: text/plain;
>>> charset="iso-8859-1"
>>>Content-Transfer-Encoding: 7bit
>>>X-Newsreader: Microsoft CDO for Windows 2000
>>>X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
>>>Thread-Index: AcJfZFqZOpnjqZjRRPq48DwQJinR+Q
==
>>>Newsgroups: microsoft.public.sqlserver.server
>>>NNTP-Posting-Host: tkmsftngxs01 207.46.230.157
>>>Path: cpmsftngxa07!tkmsftngxs01
>>>Xref: cpmsftngxa07 microsoft.public.sqlserver.server:3788
>>>X-Tomcat-NG: microsoft.public.sqlserver.server
>>>
>>>According to SQL2K BOL (Administriering SQL
>>>Server/Managing Security/Security Levels/Authentication
>>>Modes):
>>>"If a user attempts to connect to an instance of SQL
>>>Server providing a blank login name, SQL Server uses
>>>Windows Authentication. Additionally, if a user attempts
>>>to connect to an instance of SQL Server configured for
>>>Windows Authentication Mode by using a specific login,
> the
>>>login is ignored and Windows Authentication is used."
>>>
>>>This isn't working for me. I have my SQL Server 2000
>>>configured for Windows Authentication. When I use isqlw
>>>to try and establish a "SQL Server Authentication"
>>>connection with a blank userid and password, I get the
>>>message:
>>>
>>>Msg 18452, Level 16, State 1
>>>[Microsoft][ODBC SQL Server Driver][SQL Server]Login
>>>failed for user ''. Reason: Not associated with a
> trusted
>>>SQL Server connection.
>>>
>>>I should be connected with a trusted connection in the
>>>context of the userid I'm logged onto my workstation
> with
>>>(if I read the BOL correctly). Can someone explain why
>>>this isn't working?
>>>
>>>Thanks,
>>>
>>>Steve
>>>
>>>
>>
>>.
>>
>

Steve Hickle

2002-10-05, 9:11 pm

Vikrant, thanks for responding.
The MDAC Component Checker reports:
The MDAC version that is closest to the version on youur
computer is '2.7 RTM (2.70.7713.4)'.

Both the client and the server TCP/IP socket are set to
1433. I they hadn't been set right, wouldn't that have
kept me from being able to establish a trusted connection
using Windows Authentication (which I can do)?

I'm not sure what you mean by the default DSN. If you
mean an alias setting for the server in the client
utility, that is also set to 1433. I

Please advise on what to do next.

Thanks,

Steve

>-----Original Message-----
>
>
>Hello Steve,
>
>DBNETLIB is the right value of the Reg Key
> HKLM\Software\Microsoft\MSSQLS
erver\Client\ConnectTo
>
>Now the fact that you are connecting thru Named Pipes and
having problems
>with TCP/IP,
>tells us that SQL Server and the client are not
listening to the same port
>#. Make sure, that
>properties of TCP/IP shows 1433 as default port# (thru
client and server
>net utility ) on server as well as on client .
>
>Also, make sure that the default system DSN for the SQL
Server does have
>1433 for the TCP/IP protocol. ( thru client-configuration
button ).
>
>Let me know whats the MDAC version on SQL Server and the
Client.
>
>Thanks,
>
>Vikrant Dalwale
>
>Microsoft SQL Server Support Professional
>
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>Get secure ! For info, please visit
http://www.microsoft.com/security.
>Please reply to Newsgroups only.
>
>--------------------
>>Content-Class: urn:content-classes:message
>>From: "Steve Hickle" <steve.hickle@druryinn.com>
>>Sender: "Steve Hickle" <steve.hickle@druryinn.com>
>>References: <190901c25f64$5a994e40
$9de62ecf@tkmsftngxs01>
><1bOkWA4XCHA.1576@cpmsftngxa07>
>>Subject: RE: Trusted connection problems
>>Date: Thu, 19 Sep 2002 09:50:29 -0700
>>Lines: 137
>>Message-ID: < 2cb001c25ffc$a915f120$37ef2ecf
@TKMSFTNGXA13>
>>MIME-Version: 1.0
>>Content-Type: text/plain;
>> charset="iso-8859-1"
>>Content-Transfer-Encoding: 7bit
>>X-Newsreader: Microsoft CDO for Windows 2000
>>X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
>>Thread-Index: AcJf/KkVI09Ck7UoRhed2ejy8e0axw==
>>Newsgroups: microsoft.public.sqlserver.server
>>Path: cpmsftngxa08
>>Xref: cpmsftngxa08
microsoft.public.sqlserver. server:229967[colo
r=green]
>>NNTP-Posting-Host: TKMSFTNGXA13 10.201.226.41
>>X-Tomcat-NG: microsoft.public.sqlserver.server
>>
>>Vikrant, thanks for responding. I've checked the issues
>>you mentioned and everything seems to be configured
>>properly. The only one that I wasn't quite sure about[/color]
was
>>the net-lib registry entry. Mine is DBNETLIB,
regardless
>>of what protocol I say to use. I need to get this to
work
>>with just TCP/IP enabled (client and server), if
>>possible. Here's the behavior I've been experiencing as
I
>>did more testing:
>>
>>If I use named pipes I can establish a trusted
connection
>>when I specifiy SQL Server authentication in the
>>connection dialog of isqlw. This works when connecting
to
>>a remote server configured for named pipes. It only
works

>>for a connection to the local server if the "Enabled
>>shared memory protocol" check box is un-checked in the
SQL
>>Server Client Network Utility.
>>
>>If I disable named pipes and enable TCP/IP using both
the
>>client and the server network utility, I can't establish
a
>>trusted connection when I specifiy SQL Server
>>authentication in the connection dialog of isqlw. This
is
>>true for both a remote server connection and a local
>>server connection.
>>
>>Please advise on what to do next.
>>
>>Thanks,
>>
>>Steve
>>>-----Original Message-----
>>>
>>>
>>>Hello Steve,
>>>
>>>The Books On Line is correct.
>>>
>>>
>>>- Have logged in to the Workstation which is in the
same
>>domain ?
>>>
>>>- I assume that, you have setup the Windows
>>Authentication Mode correctly.
>>>You can verify using the
>>> SEM, right click on SQL Server Name and Select
>>Properties and go to
>>>Security Tab. There the radiao button on
>>> "Windows Only" should be selected under the
>>authentication.
>>>
>>>- IMP: Make sure that your NT Login Account
has " access
>>this computer from
>>>the network" rights.
>>> This can be added in the security policy. Use the
>>domain policy for
>>>Windows2000 and NT4 PDCs and BDCs.
>>> Use the local policy for NT4 member servers.
>>>
>>>- Try using both Tcp/ip and Named pipes as default net-
>>lib using the
>>>client-network utility and see if changing it makes the
>>diff.
>>>
>>>- Verify actual Net-Lib in registry at
>>>" HKLM\Software\Microsoft\MSSQLS
erver\Client\ConnectTo"
>>>
>>>
>>>
>>>Thanks,
>>>
>>>Vikrant Dalwale
>>>
>>>Microsoft SQL Server Support Professional
>>>
>>>This posting is provided "AS IS" with no warranties,
and
>>confers no rights.
>>>Get secure ! For info, please visit
>>http://www.microsoft.com/security.
>>>Please reply to Newsgroups only.
>>>
>>>--------------------
>>>>Content-Class: urn:content-classes:message
>>>>From: "Steve Hickle" <steve.hickle@druryinn.com>
>>>>Sender: "Steve Hickle" <steve.hickle@druryinn.com>
>>>>Subject: Trusted connection problems
>>>>Date: Wed, 18 Sep 2002 15:40:14 -0700
>>>>Lines: 30
>>>>Message-ID: <190901c25f64$5a994e40
$9de62ecf@tkmsftngxs01> [colo
r=darkred]
>>>>MIME-Version: 1.0
>>>>Content-Type: text/plain;
>>>> charset="iso-8859-1"
>>>>Content-Transfer-Encoding: 7bit
>>>>X-Newsreader: Microsoft CDO for Windows 2000
>>>>X-MimeOLE: Produced By Microsoft MimeOLE[/color]
V5.50.4522. 1200[
color=darkred]
>>>>Thread-Index: AcJfZFqZOpnjqZjRRPq48DwQJinR+Q
==
>>>>Newsgroups: microsoft.public.sqlserver.server
>>>>NNTP-Posting-Host: tkmsftngxs01 207.46.230.157
>>>>Path: cpmsftngxa07!tkmsftngxs01
>>>>Xref: cpmsftngxa07[/color]
microsoft.public.sqlserver. server:3788
>>>>X-Tomcat-NG: microsoft.public.sqlserver.server
>>>>
>>>>According to SQL2K BOL (Administriering SQL
>>>>Server/Managing Security/Security
Levels/ Authentication[col
or=green]
>>>>Modes):
>>>>"If a user attempts to connect to an instance of SQL
>>>>Server providing a blank login name, SQL Server uses
>>>>Windows Authentication. Additionally, if a user[/color]
attempts
>>>>to connect to an instance of SQL Server configured for
>>>>Windows Authentication Mode by using a specific login,
>>the
>>>>login is ignored and Windows Authentication is used."
>>>>
>>>>This isn't working for me. I have my SQL Server 2000
>>>>configured for Windows Authentication. When I use
isqlw

>>>>to try and establish a "SQL Server Authentication"
>>>>connection with a blank userid and password, I get the
>>>>message:
>>>>
>>>>Msg 18452, Level 16, State 1
>>>>[Microsoft][ODBC SQL Server Driver][SQL Server]Login
>>>>failed for user ''. Reason: Not associated with a
>>trusted
>>>>SQL Server connection.
>>>>
>>>>I should be connected with a trusted connection in the
>>>>context of the userid I'm logged onto my workstation
>>with
>>>>(if I read the BOL correctly). Can someone explain
why[c
olor=darkred]
>>>>this isn't working?
>>>>
>>>>Thanks,
>>>>
>>>>Steve
>>>>
>>>>
>>>
>>>.
>>>
>>
>
>.
>[/color]

Vikrant V Dalwale [MS]

2002-10-05, 9:12 pm

Hello Steve,

After further research, I have found that there is a BUG with SQL Server
when passing the Blank UserID and Pswd
when using only TCP/IP as Net-Lib.

I was just wondering why you need to have Only Tcp/Ip enabled and Named
Pipes Disabled ? If you have to work with TCP/IP Protocol,
both Named Pipes and TCP/IP network Libs can be used with TCP/IP protocol.
Net-Libs are not actual protocols they are
just means thru which SQL Server exchanges Network Packets. There is a
ref in Book Online that
"Named Pipes support is required on Microsoft Windows NT® and Microsoft
Windows® 2000 installations of SQL Server.".

At this point I would suggesst to enable both Named Pipes and TCP/IP
Net-Libs for Client-Server Communication.

Thanks,

Vikrant Dalwale

Microsoft SQL Server Support Professional

This posting is provided "AS IS" with no warranties, and confers no rights.
Get secure ! For info, please visit http://www.microsoft.com/security.
Please reply to Newsgroups only.

--------------------
>Content-Class: urn:content-classes:message
>From: "Steve Hickle" <steve.hickle@druryinn.com>
>Sender: "Steve Hickle" <steve.hickle@druryinn.com>
>References: < 190901c25f64$5a994e40$9de62ecf
@tkmsftngxs01>
<1bOkWA4XCHA.1576@cpmsftngxa07>
< 2cb001c25ffc$a915f120$37ef2ecf
@TKMSFTNGXA13>
<o3I15UFYCHA.2304@cpmsftngxa07>
>Subject: RE: Trusted connection problems
>Date: Fri, 20 Sep 2002 04:18:36 -0700
>Lines: 245
>Message-ID: < 386601c26097$76ae5560$36ef2ecf
@tkmsftngxa12>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="iso-8859-1"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
>Thread-Index: AcJgl3ap/qQUdEVOR2KfnDYh/lWirA==
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: TKMSFTNGXA12 10.201.226.40
>Path: cpmsftngxa07!tkmsftngxs02!cpms
ftngxa08
>Xref: cpmsftngxa07 microsoft.public.sqlserver.server:4118
>X-Tomcat-NG: microsoft.public.sqlserver.server
>
>Vikrant, thanks for responding.
>The MDAC Component Checker reports:
>The MDAC version that is closest to the version on youur
>computer is '2.7 RTM (2.70.7713.4)'.
>
>Both the client and the server TCP/IP socket are set to
>1433. I they hadn't been set right, wouldn't that have
>kept me from being able to establish a trusted connection
>using Windows Authentication (which I can do)?
>
>I'm not sure what you mean by the default DSN. If you
>mean an alias setting for the server in the client
>utility, that is also set to 1433. I
>
>Please advise on what to do next.
>
>Thanks,
>
>Steve
>
>>-----Original Message-----
>>
>>
>>Hello Steve,
>>
>>DBNETLIB is the right value of the Reg Key
>> HKLM\Software\Microsoft\MSSQLS
erver\Client\ConnectTo
>>
>>Now the fact that you are connecting thru Named Pipes and
>having problems
>>with TCP/IP,
>>tells us that SQL Server and the client are not
>listening to the same port
>>#. Make sure, that
>>properties of TCP/IP shows 1433 as default port# (thru
>client and server
>>net utility ) on server as well as on client .
>>
>>Also, make sure that the default system DSN for the SQL
>Server does have
>>1433 for the TCP/IP protocol. ( thru client-configuration
>button ).
>>
>>Let me know whats the MDAC version on SQL Server and the
>Client.
>>
>>Thanks,
>>
>>Vikrant Dalwale
>>
>>Microsoft SQL Server Support Professional
>>
>>This posting is provided "AS IS" with no warranties, and
>confers no rights.
>>Get secure ! For info, please visit
>http://www.microsoft.com/security.
>>Please reply to Newsgroups only.
>>
>>--------------------
>>>Content-Class: urn:content-classes:message
>>>From: "Steve Hickle" <steve.hickle@druryinn.com>
>>>Sender: "Steve Hickle" <steve.hickle@druryinn.com>
>>>References: <190901c25f64$5a994e40
>$9de62ecf@tkmsftngxs01>
>><1bOkWA4XCHA.1576@cpmsftngxa07>
>>>Subject: RE: Trusted connection problems
>>>Date: Thu, 19 Sep 2002 09:50:29 -0700
>>>Lines: 137
>>>Message-ID: < 2cb001c25ffc$a915f120$37ef2ecf
@TKMSFTNGXA13>
>>>MIME-Version: 1.0
>>>Content-Type: text/plain;
>>> charset="iso-8859-1"
>>>Content-Transfer-Encoding: 7bit
>>>X-Newsreader: Microsoft CDO for Windows 2000
>>>X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
>>>Thread-Index: AcJf/KkVI09Ck7UoRhed2ejy8e0axw==
>>>Newsgroups: microsoft.public.sqlserver.server
>>>Path: cpmsftngxa08
>>>Xref: cpmsftngxa08
>microsoft.public.sqlserver. server:229967[col
or=darkred]
>>>NNTP-Posting-Host: TKMSFTNGXA13 10.201.226.41
>>>X-Tomcat-NG: microsoft.public.sqlserver.server
>>>
>>>Vikrant, thanks for responding. I've checked the issues
>>>you mentioned and everything seems to be configured
>>>properly. The only one that I wasn't quite sure about
> was
>>>the net-lib registry entry. Mine is DBNETLIB,
> regardless
>>>of what protocol I say to use. I need to get this to
> work
>>>with just TCP/IP enabled (client and server), if
>>>possible. Here's the behavior I've been experiencing as
>I
>>>did more testing:
>>>
>>>If I use named pipes I can establish a trusted
> connection
>>>when I specifiy SQL Server authentication in the
>>>connection dialog of isqlw. This works when connecting
> to

>>>a remote server configured for named pipes. It only
> works
>>>for a connection to the local server if the "Enabled
>>>shared memory protocol" check box is un-checked in the
> SQL
>>>Server Client Network Utility.
>>>
>>>If I disable named pipes and enable TCP/IP using both
> the
>>>client and the server network utility, I can't establish
>a
>>>trusted connection when I specifiy SQL Server
>>>authentication in the connection dialog of isqlw. This
> is

>>>true for both a remote server connection and a local
>>>server connection.
>>>
>>>Please advise on what to do next.
>>>
>>>Thanks,
>>>
>>>Steve
>>>>-----Original Message-----
>>>>
>>>>
>>>>Hello Steve,
>>>>
>>>>The Books On Line is correct.
>>>>
>>>>
>>>>- Have logged in to the Workstation which is in the
> same
>>>domain ?
>>>>
>>>>- I assume that, you have setup the Windows
>>>Authentication Mode correctly.
>>>>You can verify using the
>>>> SEM, right click on SQL Server Name and Select
>>>Properties and go to
>>>>Security Tab. There the radiao button on
>>>> "Windows Only" should be selected under the
>>>authentication.
>>>>
>>>>- IMP: Make sure that your NT Login Account
>has " access
>>>this computer from
>>>>the network" rights.
>>>> This can be added in the security policy. Use the
>>>domain policy for
>>>>Windows2000 and NT4 PDCs and BDCs.
>>>> Use the local policy for NT4 member servers.
>>>>
>>>>- Try using both Tcp/ip and Named pipes as default net-
>>>lib using the
>>>>client-network utility and see if changing it makes the
>>>diff.
>>>>
>>>>- Verify actual Net-Lib in registry at
>>>>" HKLM\Software\Microsoft\MSSQLS
erver\Client\ConnectTo"
>>>>
>>>>
>>>>
>>>>Thanks,
>>>>
>>>>Vikrant Dalwale
>>>>
>>>>Microsoft SQL Server Support Professional
>>>>
>>>>This posting is provided "AS IS" with no warranties,
> and
>>>confers no rights.
>>>>Get secure ! For info, please visit
>>>http://www.microsoft.com/security.
>>>>Please reply to Newsgroups only.
>>>>
>>>>--------------------
>>>>>Content-Class: urn:content-classes:message
>>>>>From: "Steve Hickle" <steve.hickle@druryinn.com>
>>>>>Sender: "Steve Hickle" <steve.hickle@druryinn.com>
>>>>>Subject: Trusted connection problems
>>>>>Date: Wed, 18 Sep 2002 15:40:14 -0700
>>>>>Lines: 30
>>>>>Message-ID: <190901c25f64$5a994e40
>$9de62ecf@tkmsftngxs01>
>>>>>MIME-Version: 1.0
>>>>>Content-Type: text/plain;
>>>>> charset="iso-8859-1"
>>>>>Content-Transfer-Encoding: 7bit
>>>>>X-Newsreader: Microsoft CDO for Windows 2000
>>>>>X-MimeOLE: Produced By Microsoft MimeOLE
>V5.50.4522. 1200
>>>>>Thread-Index: AcJfZFqZOpnjqZjRRPq48DwQJinR+Q
==
>>>>>Newsgroups: microsoft.public.sqlserver.server
>>>>>NNTP-Posting-Host: tkmsftngxs01 207.46.230.157
>>>>>Path: cpmsftngxa07!tkmsftngxs01
>>>>>Xref: cpmsftngxa07
>microsoft.public.sqlserver. server:3788[color
=darkred]
>>>>>X-Tomcat-NG: microsoft.public.sqlserver.server
>>>>>
>>>>>According to SQL2K BOL (Administriering SQL
>>>>>Server/Managing Security/Security[/color]
>Levels/ Authentication[co
lor=darkred]
>>>>>Modes):
>>>>>"If a user attempts to connect to an instance of SQL
>>>>>Server providing a blank login name, SQL Server uses
>>>>>Windows Authentication. Additionally, if a user[/color]
> attempts
>>>>>to connect to an instance of SQL Server configured for
>>>>>Windows Authentication Mode by using a specific login,
>>>the
>>>>>login is ignored and Windows Authentication is used."
>>>>>
>>>>>This isn't working for me. I have my SQL Server 2000
>>>>>configured for Windows Authentication. When I use
> isqlw
>>>>>to try and establish a "SQL Server Authentication"
>>>>>connection with a blank userid and password, I get the
>>>>>message:
>>>>>
>>>>>Msg 18452, Level 16, State 1
>>>>>[Microsoft][ODBC SQL Server Driver][SQL Server]Login
>>>>>failed for user ''. Reason: Not associated with a
>>>trusted
>>>>>SQL Server connection.
>>>>>
>>>>>I should be connected with a trusted connection in the
>>>>>context of the userid I'm logged onto my workstation
>>>with
>>>>>(if I read the BOL correctly). Can someone explain
> why
>>>>>this isn't working?
>>>>>
>>>>>Thanks,
>>>>>
>>>>>Steve
>>>>>
>>>>>
>>>>
>>>>.
>>>>
>>>
>>
>>.
>>
>[/color]

Steve Hickle

2002-10-05, 9:12 pm

Vikrant, thanks for responding.

Is there any estimate on when this bug is going to be=20
fixed? How can I track that and find out when it is? We=20
have 3rd party applications that don't support=20
establishing trusted connections. If what I'm trying to=20
do works, I can work around that issue.

BOL in the Networking and Performance sections states:
"In general, sockets are preferred in a slow LAN, WAN, or=20
dial-up network, whereas named pipes can be a better=20
choice when network speed is not the issue, as it offers=20
more functionality, ease of use, and configuration=20
options."

We have 100+ remote sites connected via frame relay that=20
we need to connect to. Also, we don't have named pipes=20
enabled on most of our existing workstations.

I appreciate your looking into this, and anything you can=20
tell me about when a fix will be available would be=20
greatly appreciated.

Thanks,

Steve
>-----Original Message-----
>
>Hello Steve,
>
>After further research, I have found that there is a BUG=20
with SQL Server=20
>when passing the Blank UserID and Pswd
>when using only TCP/IP as Net-Lib.
>
>I was just wondering why you need to have Only Tcp/Ip=20
enabled and Named=20
>Pipes Disabled ? If you have to work with TCP/IP=20
Protocol,
>both Named Pipes and TCP/IP network Libs can be used with=20
TCP/IP protocol. =20
>Net-Libs are not actual protocols they are
>just means thru which SQL Server exchanges Network=20
Packets. There is a=20
>ref in Book Online that=20
>"Named Pipes support is required on Microsoft Windows NT=AE=20
and Microsoft=20
>Windows=AE 2000 installations of SQL Server.".
>
>At this point I would suggesst to enable both Named Pipes=20
and TCP/IP=20
>Net-Libs for Client-Server Communication.
>
>Thanks,
>
>Vikrant Dalwale=20
>
>Microsoft SQL Server Support Professional
>
>This posting is provided "AS IS" with no warranties, and=20
confers no rights.=20
>Get secure ! For info, please visit=20
http://www.microsoft.com/security.
>Please reply to Newsgroups only.
>
>--------------------
>>Content-Class: urn:content-classes:message
>>From: "Steve Hickle" <steve.hickle@druryinn.com>
>>Sender: "Steve Hickle" <steve.hickle@druryinn.com>
>>References: <190901c25f64$5a994e40
$9de62ecf@tkmsftngxs01>=20
><1bOkWA4XCHA.1576@cpmsftngxa07>=20
>< 2cb001c25ffc$a915f120$37ef2ecf
@TKMSFTNGXA13>=20
><o3I15UFYCHA.2304@cpmsftngxa07>
>>Subject: RE: Trusted connection problems
>>Date: Fri, 20 Sep 2002 04:18:36 -0700
>>Lines: 245
>>Message-ID: < 386601c26097$76ae5560$36ef2ecf
@tkmsftngxa12>
>>MIME-Version: 1.0
>>Content-Type: text/plain;
>> charset=3D"iso-8859-1"
>>Content-Transfer-Encoding: 7bit
>>X-Newsreader: Microsoft CDO for Windows 2000
>>X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
>>Thread-Index: AcJgl3ap/qQUdEVOR2KfnDYh/lWirA=3D=3D
>>Newsgroups: microsoft.public.sqlserver.server
>>NNTP-Posting-Host: TKMSFTNGXA12 10.201.226.40
>>Path: cpmsftngxa07!tkmsftngxs02!cpms
ftngxa08
>>Xref: cpmsftngxa07 microsoft.public.sqlserver.server:4118
>>X-Tomcat-NG: microsoft.public.sqlserver.server
>>
>>Vikrant, thanks for responding.
>>The MDAC Component Checker reports:
>>The MDAC version that is closest to the version on youur=20
>>computer is '2.7 RTM (2.70.7713.4)'.
>>
>>Both the client and the server TCP/IP socket are set to=20
>>1433. I they hadn't been set right, wouldn't that have=20
>>kept me from being able to establish a trusted=20
connection=20[colo
r=green]
>>using Windows Authentication (which I can do)?
>>
>>I'm not sure what you mean by the default DSN. If you=20
>>mean an alias setting for the server in the client=20
>>utility, that is also set to 1433. I
>>
>>Please advise on what to do next.
>>
>>Thanks,
>>
>>Steve
>>
>>>-----Original Message-----
>>>
>>>
>>>Hello Steve,
>>>
>>>DBNETLIB is the right value of the Reg Key=20
>>> HKLM\Software\Microsoft\MSSQLS
erver\Client\ConnectTo
>>>
>>>Now the fact that you are connecting thru Named Pipes=20[/color]
and=20
>>having problems=20
>>>with TCP/IP,
>>>tells us that SQL Server and the client are not=20
>>listening to the same port=20
>>>#. Make sure, that
>>>properties of TCP/IP shows 1433 as default port# (thru=20
>>client and server=20
>>>net utility ) on server as well as on client . =20
>>>
>>>Also, make sure that the default system DSN for the SQL=20
>>Server does have=20
>>>1433 for the TCP/IP protocol. ( thru client-
configuration=20[c
olor=green]
>>button ).
>>>
>>>Let me know whats the MDAC version on SQL Server and=20[/color]
the=20
>>Client.=20
>>>
>>>Thanks,
>>>
>>>Vikrant Dalwale=20
>>>
>>>Microsoft SQL Server Support Professional
>>>
>>>This posting is provided "AS IS" with no warranties,=20
and=20
>>confers no rights.=20
>>>Get secure ! For info, please visit=20
>>http://www.microsoft.com/security.
>>>Please reply to Newsgroups only.
>>>
>>>--------------------
>>>>Content-Class: urn:content-classes:message
>>>>From: "Steve Hickle" <steve.hickle@druryinn.com>
>>>>Sender: "Steve Hickle" <steve.hickle@druryinn.com>
>>>>References: <190901c25f64$5a994e40
>>$9de62ecf@tkmsftngxs01>=20
>>><1bOkWA4XCHA.1576@cpmsftngxa07>
>>>>Subject: RE: Trusted connection problems
>>>>Date: Thu, 19 Sep 2002 09:50:29 -0700
>>>>Lines: 137
>>>>Message-ID: <2cb001c25ffc$a915f120
$37ef2ecf@TKMSFTNGXA13> [colo
r=darkred]
>>>>MIME-Version: 1.0
>>>>Content-Type: text/plain;
>>>> charset=3D"iso-8859-1"
>>>>Content-Transfer-Encoding: 7bit
>>>>X-Newsreader: Microsoft CDO for Windows 2000
>>>>X-MimeOLE: Produced By Microsoft MimeOLE=20[/color]
V5.50.4910. 0300[
color=darkred]
>>>>Thread-Index: AcJf/ KkVI09Ck7UoRhed2ejy8e0axw=3D=3
D
>>>>Newsgroups: microsoft.public.sqlserver.server
>>>>Path: cpmsftngxa08
>>>>Xref: cpmsftngxa08=20
>>microsoft.public.sqlserver.server:229967
>>>>NNTP-Posting-Host: TKMSFTNGXA13 10.201.226.41
>>>>X-Tomcat-NG: microsoft.public.sqlserver.server
>>>>
>>>>Vikrant, thanks for responding. I've checked the=20[/color]
issues=20
>>>>you mentioned and everything seems to be configured=20
>>>>properly. The only one that I wasn't quite sure about=20
>>was=20
>>>>the net-lib registry entry. Mine is DBNETLIB,=20
>>regardless=20
>>>>of what protocol I say to use. I need to get this to=20
>>work=20
>>>>with just TCP/IP enabled (client and server), if=20
>>>>possible. Here's the behavior I've been experiencing=20
as=20

>>I=20
>>>>did more testing:
>>>>
>>>>If I use named pipes I can establish a trusted=20
>>connection=20
>>>>when I specifiy SQL Server authentication in the=20
>>>>connection dialog of isqlw. This works when=20
connecting=20[colo
r=green]
>>to=20
>>>>a remote server configured for named pipes. It only=20
>>works=20
>>>>for a connection to the local server if the "Enabled=20
>>>>shared memory protocol" check box is un-checked in the=20
>>SQL=20
>>>>Server Client Network Utility.
>>>>
>>>>If I disable named pipes and enable TCP/IP using both=20
>>the=20
>>>>client and the server network utility, I can't=20[/color]
establish=20[color
=green]
>>a=20
>>>>trusted connection when I specifiy SQL Server=20
>>>>authentication in the connection dialog of isqlw. =20[/color]
This=20
>>is=20
>>>>true for both a remote server connection and a local=20
>>>>server connection.
>>>>
>>>>Please advise on what to do next.
>>>>
>>>>Thanks,
>>>>
>>>>Steve
>>>>>-----Original Message-----
>>>>>
>>>>>
>>>>>Hello Steve,
>>>>>
>>>>>The Books On Line is correct.=20
>>>>>
>>>>>
>>>>>- Have logged in to the Workstation which is in the=20
>>same=20
>>>>domain ?=20
>>>>>
>>>>>- I assume that, you have setup the Windows=20
>>>>Authentication Mode correctly.=20
>>>>>You can verify using the
>>>>> SEM, right click on SQL Server Name and Select=20
>>>>Properties and go to=20
>>>>>Security Tab. There the radiao button on
>>>>> "Windows Only" should be selected under the=20
>>>>authentication.=20
>>>>>
>>>>>- IMP: Make sure that your NT Login Account=20
>>has "access=20
>>>>this computer from=20
>>>>>the network" rights.=20
>>>>> This can be added in the security policy. Use the=20
>>>>domain policy for=20
>>>>>Windows2000 and NT4 PDCs and BDCs.=20
>>>>> Use the local policy for NT4 member servers.
>>>>>
>>>>>- Try using both Tcp/ip and Named pipes as default=20
net- [colo
r=darkred]
>>>>lib using the=20
>>>>>client-network utility and see if changing it makes=20[/color]
the=20
>>>>diff.
>>>>>
>>>>>- Verify actual Net-Lib in registry at =20
>>>>>" HKLM\Software\Microsoft\MSSQLS
erver\Client\ConnectTo"
>>>>>
>>>>>
>>>>>
>>>>>Thanks,
>>>>>
>>>>>Vikrant Dalwale=20
>>>>>
>>>>>Microsoft SQL Server Support Professional
>>>>>
>>>>>This posting is provided "AS IS" with no warranties,=20
>>and=20
>>>>confers no rights.=20
>>>>>Get secure ! For info, please visit=20
>>>>http://www.microsoft.com/security.
>>>>>Please reply to Newsgroups only.
>>>>>
>>>>>--------------------
>>>>>>Content-Class: urn:content-classes:message
>>>>>>From: "Steve Hickle" <steve.hickle@druryinn.com>
>>>>>>Sender: "Steve Hickle" <steve.hickle@druryinn.com>
>>>>>>Subject: Trusted connection problems
>>>>>>Date: Wed, 18 Sep 2002 15:40:14 -0700
>>>>>>Lines: 30
>>>>>>Message-ID: <190901c25f64$5a994e40
>>$9de62ecf@tkmsftngxs01>
>>>>>>MIME-Version: 1.0
>>>>>>Content-Type: text/plain;
>>>>>> charset=3D"iso-8859-1"
>>>>>>Content-Transfer-Encoding: 7bit
>>>>>>X-Newsreader: Microsoft CDO for Windows 2000
>>>>>>X-MimeOLE: Produced By Microsoft MimeOLE=20
>>V5.50.4522.1200
>>>>>>Thread-Index: AcJfZFqZOpnjqZjRRPq48DwQJinR+Q
=3D=3D
>>>>>>Newsgroups: microsoft.public.sqlserver.server
>>>>>>NNTP-Posting-Host: tkmsftngxs01 207.46.230.157
>>>>>>Path: cpmsftngxa07!tkmsftngxs01
>>>>>>Xref: cpmsftngxa07=20
>>microsoft.public.sqlserver.server:3788
>>>>>>X-Tomcat-NG: microsoft.public.sqlserver.server
>>>>>>
>>>>>>According to SQL2K BOL (Administriering SQL=20
>>>>>>Server/Managing Security/Security=20
>>Levels/ Authentication=20
>>>>>>Modes):
>>>>>>"If a user attempts to connect to an instance of SQL=20
>>>>>>Server providing a blank login name, SQL Server uses=20
>>>>>>Windows Authentication. Additionally, if a user=20
>>attempts=20
>>>>>>to connect to an instance of SQL Server configured=20
for=20
>>>>>>Windows Authentication Mode by using a specific=20
login,=20
>>>>the=20
>>>>>>login is ignored and Windows Authentication is used."
>>>>>>
>>>>>>This isn't working for me. I have my SQL Server=20
2000=20
>>>>>>configured for Windows Authentication. When I use=20
>>isqlw=20
>>>>>>to try and establish a "SQL Server Authentication"=20
>>>>>>connection with a blank userid and password, I get=20
the=20
>>>>>>message:
>>>>>>
>>>>>>Msg 18452, Level 16, State 1
>>>>>>[Microsoft][ODBC SQL Server Driver][SQL Server]Login=20
>>>>>>failed for user ''. Reason: Not associated with a=20
>>>>trusted=20
>>>>>>SQL Server connection.
>>>>>>
>>>>>>I should be connected with a trusted connection in=20
the=20
>>>>>>context of the userid I'm logged onto my workstation=20
>>>>with=20
>>>>>>(if I read the BOL correctly). Can someone explain=20
>>why=20
>>>>>>this isn't working?
>>>>>>
>>>>>>Thanks,
>>>>>>
>>>>>>Steve
>>>>>>
>>>>>>
>>>>>
>>>>>.
>>>>>
>>>>
>>>
>>>.
>>>
>>
>
>.
>

Steve Hickle

2002-10-05, 9:12 pm

Vikrant, thanks for responding (again). I thought I had=20
posted a reply but it hasn't shown up so I'll do it again.

Is there an estimate on when this bug is going to be fixed=20
and how can I track when Microsoft has a fix for this bug?

We use a 3rd party application that doesn't establish=20
trusted connections when it connects. If I can get this=20
feature to work, I can get around that issue.

The main reason I want to use TCP/IP instead of named=20
pipes is performance. We have 100+ sites connected via=20
frame relay. =20

In the Network Performance section of BOL it states:
"In general, sockets are preferred in a slow LAN, WAN, or=20
dial-up network, whereas named pipes can be a better=20
choice when network speed is not the issue, as it offers=20
more functionality, ease of use, and configuration=20
options."

Most of the workstations we already have deployed do not=20
have named pipes enabled as a client network library. I=20
don't want to have to reconfigure every workstation in our=20
network to get this to work.

Thanks for your help on this issue. Please let me know if=20
there is anything else I can do to get this to work=20
without having named pipes on the client. I don't mind=20
having it on the server.

Thanks,

Steve

>-----Original Message-----
>
>Hello Steve,
>
>After further research, I have found that there is a BUG=20
with SQL Server=20
>when passing the Blank UserID and Pswd
>when using only TCP/IP as Net-Lib.
>
>I was just wondering why you need to have Only Tcp/Ip=20
enabled and Named=20
>Pipes Disabled ? If you have to work with TCP/IP=20
Protocol,
>both Named Pipes and TCP/IP network Libs can be used with=20
TCP/IP protocol. =20
>Net-Libs are not actual protocols they are
>just means thru which SQL Server exchanges Network=20
Packets. There is a=20
>ref in Book Online that=20
>"Named Pipes support is required on Microsoft Windows NT=AE=20
and Microsoft=20
>Windows=AE 2000 installations of SQL Server.".
>
>At this point I would suggesst to enable both Named Pipes=20
and TCP/IP=20
>Net-Libs for Client-Server Communication.
>
>Thanks,
>
>Vikrant Dalwale=20
>
>Microsoft SQL Server Support Professional
>
>This posting is provided "AS IS" with no warranties, and=20
confers no rights.=20
>Get secure ! For info, please visit=20
http://www.microsoft.com/security.
>Please reply to Newsgroups only.
>
>--------------------
>>Content-Class: urn:content-classes:message
>>From: "Steve Hickle" <steve.hickle@druryinn.com>
>>Sender: "Steve Hickle" <steve.hickle@druryinn.com>
>>References: <190901c25f64$5a994e40
$9de62ecf@tkmsftngxs01>=20
><1bOkWA4XCHA.1576@cpmsftngxa07>=20
>< 2cb001c25ffc$a915f120$37ef2ecf
@TKMSFTNGXA13>=20
><o3I15UFYCHA.2304@cpmsftngxa07>
>>Subject: RE: Trusted connection problems
>>Date: Fri, 20 Sep 2002 04:18:36 -0700
>>Lines: 245
>>Message-ID: < 386601c26097$76ae5560$36ef2ecf
@tkmsftngxa12>
>>MIME-Version: 1.0
>>Content-Type: text/plain;
>> charset=3D"iso-8859-1"
>>Content-Transfer-Encoding: 7bit
>>X-Newsreader: Microsoft CDO for Windows 2000
>>X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
>>Thread-Index: AcJgl3ap/qQUdEVOR2KfnDYh/lWirA=3D=3D
>>Newsgroups: microsoft.public.sqlserver.server
>>NNTP-Posting-Host: TKMSFTNGXA12 10.201.226.40
>>Path: cpmsftngxa07!tkmsftngxs02!cpms
ftngxa08
>>Xref: cpmsftngxa07 microsoft.public.sqlserver.server:4118
>>X-Tomcat-NG: microsoft.public.sqlserver.server
>>
>>Vikrant, thanks for responding.
>>The MDAC Component Checker reports:
>>The MDAC version that is closest to the version on youur=20
>>computer is '2.7 RTM (2.70.7713.4)'.
>>
>>Both the client and the server TCP/IP socket are set to=20
>>1433. I they hadn't been set right, wouldn't that have=20
>>kept me from being able to establish a trusted=20
connection=20[colo
r=green]
>>using Windows Authentication (which I can do)?
>>
>>I'm not sure what you mean by the default DSN. If you=20
>>mean an alias setting for the server in the client=20
>>utility, that is also set to 1433. I
>>
>>Please advise on what to do next.
>>
>>Thanks,
>>
>>Steve
>>
>>>-----Original Message-----
>>>
>>>
>>>Hello Steve,
>>>
>>>DBNETLIB is the right value of the Reg Key=20
>>> HKLM\Software\Microsoft\MSSQLS
erver\Client\ConnectTo
>>>
>>>Now the fact that you are connecting thru Named Pipes=20[/color]
and=20
>>having problems=20
>>>with TCP/IP,
>>>tells us that SQL Server and the client are not=20
>>listening to the same port=20
>>>#. Make sure, that
>>>properties of TCP/IP shows 1433 as default port# (thru=20
>>client and server=20
>>>net utility ) on server as well as on client . =20
>>>
>>>Also, make sure that the default system DSN for the SQL=20
>>Server does have=20
>>>1433 for the TCP/IP protocol. ( thru client-
configuration=20[c
olor=green]
>>button ).
>>>
>>>Let me know whats the MDAC version on SQL Server and=20[/color]
the=20
>>Client.=20
>>>
>>>Thanks,
>>>
>>>Vikrant Dalwale=20
>>>
>>>Microsoft SQL Server Support Professional
>>>
>>>This posting is provided "AS IS" with no warranties,=20
and=20
>>confers no rights.=20
>>>Get secure ! For info, please visit=20
>>http://www.microsoft.com/security.
>>>Please reply to Newsgroups only.
>>>
>>>--------------------
>>>>Content-Class: urn:content-classes:message
>>>>From: "Steve Hickle" <steve.hickle@druryinn.com>
>>>>Sender: "Steve Hickle" <steve.hickle@druryinn.com>
>>>>References: <190901c25f64$5a994e40
>>$9de62ecf@tkmsftngxs01>=20
>>><1bOkWA4XCHA.1576@cpmsftngxa07>
>>>>Subject: RE: Trusted connection problems
>>>>Date: Thu, 19 Sep 2002 09:50:29 -0700
>>>>Lines: 137
>>>>Message-ID: <2cb001c25ffc$a915f120
$37ef2ecf@TKMSFTNGXA13> [colo
r=darkred]
>>>>MIME-Version: 1.0
>>>>Content-Type: text/plain;
>>>> charset=3D"iso-8859-1"
>>>>Content-Transfer-Encoding: 7bit
>>>>X-Newsreader: Microsoft CDO for Windows 2000
>>>>X-MimeOLE: Produced By Microsoft MimeOLE=20[/color]
V5.50.4910. 0300[
color=darkred]
>>>>Thread-Index: AcJf/ KkVI09Ck7UoRhed2ejy8e0axw=3D=3
D
>>>>Newsgroups: microsoft.public.sqlserver.server
>>>>Path: cpmsftngxa08
>>>>Xref: cpmsftngxa08=20
>>microsoft.public.sqlserver.server:229967
>>>>NNTP-Posting-Host: TKMSFTNGXA13 10.201.226.41
>>>>X-Tomcat-NG: microsoft.public.sqlserver.server
>>>>
>>>>Vikrant, thanks for responding. I've checked the=20[/color]
issues=20
>>>>you mentioned and everything seems to be configured=20
>>>>properly. The only one that I wasn't quite sure about=20
>>was=20
>>>>the net-lib registry entry. Mine is DBNETLIB,=20
>>regardless=20
>>>>of what protocol I say to use. I need to get this to=20
>>work=20
>>>>with just TCP/IP enabled (client and server), if=20
>>>>possible. Here's the behavior I've been experiencing=20
as=20

>>I=20
>>>>did more testing:
>>>>
>>>>If I use named pipes I can establish a trusted=20
>>connection=20
>>>>when I specifiy SQL Server authentication in the=20
>>>>connection dialog of isqlw. This works when=20
connecting=20[colo
r=green]
>>to=20
>>>>a remote server configured for named pipes. It only=20
>>works=20
>>>>for a connection to the local server if the "Enabled=20
>>>>shared memory protocol" check box is un-checked in the=20
>>SQL=20
>>>>Server Client Network Utility.
>>>>
>>>>If I disable named pipes and enable TCP/IP using both=20
>>the=20
>>>>client and the server network utility, I can't=20[/color]
establish=20[color
=green]
>>a=20
>>>>trusted connection when I specifiy SQL Server=20
>>>>authentication in the connection dialog of isqlw. =20[/color]
This=20
>>is=20
>>>>true for both a remote server connection and a local=20
>>>>server connection.
>>>>
>>>>Please advise on what to do next.
>>>>
>>>>Thanks,
>>>>
>>>>Steve
>>>>>-----Original Message-----
>>>>>
>>>>>
>>>>>Hello Steve,
>>>>>
>>>>>The Books On Line is correct.=20
>>>>>
>>>>>
>>>>>- Have logged in to the Workstation which is in the=20
>>same=20
>>>>domain ?=20
>>>>>
>>>>>- I assume that, you have setup the Windows=20
>>>>Authentication Mode correctly.=20
>>>>>You can verify using the
>>>>> SEM, right click on SQL Server Name and Select=20
>>>>Properties and go to=20
>>>>>Security Tab. There the radiao button on
>>>>> "Windows Only" should be selected under the=20
>>>>authentication.=20
>>>>>
>>>>>- IMP: Make sure that your NT Login Account=20
>>has "access=20
>>>>this computer from=20
>>>>>the network" rights.=20
>>>>> This can be added in the security policy. Use the=20
>>>>domain policy for=20
>>>>>Windows2000 and NT4 PDCs and BDCs.=20
>>>>> Use the local policy for NT4 member servers.
>>>>>
>>>>>- Try using both Tcp/ip and Named pipes as default=20
net- [colo
r=darkred]
>>>>lib using the=20
>>>>>client-network utility and see if changing it makes=20[/color]
the=20
>>>>diff.
>>>>>
>>>>>- Verify actual Net-Lib in registry at =20
>>>>>" HKLM\Software\Microsoft\MSSQLS
erver\Client\ConnectTo"
>>>>>
>>>>>
>>>>>
>>>>>Thanks,
>>>>>
>>>>>Vikrant Dalwale=20
>>>>>
>>>>>Microsoft SQL Server Support Professional
>>>>>
>>>>>This posting is provided "AS IS" with no warranties,=20
>>and=20
>>>>confers no rights.=20
>>>>>Get secure ! For info, please visit=20
>>>>http://www.microsoft.com/security.
>>>>>Please reply to Newsgroups only.
>>>>>
>>>>>--------------------
>>>>>>Content-Class: urn:content-classes:message
>>>>>>From: "Steve Hickle" <steve.hickle@druryinn.com>
>>>>>>Sender: "Steve Hickle" <steve.hickle@druryinn.com>
>>>>>>Subject: Trusted connection problems
>>>>>>Date: Wed, 18 Sep 2002 15:40:14 -0700
>>>>>>Lines: 30
>>>>>>Message-ID: <190901c25f64$5a994e40
>>$9de62ecf@tkmsftngxs01>
>>>>>>MIME-Version: 1.0
>>>>>>Content-Type: text/plain;
>>>>>> charset=3D"iso-8859-1"
>>>>>>Content-Transfer-Encoding: 7bit
>>>>>>X-Newsreader: Microsoft CDO for Windows 2000
>>>>>>X-MimeOLE: Produced By Microsoft MimeOLE=20
>>V5.50.4522.1200
>>>>>>Thread-Index: AcJfZFqZOpnjqZjRRPq48DwQJinR+Q
=3D=3D
>>>>>>Newsgroups: microsoft.public.sqlserver.server
>>>>>>NNTP-Posting-Host: tkmsftngxs01 207.46.230.157
>>>>>>Path: cpmsftngxa07!tkmsftngxs01
>>>>>>Xref: cpmsftngxa07=20
>>microsoft.public.sqlserver.server:3788
>>>>>>X-Tomcat-NG: microsoft.public.sqlserver.server
>>>>>>
>>>>>>According to SQL2K BOL (Administriering SQL=20
>>>>>>Server/Managing Security/Security=20
>>Levels/ Authentication=20
>>>>>>Modes):
>>>>>>"If a user attempts to connect to an instance of SQL=20
>>>>>>Server providing a blank login name, SQL Server uses=20
>>>>>>Windows Authentication. Additionally, if a user=20
>>attempts=20
>>>>>>to connect to an instance of SQL Server configured=20
for=20
>>>>>>Windows Authentication Mode by using a specific=20
login,=20
>>>>the=20
>>>>>>login is ignored and Windows Authentication is used."
>>>>>>
>>>>>>This isn't working for me. I have my SQL Server=20
2000=20
>>>>>>configured for Windows Authentication. When I use=20
>>isqlw=20
>>>>>>to try and establish a "SQL Server Authentication"=20
>>>>>>connection with a blank userid and password, I get=20
the=20
>>>>>>message:
>>>>>>
>>>>>>Msg 18452, Level 16, State 1
>>>>>>[Microsoft][ODBC SQL Server Driver][SQL Server]Login=20
>>>>>>failed for user ''. Reason: Not associated with a=20
>>>>trusted=20
>>>>>>SQL Server connection.
>>>>>>
>>>>>>I should be connected with a trusted connection in=20
the=20
>>>>>>context of the userid I'm logged onto my workstation=20
>>>>with=20
>>>>>>(if I read the BOL correctly). Can someone explain=20
>>why=20
>>>>>>this isn't working?
>>>>>>
>>>>>>Thanks,
>>>>>>
>>>>>>Steve
>>>>>>
>>>>>>
>>>>>
>>>>>.
>>>>>
>>>>
>>>
>>>.
>>>
>>
>
>.
>

Sponsored Links