Re: Sql Express (Build 2047) XP SP2 not listening

Did you check the SQL Server logs from the startup to see if
the protocols are listed and what ports it's actually
listening on?
Did you enable remote connections for the protocols?
If it's a named instance - I think that's the default for
express - did you start the browser service (or restart
after changing connectivity settings)?
And also for the firewall, try creating an exception to
allow communication for sqlservr.exe and sqlbrowser.exe.

-Sue

On 24 Sep 2006 18:25:46 -0700, "Rlane"
<rmathuln@xxxxxxxxxxx> wrote:

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: IIS, SQL 2000 & XPs Firewall
    ... Queries to the Data Engine must go to the port that SQL Server is listening ... More info: How to: Configure a Windows Firewall for Database Engine Access ...
    (microsoft.public.sqlserver.connect)
  • Re: Remote connection problems
    ... tab has Listen All as Yes, then the individual settings for IP1 and IP2 are ... like you are listening on dynamic ports and it is currently listening on ... different port. ... and pick a port number you like, and then restart SQL Server. ...
    (microsoft.public.sqlserver.connect)
  • Re: Connecting to DB with Static IP over the internet
    ... port and dmz was forward to the incorect internal ip address:) ... and any other ms sql server related ports on the server. ... item on the connection string. ... is listening, I do netstat -a and it does list that it is being listened ...
    (microsoft.public.sqlserver.setup)
  • Re: Server not listening on 1433
    ... sql server may be listening in a different port. ... >>> Server error log. ...
    (microsoft.public.sqlserver.setup)
  • Re: Blocking UDP Port 1434
    ... You can configure SQL Server ... >>> planning to block UDP Port 1434 on all gateways. ... >>> the sql instance is listening on can be re-assigned, ...
    (microsoft.public.sqlserver.server)