I'm having trouble connecting to a named instance on a SQL 2000 EE cluster
(Windows 2003). I have no problems connecting to the first virtual server by
name or IP address, but I can only connect to the named instance by using
the IP address and specifying a port (192.168.0.1, 1434).

I can connect to the named instance by IP or name from both cluster nodes,
the problem only arises with remote clients. The client machine I am testing
from is running Windows XP SP2, MDAC 2.8

Thanks in advance,

Curtis

Curtis O. Bouknight wrote:
1433 is the default sql port. The problem could be with the udp listener
which tells the client where the instance is running.

when you installed the named instance you created an alias on both nodes.
Did you remove these, and if so does the sql agent connect with lpc or is it
still using named pipes? If so clean the registry
HKLM\SOFTWARE\Microsoft\MSSQLServer\Client\SuperSo cketNetLib\LastConnect
and restart sql agent and see it fail?

Are both sqlservices running as local admin?

--
Hans

Welcome to my world.

This issue has been ongoing for me with Microsoft for almost a year now.
They have bounced around from it being a SQL Problem, to a network problem,
back to a SQL Problem, now they are looking at an OS problem. If you call
support, be ready to take system dumps, netstats, captures, etc...

One thing you can do to "verify" that you have the problem is to take a
tasklist and a netstat -aon on each node, then match the PID's up. One will
not have a listener on UDP 1434, and the other will. We had the same
scenario for quite some time, then suddenly the other node started exhibiting
the same behavior. We now tell customers to just go directly to the TCP/IP
port for both nodes to solve any confusion down the way.

js

"Curtis O. Bouknight" wrote: