[TCP/IP sockets]sql server does not exist or access denied

I reinstalled sql server 2000 on Windoes server 2003 three times due to diff
errors - 1st time replication recovery did not work; 2nd time typo in the
file name ; 3rd time typo in the server name. Then when I installed it the
4th time , the installation failed with system error [TCP/IP sockets] sq
l
server does not exist or access denied. Is this possible that the problem
is related to the port conflict in the machine?
Please advise !!!
Thanks.
Wen ChangRestart ur server delete all the installation files.
HTH
from
Doller
Wen Chang wrote:
> I reinstalled sql server 2000 on Windoes server 2003 three times due to di
ff
> errors - 1st time replication recovery did not work; 2nd time typo in the
> file name ; 3rd time typo in the server name. Then when I installed it th
e
> 4th time , the installation failed with system error [TCP/IP sockets]
sql
> server does not exist or access denied. Is this possible that the proble
m
> is related to the port conflict in the machine?
> Please advise !!!
> Thanks.
> Wen Chang

[TCP/IP Sockets]ConnectionCheckForData()) Error

Error was returned when we compiled a proc. The proc compiles under SP3a.
We're using Standard Edition SP4.
The offending statement is a sub-select in a where clause that uses a union:
and mv.INSTR_ID in
(
select @.INSTR_ID
union
select ridf.INSTR_ID
from FT_T_RIDF ridf
join FT_T_RISS riss on riss.RLD_ISS_FEAT_ID = ridf.RLD_ISS_FEAT_ID
and riss.PART_UNITS_TYP = 'Option' and riss.INSTR_ID = @.INSTR_ID
where ridf.REL_TYP = 'OPTION'
)change to:
( select @.INSTR_ID AS [ID]
union
select ridf.INSTR_ID
from FT_T_RIDF ridf
join FT_T_RISS riss on riss.RLD_ISS_FEAT_ID = ridf.RLD_ISS_FEAT_ID
and riss.PART_UNITS_TYP = 'Option' and riss.INSTR_ID = @.INSTR_ID
where ridf.REL_TYP = 'OPTION'
)
--
-oj
"davidhg" <davidhg@.discussions.microsoft.com> wrote in message
news:3255283F-3B9E-435B-BFC4-51CF9B5069BD@.microsoft.com...
> Error was returned when we compiled a proc. The proc compiles under SP3a.
> We're using Standard Edition SP4.
> The offending statement is a sub-select in a where clause that uses a
> union:
> and mv.INSTR_ID in
> (
> select @.INSTR_ID
> union
> select ridf.INSTR_ID
> from FT_T_RIDF ridf
> join FT_T_RISS riss on riss.RLD_ISS_FEAT_ID = ridf.RLD_ISS_FEAT_ID
> and riss.PART_UNITS_TYP = 'Option' and riss.INSTR_ID = @.INSTR_ID
> where ridf.REL_TYP = 'OPTION'
> )
>|||Hi oj,
Unfortunately, the error still occurs. To compile the proc, we created a
pseudo-talbe from the sub-select with the union statement and joined it
directly to the other tables. FYI, I opened a case with MS.
--
Dave
"oj" wrote:
> change to:
> ( select @.INSTR_ID AS [ID]
> union
> select ridf.INSTR_ID
> from FT_T_RIDF ridf
> join FT_T_RISS riss on riss.RLD_ISS_FEAT_ID = ridf.RLD_ISS_FEAT_ID
> and riss.PART_UNITS_TYP = 'Option' and riss.INSTR_ID = @.INSTR_ID
> where ridf.REL_TYP = 'OPTION'
> )
> --
> -oj
>
> "davidhg" <davidhg@.discussions.microsoft.com> wrote in message
> news:3255283F-3B9E-435B-BFC4-51CF9B5069BD@.microsoft.com...
> > Error was returned when we compiled a proc. The proc compiles under SP3a.
> > We're using Standard Edition SP4.
> >
> > The offending statement is a sub-select in a where clause that uses a
> > union:
> > and mv.INSTR_ID in
> > (
> > select @.INSTR_ID
> > union
> > select ridf.INSTR_ID
> > from FT_T_RIDF ridf
> > join FT_T_RISS riss on riss.RLD_ISS_FEAT_ID = ridf.RLD_ISS_FEAT_ID
> > and riss.PART_UNITS_TYP = 'Option' and riss.INSTR_ID = @.INSTR_ID
> > where ridf.REL_TYP = 'OPTION'
> > )
> >
> >
>
>|||Okay. Without seeing the *whole* thing I'm not sure what would be the case.
The syntax looks right to me.
Do post back if you hear anything.
--
-oj
"davidhg" <davidhg@.discussions.microsoft.com> wrote in message
news:21FFCFE8-EED9-47FA-821C-AE224C630FDC@.microsoft.com...
> Hi oj,
> Unfortunately, the error still occurs. To compile the proc, we created a
> pseudo-talbe from the sub-select with the union statement and joined it
> directly to the other tables. FYI, I opened a case with MS.
> --
> Dave
>
> "oj" wrote:
>> change to:
>> ( select @.INSTR_ID AS [ID]
>> union
>> select ridf.INSTR_ID
>> from FT_T_RIDF ridf
>> join FT_T_RISS riss on riss.RLD_ISS_FEAT_ID = ridf.RLD_ISS_FEAT_ID
>> and riss.PART_UNITS_TYP = 'Option' and riss.INSTR_ID = @.INSTR_ID
>> where ridf.REL_TYP = 'OPTION'
>> )
>> --
>> -oj
>>
>> "davidhg" <davidhg@.discussions.microsoft.com> wrote in message
>> news:3255283F-3B9E-435B-BFC4-51CF9B5069BD@.microsoft.com...
>> > Error was returned when we compiled a proc. The proc compiles under
>> > SP3a.
>> > We're using Standard Edition SP4.
>> >
>> > The offending statement is a sub-select in a where clause that uses a
>> > union:
>> > and mv.INSTR_ID in
>> > (
>> > select @.INSTR_ID
>> > union
>> > select ridf.INSTR_ID
>> > from FT_T_RIDF ridf
>> > join FT_T_RISS riss on riss.RLD_ISS_FEAT_ID = ridf.RLD_ISS_FEAT_ID
>> > and riss.PART_UNITS_TYP = 'Option' and riss.INSTR_ID = @.INSTR_ID
>> > where ridf.REL_TYP = 'OPTION'
>> > )
>> >
>> >
>>sql

