Posted by Danieltbt05 on 11/18/05 02:28

Hi, from the server itself I installed client login and I could login.
I noticed the server itself has ODBC DS installed in ODBC control
panel. Do I need to install it for client ? Both netlib is supporting
TCP/IP with fixed port 1433 as this is default instance. Doesn;t that
name pipe is more suitable for local system as server and client ?

Regards
Daniel


Erland Sommarskog wrote:
> (Danieltbt05@gmail.com) writes:
> > Hi, I have SP4. When i use netstat -an, there is no connection to my
> > client machine. Do you mean both server and client can set up port as
> > 1234 ? I also attached my errorlog, maybe can look at it ? Btw if both
> > machine can ping by ip and name then it shouldn't be any connection
> > problem right ? Thanks.
>
> OK, here is an interesting tidbit:
>
> > 2005-11-19 00:21:20.90 server SQL server listening on Shared Memory,
> > Named Pipes.
>
> Not a word on TCP/IP, even less a port number. This is how my errorlog looks
> like:
>
> 2005-11-05 09:57:47.61 server SQL server listening on 172.16.18.28: 1433.
> 2005-11-05 09:57:47.61 server SQL server listening on 127.0.0.1: 1433.
> 2005-11-05 09:57:47.68 server SQL server listening on TCP, Shared Memory.
> 2005-11-05 09:57:47.68 server SQL Server is ready for client connections
>
> So either you use the Server Network Utility and enable TCP/IP for the
> server, and the restart the server. Or you use the Client Network Utitilty
> on the client box and enable Named Pipes. I recommend the first opion.
>
>
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
>
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

[Back to original message]