Re: SQL Server 2000 SP4 client connection problem

On Mon, 18 Feb 2008 08:58:26 -0800, "Rick Byham, \(MSFT\)"
<rickbyh@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
<BC4EDAA5-725F-4D25-ADD1-40EA86C8E60B@xxxxxxxxxxxxx>:

Tough one.
Using Query Analyzer on ClientB, try connecting to: tcp:ipaddress,1433
The "tcp:" prefix will force the connection to use tcp, to confirm it's not
trying to use named pipes.

This isn't working either, though I found something else interesting
by accident. I typed the username incorrectly and got an
authentication error very quickly. I can duplicate this using
"tcp:ipaddress,1433", just the IP or just the hostname.

This makes me think that the problem isn't reaching the server, but
rather the communication during authentication. Since the issue only
occurs when communicating with the server from ClientB, it is most
likely a problem on ClientB.

I think that I will reinstall the tools and see what happens.

Is there any chance you have an alias configured using the ClientB Client
Network Tools?

The alias list is empty.

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.
If the name is listed with the wrong ip address you can clear the DNS cache
with ipconfig /flushdns. I admit this is less likely to be the problem.

I checked and found no entry for the server, either by hostname or IP.
--
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
    ... 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
    ... 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: Ad-hoc network using TCP
    ... I'd set the ProtocolType to either Unspecified or IP, not TCP. ... I'm having some problems connecting two devices ... thinks he's connecting to the server and the server never assumes to be ... connected to any client. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: outbound email problems
    ... VSI 1 has the following external DNS servers: ... DNS server did not return a valid SOA record. ... The TCP DNS query returned no results. ... Connecting to xbs.xerox.ca on port 25. ...
    (microsoft.public.win2000.dns)
  • Re: outbound email problems
    ... Searching for Exchange external DNS settings. ... DNS server did not return a valid SOA record. ... The TCP DNS query returned no results. ... Connecting to xbs.xerox.ca on port 25. ...
    (microsoft.public.win2000.dns)
Loading