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.
Showing posts with label tcp. Show all posts
Showing posts with label tcp. Show all posts
Friday, March 30, 2012
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.
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.
Friday, March 23, 2012
MSDE over TCP/IP
I've got a SQL Server Desktop Engine (version 8.00.2039 - SP4) installation
running our SharePoint site. I now need to connect to this database remotely
via TCP/IP, but can't get it to enable the protocol.
The log file always just says:
2007-12-11 12:13:46.39 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2007-12-11 12:13:46.39 server SQL server listening on Shared Memory.
I've tried all the suggestions I've heard on the internet. What I've tried:
Install the latest MSDE Service Pack (SP4)
Use SVRNETCN.exe to enable the TCP/IP Protocol
Enable TCP/IP, Set to Port 0, Restart Service, Set to Port 1433, Restart
Service.
I've hard reset the machine, I've installed all the latest service packs on
this machine. I've disabled the firewall. I've tried ports other than 1433.
I've tried enabling Named Pipes & NWLink at various times as well. No matter
what I do, the log still shows it listening only on shared memory.
Any assistance would be greatly appreciated as I'm completely stumped.
Andrew Faust
http://www.andrewfaust.com
=?Utf-8?B?QW5kcmV3IEZhdXN0?= <andrew [at] andrewfaust.com> wrote in
news:23AE3B12-517E-4970-8F7D-3E094BE07541@.microsoft.com:
> I've got a SQL Server Desktop Engine (version 8.00.2039 - SP4)
> installation running our SharePoint site. I now need to connect to
> this database remotely via TCP/IP, but can't get it to enable the
> protocol.
> The log file always just says:
> 2007-12-11 12:13:46.39 server Using 'SSNETLIB.DLL' version
> '8.0.2039'. 2007-12-11 12:13:46.39 server SQL server listening on
> Shared Memory.
> I've tried all the suggestions I've heard on the internet. What I've
> tried:
> Install the latest MSDE Service Pack (SP4)
> Use SVRNETCN.exe to enable the TCP/IP Protocol
> Enable TCP/IP, Set to Port 0, Restart Service, Set to Port 1433,
> Restart Service.
> I've hard reset the machine, I've installed all the latest service
> packs on this machine. I've disabled the firewall. I've tried ports
> other than 1433. I've tried enabling Named Pipes & NWLink at various
> times as well. No matter what I do, the log still shows it listening
> only on shared memory.
> Any assistance would be greatly appreciated as I'm completely stumped.
If you see no effects at all from using svrnetcn.exe, perhaps you have got
multiple instances installed. Drop down the "Instances on this server"
combo at the top of the General tab of the svrnetcn.exe dialog (similarly
the Server combo at the top of the SQL Server Service Manager dialog).
|||Thanks for the response.
Unfortunately, that's not the problem. There is only 1 instance installed on
this server. I forgot to mention this before and don't know if it makes a
difference, but this is a named instance. It's called DOCMGR\SHAREPOINT. It's
also running on Windows Server 2003 with all the latest service packs
installed.
Andrew Faust
http://www.andrewfaust.com
"Chris.Cheney" wrote:
> =?Utf-8?B?QW5kcmV3IEZhdXN0?= <andrew [at] andrewfaust.com> wrote in
> news:23AE3B12-517E-4970-8F7D-3E094BE07541@.microsoft.com:
>
> If you see no effects at all from using svrnetcn.exe, perhaps you have got
> multiple instances installed. Drop down the "Instances on this server"
> combo at the top of the General tab of the svrnetcn.exe dialog (similarly
> the Server combo at the top of the SQL Server Service Manager dialog).
>
|||=?Utf-8?B?QW5kcmV3IEZhdXN0?= <andrew [at] andrewfaust.com> wrote in
news:B66EA507-0750-48F2-8E5F-F7B8FC60ED9F@.microsoft.com:
> Thanks for the response.
> Unfortunately, that's not the problem. There is only 1 instance
> installed on this server. I forgot to mention this before and don't
> know if it makes a difference, but this is a named instance. It's
> called DOCMGR\SHAREPOINT. It's also running on Windows Server 2003
> with all the latest service packs installed.
>
Well, it was something that was possible, given the symptoms you described.
Sorry, I'm out of further ideas. Good luck!
|||I appreciate the effort. I've finally given up on trying to make it work and
have moved my SharePoint to a full install of SQL Server 2000 and gotten the
functionality I needed.
Andrew Faust
http://www.andrewfaust.com
"Chris.Cheney" wrote:
> =?Utf-8?B?QW5kcmV3IEZhdXN0?= <andrew [at] andrewfaust.com> wrote in
> news:B66EA507-0750-48F2-8E5F-F7B8FC60ED9F@.microsoft.com:
>
> Well, it was something that was possible, given the symptoms you described.
> Sorry, I'm out of further ideas. Good luck!
>
running our SharePoint site. I now need to connect to this database remotely
via TCP/IP, but can't get it to enable the protocol.
The log file always just says:
2007-12-11 12:13:46.39 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2007-12-11 12:13:46.39 server SQL server listening on Shared Memory.
I've tried all the suggestions I've heard on the internet. What I've tried:
Install the latest MSDE Service Pack (SP4)
Use SVRNETCN.exe to enable the TCP/IP Protocol
Enable TCP/IP, Set to Port 0, Restart Service, Set to Port 1433, Restart
Service.
I've hard reset the machine, I've installed all the latest service packs on
this machine. I've disabled the firewall. I've tried ports other than 1433.
I've tried enabling Named Pipes & NWLink at various times as well. No matter
what I do, the log still shows it listening only on shared memory.
Any assistance would be greatly appreciated as I'm completely stumped.
Andrew Faust
http://www.andrewfaust.com
=?Utf-8?B?QW5kcmV3IEZhdXN0?= <andrew [at] andrewfaust.com> wrote in
news:23AE3B12-517E-4970-8F7D-3E094BE07541@.microsoft.com:
> I've got a SQL Server Desktop Engine (version 8.00.2039 - SP4)
> installation running our SharePoint site. I now need to connect to
> this database remotely via TCP/IP, but can't get it to enable the
> protocol.
> The log file always just says:
> 2007-12-11 12:13:46.39 server Using 'SSNETLIB.DLL' version
> '8.0.2039'. 2007-12-11 12:13:46.39 server SQL server listening on
> Shared Memory.
> I've tried all the suggestions I've heard on the internet. What I've
> tried:
> Install the latest MSDE Service Pack (SP4)
> Use SVRNETCN.exe to enable the TCP/IP Protocol
> Enable TCP/IP, Set to Port 0, Restart Service, Set to Port 1433,
> Restart Service.
> I've hard reset the machine, I've installed all the latest service
> packs on this machine. I've disabled the firewall. I've tried ports
> other than 1433. I've tried enabling Named Pipes & NWLink at various
> times as well. No matter what I do, the log still shows it listening
> only on shared memory.
> Any assistance would be greatly appreciated as I'm completely stumped.
If you see no effects at all from using svrnetcn.exe, perhaps you have got
multiple instances installed. Drop down the "Instances on this server"
combo at the top of the General tab of the svrnetcn.exe dialog (similarly
the Server combo at the top of the SQL Server Service Manager dialog).
|||Thanks for the response.
Unfortunately, that's not the problem. There is only 1 instance installed on
this server. I forgot to mention this before and don't know if it makes a
difference, but this is a named instance. It's called DOCMGR\SHAREPOINT. It's
also running on Windows Server 2003 with all the latest service packs
installed.
Andrew Faust
http://www.andrewfaust.com
"Chris.Cheney" wrote:
> =?Utf-8?B?QW5kcmV3IEZhdXN0?= <andrew [at] andrewfaust.com> wrote in
> news:23AE3B12-517E-4970-8F7D-3E094BE07541@.microsoft.com:
>
> If you see no effects at all from using svrnetcn.exe, perhaps you have got
> multiple instances installed. Drop down the "Instances on this server"
> combo at the top of the General tab of the svrnetcn.exe dialog (similarly
> the Server combo at the top of the SQL Server Service Manager dialog).
>
|||=?Utf-8?B?QW5kcmV3IEZhdXN0?= <andrew [at] andrewfaust.com> wrote in
news:B66EA507-0750-48F2-8E5F-F7B8FC60ED9F@.microsoft.com:
> Thanks for the response.
> Unfortunately, that's not the problem. There is only 1 instance
> installed on this server. I forgot to mention this before and don't
> know if it makes a difference, but this is a named instance. It's
> called DOCMGR\SHAREPOINT. It's also running on Windows Server 2003
> with all the latest service packs installed.
>
Well, it was something that was possible, given the symptoms you described.
Sorry, I'm out of further ideas. Good luck!
|||I appreciate the effort. I've finally given up on trying to make it work and
have moved my SharePoint to a full install of SQL Server 2000 and gotten the
functionality I needed.
Andrew Faust
http://www.andrewfaust.com
"Chris.Cheney" wrote:
> =?Utf-8?B?QW5kcmV3IEZhdXN0?= <andrew [at] andrewfaust.com> wrote in
> news:B66EA507-0750-48F2-8E5F-F7B8FC60ED9F@.microsoft.com:
>
> Well, it was something that was possible, given the symptoms you described.
> Sorry, I'm out of further ideas. Good luck!
>
Subscribe to:
Posts (Atom)