[TCP/IP Sockets]ConnectionCheckForData()) Error

Error was returned when we compiled a proc. The proc compiles under SP3a.
We're using Standard Edition SP4.
The offending statement is a sub-select in a where clause that uses a union:
and mv.INSTR_ID in
(
select @.INSTR_ID
union
select ridf.INSTR_ID
from FT_T_RIDF ridf
join FT_T_RISS riss on riss.RLD_ISS_FEAT_ID = ridf.RLD_ISS_FEAT_ID
and riss.PART_UNITS_TYP = 'Option' and riss.INSTR_ID = @.INSTR_ID
where ridf.REL_TYP = 'OPTION'
)change to:
( select @.INSTR_ID AS [ID]
union
select ridf.INSTR_ID
from FT_T_RIDF ridf
join FT_T_RISS riss on riss.RLD_ISS_FEAT_ID = ridf.RLD_ISS_FEAT_ID
and riss.PART_UNITS_TYP = 'Option' and riss.INSTR_ID = @.INSTR_ID
where ridf.REL_TYP = 'OPTION'
)
-oj
"davidhg" <davidhg@.discussions.microsoft.com> wrote in message
news:3255283F-3B9E-435B-BFC4-51CF9B5069BD@.microsoft.com...
> Error was returned when we compiled a proc. The proc compiles under SP3a.
> We're using Standard Edition SP4.
> The offending statement is a sub-select in a where clause that uses a
> union:
> and mv.INSTR_ID in
> (
> select @.INSTR_ID
> union
> select ridf.INSTR_ID
> from FT_T_RIDF ridf
> join FT_T_RISS riss on riss.RLD_ISS_FEAT_ID = ridf.RLD_ISS_FEAT_ID
> and riss.PART_UNITS_TYP = 'Option' and riss.INSTR_ID = @.INSTR_ID
> where ridf.REL_TYP = 'OPTION'
> )
>|||Hi oj,
Unfortunately, the error still occurs. To compile the proc, we created a
pseudo-talbe from the sub-select with the union statement and joined it
directly to the other tables. FYI, I opened a case with MS.
--
Dave
"oj" wrote:

