|
|
Posted by Danieltbt05 on 06/14/80 11:32
Hi, thanks for your help, my problem solved when I upgrade to SP4. My
client have 2 NICs (multi-homed) thats the problem. An issue with SQL.
Regards
Daniel
Erland Sommarskog wrote:
> (Danieltbt05@gmail.com) writes:
> > 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 ?
>
> No.
>
> > 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 ?
>
> I don't know what you are trying to say in your last sentence, but the
> errorlog you included shows that the server is *not* listening to TCP/IP.
> Change this in the Server Configuration Utility.
>
> And, oh, there is one very important thing that I missed in the post of your
> previous error log.
>
> >2005-11-19 00:21:08.26 server Microsoft SQL Server 2000 - 8.00.194
> >(Intel X86)
>
> You are running SQL 2000 RTM on Windows 2003, which is not supported.
> Install SP 3 (8.00.760) or SP4 (8.00.2039).
>
> > Hi, forget to tell that my client is a multihomed machine. Does it
> > matters ?
>
> Multi-homed, do you mean that you have several boot partitions or do you
> mean something else?
>
>
> --
> 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
Navigation:
[Reply to this message]
|