|
|
Posted by Ted on 10/04/76 11:56
Erland Sommarskog wrote:
> Ted (r.ted.byers@rogers.com) writes:
> > As you can see, remote access to the default instance works fine, but I
> > get an error when I try to access the named instance.
> >
> > I have used the SQL Server Management Studio to verify that mixed
> > authentication, and remote connections, are enabled on the named
> > instance (and the uid was create in the same way, using the same pwd,
> > on both instances).
>
> Mangement Studio?
>
> A better place to look is the SQL Server Configuration Manager or the
> Surface Area Configuration tool. You need to enable the new instance
> for remote connections as well.
>
> Also, a named instance may require that the SQL Browser Service is running.
>
It looks like I needed all three. I verified that all machines and
instances use TCP/IP and that they are enabled for remote connections.
And on my desktop, I noticed that SQL Browser Service had somehow been
stopped, so I restarted it. Using all three tools, I checked all of
the security and connection properties on both machines, and I made
sure that all installed servers/services/instances are running.
The outcome is that I CAN now connect to the named instance on my
desktop using SQLCMD on my notebook without difficulty, now at least.
However, I can not connect to the named instance on my notebook using
SQLCMD on my desktop. In this case, I get the same error that I
reported previously. This isn't a showstopper since I can work with
the connections going in only one direction, but it makes me nervous
since, not understanding why connections from my desktop to my notebook
don't work, it seems possible that when we set this up on our client's
network, similar problems may arise. I will need to write up a
procedure that my colleagues can use to create and set up named
instances as the need arises.
Any ideas?
Ted
Navigation:
[Reply to this message]
|