SQL Server open port
-
Hi all I just had a security problem & hope anyone of u can help me. I'm using a trial desktop program that connets to SQL server & while it's open my antivirus kept popping up a message saying that there is a port opened by SQL server. So is there any patch to solve this? Thanks a lot Happy
-
Hi all I just had a security problem & hope anyone of u can help me. I'm using a trial desktop program that connets to SQL server & while it's open my antivirus kept popping up a message saying that there is a port opened by SQL server. So is there any patch to solve this? Thanks a lot Happy
Normally SQL Server opens ports when it's started, if configured to do so. I suppose it's possible that the desktop program is starting the SQL Server service and the ports are being opened at that point. You can configure the network settings of SQL Server using the Server Network Utility from the Microsoft SQL Server program group. If this isn't on your start menu, look for svrnetcn.exe typically in the C:\Program Files\Microsoft SQL Server\80\Tools\Binn folder. Disable all network protocols you're not using - if you don't need remote access to this instance of SQL Server, disable everything except Shared Memory. Shared Memory may not actually be shown in this list - if not, just disable everything. If you still get the problem, it may be that SQL Server has not been upgraded to SP3 or later. Earlier versions still opened UDP port 1434 (used to map instance names to TCP ports) even if the TCP/IP protocol was disabled. If the version installed is actually MSDE (shown as Desktop Engine or Desktop Edition) and it was installed using the merge modules, it may not be possible to apply the downloadable SP4. You should check with the program's author.
Stability. What an interesting concept. -- Chris Maunder
-
Normally SQL Server opens ports when it's started, if configured to do so. I suppose it's possible that the desktop program is starting the SQL Server service and the ports are being opened at that point. You can configure the network settings of SQL Server using the Server Network Utility from the Microsoft SQL Server program group. If this isn't on your start menu, look for svrnetcn.exe typically in the C:\Program Files\Microsoft SQL Server\80\Tools\Binn folder. Disable all network protocols you're not using - if you don't need remote access to this instance of SQL Server, disable everything except Shared Memory. Shared Memory may not actually be shown in this list - if not, just disable everything. If you still get the problem, it may be that SQL Server has not been upgraded to SP3 or later. Earlier versions still opened UDP port 1434 (used to map instance names to TCP ports) even if the TCP/IP protocol was disabled. If the version installed is actually MSDE (shown as Desktop Engine or Desktop Edition) and it was installed using the merge modules, it may not be possible to apply the downloadable SP4. You should check with the program's author.
Stability. What an interesting concept. -- Chris Maunder
Hi Mike Thanks a loooooot. But I had another question,how can the program author solve this?? Should he download SP4 and then re-compile the program? Thanks again :) Happy
-
Hi Mike Thanks a loooooot. But I had another question,how can the program author solve this?? Should he download SP4 and then re-compile the program? Thanks again :) Happy
SP4 and recompiling won't make any difference. Does your app come with and install MSDE or SQL Express??
Dave Kreskowiak Microsoft MVP - Visual Basic
-
SP4 and recompiling won't make any difference. Does your app come with and install MSDE or SQL Express??
Dave Kreskowiak Microsoft MVP - Visual Basic
Hi Dave It installs MSDE.. So what is the solution??
-
Hi Dave It installs MSDE.. So what is the solution??
MSDE installs with network protocols turned on by default. You can turn them off at installation time in either of two ways: If your installing MSDE as part of a Merge Module in your applications Setup: [MSDE Deployment Toolkit](http://www.microsoft.com/downloads/details.aspx?FamilyID=6e9a7403-c4ba-4d98-bb0b-
2c9d6414071f&DisplayLang=en)[^] MSDE Deployment Toolkit in Action article[^] Or, if you're running the MSDE Setup yourself, you can turn the networking protocols off from the Setup command line. See "Customizing Desktop Engine Setup.exe[^]" for more information. But, in the simplest form, the MSDE Setup command line could look something like this:setup DISABLENETWORKPROTOCOLS=1
Dave Kreskowiak Microsoft MVP - Visual Basic