XP Service Pack 2 disabled TCP

  • Hi

    Since I installed service pack TCP has been disabled on SqlServer. Event message is:

    You are running a version of Microsoft SQL Server 2000 or Microsoft SQL Server 2000 Desktop Engine (also called MSDE) that has known security vulnerabilities when used in conjunction with this version of Windows. To reduce your computer's vulnerability to certain virus attacks, the TCP/IP and UDP network ports of Microsoft SQL Server 2000, MSDE, or both have been disabled. To enable these ports, you must install a patch, or the most recent service pack for Microsoft SQL Server 2000 or MSDE from http://www.microsoft.com/sql/downloads/default.asp

    I would rather not install the patch at this moment in time. Is there anything I can do to disable this message?

    Thanks

    Glyn

  • Check to see if the TCP is disabled in the Networking settings for SQL Server. It might have been removed and you can add it back. Also the XP firewall is probably blocking 1433. Change this to allow 1433 to come through to connect.

  • Thanks for the reply. TCP was in the config but must have been disabled in the sqlserver startup by windows as there were no processes listening on 1433 according to netstat. I have rolled back service pack 2 and am back to normal until I'm ready to roll them all forward again. Thanks for your help.

  • Check the Microsoft website. Can't recall the KB number at the moment, but there are specific instructions of what you need to do to allow SQL to communicate via TCP.

    --------------------
    Colt 45 - the original point and click interface

  • according to lots of articles on micorosoft.com xp sp2 disables ports 1433 and 1434 and 455(TCP and UDP and Named pipes) by default

    you can re-enable these in the XP security centre by adding a firewall excusion to those port numbers

    heres is the areticle on how to configure it

    http://support.microsoft.com/default.aspx?scid=kb;en-us;841249

    MVDBA

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply