listening on tcp port

Can someone please help me. For somereason my sql server isnt listening on the TCP ports but is listening on the shared pipes port. I congifured the server network utility to listen on the tcp port but when i look at the logs it still isnt listening. I
restarted the server and agent after i configured it and i even started the server. Doese anyone know how to enable SQL server to listen on TCP ports if it isnt already doing so.
Thanks
John
Hi
You can see the server protocols through server network manager. It could be
that it is not listening on the ports that you exepect. Therefore check out
the properties for TCP/IP.
John
"jaccurso" <jaccurso@.liserver.com> wrote in message
news:76A57F55-303E-4C38-8699-A2AD5E7C7D0D@.microsoft.com...
> Can someone please help me. For somereason my sql server isnt listening
on the TCP ports but is listening on the shared pipes port. I congifured
the server network utility to listen on the tcp port but when i look at the
logs it still isnt listening. I restarted the server and agent after i
configured it and i even started the server. Doese anyone know how to
enable SQL server to listen on TCP ports if it isnt already doing so.
> Thanks
> John

listening on tcp port

Can someone please help me. For somereason my sql server isnt listening on
the TCP ports but is listening on the shared pipes port. I congifured the s
erver network utility to listen on the tcp port but when i look at the logs
it still isnt listening. I
restarted the server and agent after i configured it and i even started the
server. Doese anyone know how to enable SQL server to listen on TCP ports i
f it isnt already doing so.
Thanks
JohnHi
You can see the server protocols through server network manager. It could be
that it is not listening on the ports that you exepect. Therefore check out
the properties for TCP/IP.
John
"jaccurso" <jaccurso@.liserver.com> wrote in message
news:76A57F55-303E-4C38-8699-A2AD5E7C7D0D@.microsoft.com...
> Can someone please help me. For somereason my sql server isnt listening
on the TCP ports but is listening on the shared pipes port. I congifured
the server network utility to listen on the tcp port but when i look at the
logs it still isnt listening. I restarted the server and agent after i
configured it and i even started the server. Doese anyone know how to
enable SQL server to listen on TCP ports if it isnt already doing so.
> Thanks
> John

listening on tcp port

Can someone please help me. For somereason my sql server isnt listening on the TCP ports but is listening on the shared pipes port. I congifured the server network utility to listen on the tcp port but when i look at the logs it still isnt listening. I restarted the server and agent after i configured it and i even started the server. Doese anyone know how to enable SQL server to listen on TCP ports if it isnt already doing so
Thank
JohnHi
You can see the server protocols through server network manager. It could be
that it is not listening on the ports that you exepect. Therefore check out
the properties for TCP/IP.
John
"jaccurso" <jaccurso@.liserver.com> wrote in message
news:76A57F55-303E-4C38-8699-A2AD5E7C7D0D@.microsoft.com...
> Can someone please help me. For somereason my sql server isnt listening
on the TCP ports but is listening on the shared pipes port. I congifured
the server network utility to listen on the tcp port but when i look at the
logs it still isnt listening. I restarted the server and agent after i
configured it and i even started the server. Doese anyone know how to
enable SQL server to listen on TCP ports if it isnt already doing so.
> Thanks
> John

Lisen Port

Hello,
I've an aplication make with Apache TomCat that uses the SQL as a DB motor,
i've installed the MSDE version.
Now the Apache couldn't conect with SQL, i think that the problem is in the
conection port, because i created an ODBC conection (in the server machine)
and it only runs property when i mark the option "detect port automaticly",
when i indicated the 1433 port the conection fails. In the apache
configuration i must put the conection port (pe. MYSERVER:1433), i tried
with the port 1433 but it don't works.
could somebody help me?
thanks
hi Tolo,
Tolo wrote:
> Hello,
> I've an aplication make with Apache TomCat that uses the SQL as a DB
> motor, i've installed the MSDE version.
> Now the Apache couldn't conect with SQL, i think that the problem is
> in the conection port, because i created an ODBC conection (in the
> server machine) and it only runs property when i mark the option
> "detect port automaticly", when i indicated the 1433 port the
> conection fails. In the apache configuration i must put the conection
> port (pe. MYSERVER:1433), i tried with the port 1433 but it don't
> works.
> could somebody help me?
> thanks
if you installed a default instance of MSDE it will listen on TCP/IP 1433
port, where named instances usually use dynamically assigned ports, those
requiring UDP 1434 port to be available for the SQL Server Resolution
Service, which will then report the appropriate network endpoints to use for
the particular SQL Server instance, redirecting the MDAC (requires MDAC 2.6
or above) client connections to the appropriate TCP port
you can however set a fixed port using the Server Network Utility
(svrnetcn.exe) and specifying the preferred port (TCP/IP 1433 in your case)
and thus resolving your problem...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Solved,
Thanks, thanks, thanks :D
best reggards,
Tolo
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> escribi en el mensaje
news:36pe05F52ncdvU1@.individual.net...
> hi Tolo,
> Tolo wrote:
> if you installed a default instance of MSDE it will listen on TCP/IP 1433
> port, where named instances usually use dynamically assigned ports, those
> requiring UDP 1434 port to be available for the SQL Server Resolution
> Service, which will then report the appropriate network endpoints to use
for
> the particular SQL Server instance, redirecting the MDAC (requires MDAC
2.6
> or above) client connections to the appropriate TCP port
> you can however set a fixed port using the Server Network Utility
> (svrnetcn.exe) and specifying the preferred port (TCP/IP 1433 in your
case)
> and thus resolving your problem...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>