[dba-SQLServer] PRETTY URGENT: How to connect to SQL Server 2005 on a workstation, not the server

Jeff,

I just tried setting up an Access 2003 ADP project on my wife's PC at home
connecting to SQL Server 2005 on my workstation.  We don't have anything
other than the Windows peer-to-peer network running.  I was able to connect
to the SQL Server on my system which is NOT a named copy.  The SQL Server
has the same name as my PC.

It's gotta be something related to access rights/sharing on that workstation
at my wife's office.  They have only the one server which does everything:
Exchange, SBS, SQL Server.  It also hosted the Access back end for the
application they run that they just recently upgraded to the SQL Server
version with ODBC connections to the Access front end.

Steve Erbach
Neenah, WI

On Tue, Dec 8, 2009 at 2:05 PM, Jeff B <jeff.developer at gmail.com> wrote:

> I believe that you need a NAMED copy of SQL Server in order to connect from
> a different workstation.
>
> Jeff Barrows
> MCP, MCAD, MCSD
>
> Outbak Technologies, LLC
> Racine, WI
> jeff.developer at gmail.com
>
> -----Original Message-----
> From: dba-sqlserver-bounces at databaseadvisors.com
> [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Steve
> Erbach
> Sent: Tuesday, December 08, 2009 12:58 PM
> To: Discussion concerning MS SQL Server
> Subject: [dba-SQLServer] PRETTY URGENT: How to connect to SQL Server 2005
> on
> a workstation, not the server
>
> Dear Group,
>
> I'm trying to help my wife who is the de facto network administrator for
> the
> small company she works for.  The main order processing application uses
> SQL
> Server 2005 on the domain server.  That SQL Server is having problems.
>
> What we've tried is to copy the MDF and log file to a workstation that has
> SQL Server 2005 installed on it.  The application is an Access MDB
> connected
> via ODBC to the SQL Server database.  We can connect to the SQL Server
> database just fine if we run the Access application on that workstation.
>
> The problem comes in when we try to connect to the database from another
> workstation on the LAN.  We keep getting "SQL Server not found".  I can't
> get the System ODBC connection to "see" the SQL Server on the
> workstation...nor can I get Access 2003 to create an ADP project to connect
> directly to SQL Server 2005 on that other workstation.
>
> We've got a call into Microsoft support to do the surgery necessary to get
> the main domain server's installation of SQL Server up and running...it's
> just that we thought we could point the Access application to the database
> on the workstation copy of SQL Server 2005 and at least get a couple
> workstations going with entering orders, etc.
>
> The server is Windows Small Business Server 2008 which includes SQL Server
> 2005 Standard edition.  The installation of SQL Server 2005 on the
> workstation is also Standard edition.
>
> Any clue as to how we can connect to a workstation copy of SQL Server?  I'm
> pulling my hair out trying to figure out why other workstations cannot
> "see"
> the SQL Server on the workstation.
>
> Regards,
>
> Steve Erbach
>