Reposting this question to microsoft.public.sqlserver.clustering (was
originally in microsoft.public.sqlserver.jdbcdriver):

From: =?Utf-8?B?Sm9lbCBBcmFuZGlh?= <anonymous (AT) discussions (DOT) microsoft.com>
Subject: SuperSocket Info: Bind failed on TCP port 1433.
Date: Wed, 26 Nov 2003 13:06:20 -0800
Newsgroups: microsoft.public.sqlserver.jdbcdriver

"SuperSocket Info: Bind failed on TCP port 1433."

so the fix is supposed to be this:

http://support.microsoft.com/default...b;EN-US;319578

You're supposed to run sqlsetup and go to advanced options and redo the ip
address there.

But what if it hangs right after the security dialog? That's what it does
for me.

After I put in the cluster admin's username and password, it just
disappears and the sqlsetup process is just floating out there doing
nothing.

There are several potential causes/fixes for the bind failed message, if
you search on the error you will find 4-5 articles.

As a workaround while you try to run the setup program and reset the IP
address, you can try creating a named pipes alias in cliconfg.exe for the
SQL/instance.

Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.