Re: Server Listing for TCP connection
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Tue, 25 Oct 2005 22:01:47 +0000 (UTC)
N. Graves (ngraves@xxxxxxxxxxxxxxx) writes:
> I'm having trouble with an ODBC User that can't connect to 2003
> Windows Server with SQL2000.
>
> The ODBC fails when he tries to contact with TCP client connection.
> When I view the Network Connection it is displaying TCP is checked,
> but when I view the error log is doesn't display that it is listening
> for TCP.
>
> Is there any way to prove that my TCP connections are working
> correctly or a way to make sure that my SQL server is listening for
> TCP?
When you are saying Network Connection, do you mean the Server Network
Utility?
Note that if you make a change here, it does not have effect until
you restart the server.
And, of course, watch out for Windows Firewall.
--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
.
- Follow-Ups:
- Re: Server Listing for TCP connection
- From: Danny
- Re: Server Listing for TCP connection
- References:
- Server Listing for TCP connection
- From: N . Graves
- Server Listing for TCP connection
- Prev by Date: Re: User Defined Functions, passing parameters from another udf's results (end result=Crosstab)
- Next by Date: Re: Identical database w/ identical stored procedures?
- Previous by thread: Server Listing for TCP connection
- Next by thread: Re: Server Listing for TCP connection
- Index(es):
Relevant Pages
|
