Problem when connecting to a named sql 2000 instance

Hi,
I have a problem when connecting to a named sql 2000 instance . The instance
is running in a 2 node cluster configuration. The second instance on the
other node works fine.
When I try to connect with a client on another pc, the connection only works
when I set the correct (static) port number.
But if I leave it to dynamically determine ports it is not able to connect.
There is no firewall between the client pc and the database server
and udp port 1434 is listening.
Stranger is that this problem also occurs on the server itself. When i
connect to the servernode where the instance of sql is running,
i have to set an alias with the portnumber to be able to connect to the
instance. Without this the connection fails.
Anybody any idea(s)?
Regards,
CihatUnfortunately no response. Here my response so that others with same problem
maybe solve it more quickly. When this happens and all checks appear okey,
you have to failover the group and reboot the server where this problem
occur. After the reboot it worked fine for me. Still dont know the cause, bu
t
it works now.
"Cihat" wrote:

> Hi,
> I have a problem when connecting to a named sql 2000 instance . The instan
ce
> is running in a 2 node cluster configuration. The second instance on the
> other node works fine.
> When I try to connect with a client on another pc, the connection only wor
ks
> when I set the correct (static) port number.
> But if I leave it to dynamically determine ports it is not able to connect
.
> There is no firewall between the client pc and the database server
> and udp port 1434 is listening.
> Stranger is that this problem also occurs on the server itself. When i
> connect to the servernode where the instance of sql is running,
> i have to set an alias with the portnumber to be able to connect to the
> instance. Without this the connection fails.
> Anybody any idea(s)?
> Regards,
> Cihat
>