| Groups | Blog | Home |
sql server connect : MSDE instance being broadcast
I work in a domain environment with a couple of Enterprise Edition SQL
Servers. Using SSMS, when I go to register a new installation and I 'Browse for more' in the dialog box, I see a whole bunch of workstations that I know are set up with MSDE. How do I keep these machines from broadcasting their presence to the domain? All these MSDE installs are strictly for local machine use only and none of them should allow external connections. The fact that they are broadcasting their presence (they don't have SQL Browser because they are only MSDE) I see as a security risk. How can I stop this? Any suggestions. Thanks -- Todd Chittenden
Yes, it is a security risk. It's been some time since I worked with MSDE,
but I would investigate disabling the ports and protocols--much as the surface area configuration tool does for SQL Express 2005. This can be done if the applications are coded to use the shared memory provider (and bypass the network) and are not (in fact) shared on the net. hth -- ____________________________________ William (Bill) Vaughn Author, Mentor, Consultant Microsoft MVP INETA Speaker www.betav.com/blog/billva www.betav.com Please reply only to the newsgroup so that others can benefit. This posting is provided "AS IS" with no warranties, and confers no rights. __________________________________ Visit www.hitchhikerguides.net to get more information on my latest book: Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition) and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook) ----------------------------------------------------------------------------------------------------------------------- [quoted text, click to view] "Todd C" <ToddC@discussions.microsoft.com> wrote in message news:E302F2D1-165D-4DDB-BCA4-9BA587CBB237@microsoft.com... >I work in a domain environment with a couple of Enterprise Edition SQL > Servers. Using SSMS, when I go to register a new installation and I > 'Browse > for more' in the dialog box, I see a whole bunch of workstations that I > know > are set up with MSDE. > > How do I keep these machines from broadcasting their presence to the > domain? > All these MSDE installs are strictly for local machine use only and none > of > them should allow external connections. The fact that they are > broadcasting > their presence (they don't have SQL Browser because they are only MSDE) I > see > as a security risk. How can I stop this? > > Any suggestions. > > Thanks > -- > Todd Chittenden >
Bill:
That's all well and good, but HOW do I go about configuring an instance of MSDE when there is no user interface installed because it came packaged as part of some 3rd party app? Thanks -- Todd Chittenden [quoted text, click to view] "William (Bill) Vaughn" wrote:
> Yes, it is a security risk. It's been some time since I worked with MSDE, > but I would investigate disabling the ports and protocols--much as the > surface area configuration tool does for SQL Express 2005. This can be done > if the applications are coded to use the shared memory provider (and bypass > the network) and are not (in fact) shared on the net. > > hth > > -- > ____________________________________ > William (Bill) Vaughn > Author, Mentor, Consultant > Microsoft MVP > INETA Speaker > www.betav.com/blog/billva > www.betav.com > Please reply only to the newsgroup so that others can benefit. > This posting is provided "AS IS" with no warranties, and confers no rights. > __________________________________ > Visit www.hitchhikerguides.net to get more information on my latest book: > Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition) > and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook) > ----------------------------------------------------------------------------------------------------------------------- > > "Todd C" <ToddC@discussions.microsoft.com> wrote in message > news:E302F2D1-165D-4DDB-BCA4-9BA587CBB237@microsoft.com... > >I work in a domain environment with a couple of Enterprise Edition SQL > > Servers. Using SSMS, when I go to register a new installation and I > > 'Browse > > for more' in the dialog box, I see a whole bunch of workstations that I > > know > > are set up with MSDE. > > > > How do I keep these machines from broadcasting their presence to the > > domain? > > All these MSDE installs are strictly for local machine use only and none > > of > > them should allow external connections. The fact that they are > > broadcasting > > their presence (they don't have SQL Browser because they are only MSDE) I > > see > > as a security risk. How can I stop this? > > > > Any suggestions. > > > > Thanks > > -- > > Todd Chittenden > > > >
Again, it's been some time since I worked with MSDE and no, I know it does
not come with configuration tools. I expect you're going to have to visit each system and run a reconfig script or use SQL Server Management studio (not as easy). I found a site that seems to address some of these issues. http://www.codeproject.com/database/ConfigureMSDE.asp#7. I hope it helps. -- ____________________________________ William (Bill) Vaughn Author, Mentor, Consultant Microsoft MVP INETA Speaker www.betav.com/blog/billva www.betav.com Please reply only to the newsgroup so that others can benefit. This posting is provided "AS IS" with no warranties, and confers no rights. __________________________________ Visit www.hitchhikerguides.net to get more information on my latest book: Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition) and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook) ----------------------------------------------------------------------------------------------------------------------- [quoted text, click to view] "Todd C" <ToddC@discussions.microsoft.com> wrote in message news:2DF6889A-A64A-483F-BE42-766155FC8AF7@microsoft.com... > Bill: > That's all well and good, but HOW do I go about configuring an instance of > MSDE when there is no user interface installed because it came packaged as > part of some 3rd party app? > > Thanks > -- > Todd Chittenden > > "William (Bill) Vaughn" wrote: > >> Yes, it is a security risk. It's been some time since I worked with MSDE, >> but I would investigate disabling the ports and protocols--much as the >> surface area configuration tool does for SQL Express 2005. This can be >> done >> if the applications are coded to use the shared memory provider (and >> bypass >> the network) and are not (in fact) shared on the net. >> >> hth >> >> -- >> ____________________________________ >> William (Bill) Vaughn >> Author, Mentor, Consultant >> Microsoft MVP >> INETA Speaker >> www.betav.com/blog/billva >> www.betav.com >> Please reply only to the newsgroup so that others can benefit. >> This posting is provided "AS IS" with no warranties, and confers no >> rights. >> __________________________________ >> Visit www.hitchhikerguides.net to get more information on my latest book: >> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition) >> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook) >> ----------------------------------------------------------------------------------------------------------------------- >> >> "Todd C" <ToddC@discussions.microsoft.com> wrote in message >> news:E302F2D1-165D-4DDB-BCA4-9BA587CBB237@microsoft.com... >> >I work in a domain environment with a couple of Enterprise Edition SQL >> > Servers. Using SSMS, when I go to register a new installation and I >> > 'Browse >> > for more' in the dialog box, I see a whole bunch of workstations that I >> > know >> > are set up with MSDE. >> > >> > How do I keep these machines from broadcasting their presence to the >> > domain? >> > All these MSDE installs are strictly for local machine use only and >> > none >> > of >> > them should allow external connections. The fact that they are >> > broadcasting >> > their presence (they don't have SQL Browser because they are only MSDE) >> > I >> > see >> > as a security risk. How can I stop this? >> > >> > Any suggestions. >> > >> > Thanks >> > -- >> > Todd Chittenden >> > >> >> >>
Bill:
Thanks. Good stuff! --
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
August 2008
| home · blog · groups | Questions? Comments? Contact the dn |