MSDE TCP listen problem

I have recently installed a MSDE 2000 (unfortunately with no service pack yet) on a Standard Windows 2003 server. I have used the srvntcn.exe utility to make the MSDE server listen on TCP/IP port 1433. But it will not listen on that port! Or any other TCP
/IP port!! There is no information in the ERRORLOG file. This file just tells me, that MSDE is listening on Named Pipes and Shared Memory.
I have tried making my own application listen on port 1433 to see if there were some security settings on that port. And my application had no problem in listening on port 1433.
After looking in the Event Viewer I found a solution to my problem: Windows 2003 Server automatically close down TCP/IP listening for MSDE, if MSDE is not updated with a Service Pack. MSDE without Service Pack is not very secure to virusses like Slammer.
|||As a side note, this does not just occur for MSDE 2000. TCP/IP is shutdown
for all editions of SQL Server 2000 without service pack 3 on Windows 2003.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||I have updated with sp3a , but Windows 2003 server still automatically close
down TCP/IP listening for SQL , How do I alter it manual ?
"Finn Rasmussen" <anonymous@.discussions.microsoft.com> bl
news:BD399D59-0EA9-4981-82D7-1F4ADED91C4C@.microsoft.com g...
> After looking in the Event Viewer I found a solution to my problem:
Windows 2003 Server automatically close down TCP/IP listening for MSDE, if
MSDE is not updated with a Service Pack. MSDE without Service Pack is not
very secure to virusses like Slammer.

MSDE TCP listen problem

I have recently installed a MSDE 2000 (unfortunately with no service pack ye
t) on a Standard Windows 2003 server. I have used the srvntcn.exe utility to
make the MSDE server listen on TCP/IP port 1433. But it will not listen on
that port! Or any other TCP
/IP port!! There is no information in the ERRORLOG file. This file just tell
s me, that MSDE is listening on Named Pipes and Shared Memory.
I have tried making my own application listen on port 1433 to see if there w
ere some security settings on that port. And my application had no problem i
n listening on port 1433.After looking in the Event Viewer I found a solution to my problem: Windows
2003 Server automatically close down TCP/IP listening for MSDE, if MSDE is n
ot updated with a Service Pack. MSDE without Service Pack is not very secure
to virusses like Slammer.|||As a side note, this does not just occur for MSDE 2000. TCP/IP is shutdown
for all editions of SQL Server 2000 without service pack 3 on Windows 2003.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||I have updated with sp3a , but Windows 2003 server still automatically close
down TCP/IP listening for SQL , How do I alter it manual ?
"Finn Rasmussen" <anonymous@.discussions.microsoft.com> bl
news:BD399D59-0EA9-4981-82D7-1F4ADED91C4C@.microsoft.com g...
> After looking in the Event Viewer I found a solution to my problem:
Windows 2003 Server automatically close down TCP/IP listening for MSDE, if
MSDE is not updated with a Service Pack. MSDE without Service Pack is not
very secure to virusses like Slammer.

MSDE taskbar utility icon

