Re: SQL Server 2000 SP4 client connection problem
- From: Charles Calvert <cbciv@xxxxxxxxx>
- Date: Thu, 28 Feb 2008 15:20:38 -0500
On Thu, 28 Feb 2008 12:57:08 -0500, Charles Calvert <cbciv@xxxxxxxxx>
wrote in <kjsds3p0ado09ef32nboec6j9fiqi5vnr2@xxxxxxx>:
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.
Reinstalling changed nothing. It still hangs during authentication,
either with Windows or SQL Server credentials.
--
Charles Calvert | Software Design/Development
Celtic Wolf, Inc. | Project Management
http://www.celticwolf.com/ | Technical Writing
(703) 580-0210 | Research
.
- References:
- SQL Server 2000 SP4 client connection problem
- From: Charles Calvert
- Re: SQL Server 2000 SP4 client connection problem
- From: Rick Byham, \(MSFT\)
- Re: SQL Server 2000 SP4 client connection problem
- From: Charles Calvert
- SQL Server 2000 SP4 client connection problem
- Prev by Date: Re: SQL Server 2000 SP4 client connection problem
- Next by Date: Re: SQL Server 2000 SP4 client connection problem
- Previous by thread: Re: SQL Server 2000 SP4 client connection problem
- Next by thread: Re: SQL Server 2000 SP4 client connection problem
- Index(es):
Relevant Pages
|
Loading