Re: integratedSecurity and SQL Server 200
- From: evanba@xxxxxxxxxxxxxxxxxxxx (Evan T. Basalik (MSFT))
- Date: Tue, 20 Mar 2007 18:58:17 GMT
Jarrod,
Generally, we would take a look at the client/server network captures to see where we were dying out. Unfortunately, analyzing network traces is not very
easy to do over the web. :(
If you want to troubleshoot this any further, I would strongly encourage you to open up a support case with us.
Evan
--------------------
From: jarroda@xxxxxxxxxp15g2000hsd.googlegroups.com!not-for-mail
Newsgroups: microsoft.public.sqlserver.jdbcdriver
Subject: Re: integratedSecurity and SQL Server 200
Date: 14 Mar 2007 22:15:04 -0700
Organization: http://groups.google.com
Lines: 100
Message-ID: <1173935704.659009.325700@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
References: <1173249681.180298.241030@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
<w$Zf3vbZHHA.552@xxxxxxxxxxxxxxxxxxxxxx>
NNTP-Posting-Host: 202.7.166.163
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Trace: posting.google.com 1173935706 26679 127.0.0.1 (15 Mar 2007 05:15:06 GMT)
X-Complaints-To: groups-abuse@xxxxxxxxxx
NNTP-Posting-Date: Thu, 15 Mar 2007 05:15:06 +0000 (UTC)
In-Reply-To: <w$Zf3vbZHHA.552@xxxxxxxxxxxxxxxxxxxxxx>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.2) Gecko/20070219 Firefox/2.0.0.2,gzip(gfe),gzip(gfe)
X-HTTP-Via: 1.1 AUMEIS70, 1.1 syd-pow-pr1.tpgi.com.au:3128 (squid/2.5.STABLE9)
Complaints-To: groups-abuse@xxxxxxxxxx
Injection-Info: p15g2000hsd.googlegroups.com; posting-host=202.7.166.163;
posting-account=kalmrQ0AAAAM1P9x3ryTJLVbuVBU2eO3
Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS02.phx.gbl!msrtrans!newsfeed.media.kyoto-u.ac.jp!postnews.google.com!
Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.jdbcdriver:131not-
X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver
I've tried several different installs of SQL Server 2000 on different
machines - all patched with SP4, all seem to behave similarly.
I can connect to these SQL Server 2000 instances with other clients -
even the JDBC drivers, just not with integratedSecurity=true. I can
connect with Query Analyzer using windows authentication.
Using the IP address or servername rather than localhost doesn't seem
to make any difference either.
When trying to connect with integratedSecurity=true, the connection
attempt takes several minutes to fail if thats useful information.
Jarrod
Evan T. Basalik MSFT wrote:
That error message sounds like a connectivity issue that is likely not specific to the JDBC driver itself.
Are you having this problem with multiple SQL Server 2000 machines, or just one specific machine? Can you connect to the failing SQL Server 2000
instance with other applications? Can you try using IP address or servername instead of localhost?
Evan
--------------------
From: jarroda@xxxxxxxxxnewscon02.news.prodigy.net!prodigy.net!border1.nntp.dca.giganews.com!nntp.giganews.com!postnews.google.com!j27g2000cwj.googlegroups.com!
Newsgroups: microsoft.public.sqlserver.jdbcdriver
Subject: integratedSecurity and SQL Server 200
Date: 6 Mar 2007 22:41:21 -0800
Organization: http://groups.google.com
Lines: 49
Message-ID: <1173249681.180298.241030@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
NNTP-Posting-Host: 202.7.166.163
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1173249700 17356 127.0.0.1 (7 Mar 2007 06:41:40 GMT)
X-Complaints-To: groups-abuse@xxxxxxxxxx
NNTP-Posting-Date: Wed, 7 Mar 2007 06:41:40 +0000 (UTC)
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.2) Gecko/20070219 Firefox/2.0.0.2,gzip(gfe),gzip(gfe)
X-HTTP-Via: 1.1 AUMEIS70, 1.1 syd-pow-pr1.tpgi.com.au:3128 (squid/2.5.STABLE9)
Complaints-To: groups-abuse@xxxxxxxxxx
Injection-Info: j27g2000cwj.googlegroups.com; posting-host=202.7.166.163;
posting-account=kalmrQ0AAAAM1P9x3ryTJLVbuVBU2eO3
Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTFEEDS02.phx.gbl!news-out.cwix.com!newsfeed.cwix.com!
for-mail
Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.sqlserver.jdbcdriver:122
X-Tomcat-NG: microsoft.public.sqlserver.jdbcdriver
I'm trying to connect to SQL Server 2000 using the SQL Server 2005 1.1
JDBC drivers using integratedSecurity=true. However whenever I try
to connect I'm thrown the following exception;
com.microsoft.sqlserver.jdbc.SQLServerException: An exception
occurred during the DBComms.receive method. Operation:Connection
reset. Context:(1) [Thread[main,5,main], IO:935c3, Dbc:875c3]. PktNum:
1. TotalReceived:177. PktSize:4,096.
at
com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(Unknown
Source)
at com.microsoft.sqlserver.jdbc.DBComms.receive(Unknown
Source)
at com.microsoft.sqlserver.jdbc.DBComms.receive(Unknown
Source)
at
com.microsoft.sqlserver.jdbc.SQLServerConnection.sendLogon(Unknown
Source)
at
com.microsoft.sqlserver.jdbc.SQLServerConnection.logon(Unknown Source)
at
com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(Unknown
Source)
at
com.microsoft.sqlserver.jdbc.SQLServerConnection.loginWithoutFailover(Unknown
Source)
at
com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown
Source)
at
com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:
538)
at java.sql.DriverManager.getConnection(DriverManager.java:
210)
at TestMS.main(TestMS.java:36)
The URL I'm using to connect is - "jdbc:sqlserver://
localhost;integratedSecurity=true;" and the user can connect with the
Query Analyzer fine. I'm using Sun's JDK 1.4.2 and just doing a
DriverManager.getConnection(url).
I can however connect to SQL Server 2005 with no problems, and I can
connect to SQL Server 2000 with integratedSecurity=false and a native
database user credentials.
Has anyone had any success connecting to SQL Server 2000 with
integratedSecurity=true or know if this is unsupported?
.
- References:
- integratedSecurity and SQL Server 200
- From: jarroda
- Re: integratedSecurity and SQL Server 200
- From: jarroda
- integratedSecurity and SQL Server 200
- Prev by Date: Re: java.lang.reflect.InvocationTargetException
- Next by Date: Connection Reset Issue with MS SQL 2005
- Previous by thread: Re: integratedSecurity and SQL Server 200
- Next by thread: Re: instjdbc.sql and sqljdbc.dll
- Index(es):
Relevant Pages
|