I used to have an icon on then notification area of the taskbar which I
could use to start and stop MSDE. It has recently disappeard and I don't
have a clue how to restore it to the taskbar.
Can anyone give me a hint what this little utility is and how to make it
appear on the taskbar.
Thanks much.
Hi Michael,
It's the Service Manager. Try running it from Start>Programs>MSDE>Service
Manager.
If it doesn't appear, it might be that you have network connections
disabled. Look in svrnetcn.exe.
HTH,
Greg Low (MVP)
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Michael Appelmans" <mla@.zitinko.com> wrote in message
news:MPG.1b44e34cb08b40d89896aa@.news.microsoft.com ...
> I used to have an icon on then notification area of the taskbar which I
> could use to start and stop MSDE. It has recently disappeard and I don't
> have a clue how to restore it to the taskbar.
> Can anyone give me a hint what this little utility is and how to make it
> appear on the taskbar.
> Thanks much.
|||Hello,
You can also create a shortuc with the following command line in the start
menu (autostart)
"C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlmangr.exe" /n
"Greg Low (MVP)" <greglow@.lowell.com.au> a crit dans le message de
news:elpz3PkWEHA.2940@.TK2MSFTNGP09.phx.gbl...
> Hi Michael,
> It's the Service Manager. Try running it from Start>Programs>MSDE>Service
> Manager.
> If it doesn't appear, it might be that you have network connections
> disabled. Look in svrnetcn.exe.
> HTH,
> --
> Greg Low (MVP)
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "Michael Appelmans" <mla@.zitinko.com> wrote in message
> news:MPG.1b44e34cb08b40d89896aa@.news.microsoft.com ...
>
|||I don't seem to have an MSDE entry in my Start > All Programs menu. Not=20
sure why. The service manager runs fine when I use the command line you=20
provided.
Thanks much.
Michael
In article <eGpLWznWEHA.4020@.TK2MSFTNGP09.phx.gbl>, fa097770
@.nospam.skynet.be says...
> Hello,
>=20
> You can also create a shortuc with the following command line in the star=
t
> menu (autostart)
> "C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlmangr.exe" /n
>=20
>=20
> "Greg Low (MVP)" <greglow@.lowell.com.au> a =E9crit dans le message de
[vbcol=seagreen]
> news:elpz3PkWEHA.2940@.TK2MSFTNGP09.phx.gbl...
ce[vbcol=seagreen]
I[vbcol=seagreen]
n't[vbcol=seagreen]
it
>=20
>=20
>=20
|||Hello,
You can create a shortcut with the command line and after that move that
shortcut to the start menu.
"Michael Appelmans" <mla@.zitinko.com> a crit dans le message de
news:MPG.1b461a353834af939896ac@.news.microsoft.com ...
I don't seem to have an MSDE entry in my Start > All Programs menu. Not
sure why. The service manager runs fine when I use the command line you
provided.
Thanks much.
Michael
In article <eGpLWznWEHA.4020@.TK2MSFTNGP09.phx.gbl>, fa097770
@.nospam.skynet.be says...
> Hello,
> You can also create a shortuc with the following command line in the start
> menu (autostart)
> "C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqlmangr.exe" /n
>
> "Greg Low (MVP)" <greglow@.lowell.com.au> a crit dans le message de
[vbcol=seagreen]
> news:elpz3PkWEHA.2940@.TK2MSFTNGP09.phx.gbl...
Start>Programs>MSDE>Service[vbcol=seagreen]
I[vbcol=seagreen]
don't[vbcol=seagreen]
it
>
>
sql

MSDE OSQL Utility

Dear all,
I have a question about the OSQL utility and the installation of MSDE. I
tried to install MSDE and SQL Server on the same machine. This should work
some people told me. As a result however my application is no longer showing
me the available servers on the machine. (laptop).
I removed everything and reinstalled only MSDE.
When I use the OSQL utility and enter OSQL -L it says there are no servers.
Should it not say which server is available.
Has anyone experienced this before. My system is no longer showing the
available servers. My application still seems to work because when I type in
the name of the server manually it is located.
How can I solve this problem.
regards,
Danny Gaethofs
hi Danny,
"Danny Gaethofs" <dangaet@.home.nl> ha scritto nel messaggio
news:uAGDu0P4EHA.2404@.TK2MSFTNGP14.phx.gbl
> Dear all,
> I have a question about the OSQL utility and the installation of
> MSDE. I tried to install MSDE and SQL Server on the same machine.
> This should work some people told me. As a result however my
> application is no longer showing me the available servers on the
> machine. (laptop).
> I removed everything and reinstalled only MSDE.
> When I use the OSQL utility and enter OSQL -L it says there are no
> servers. Should it not say which server is available.
> Has anyone experienced this before. My system is no longer showing the
> available servers. My application still seems to work because when I
> type in the name of the server manually it is located.
> How can I solve this problem.
> regards,
> Danny Gaethofs
MSDE installs by default disabling network protocols in order to minimize
external (malicious) attacks, preventing the installed instances to be
available for remote connections and disabling it's broadcast enlisting for
available SQL Server/MSDE instances...
to make it available for remote users and to enable server enlistment you
have to use Server Network Utility (svrnetcn.exe) and enable the
desired/preferred network protocol(s)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE in WinXP Pro SP2

I have installed MSDE in WinXP Professional SP2, and already enabled the
TCP/IP protocol in SQL Server Network Utility. However, I find that it is
failure to connect the database by calling the IP Address even I test it
locally (use sa/window authorization) , but it is ok by calling the computer
name or (local) (also use sa/window authorization) . I have disabled the
firewall and the situation is no change.
Anyone have same experience on this case?

> Anyone have same experience on this case?
Yes, I have. But I have no answer how to fix it. There must be a bug
somwhere.
Regards,
Lars-Inge Tonnessen