Sql Express (Build 2047) XP SP2 not listening

Tech-Archive recommends: Fix windows errors by optimizing your registry

I have installed Sql Server 2005 Express on a Windows XP PC running
SP2.
The Windows Firewall has ports 1433 and 1434 opened.
I ran the Sql Server Configuration Manager to set the Protocols for
SqlExpress and the Client Protocols to TCP and port 1433.
Restarted the PC.
Verified teh services are running.
Can connect on the same PC using Management Studio.
Cannot connect from other PCs though.
I run netstat -ano and I still cannot see the service listening on port
1433. I see the port 1434 there (SqlBrowser) but under UDP.

Am I missing a step(s) here?

.

Relevant Pages

  • Re: SQL 2000 personal vs TCP
    ... Windows XP Professional service pack 2 turns on the Windows Firewall. ... opening port 1433 or opening an exception for sqlservr.exe. ... Everything seems to be configured ok, right port, etc, but I discover my ... SQL Server is not listening on TCP. ...
    (microsoft.public.sqlserver.connect)
  • Re: ADP problems after SQL 2005 Upgrade
    ... Use the SQL Server Configuration Manager to create aliases; ... each port can be associated only with a single instance. ... Sylvain Lafontaine, ing. ...
    (microsoft.public.access.adp.sqlserver)
  • [NT] Microsoft SQL Server 2000 Unauthenticated System Compromise
    ... The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com ... Microsoft's database server SQL Server 2000 exhibits two buffer-overrun ... clients connecting to TCP port 1433 or both. ... This message is a single byte packet, ...
    (Securiteam)
  • Re: Do SqlServer 2000 & SqlServer 2005 co-exist
    ... Either SQL Server 2000 or SQL Server 2005. ... So you have to move one of them to another port. ... You could allow an program exception in your firewall instead of a port number exception. ... I understand that you can connect to SQL 2000 named instance on the local ...
    (microsoft.public.sqlserver.setup)
  • Re: IIS, SQL 2000 & XPs Firewall
    ... Only one instance of SQL Server can use TCP port 1434. ... You may find it easier to use SQL Server Configuration Manager ... 2008 will be a named instance ... you will have to open those as exceptions in the firewall. ...
    (microsoft.public.sqlserver.connect)