> change to:
> ( select @.INSTR_ID AS [ID]
> union
> select ridf.INSTR_ID
> from FT_T_RIDF ridf
> join FT_T_RISS riss on riss.RLD_ISS_FEAT_ID = ridf.RLD_ISS_FEAT_ID
> and riss.PART_UNITS_TYP = 'Option' and riss.INSTR_ID = @.INSTR_ID
> where ridf.REL_TYP = 'OPTION'
> )
> --
> -oj
>
> "davidhg" <davidhg@.discussions.microsoft.com> wrote in message
> news:3255283F-3B9E-435B-BFC4-51CF9B5069BD@.microsoft.com...
>
>|||Okay. Without seeing the *whole* thing I'm not sure what would be the case.
The syntax looks right to me.
Do post back if you hear anything.
-oj
"davidhg" <davidhg@.discussions.microsoft.com> wrote in message
news:21FFCFE8-EED9-47FA-821C-AE224C630FDC@.microsoft.com...[vbcol=seagreen]
> Hi oj,
> Unfortunately, the error still occurs. To compile the proc, we created a
> pseudo-talbe from the sub-select with the union statement and joined it
> directly to the other tables. FYI, I opened a case with MS.
> --
> Dave
>
> "oj" wrote:
>

[TCP/IP Sockets]ConnectionCheckForData()) Error

Error was returned when we compiled a proc. The proc compiles under SP3a.
We're using Standard Edition SP4.
The offending statement is a sub-select in a where clause that uses a union:
and mv.INSTR_ID in
(
select @.INSTR_ID
union
select ridf.INSTR_ID
from FT_T_RIDF ridf
join FT_T_RISS riss on riss.RLD_ISS_FEAT_ID = ridf.RLD_ISS_FEAT_ID
and riss.PART_UNITS_TYP = 'Option' and riss.INSTR_ID = @.INSTR_ID
where ridf.REL_TYP = 'OPTION'
)
change to:
( select @.INSTR_ID AS [ID]
union
select ridf.INSTR_ID
from FT_T_RIDF ridf
join FT_T_RISS riss on riss.RLD_ISS_FEAT_ID = ridf.RLD_ISS_FEAT_ID
and riss.PART_UNITS_TYP = 'Option' and riss.INSTR_ID = @.INSTR_ID
where ridf.REL_TYP = 'OPTION'
)
-oj
"davidhg" <davidhg@.discussions.microsoft.com> wrote in message
news:3255283F-3B9E-435B-BFC4-51CF9B5069BD@.microsoft.com...
> Error was returned when we compiled a proc. The proc compiles under SP3a.
> We're using Standard Edition SP4.
> The offending statement is a sub-select in a where clause that uses a
> union:
> and mv.INSTR_ID in
> (
> select @.INSTR_ID
> union
> select ridf.INSTR_ID
> from FT_T_RIDF ridf
> join FT_T_RISS riss on riss.RLD_ISS_FEAT_ID = ridf.RLD_ISS_FEAT_ID
> and riss.PART_UNITS_TYP = 'Option' and riss.INSTR_ID = @.INSTR_ID
> where ridf.REL_TYP = 'OPTION'
> )
>
|||Hi oj,
Unfortunately, the error still occurs. To compile the proc, we created a
pseudo-talbe from the sub-select with the union statement and joined it
directly to the other tables. FYI, I opened a case with MS.
Dave
"oj" wrote:

