Client Cannot See SQL 2000 Server Database

TheMSsForum.com: The Microsoft Software Forum

This is a multi-part message in MIME format.

------=_NextPart_000_011A_01C36729.1836F200
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

We have SQL 2000 running on a customer's Windows 2000 server.

Client Network Utility has been run on all Workstations, but we cannot =
connect to the SQL Database.

MDAC 2.7 SP1 Refresh has been applied to all machines.

We can Ping from machine to machine using Name and IP Address.

We have Shared the Database Folder, and can "see" the folder from every =
machine.

The Users in question are all given Administrator rights.

What setting/settings on Windows 2000 Server should we check that might =
be blocking access to the Network Database?

Thanks,


--=20
George H Bergmark
Business Systems & Solutions Inc.
1502 Augusta Drive, Suite 394
Houston, Texas 77057


------=_NextPart_000_011A_01C36729.1836F200
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4731.2200" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>We have SQL 2000 running on a customer's Windows =
2000=20
server.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Client Network Utility has been run on all =
Workstations, but=20
we cannot connect to the SQL Database.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>MDAC 2.7 SP1 Refresh has been applied to all=20
machines.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>We can Ping from machine to machine using Name and =
IP=20
Address.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>We have Shared the Database Folder, and can "see" =
the folder=20
from every machine.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>The Users in question are all given Administrator=20
rights.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>What setting/settings on Windows 2000 Server should =
we check=20
that might be blocking access to the Network Database?</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Thanks,</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV><FONT size=3D2>
<DIV><BR>-- <BR>George H Bergmark<BR>Business Systems &amp; Solutions=20
Inc.<BR>1502 Augusta Drive, Suite 394<BR>Houston, Texas=20
77057<BR></DIV></FONT></BODY></HTML>

------=_NextPart_000_011A_01C36729.1836F200--
Top

Re: Client Cannot See SQL 2000 Server Database by Steve

Steve
Wed Aug 20 17:18:56 CDT 2003

George Bergmark wrote:

> We have SQL 2000 running on a customer's Windows 2000 server.
>
> Client Network Utility has been run on all Workstations, but we
> cannot connect to the SQL Database.
>
> MDAC 2.7 SP1 Refresh has been applied to all machines.
>
> We can Ping from machine to machine using Name and IP Address.
>
> We have Shared the Database Folder, and can "see" the folder from
> every machine.
>
> The Users in question are all given Administrator rights.
>
> What setting/settings on Windows 2000 Server should we check that
> might be blocking access to the Network Database?
>
> Thanks,

How are you trying to connect to the SQL Server? What application are
you using to communicate with it?

Have you tried to use Enterprise Manager from a workstation while
logged on as domain\Administrator?

You have granted users rights to access SQL Server right? OOB, only
members of the domain Administrators group can connect.

--
Steve Foster [SBS MVP]
---------------------------------------
MVPs do not work for Microsoft. Please reply only to the newsgroups.
Top

Re: Client Cannot See SQL 2000 Server Database by George

George
Thu Aug 21 12:35:13 CDT 2003

Steve,

The Application we have installed is Microsoft Retail Management System
which can use MSDE or SQL Server 2000.

We have brought the client's Server and POS workstation back to our office
for testing.

We are logged on the Network as the Administrator.

SQL Enterprise Manager is loaded on each machine, and can see it's local
instance of MSDE.

But not accross the Network to see the other databases.

We are using SQL Authentication and the SA User/password for access to the
SQL Servers.

We have tried switching to Mixed Mode for NT Authentication, but no joy.

George


"Steve Foster [SBS MVP]" <steve.foster@picamar.co.uk> wrote in message
news:uuJpMk2ZDHA.2620@TK2MSFTNGP09.phx.gbl...
> George Bergmark wrote:
>
> > We have SQL 2000 running on a customer's Windows 2000 server.
> >
> > Client Network Utility has been run on all Workstations, but we
> > cannot connect to the SQL Database.
> >
> > MDAC 2.7 SP1 Refresh has been applied to all machines.
> >
> > We can Ping from machine to machine using Name and IP Address.
> >
> > We have Shared the Database Folder, and can "see" the folder from
> > every machine.
> >
> > The Users in question are all given Administrator rights.
> >
> > What setting/settings on Windows 2000 Server should we check that
> > might be blocking access to the Network Database?
> >
> > Thanks,
>
> How are you trying to connect to the SQL Server? What application are
> you using to communicate with it?
>
> Have you tried to use Enterprise Manager from a workstation while
> logged on as domain\Administrator?
>
> You have granted users rights to access SQL Server right? OOB, only
> members of the domain Administrators group can connect.
>
> --
> Steve Foster [SBS MVP]
> ---------------------------------------
> MVPs do not work for Microsoft. Please reply only to the newsgroups.


Top

Re: Client Cannot See SQL 2000 Server Database by Steve

Steve
Sat Aug 23 06:05:28 CDT 2003

George Bergmark wrote:

> Steve,
>
> The Application we have installed is Microsoft Retail Management
> System which can use MSDE or SQL Server 2000.
>
> We have brought the client's Server and POS workstation back to our
> office for testing.
>
> We are logged on the Network as the Administrator.
>
> SQL Enterprise Manager is loaded on each machine, and can see it's
> local instance of MSDE.
>
> But not accross the Network to see the other databases.
>
> We are using SQL Authentication and the SA User/password for access
> to the SQL Servers.
>
> We have tried switching to Mixed Mode for NT Authentication, but no
> joy.
>
> George

What error message does EM give when you try to register the network
SQL server?

Have you tried using Query Analyzer?

--
Steve Foster [SBS MVP]
---------------------------------------
MVPs do not work for Microsoft. Please reply only to the newsgroups.
Top

Re: Client Cannot See SQL 2000 Server Database by jimbehning(doesthisblockpork?)

jimbehning(doesthisblockpork?)
Sat Aug 23 09:04:49 CDT 2003

I know little about SQL. What happens when you go through the ODBC
stuff? I think it is system dsn where you build a connection to the
server and there is a test connection button.

"Steve Foster [SBS MVP]" <steve.foster@picamar.co.uk> wrote:

>George Bergmark wrote:
>
>> Steve,
>>
>> The Application we have installed is Microsoft Retail Management
>> System which can use MSDE or SQL Server 2000.
>>
>> We have brought the client's Server and POS workstation back to our
>> office for testing.
>>
>> We are logged on the Network as the Administrator.
>>
>> SQL Enterprise Manager is loaded on each machine, and can see it's
>> local instance of MSDE.
>>
>> But not accross the Network to see the other databases.
>>
>> We are using SQL Authentication and the SA User/password for access
>> to the SQL Servers.
>>
>> We have tried switching to Mixed Mode for NT Authentication, but no
>> joy.
>>
>> George
>
>What error message does EM give when you try to register the network
>SQL server?
>
>Have you tried using Query Analyzer?

Jim B. SBS MVP
Top

Re: Client Cannot See SQL 2000 Server Database by George

George
Mon Aug 25 12:06:56 CDT 2003

Yes, we connect locally, but not across the network

george

