sql server connect: I've just built our new 2005 cluster and I'm having some issues with
connectivity via a client network alias. It's a 2 node active/active 64 bit
Ent Edit, sp1, 32gb ram. Both nodes are listening on port 1433 with both tcp
and named pipes (although we never use named pipes)

Node Names are:
vdb1
vdb2\ins2

Most everything is working like a champ. Except setting up a local alias
from my machine.

I setup an alias that connects to vdb2\ins2. The alias name is vdb2, port is
1433. I cannot get sqlwb to connect via the alias.

Error message pop up is "An error has occurred while establishing a
connection to the server. When connecting to SQL Server 2005, this failure
may be caused by the fact that under the default settings SQL Server does not
allow remote connections. (Provider: TCP Provider, error: 0 - No Connection
could be made because the target machine actively refused it) (Microsoft SQL
Server, Error 10061).

I can connect directly to vbdb2\ins2 (not using the alias) without failure.

The reason why this is important is I have lots of linked server code on
vdb1 that references vdb2.dbname.dbo.tablename. I would have to touch a lot
of code (probably 100 stored procs) to be [vdb2\ins2].dbname.dbo.tablename.

The aliases are working in 2000 on our current production boxes, but it
doesn't work on 2005. Any ideas?

I am having this exact same problem. Does anyone have any ideas??