|
|
Posted by Erland Sommarskog on 10/02/80 11:56
Ted (r.ted.byers@rogers.com) writes:
> 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?
Obviously, when you try to debug connection issues on machines that you
don't see, you will have to rely on what you are told about the machines.
I can really only suggest that you review the desktop machine in the same
manner, and also verify that there is no firewall in the way.
If you are really desperate, you can get the port number for the
instance from SQL Configureation Manager, and then connect with:
SQLCMD -S MACHINE,2056
where you replace 2056 with the actual port number.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|