cannot locally telnet to 1433 but Mgt Studio ok ?

Hi,
I have a hosted server running win2003, sql express and an app I need to
connect to 1433.
In a cmd prompt I enter "telnet 99.99.99.99 1433" and I cannot connect.
(this works on every other server I have tested).
I CAN open sql mgt studio an connect ok (again on 1433 I guess by default)
and connect to the correct DB using the user my app uses.
My app throws an error as it cannot connect, I think I need to get this
telnet test working before my app will work. (app passes user + pass + IP +
DB).
What would block telnet on 1433 but still allow SQL Mgt Studio to connect on
1433 ?
My server IP is public, and telnet test uses public IP. Is it possible
telnet test is not routed locally and the Mgt Studio connection is routed
locally ?
I tried telnet on ip loop back but that did not work i.e "telnet 127.0.0.1
1433"
Thanks for any advice.
Scottsorry failed to mention Mgt Studio uses netbios name ... when i enter IP i
does not work ... so i guess its the way traffic is routed. must be a
filtered somewhere in security policy or routers. both win + sql
authenrtication work using netbios name but neither with ip.
can someone confirm how traffic in these situations is routed ?|||"Scott" <scott@.> wrote in message
news:eiCIekDIHHA.4688@.TK2MSFTNGP04.phx.gbl...
> sorry failed to mention Mgt Studio uses netbios name ... when i enter IP i
> does not work ... so i guess its the way traffic is routed. must be a
> filtered somewhere in security policy or routers. both win + sql
> authenrtication work using netbios name but neither with ip.
> can someone confirm how traffic in these situations is routed ?
>
SQL Server supports multiple network libraries, TCP/IP is one, but Named
Pipes and Shared Memory are two others. Locally on the box you will often
be using the Shared Memory library.
It sounds like TCP/IP is just not enabled. Check the SQL SErver log to be
sure. IT will tell you on startup all the listener endpoints it starts.
Here's my log
12/15/2006 08:44:40,Server,Unknown,SQL Server is now ready for client
connections. This is an . ..
12/15/2006 08:44:40,Server,Unknown,Server is listening on [ 127.0.0.1 <ipv4>
1434].
12/15/2006 08:44:40,Server,Unknown,Server is listening on [ ::1 <ipv6>
1434].
12/15/2006 08:44:40,Server,Unknown,Server local connection provider is ready
to accept connection on [ \\.\pipe\sql\query ].
12/15/2006 08:44:40,Server,Unknown,Server local connection provider is ready
to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
12/15/2006 08:44:40,Server,Unknown,Server is listening on [ 'any' <ipv4>
1433].
12/15/2006 08:44:40,Server,Unknown,Server is listening on [ 'any' <ipv6>
1433].
You can change the protocols used by your server using the SQL Server
Configuration Manager.
David|||many thanks for reply.
i think you are right about this.
Cheers
Scott