MSDE 2000 SP3 Connection Problem

I am have a problem which has only just started happening while trying to
connect (locally) to MSDE 2000 (SP3a) which also prevents me from using
VS.NET Server Explorer.
When I try OSQL -E -S mimpc\NetSDK (this use to work) I get the following
error
[Named Pipes]SQL Server does not exist or access denied.
[Named Pipes]ConnectionOpen (Connect()).
But it works fine when I call OSQL -E -S (local)\NetSDK or OSQL -E -S
127.0.0.1\NetSDK.
In SVRNETCN application both TCP and Named Pipes are enabled.
I am running Windows XP Professional with 2 network card 1 being Wireless.
The log seems to suggest that the server is listening on all IP address on
port 1433
2004-04-20 18:35:55.50 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 1)
2004-04-20 18:35:55.58 server Copyright (C) 1988-2002 Microsoft
Corporation.
2004-04-20 18:35:55.58 server All rights reserved.
2004-04-20 18:35:55.58 server Server Process ID is 1092.
2004-04-20 18:35:55.58 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$NETSDK\LOG\ERRORLOG'.
2004-04-20 18:35:55.73 server SQL Server is starting at priority
class 'normal'(1 CPU detected).
2004-04-20 18:35:56.61 server SQL Server configured for thread mode
processing.
2004-04-20 18:35:56.62 server Using dynamic lock allocation. [500]
Lock Blocks, [1000] Lock Owner Blocks.
2004-04-20 18:35:56.74 spid3 Starting up database 'master'.
2004-04-20 18:35:57.40 server Using 'SSNETLIB.DLL' version
'8.0.760'.
2004-04-20 18:35:57.40 spid5 Starting up database 'model'.
2004-04-20 18:35:57.65 server SQL server listening on 198.3.0.27:
1433.
2004-04-20 18:35:57.65 server SQL server listening on 198.2.0.100:
1433.
2004-04-20 18:35:57.65 server SQL server listening on 127.0.0.1:
1433.
2004-04-20 18:35:57.65 server SQL server listening on TCP, Shared
Memory, Named Pipes.
2004-04-20 18:35:57.65 server SQL Server is ready for client
connections
2004-04-20 18:35:57.68 spid3 Server name is 'MIMPC\NETSDK'.
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
4
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
5
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
6
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
7
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
8
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
9
2004-04-20 18:35:57.68 spid3 Skipping startup of clean database id
10
2004-04-20 18:35:57.93 spid5 Clearing tempdb database.
2004-04-20 18:35:58.95 spid5 Starting up database 'tempdb'.
2004-04-20 18:35:59.28 spid3 Recovery complete.
2004-04-20 18:35:59.28 spid3 SQL global counter collection task is
created.
2004-04-20 19:15:47.20 spid51 Starting up database 'RT_TEST'.
I have gone through all the MS support articles which sugests enabling TCP
but it is or install SP3 which I did.
Any help would be appreciated.
MarkSorry.
I have just noticed it works when I add TCP: in front of the server name
osql -E -S tcp:mimpc\NetSDK
So from this I am assuming I have an issue with Named Pipes protocol.
Mark
"Mark Miles" <milesfam@.idirect.com> wrote in message
news:gyihc.165608$2oI1.24269@.twister01.bloor.is.net.cable.rogers.com...
> I am have a problem which has only just started happening while trying to
> connect (locally) to MSDE 2000 (SP3a) which also prevents me from using
> VS.NET Server Explorer.
> When I try OSQL -E -S mimpc\NetSDK (this use to work) I get the following
> error
> [Named Pipes]SQL Server does not exist or access denied.
> [Named Pipes]ConnectionOpen (Connect()).
> But it works fine when I call OSQL -E -S (local)\NetSDK or OSQL -E -S
> 127.0.0.1\NetSDK.
> In SVRNETCN application both TCP and Named Pipes are enabled.
> I am running Windows XP Professional with 2 network card 1 being Wireless.
> The log seems to suggest that the server is listening on all IP address on
> port 1433
> 2004-04-20 18:35:55.50 server Microsoft SQL Server 2000 -
8.00.760
> (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 1)
> 2004-04-20 18:35:55.58 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2004-04-20 18:35:55.58 server All rights reserved.
> 2004-04-20 18:35:55.58 server Server Process ID is 1092.
> 2004-04-20 18:35:55.58 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL$NETSDK\LOG\ERRORLOG'.
> 2004-04-20 18:35:55.73 server SQL Server is starting at priority
> class 'normal'(1 CPU detected).
> 2004-04-20 18:35:56.61 server SQL Server configured for thread
mode
> processing.
> 2004-04-20 18:35:56.62 server Using dynamic lock allocation. [500]
> Lock Blocks, [1000] Lock Owner Blocks.
> 2004-04-20 18:35:56.74 spid3 Starting up database 'master'.
> 2004-04-20 18:35:57.40 server Using 'SSNETLIB.DLL' version
> '8.0.760'.
> 2004-04-20 18:35:57.40 spid5 Starting up database 'model'.
> 2004-04-20 18:35:57.65 server SQL server listening on 198.3.0.27:
> 1433.
> 2004-04-20 18:35:57.65 server SQL server listening on 198.2.0.100:
> 1433.
> 2004-04-20 18:35:57.65 server SQL server listening on 127.0.0.1:
> 1433.
> 2004-04-20 18:35:57.65 server SQL server listening on TCP, Shared
> Memory, Named Pipes.
> 2004-04-20 18:35:57.65 server SQL Server is ready for client
> connections
> 2004-04-20 18:35:57.68 spid3 Server name is 'MIMPC\NETSDK'.
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 4
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 5
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 6
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 7
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 8
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 9
> 2004-04-20 18:35:57.68 spid3 Skipping startup of clean database
id
> 10
> 2004-04-20 18:35:57.93 spid5 Clearing tempdb database.
> 2004-04-20 18:35:58.95 spid5 Starting up database 'tempdb'.
> 2004-04-20 18:35:59.28 spid3 Recovery complete.
> 2004-04-20 18:35:59.28 spid3 SQL global counter collection task
is
> created.
> 2004-04-20 19:15:47.20 spid51 Starting up database 'RT_TEST'.
> I have gone through all the MS support articles which sugests enabling TCP
> but it is or install SP3 which I did.
> Any help would be appreciated.
> Mark
>