Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Other Technologies / Clustering / April 2006

Tip: Looking for answers? Try searching our database.

Bind failed on TCP port 1433

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Manoj - 25 Apr 2006 17:22 GMT
Hi,

We recently change the IP of SQL Virtual server, the IP was updated using
the installation wizard. SQL Server starts but does not listens on port 1433,
below error is logged in event log

"19012 : SuperSocket Info: Bind failed on TCP port 1433."
"SuperSocket info: (SpnRegister) : Error 8344."

Any help is really appreciated.
Nils Loeber - 26 Apr 2006 09:29 GMT
Are you sure that there is no other application on port 1433? Check with
netstat. The second error message concerns Kerberos registration in Active
Directory and should have nothing to do with your problem.

Best regards,
Nils Loeber

> Hi,
>
[quoted text clipped - 7 lines]
>
> Any help is really appreciated.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.