[quoted text, click to view] Peter Lecki wrote:
> Have an MSDE named instance which works just fine. Just installed
> another instance of the same and can only connect to it using OSQL
> locally, nothing across the network. I made sure to use all the
> gotcha flags during install to enable network access, etc:
>
> setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="sapassword"
> INSTANCENAME="instancename" SECURITYMODE=SQL /L*v
> c:\temp\msdeinstlog.txt
>
> After the install and reboot, also verified that network access is
> allowed using SVRNETCN, where both named pipes and TCP connections are
> enabled.
>
> Tried connecting using "sa" and trusted NT auth and both work locally,
> but across the network it's always:
>
> [DBNETLIB]SQL Server does not exist or access denied.
> [DBNETLIB]ConnectionOpen (Connect()).
>
> No firewalls in the way from client to server. As a matter of fact,
> when I telnet to the TCP port shown in SVRNETCN, the connection is
> established, so the port is obviously open.
>
> I'm racking my brain on this one... What gives?
>
> Thanks guys,
> -Peter.
Starting with SQL Server Desktop Engine (also known as MSDE 2000)
Service Pack 3 (SP3) or SP3a , only local connectivity is permitted, by
default. If you want to permit remote connections to SQL Server Desktop
Engine, follow the steps in the following article:
814130 (
http://support.microsoft.com/kb/814130/) How to help secure
network connectivity for SQL Server 2000 local databases
http://support.microsoft.com/kb/814130/ --
David Gugick
Quest Software
www.quest.com