Posted by Erland Sommarskog on 10/26/05 01:01

N. Graves (ngraves@REMOVEyahoo.com) 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@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp

• Next in forum: Re: Identical database w/ identical stored procedures?
• Prev in forum: Re: User Defined Functions, passing parameters from another udf's results (end result=Crosstab)
• Thread view: Re: Server Listing for TCP connection

[Reply to this message]