Results 1 to 3 of 3

Thread: Bind Failed on TCP port

  1. #1
    Manesh Guest

    Bind Failed on TCP port

    On SQL Cluster server I changed the IP address for the virtual sql server to diffreent ip segment. Scient then I am getting followin error on eventlog
    "19012 :
    SuperSocket Info: Bind failed on TCP port 1433."
    Users can connect thru named pipe not thru TCP/IP. Any help or suggestion?.

    Thanks
    Manesh



  2. #2
    Ray Miao Guest

    Bind Failed on TCP port (reply)

    IP address for virtual sql server has to be on same segment as physical node's.


    ------------
    Manesh at 12/20/2001 3:37:47 PM

    On SQL Cluster server I changed the IP address for the virtual sql server to diffreent ip segment. Scient then I am getting followin error on eventlog
    "19012 :
    SuperSocket Info: Bind failed on TCP port 1433."
    Users can connect thru named pipe not thru TCP/IP. Any help or suggestion?.

    Thanks
    Manesh



  3. #3
    Manesh Guest

    Bind Failed on TCP port (reply)


    Yes, It is the same segment as physical node's.

    ------------
    Ray Miao at 12/20/2001 4:45:25 PM

    IP address for virtual sql server has to be on same segment as physical node's.


    ------------
    Manesh at 12/20/2001 3:37:47 PM

    On SQL Cluster server I changed the IP address for the virtual sql server to diffreent ip segment. Scient then I am getting followin error on eventlog
    "19012 :
    SuperSocket Info: Bind failed on TCP port 1433."
    Users can connect thru named pipe not thru TCP/IP. Any help or suggestion?.

    Thanks
    Manesh



Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •