Cannot connect to SQL 2000 remotely

I'm trying to install a bespoke application for a new client, and am
embarassed by not being able to connect to their DB Server.
The server and clients are XP all running on a workgroup called OFFICE
File access is not problem and the DB Server name appears in a dropdown box
of SQL servers on the network - e.g. when trying to create an ODBC DSN.
The SQL Server is now configured to accept Windows and SQL authentication
connection requests - and restarted.
I have switched off or uninstalled everything that looks like a firewall on
both server and clients.
When trying to set up local ODBC DSN to connect as sa, I can connect no
problem, but from one of the client laptops I just get the error:
"Access denied or SQL Server does not exist"
Can anyone tell me where else to look or what else to try?
Is there a step by step procedure which could take me to the cause of the
problem?
The network is a wireless Lan - and IPX/SPX is featuring in the network
stack. Could that be something to do with it?
Any help very very much appreaciated!
Thank you
Clive (London UK)On the server, from the Start menu, point to All Programs, point to
Microsoft SQL Server, and then click Server Network Utility. That utility
should help you understand if SQL Server is using the IPX/SPX or TCP/IP
protocols, which might indicate a problem. On the client there is a similar
program, the Client Network Utility. Obviously the client and server should
be using the same protocols.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Clive" <clive.elsworth@.takeoutonetel.net> wrote in message
news:OxUCSSVyHHA.5856@.TK2MSFTNGP02.phx.gbl...
> I'm trying to install a bespoke application for a new client, and am
> embarassed by not being able to connect to their DB Server.
> The server and clients are XP all running on a workgroup called OFFICE
> File access is not problem and the DB Server name appears in a dropdown
> box of SQL servers on the network - e.g. when trying to create an ODBC
> DSN.
> The SQL Server is now configured to accept Windows and SQL authentication
> connection requests - and restarted.
> I have switched off or uninstalled everything that looks like a firewall
> on both server and clients.
> When trying to set up local ODBC DSN to connect as sa, I can connect no
> problem, but from one of the client laptops I just get the error:
> "Access denied or SQL Server does not exist"
> Can anyone tell me where else to look or what else to try?
> Is there a step by step procedure which could take me to the cause of the
> problem?
> The network is a wireless Lan - and IPX/SPX is featuring in the network
> stack. Could that be something to do with it?
> Any help very very much appreaciated!
> Thank you
> Clive (London UK)
>
>
>
>|||Could it be because the default MSDE 2000 sp3a setup is to Disable network
protocols?
It seems that you can't rely on the setup utility to warn of this kind of
change between sp3 and sp3a. You just have to make sure you read all the
gumf every time - just in case they've decided to quietly cripple your
system this time.
"Rick Byham, (MSFT)" <rickbyh@.REDMOND.CORP.MICROSOFT.COM> wrote in message
news:1CAB65A1-509E-4338-8C33-65D98FDA7300@.microsoft.com...
> On the server, from the Start menu, point to All Programs, point to
> Microsoft SQL Server, and then click Server Network Utility. That utility
> should help you understand if SQL Server is using the IPX/SPX or TCP/IP
> protocols, which might indicate a problem. On the client there is a
> similar program, the Client Network Utility. Obviously the client and
> server should be using the same protocols.
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Clive" <clive.elsworth@.takeoutonetel.net> wrote in message
> news:OxUCSSVyHHA.5856@.TK2MSFTNGP02.phx.gbl...
>|||Apologies for flame throwing. Default of DisableNetworkProtocols WAS the
problem, but in any case
thank for taking the time and trouble to get back to me Rick.
Clive Elsworth
"Rick Byham, (MSFT)" <rickbyh@.REDMOND.CORP.MICROSOFT.COM> wrote in message
news:1CAB65A1-509E-4338-8C33-65D98FDA7300@.microsoft.com...
> On the server, from the Start menu, point to All Programs, point to
> Microsoft SQL Server, and then click Server Network Utility. That utility
> should help you understand if SQL Server is using the IPX/SPX or TCP/IP
> protocols, which might indicate a problem. On the client there is a
> similar program, the Client Network Utility. Obviously the client and
> server should be using the same protocols.
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Clive" <clive.elsworth@.takeoutonetel.net> wrote in message
> news:OxUCSSVyHHA.5856@.TK2MSFTNGP02.phx.gbl...
>|||Glad to help. I recognize customers stress and confusion as a problem that
we (Microsoft) often cause... and have an obligation to resolve.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Clive" <clive.elsworth@.takeoutonetel.net> wrote in message
news:O7J9R4pzHHA.3400@.TK2MSFTNGP03.phx.gbl...
> Apologies for flame throwing. Default of DisableNetworkProtocols WAS the
> problem, but in any case
> thank for taking the time and trouble to get back to me Rick.
> Clive Elsworth
>
>
> "Rick Byham, (MSFT)" <rickbyh@.REDMOND.CORP.MICROSOFT.COM> wrote in message
> news:1CAB65A1-509E-4338-8C33-65D98FDA7300@.microsoft.com...
>