SQL Server 2000 SP4 client connection problem

Description: I have a server and two clients (ClientA and ClientB).
All are on static IP, on the same LAN segment.

Server
------
W2K3 Enterprise SP2
SQL Server 2000 SP4

Clients
-------
WinXP SP2


Attempts to connect from ClientB result in the application's hanging.
Attempts from ClientA work. This is a new problem. ClientB was able
to connect via the IP (but not hostname) until today.

Things checked:

1. Both client and server have been rebooted.

2. Cannot connect using either hostname or IP from ClientB, both work
from ClientA.

3. Tested with Query Analyzer, Enterprise Manager and osql. None work
on ClientB and all work on ClientA.

4. Cannot connect using either Windows Authentication or SQL Server
Authentication from ClientB, both work from ClientA.

5. Can successfully ping the server from ClientB, using both hostname
and IP.

6. Can successfully telnet to port 1433 from ClientB, using either
hostname or IP.

7. Checked servername vs. NetBIOS name:

SELECT @@servername
SELECT SERVERPROPERTY('servername')

They are identical.

8. Turned off firewall on server and ClientB. No change.

9. Tried creating a DSN. Was able to specify server name, but after
specifying authentication type and clicking on "Next", it hung.

I've been googling, but I haven't found anything else to try. I can
reinstall the tools on ClientB, but I can't think of anything else to
try.
--
Charles Calvert | Software Design/Development
Celtic Wolf, Inc. | Project Management
http://www.celticwolf.com/ | Technical Writing
(703) 580-0210 | Research
.

Relevant Pages

  • Re: SQL Server 2000 SP4 client connection problem
    ... The "tcp:" prefix will force the connection to use tcp, to confirm it's not trying to use named pipes. ... Is there any chance you have an alias configured using the ClientB Client Network Tools? ... ClientB can ping the server by name, so I think name resolution is OK, but I would still check the DNS cache on ClientB by running ipconfig /displaydns. ... Cannot connect using either hostname or IP from ClientB, ...
    (microsoft.public.sqlserver.connect)
  • Re: SQL Server 2000 SP4 client connection problem
    ... Using Query Analyzer on ClientB, try connecting to: tcp:ipaddress,1433 ... The "tcp:" prefix will force the connection to use tcp, ... occurs when communicating with the server from ClientB, ...
    (microsoft.public.sqlserver.connect)
  • Re: SQL Server 2000 SP4 client connection problem
    ... Using Query Analyzer on ClientB, try connecting to: tcp:ipaddress,1433 ... The "tcp:" prefix will force the connection to use tcp, ... occurs when communicating with the server from ClientB, ...
    (microsoft.public.sqlserver.connect)
  • Unfair TCP client servicing
    ... We have an internal program that process batches of information. ... information to the Server. ... Batch 89 from ClientA ... Batch 5041 from ClientB ...
    (comp.os.linux.networking)
  • Re: Workstation of user logged
    ... If the hostid and hostname are serverid and name, is this a web app or a COM ... component running with its own user account, a proxy account, that is ... the caller and pass that along to the SQL Server as a parameter. ...
    (microsoft.public.sqlserver.programming)
Loading