Connecting to SharePoint MSDE Database

I have a SharePoint server that I want to be able to connect to its database
and pull info off. When I installed the Sharepoint server it installed an
instance of msde. For the life of me I cannot remotely connect to this MSDE
instance. I am able to remotely connect to the backup exec instance on the
same server and I am able to connect to it when logged in locally. I read
somewhere that you can only connect to the default instance of msde, is this
true? If so is there a way to change the sharepoint instance to the default
instance? any suggestions to this would be greatly appreciated.
OK, the error I get when attempting to connect to the sharepoint instance
from computer on LAN on port 1433 is:
SQL server does not exist or access denied
I can connect to Backup Exec instance from same computer on LAN. This
instance uses port 1207
I can connect to Sharepoint instance when logged on locally to the
sharepoint server.
I have port scanned the server and it is listening on port 1207 but not on
port 1433. I can telnet to port 1207 but not to 1433.
I have attempted to change the port # for the sharepoint instance and still
no success. There are no firewalls inbetween the connection.
I am running MSDE for 2000 with sp4 on it
TCP/IP and Named Pipes are enabled on both instances of MSDE.
We are discussing connecting to backupexec instance and linking servers to
sharepoint instance and then pull data off but this is kind of backwards way
of doing this...
"JPD" wrote:

> Hi,
> You should be able to connect to any instance of MSDE, whether or not it
> is a default or named instance. In fact you are already connecting to a
> named instance (the BACKUPEXEC one). Named instances are identified as
> follows:
> server_name\instance_name
> Default instances are identified just by the server (host) name.
> Furthermore you cannot change which instance is the default instance on
> your server. There is no such thing as a DEFAULT property associated
> with an instance. A default instance is one that uses the name of the
> host server. Named instances are a development over SQL Server 7.0 in
> which only one instance could be installed per Windows server. To get
> around this in SQL Server 2000 and later you can install multiple
> instances. You can choose to give them all a unique name or you could
> give up to one instance no name. It assumes the name of the host and is
> called the default instance.
> As far as your problem is concerned, in order to help further you need
> to tell us what error message you are getting when you attempting a
> connection.
> Jonathan
>
> APT SA wrote:
>
sqlsql