> change to:
> ( select @.INSTR_ID AS [ID]
> union
> select ridf.INSTR_ID
> from FT_T_RIDF ridf
> join FT_T_RISS riss on riss.RLD_ISS_FEAT_ID = ridf.RLD_ISS_FEAT_ID
> and riss.PART_UNITS_TYP = 'Option' and riss.INSTR_ID = @.INSTR_ID
> where ridf.REL_TYP = 'OPTION'
> )
> --
> -oj
>
> "davidhg" <davidhg@.discussions.microsoft.com> wrote in message
> news:3255283F-3B9E-435B-BFC4-51CF9B5069BD@.microsoft.com...
>
>
|||Okay. Without seeing the *whole* thing I'm not sure what would be the case.
The syntax looks right to me.
Do post back if you hear anything.
-oj
"davidhg" <davidhg@.discussions.microsoft.com> wrote in message
news:21FFCFE8-EED9-47FA-821C-AE224C630FDC@.microsoft.com...[vbcol=seagreen]
> Hi oj,
> Unfortunately, the error still occurs. To compile the proc, we created a
> pseudo-talbe from the sub-select with the union statement and joined it
> directly to the other tables. FYI, I opened a case with MS.
> --
> Dave
>
> "oj" wrote:

[TCP/IP Sockets]ConnectionCheckForData (CheckforData())

MS SQL 2000.
When I attempt a SELECT I get the following:
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionCheckForData
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
The offending SELECT
select a.account
from table1 a
where a.doc = '123456A'
and (select count(1)
from table1 b
where a.account = b.account
and a.doc = b.doc
and a.oseq = b.oseq
and a.party = b.party) > 1
If I do the SELECT with out the sub select it works fine. Suggestions?
Hi Scott
Having DDL and sample data with the expected results from that data would be
nice. See http://www.aspfaq.com/etiquette.asp?id=5006
"Scott Sheen" wrote:

