Server not listening on TCP/IP

  • SQL Server 2005 is not listening on TCP/IP

    I can connect remotely with 'named pipes' but I need to connect from outside the network (i.e. home) via TCP/IP

    can any body explain/help

    here are the details...

    SQL Server 2005 developer edition, with SP1

    Surface area is set to 'using both TCP/IP and named pipes'

    SQL Server Configuration Manager > SQL Server 2005 Network Configuration > Protocols for is set as follows

    Shared Memory - Enabled

    Named Pipes - Enabled

    TCP/IP - Enabled

    VIA - Disabled

    TCP/IP is set as follows

    Protocol >

    Enabled: Yes

    Keep Alive: 30000

    Listen All: Yes

    No Delay: No

    IP Addresses >

    IP1:

    Active: Yes

    Enabled: Yes

    IP Adress: 172.16.5.21 (the address of the NIC)

    TCP Dynamic Ports: [empty]

    TCP Port: 1433

    IP2:

    Active: yes

    Enabled: No

    IP Adress: 127.0.0.1

    TCP Dynamic Ports: [empty]

    TCP Port: [empty]

    IPall:

    TCP Dynamic Ports: [empty]

    TCP Port: [empty]

    ERROR LOG (partial extract of relevant section) reports:

    006-10-27 12:46:03.21 spid5s Server name is 'THEBEAST\BEAST'. This is an informational message only. No user action is required.

    2006-10-27 12:46:03.43 Server A self-generated certificate was successfully loaded for encryption.

    2006-10-27 12:46:03.43 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\BEAST ].

    2006-10-27 12:46:03.43 Server Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$BEAST\sql\query ].

    2006-10-27 12:46:03.45 spid9s Starting up database 'model'.

    2006-10-27 12:46:03.46 Server Server is listening on [ 127.0.0.1 1059].

    The last line seems to be incompatible with the settings?

    I have also looked at netstat -a and there is something listening on 1059, but there is no listening port for 1433?

    can any body suggest where I might look, what I might do

    thanks in anticpation of some help...

    Garry

  • doesn't it always happen this way?!?!?!?

    I changed the TCP Port in IP all and it worked...

    IPall:

    TCP Dynamic Ports: [empty]

    TCP Port: 1433

    if anyone has the inclinination and time could they explain this to me?

Viewing 2 posts - 1 through 1 (of 1 total)

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