Re: SQL Server 2000 SP4 client connection problem

Well, that's some progress.
If you can connect locally using TCP, the SQL Server must be listening on TCP properly.
And if you see the connection attempts in the log, then TCP/IP must be passing something to SQL Server.
So your comment about the handshake or authentication being the problem makes sense to me too.
Is SQL Server in mixed mode authentication and are you still trying to connect using sa?
If you are using integrated authentication, there are some possible issues though they should leave errors in the Windows event log. I'm thinking of http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=SQL%20Server&ProdVer=10.0&EvtID=17832&EvtSrc=MSSQLServer&LCID=1033 though that's pretty obscure.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.

"Charles Calvert" <cbciv@xxxxxxxxx> wrote in message news:m8nqu3lnaqert0i6bhm4k2h9amolcrcoeu@xxxxxxxxxx
On Fri, 28 Mar 2008 12:48:20 -0400, Charles Calvert <cbciv@xxxxxxxxx>
wrote in <8l5qu39sl9c5h6t595ds1nm97joslerbi3@xxxxxxx>:

On Fri, 28 Mar 2008 08:44:45 -0700, "Rick Byham, \(MSFT\)"
<rickbyh@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
<4E64E165-0C75-4D06-A290-2DD76B00550B@xxxxxxxxxxxxx>:

Important note: it looks like I have a corrupted installation. When I
execute "SELECT @@VERSION", I get back 8.00.2039, but when I use
PortQryUI
<http://www.microsoft.com/downloads/details.aspx?FamilyID=8355E537-1EA6-4569-AABB-F248F4BD91D0&displaylang=en>,
I get back version 8.00.129. According to the support engineer at MS,
the latter version is SQL Server 2000 with no service packs, while the
former is SP4.

I'm reinstalling right now. Note that I had already reinstalled once.
I have installed SQL Server 2000 Enterprise, then installed SP4. I
did not bother with previous service packs or hotfixes, because the
download details for SP4
<http://www.microsoft.com/downloads/details.aspx?FamilyID=8e2dfc8d-c20e-4446-99a9-b7f0213f8bc5>
indicate that it includes all fixes from previous service packs.

After working with an engineer from the installation support group,
the product is reinstalled, but Port Query still reports the version
as 8.00.129, whereas everything else indicates version 8.00.2039.

[snip]

Locally (on the same computer as the SQL Server) try forcing a TCP
connection through the loopback connector (127.0.0.1) which is the TCP
simplest code path by connecting to: TCP:127.0.0.1,1043

If SQL Server is listening on TCP and if 127.0.0.1 is enabled, and if it's
listening on port 1043, then it's hard to see how this could fail.

I didn't try 127.0.0.1, though I did try 192.168.1.21. I'll give that
a shot if the reinstallation doesn't fix it.

Local connections are now working using TCP (named pipes are
disabled), but the clients cannot connect. The firewalls are turned
off.

Note that the connections appear in the log, but QA hangs, making me
think that the problem is in the handshake or authentication.

The best tool would be a version of QA or similar tool that dumps a
log of the sockets session, but I don't know if such a thing exists.
--
Charles Calvert | Software Design/Development
Celtic Wolf, Inc. | Project Management
http://www.celticwolf.com/ | Technical Writing
(703) 580-0210 | Research

.

Relevant Pages

  • Re: .NET SqlConnection: connect error SQL Server 2005 DEV on same
    ... If I wanted to specify the port in the conenct string, ... enable TCP in the surface area configuration? ... Rick Byham, SQL Server Books Online ... An error has occurred while establishing a connection to the ...
    (microsoft.public.sqlserver.connect)
  • Re: ActiveSync 3.8/WIFI
    ... In the Wi-Fi connection on the iPAQ did you enter the ip 192.168.10.98 as ... I can tell you, however, that I can use> File Explorer on the iPaq to successfully map to a share on the laptop. ... >>> Microsoft article Q25369 suggests that ActiveSync uses TCP ports 990, ... >>> TCP 0.0.0.0:135 0.0.0.0:0 LISTENING>>> ...
    (microsoft.public.pocketpc.activesync)
  • Re: ActiveSync 3.8/WIFI
    ... enter the desktop's IP address as the WINS server in the Wi-Fi connection? ... > TCP 0.0.0.0:135 0.0.0.0:0 LISTENING> ... > UDP 0.0.0.0:445 *:* ...
    (microsoft.public.pocketpc.activesync)
  • Re: SQL Server 2000 SP4 client connection problem
    ... If you can connect locally using TCP, the SQL Server must be listening on ... TCP properly. ... And if you see the connection attempts in the log, ... but ODBC connections fail. ...
    (microsoft.public.sqlserver.connect)
  • ActiveSync 3.8/WIFI
    ... I'm having issues with ActiveSync over my WIFI connection. ... The laptop can PING the iPaq both by IP address and name; ... TCP 0.0.0.0:135 0.0.0.0:0 LISTENING ...
    (microsoft.public.pocketpc.activesync)