>>Hi,
>>
>>In the attempt to troubleshoot an issue where customers cannot connect to the SQL Server, I came across the following:
>>
>>When running NETSTAT I don't see the SQL Server listening on the port 1433. On another server when executing NETSTAT there is a line:
>>
>>TCP 999.99.99.999:1433 ESTABLISHED
>>
>>
>>But not on this server. Where can I go to Connections properties on SQL Server (this is SQL Server 2008 Express) the box Allow remote connections to this server is checked.
>>In the SQL Server Configuration Manager the Protocols for SQLEXPRESS TCP/IP is enabled.
>>
>>The only thing Stopped is SQL Server Agent. Does it need to be started?
>>
>>Where else should I look? TIA
>
>
>You can't start Agent on Express version of SQL Server.
>By default SQL Server Express is installed on named instance and it not use 1433 port.
>It uses dynamic ports.
You are right about the Agent.
If SQL Server Express is installed on named instance (which is so) and not use port 1433, how do I find out what port is used? And how to I find out what is blocking user access to the SQL?
Thank you.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
