I just got a new link to a remove network that has a SQL Server on it.
When trying to connect through EM, I type the IP and try to register the
server and EM hangs (over 1/2 hour before process killed).
When trying to connect from QA - I get:
Unable to connect to server 192.168.3.101
Msg 17, Level 16, State 1
[MS][ODBC SQL Server][TCP/IP Sockets]SQL Server does not exist or access
denied.

I also tried ISQL and OSQL and get similar connection errors.

I can ping the server. I can connect via terminal server, so I know it is
not a routing issue. From the remote server, I can connect to SQL Servers on
my network using IPs. I can also connect to another remote SQL Server on a
third network using the IP.

Security is checked, both NT and SQL authentication. Changed and verified
pwd for the account. Remote server is SQL Server 2000.

I created a test ASP page on my machine that uses OLE-DB and it connects
fine to the remote server. The ASP page connects using the IP.

The only strange thing about the remote server is that it is dual homed.

After a good nights sleep, I added an alias on my local machine to use named
pipes and \[ip address]pipesqlquery and it works.

I checked the SQL Server (2000) and it has both named pipes and TCP/IP
Sockets, but named pipes is first. There does not appear to be a way to
change the ordering, so I am not sure what precendence is applied, or if it
matters.

Two other SQL 2000 servers on the local LAN have the same setup as my remote
server. They connect fine by default (my local client default is TCP/IP then
named pipes).

TCP/IP is the only protocol bound to all clients and servers on the LAN.

Anyone have any ideas?

Thanks in advance


way0utwest