"Buddy Greenshield" <gcs-at-bendcable-dot-com> wrote in message
news:edmbMjyaDHA.2620@TK2MSFTNGP09.phx.gbl...
> This may be stupid, but is the sql server service actually running? Can
you
> connect to the server via enterprise manager at the server's console?
>
> Buddy
> "George Bergmark" <ghbergm@solutions-intl.com> wrote in message
> news:%23yXihPyaDHA.2548@TK2MSFTNGP09.phx.gbl...
> > 1) Created a Folder across the Network and added files, so we have Full
> > permissions
> >
> > 2) Attempted the ODBC connection(which we had actually done before).
> > Failed - Error Message follows:
> > Microsoft SQL Server Login
> > SQLState: '01000'
> > SQL Server Error: 10061
> > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]
> > ConnectionOpen(Connect())
> > Connection Failed:
> > SQLState: '08001'
> > SQL Server Error: 17
> > [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets] SQL Server Does Not
> > Exist or Access Denied.
> >
> > Similar error message from SQL Enterprise Manager.
> >
> >
> > 3) Errorlog File on Windows 2000 Server
> > 2003-08-22 17:01:42.53 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.0 (Build 2195: Service Pack 4)
> >
> > 2003-08-22 17:01:42.61 server Copyright (C) 1988-2002 Microsoft
> > Corporation.
> > 2003-08-22 17:01:42.61 server All rights reserved.
> > 2003-08-22 17:01:42.61 server Server Process ID is 964.
> > 2003-08-22 17:01:42.61 server Logging SQL Server messages in file
> > 'C:\Program Files\Microsoft SQL Server\MSSQL\LOG\ERRORLOG'.
> > 2003-08-22 17:01:42.75 server SQL Server is starting at priority
class
> > 'normal'(1 CPU detected).
> > 2003-08-22 17:01:44.03 server SQL Server configured for thread mode
> > processing.
> > 2003-08-22 17:01:44.09 server Using dynamic lock allocation. [500]
Lock
> > Blocks, [1000] Lock Owner Blocks.
> > 2003-08-22 17:01:44.39 spid3 Starting up database 'master'.
> > 2003-08-22 17:01:47.53 server Using 'SSNETLIB.DLL' version '8.0.766'.
> > 2003-08-22 17:01:47.53 spid5 Starting up database 'model'.
> > 2003-08-22 17:01:47.65 spid3 Server name is 'EXCALIBURCENTRA'.
> > 2003-08-22 17:01:47.65 spid3 Skipping startup of clean database id 4
> > 2003-08-22 17:01:47.71 spid3 Skipping startup of clean database id 5
> > 2003-08-22 17:01:48.12 server SQL server listening on Shared Memory.
> > 2003-08-22 17:01:48.12 server SQL Server is ready for client
> connections
> > 2003-08-22 17:01:48.75 spid5 Clearing tempdb database.
> > 2003-08-22 17:01:54.71 spid5 Starting up database 'tempdb'.
> > 2003-08-22 17:01:55.99 spid3 Recovery complete.
> > 2003-08-22 17:01:55.99 spid3 SQL global counter collection task is
> > created.
> >
> > Attached files: Errorlog
> >
> > George Bergmark
> > Business Systems & Solutions Inc.
> > Houston, TX
> > www.solutions-intl.com
> >
> > "Steve Foster [SBS MVP]" <steve.foster@picamar.co.uk> wrote in message
> > news:#TTU3ZWaDHA.736@TK2MSFTNGP09.phx.gbl...
> > > George Bergmark wrote:
> > >
> > > > Steve,
> > > >
> > > > The Application we have installed is Microsoft Retail Management
> > > > System which can use MSDE or SQL Server 2000.
> > > >
> > > > We have brought the client's Server and POS workstation back to our
> > > > office for testing.
> > > >
> > > > We are logged on the Network as the Administrator.
> > > >
> > > > SQL Enterprise Manager is loaded on each machine, and can see it's
> > > > local instance of MSDE.
> > > >
> > > > But not accross the Network to see the other databases.
> > > >
> > > > We are using SQL Authentication and the SA User/password for access
> > > > to the SQL Servers.
> > > >
> > > > We have tried switching to Mixed Mode for NT Authentication, but no
> > > > joy.
> > > >
> > > > George
> > >
> > > What error message does EM give when you try to register the network
> > > SQL server?
> > >
> > > Have you tried using Query Analyzer?
> > >
> > > --
> > > Steve Foster [SBS MVP]
> > > ---------------------------------------
> > > MVPs do not work for Microsoft. Please reply only to the newsgroups.
> >
> >
>
>


Top