<rmathuln@pacbell.net> wrote:

>The log says "Server is listening on [ 'any' <ipv4> 1043]."
>I've rechecked all of teh settings in teh Sql Configuration Utility
>Protocols for SQLEXPRESS and Client Protocols. All of the settings
>there are for port 1433.
>I have restarted teh PC without any chnage.
>Is there somewhere else to set this other that heh Sql Configuration
>Utility?
>
>
>On Sun, 24 Sep 2006 20:10:30 -0600, Sue Hoegemeier
><Sue_H@nomail.please> wrote:
>
>>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@pacbell.net> 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?