> MS SQL 2000.
> When I attempt a SELECT I get the following:
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionCheckForData
> (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
>
> The offending SELECT
> select a.account
> from table1 a
> where a.doc = '123456A'
> and (select count(1)
> from table1 b
> where a.account = b.account
> and a.doc = b.doc
> and a.oseq = b.oseq
> and a.party = b.party) > 1
If this worked it wouldreturn multiple rows of the same account number

>
How about:
SELECT a.account
FROM table1 a
JOIN table1 b ON a.account = b.account
and a.doc = b.doc
and a.oseq = b.oseq
and a.party = b.party
WHERE a.doc = '123456A'
GROUP BY a.account
HAVING COUNT(*) > 1

> If I do the SELECT with out the sub select it works fine. Suggestions?
>
John
|||Reworking the statement worked around the issue.
=?Utf-8?B?Sm9obiBCZWxs?= <jbellnewsposts@.hotmail.com> wrote:
>Hi Scott
>Having DDL and sample data with the expected results from that data would be
>nice. See http://www.aspfaq.com/etiquette.asp?id=5006
>"Scott Sheen" wrote:
>
>If this worked it wouldreturn multiple rows of the same account number
>How about:
>SELECT a.account
>FROM table1 a
>JOIN table1 b ON a.account = b.account
> and a.doc = b.doc
> and a.oseq = b.oseq
> and a.party = b.party
>WHERE a.doc = '123456A'
>GROUP BY a.account
>HAVING COUNT(*) > 1
>
>John
|||Hi Scott
"Scott Sheen" wrote:

> Reworking the statement worked around the issue.
>
Was this the statement I posted or something different? How many I/O is it
doing?
John

[TCP/IP Sockets]ConnectionCheckForData (CheckforData())

MS SQL 2000.
When I attempt a SELECT I get the following:
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionChe
ckForData
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
The offending SELECT
select a.account
from table1 a
where a.doc = '123456A'
and (select count(1)
from table1 b
where a.account = b.account
and a.doc = b.doc
and a.oseq = b.oseq
and a.party = b.party) > 1
If I do the SELECT with out the sub select it works fine. Suggestions?Hi Scott
Having DDL and sample data with the expected results from that data would be
nice. See http://www.aspfaq.com/etiquette.asp?id=5006
"Scott Sheen" wrote:

> MS SQL 2000.
> When I attempt a SELECT I get the following:
> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionC
heckForData
> (CheckforData()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> Connection Broken
>
> The offending SELECT
> select a.account
> from table1 a
> where a.doc = '123456A'
> and (select count(1)
> from table1 b
> where a.account = b.account
> and a.doc = b.doc
> and a.oseq = b.oseq
> and a.party = b.party) > 1
If this worked it wouldreturn multiple rows of the same account number

>
How about :
SELECT a.account
FROM table1 a
JOIN table1 b ON a.account = b.account
and a.doc = b.doc
and a.oseq = b.oseq
and a.party = b.party
WHERE a.doc = '123456A'
GROUP BY a.account
HAVING COUNT(*) > 1

> If I do the SELECT with out the sub select it works fine. Suggestions?
>
John|||Reworking the statement worked around the issue.
examnotes <jbellnewsposts@.hotmail.com> wrote:
>Hi Scott
>Having DDL and sample data with the expected results from that data would b
e
>nice. See http://www.aspfaq.com/etiquette.asp?id=5006
>"Scott Sheen" wrote:
>
>If this worked it wouldreturn multiple rows of the same account number
>
>How about :
>SELECT a.account
>FROM table1 a
>JOIN table1 b ON a.account = b.account
> and a.doc = b.doc
> and a.oseq = b.oseq
> and a.party = b.party
>WHERE a.doc = '123456A'
>GROUP BY a.account
>HAVING COUNT(*) > 1
>
>John|||Hi Scott
"Scott Sheen" wrote:

> Reworking the statement worked around the issue.
>
Was this the statement I posted or something different? How many I/O is it
doing?
John

[TCP/IP Sockets]ConnectionCheckForData (CheckforData())

MS SQL 2000.
When I attempt a SELECT I get the following:
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionCheckForData
(CheckforData()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken
The offending SELECT
select a.account
from table1 a
where a.doc = '123456A'
and (select count(1)
from table1 b
where a.account = b.account
and a.doc = b.doc
and a.oseq = b.oseq
and a.party = b.party) > 1
If I do the SELECT with out the sub select it works fine. Suggestions?Reworking the statement worked around the issue.
=?Utf-8?B?Sm9obiBCZWxs?= <jbellnewsposts@.hotmail.com> wrote:
>Hi Scott
>Having DDL and sample data with the expected results from that data would be
>nice. See http://www.aspfaq.com/etiquette.asp?id=5006
>"Scott Sheen" wrote:
>> MS SQL 2000.
>> When I attempt a SELECT I get the following:
>> [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionCheckForData
>> (CheckforData()).
>> Server: Msg 11, Level 16, State 1, Line 0
>> General network error. Check your network documentation.
>> Connection Broken
>>
>> The offending SELECT
>> select a.account
>> from table1 a
>> where a.doc = '123456A'
>> and (select count(1)
>> from table1 b
>> where a.account = b.account
>> and a.doc = b.doc
>> and a.oseq = b.oseq
>> and a.party = b.party) > 1
>If this worked it wouldreturn multiple rows of the same account number
>How about:
>SELECT a.account
>FROM table1 a
>JOIN table1 b ON a.account = b.account
> and a.doc = b.doc
> and a.oseq = b.oseq
> and a.party = b.party
>WHERE a.doc = '123456A'
>GROUP BY a.account
>HAVING COUNT(*) > 1
>
>> If I do the SELECT with out the sub select it works fine. Suggestions?
>>
>Johnsql

[TCP/IP Sockets] Specified SQL Server not found

Connections, using ODBC (version 3.520) and from a couple web apps, to one of
my SQL Server 2000 systems (with SP3) had been fine until a couple days ago.
Suddenly some of my systems (but not all) are unable to connect to that one
server. The message when ODBC attempts to login into the SQL Server is:
Connection failed:
SQLState: '01000', SQL Server Error: 11001, [TCP/IP Sockets]ConnectionOpen
(Connect())
SQLState: '08001', SQL Server Error: 6, [TCP/IP Sockets]Specified SQL Server
not found
My web apps (including a web service) display a similar (though abbreviated)
message when the user is trying to connect to the SQL server to
login/authenticate.
From that same system that can't get to the first SQL Server, I can use ODBC
to connect to a different SQL Server with no trouble. I've tried Named Pipes
with no success. Enterprise Manager connects fine from other systems. I am
certain that MDAC 2.8 has been installed on all systems but, regardless, I
hadn't done any Windows updates on any systems for at least a week and no
MDAC/ODBC updates for a couple months.
What can I check or fix?
Thanks.
Jon
jlimmer@.gmbeverage.com
On the surface it sounds like a name resoultion problem. What happens if
you ping the SQL Server name from the web server. Does it return? Als try
ping -a <ip address of the SQL Server machine>. Does it return the correct
server name?
Can you connect from a DSN using the ip address of the SQL Server as the
server name?
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Very interesting, Rand.
I can ping the SQL server both using the server name and using the -a switch
(which does resolve the server name).
I also can sucessfully use the IP address in the SQL Server instance name in
the DSN to connect.
So, what does that indicate is the problem, if DNS is working?
Jon

[TCP/IP Sockets] Specified SQL Server not found

Connections, using ODBC (version 3.520) and from a couple web apps, to one o
f
my SQL Server 2000 systems (with SP3) had been fine until a couple days ago.
Suddenly some of my systems (but not all) are unable to connect to that one
server. The message when ODBC attempts to login into the SQL Server is:
Connection failed:
SQLState: '01000', SQL Server Error: 11001, [TCP/IP Sockets]ConnectionOp
en
(Connect())
SQLState: '08001', SQL Server Error: 6, [TCP/IP Sockets]Specified SQL Se
rver
not found
My web apps (including a web service) display a similar (though abbreviated)
message when the user is trying to connect to the SQL server to
login/authenticate.
From that same system that can't get to the first SQL Server, I can use ODBC
to connect to a different SQL Server with no trouble. I've tried Named Pipe
s
with no success. Enterprise Manager connects fine from other systems. I am
certain that MDAC 2.8 has been installed on all systems but, regardless, I
hadn't done any Windows updates on any systems for at least a week and no
MDAC/ODBC updates for a couple months.
What can I check or fix?
Thanks.
Jon
jlimmer@.gmbeverage.comOn the surface it sounds like a name resoultion problem. What happens if
you ping the SQL Server name from the web server. Does it return? Als try
ping -a <ip address of the SQL Server machine>. Does it return the correct
server name?
Can you connect from a DSN using the ip address of the SQL Server as the
server name?
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Very interesting, Rand.
I can ping the SQL server both using the server name and using the -a switch
(which does resolve the server name).
I also can sucessfully use the IP address in the SQL Server instance name in
the DSN to connect.
So, what does that indicate is the problem, if DNS is working?
Jon

[DBNETLIB][ConnectionWrite (send()).] General network error.

Hi,
in our environment
- Windows XP
- SQL Server Express 2005
- Internet connection via TCP/IP protocol

The described network error occurs, when we unplug the network cable:
[DBNETLIB][ConnectionWrite (send()).] General network error.

The affected database resides on the locally installed SQLExpress, it doesn't use any network connections. The error doesn't occur immediately, in most cases there are up to 30 seconds where data can be (correctly!) written to the recordset, but after that timeout the connetion is broken.

We already tried out the described workarounds:
- disable named pipes protocol
- set SynAttackProtect=0 in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

The error doesn't occur with MSDE (SQL 2000) or under Vista.

Thanks for help!

Mathias

I suggest using shared memory to connect locally or making sure your server specification is one that correctly gets resolved to use the loopback (e.g. .\ or (local) or localhost). You may also want to see if your hosts file has an entry for the machine to make sure it resolves its own name. Right now, it appears as though your communications are going out over the network. You may have some amount of data transfer after unplugging the cable because the network connection is buffered, so the server still has that much data in its network buffer before it runs out. I think the connection timeout is consuming the bulk of that 30 seconds. Vista most likely has its own hostname in its hosts file, or has some other trick for self-resolving its computer name. More than likely, your instance of SQL 2000 is using shared memory to connect or using a different specification of the hostname.

Hope that helps,

John