Question about "Connect to the sql server 2000 installed on windows xp sp2"

Hi

I have another question now.

As the topic said, my sql server 2000 installed on windows xp sp2, the computer's name is "ADMIN" and the server 2000's name is "ADMIN".

When i startup the sql server 2000, it just listening on shared memory and name pipes, not including the "TCP/IP" . So i can not connect to the sql server using the port 1433.

Some people said that the reason was the system's firewall. I also found some supports on the websites 'www.support.microsoft.com'. It said that you can set the port 1433 or the sqlservr.exe to the execption. I also do that, but still not works.

Is there any things i forget and how can i solve the problems! Thanks for advances.

Try disabling your firewall first then connect to SQL Server. I am using SQL Server 2000 and SQL Server 2005 (instance) on my Windows XP Pro SP2 and everything works fine. Also, check you Server Network Utility and Client Network Utility. Since your client is also your server (machine), the enabled protocols in your Server Network Utility should be the same as your Client Network Utility|||

Like bass_player stated, you should check the server's network settings and verify that TCP/IP has been enabled. Otherwise, please provide the error text that you're receiving and the connection string that you used.

Il-Sung.

|||

Thanks.

I am sorry. I will describe my sql server 2000's environment now.

OS: windows xp sp2, Firewall had been shutdown

Server Network Utility : just enable the TCP/IP and use the default port 1433

Client Network Utility : also just enable the TCP/IP default port 1433

I found in the sql server's log that it just listening on shared memory.

|||

hi

try forcing a connection from the client using tcp/ip.

from the client open QA or EM

connect using (tcp\ip)\instance_name

such as (192.168.0.1)\mysqlinstance.

dont forget to chcek everything from your client network utility

and server netwrok utility which are found in

start>programs>microsoft sql server 2000> client network utility or server netwrok utility

regards,

joey

|||

joeydj wrote:

hi

try forcing a connection from the client using tcp/ip.

from the client open QA or EM

connect using (tcp\ip)\instance_name

such as (192.168.0.1)\mysqlinstance.

dont forget to chcek everything from your client network utility

and server netwrok utility which are found in

start>programs>microsoft sql server 2000> client network utility or server netwrok utility

regards,

joey

As joeydj said, i had been try like that. But it still not works. Now the problem is not on the client side, but the server side. The Sql Server 2000 do not listen on the port 1433 or others is the major problem.

Anyway, Thanks!

|||

Hi

I find another error message now.

It is "Failed to obtain TransactionDispenserInterface: Result Code = 0x8004d01b"

Why?

|||

hi,

what version of Sql server are you using

for best performance. I recommend sql server enterprise on

windows 2000 server or windows 2003 server.

I think you computer is currently in trouble

you may have to reformat it

regards,

joey

|||

Hi, joey.

The version of my sql server 2000 is just evolution edition. Is there any problem? Can you tell me the reason?

And should i reinstall my os now?

|||Recently, i enable the multiprotocol on both the client and server side(in fact the client and server is on the same computer), i can connect to the sql server 2000 local , but i can not connect to it from another computer, because the tcp/ip doesn't listen on the port 1433 all the same.|||

I get the answer now.

First, i should update the sql server 2000 to sp4.

Second, the firewall should set an exception to the port (default is 1433).

Third, we should guarantee the sequence of the protocol on the client side. That means if your sql server just listoning on shared memory or name pipe or both of them, then you should not use TCP/IP first, otherwise you may not connect to the server.