Can’t a client easily register an instance of MSDE using any third party GUI
or EM and get hold of our data structure? How can I over come this issue, if
I am installing MSDE on client computer?
thanx
hi,
"Job Lot" <JobLot@.discussions.microsoft.com> ha scritto nel messaggio
news:7002631C-B28D-4785-8C16-2EFE5D74BD50@.microsoft.com
> Can’t a client easily register an instance of MSDE using any third
> party GUI or EM and get hold of our data structure? How can I over
> come this issue, if I am installing MSDE on client computer?
> thanx
a MSDE instance can be easly registered as a linked server or in EM, from
remote (as long as the required network protocols are enabled) or local pc,
or using third party tools... as long as login privileges are set to the
logged user or a valid SQL Server login is known...
to access the databases, another issue must be granted (quite easy), that's
to say the logged user (login) is mapped to a valid database user...
if the login (both NT [trusted connections] or SQL Server [requiring "user"
and "pwd" credentials]) is member of WinNT administrators group (and thus)
or sysadmins server roles, he/she can actually do whatever he/she wants as
that membership grants illimitate privileges...
this design is part of the SQL Server security and can not be cut... so you
have to grant minimal privileges (server side) to logins in order to allow
only to specific logins the ability to access you databases..
a good article about security model is presented at
http://www.sql-server-performance.co...l_security.asp and
http://www.microsoft.com/technet/pro.../sp3sec03.mspx
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
Showing posts with label register. Show all posts
Showing posts with label register. Show all posts
Monday, March 12, 2012
Friday, March 9, 2012
MSDE instance registration in Enterprise Manager
Hi All,
I'm trying to register an instance of MSDE on a remote machine using EM on my desktop. The remote machine has 2
named instances of MSDE running. I am able to register 1 instance with no problems. I had to register it using
"RemoteServer1\InstanceName" rather than just the remote machines name.
For the life of me I can not get the other instance to register. I get the "SQL Server does not exist or access
denied" error. I've tried just registering the 2nd instance without the first with the same results. I can see
no difference in the way either of the 2 instances were set up or in their properties. I am a machine admin on
the remote machine and am connecting using Windows Auth.
What am I missing and how can I register that 2nd instance?
Thank you.
gdr
Gary D. Rezek
University Networking Systems and Services
South Dakota State University
hi Gary,
Gary D. Rezek wrote:
> Hi All,
> I'm trying to register an instance of MSDE on a remote machine using
> EM on my desktop. The remote machine has 2 named instances of MSDE
> running. I am able to register 1 instance with no problems. I had to
> register it using "RemoteServer1\InstanceName" rather than just the
> remote machines name.
this is normal as a named instance full qualified name is
ComputerName\InstanceName...
> For the life of me I can not get the other instance to register. I
> get the "SQL Server does not exist or access denied" error. I've
> tried just registering the 2nd instance without the first with the
> same results. I can see no difference in the way either of the 2
> instances were set up or in their properties. I am a machine admin on
> the remote machine and am connecting using Windows Auth. What am I
> missing and how can I register that 2nd instance?
at least 1 difference must be present... the name... MSDE/SQL Server 2000
can be installed as a default instance or a named instance... but only a
default instance can be present, wit up to other 15 named instances per
computer...
as you already saw, a default instance is available as ComputerName, where a
named instance will be as ComputerName\InstanceName...
you can inspect your (remote) services for MSSQLSERVER and
MSSQL$InstanceName to see what is going on...
MSDE installs by default disabling network protocols, thus not allowing
remote connections... please verify using the Server Network Utiliy
(svrnetcn.exe) that the "failing" instance has enabled network protocols...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea,
Thanks for your answer. It eventually led me to http://tinyurl.com/8q95s this post. In that post I found this
quote...
"You need to look for a line in the error log which states:
"SQL server listening on TCP, Shared Memory, Named Pipes.
"If you only have Shared Memory on this list, then only local connections are allowed."
In the instance I have been trying to connect, Shared Memory is the only thing listed in the errorlog, so no
TCP/IP or Named Pipes. I asked the individual who is responsible for the application which created this instance
of MSDE (and also the one who asked me WHY can't he connect through EM), I learned that this is the way it
should be. :^/ I've worked with MSDE very, very little, but I still should have looked at the ErrorLog to
begin with.
Thank you very much for your help
gdr
Gary D. Rezek
University Networking Systems and Services
South Dakota State University
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message news:3jg2rjFpnmhnU1@.individual.net...
> hi Gary,
> Gary D. Rezek wrote:
> this is normal as a named instance full qualified name is ComputerName\InstanceName...
>
> at least 1 difference must be present... the name... MSDE/SQL Server 2000 can be installed as a default
> instance or a named instance... but only a default instance can be present, wit up to other 15 named instances
> per computer...
> as you already saw, a default instance is available as ComputerName, where a named instance will be as
> ComputerName\InstanceName...
> you can inspect your (remote) services for MSSQLSERVER and MSSQL$InstanceName to see what is going on...
> MSDE installs by default disabling network protocols, thus not allowing remote connections... please verify
> using the Server Network Utiliy (svrnetcn.exe) that the "failing" instance has enabled network protocols...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual interface)
> -- remove DMO to reply
>
|||h Gary,
Gary D. Rezek wrote:
> Hi Andrea,
> Thanks for your answer. It eventually led me to
> http://tinyurl.com/8q95s this post. In that post I found this quote...
> "You need to look for a line in the error log which states:
> "SQL server listening on TCP, Shared Memory, Named Pipes.
> "If you only have Shared Memory on this list, then only local
> connections are allowed."
you always have to verify (on the server using Server Network Utility
[svrnetcn.exe] and on the client using Client Network Utility
[cliconfg.exe]) that a common network protocol is available for the client
and the server to dialog...
> In the instance I have been trying to connect, Shared Memory is the
> only thing listed in the errorlog, so no TCP/IP or Named Pipes. I
> asked the individual who is responsible for the application which
> created this instance of MSDE (and also the one who asked me WHY
> can't he connect through EM), I learned that this is the way it
> should be. :^/
if Shared Memory is the only protocol that "must" be enabled, then no remote
connections will be available... but it can be ok in local scenarios
..
MSDE will then actually be used as a local desktop database..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
I'm trying to register an instance of MSDE on a remote machine using EM on my desktop. The remote machine has 2
named instances of MSDE running. I am able to register 1 instance with no problems. I had to register it using
"RemoteServer1\InstanceName" rather than just the remote machines name.
For the life of me I can not get the other instance to register. I get the "SQL Server does not exist or access
denied" error. I've tried just registering the 2nd instance without the first with the same results. I can see
no difference in the way either of the 2 instances were set up or in their properties. I am a machine admin on
the remote machine and am connecting using Windows Auth.
What am I missing and how can I register that 2nd instance?
Thank you.
gdr
Gary D. Rezek
University Networking Systems and Services
South Dakota State University
hi Gary,
Gary D. Rezek wrote:
> Hi All,
> I'm trying to register an instance of MSDE on a remote machine using
> EM on my desktop. The remote machine has 2 named instances of MSDE
> running. I am able to register 1 instance with no problems. I had to
> register it using "RemoteServer1\InstanceName" rather than just the
> remote machines name.
this is normal as a named instance full qualified name is
ComputerName\InstanceName...
> For the life of me I can not get the other instance to register. I
> get the "SQL Server does not exist or access denied" error. I've
> tried just registering the 2nd instance without the first with the
> same results. I can see no difference in the way either of the 2
> instances were set up or in their properties. I am a machine admin on
> the remote machine and am connecting using Windows Auth. What am I
> missing and how can I register that 2nd instance?
at least 1 difference must be present... the name... MSDE/SQL Server 2000
can be installed as a default instance or a named instance... but only a
default instance can be present, wit up to other 15 named instances per
computer...
as you already saw, a default instance is available as ComputerName, where a
named instance will be as ComputerName\InstanceName...
you can inspect your (remote) services for MSSQLSERVER and
MSSQL$InstanceName to see what is going on...
MSDE installs by default disabling network protocols, thus not allowing
remote connections... please verify using the Server Network Utiliy
(svrnetcn.exe) that the "failing" instance has enabled network protocols...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea,
Thanks for your answer. It eventually led me to http://tinyurl.com/8q95s this post. In that post I found this
quote...
"You need to look for a line in the error log which states:
"SQL server listening on TCP, Shared Memory, Named Pipes.
"If you only have Shared Memory on this list, then only local connections are allowed."
In the instance I have been trying to connect, Shared Memory is the only thing listed in the errorlog, so no
TCP/IP or Named Pipes. I asked the individual who is responsible for the application which created this instance
of MSDE (and also the one who asked me WHY can't he connect through EM), I learned that this is the way it
should be. :^/ I've worked with MSDE very, very little, but I still should have looked at the ErrorLog to
begin with.
Thank you very much for your help
gdr
Gary D. Rezek
University Networking Systems and Services
South Dakota State University
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message news:3jg2rjFpnmhnU1@.individual.net...
> hi Gary,
> Gary D. Rezek wrote:
> this is normal as a named instance full qualified name is ComputerName\InstanceName...
>
> at least 1 difference must be present... the name... MSDE/SQL Server 2000 can be installed as a default
> instance or a named instance... but only a default instance can be present, wit up to other 15 named instances
> per computer...
> as you already saw, a default instance is available as ComputerName, where a named instance will be as
> ComputerName\InstanceName...
> you can inspect your (remote) services for MSSQLSERVER and MSSQL$InstanceName to see what is going on...
> MSDE installs by default disabling network protocols, thus not allowing remote connections... please verify
> using the Server Network Utiliy (svrnetcn.exe) that the "failing" instance has enabled network protocols...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual interface)
> -- remove DMO to reply
>
|||h Gary,
Gary D. Rezek wrote:
> Hi Andrea,
> Thanks for your answer. It eventually led me to
> http://tinyurl.com/8q95s this post. In that post I found this quote...
> "You need to look for a line in the error log which states:
> "SQL server listening on TCP, Shared Memory, Named Pipes.
> "If you only have Shared Memory on this list, then only local
> connections are allowed."
you always have to verify (on the server using Server Network Utility
[svrnetcn.exe] and on the client using Client Network Utility
[cliconfg.exe]) that a common network protocol is available for the client
and the server to dialog...
> In the instance I have been trying to connect, Shared Memory is the
> only thing listed in the errorlog, so no TCP/IP or Named Pipes. I
> asked the individual who is responsible for the application which
> created this instance of MSDE (and also the one who asked me WHY
> can't he connect through EM), I learned that this is the way it
> should be. :^/
if Shared Memory is the only protocol that "must" be enabled, then no remote
connections will be available... but it can be ok in local scenarios
..MSDE will then actually be used as a local desktop database..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
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)
------
"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
"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...
>
>
|||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)
------
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:2DF6889A-A64A-483F-BE42-766155FC8AF7@.microsoft.com...[vbcol=seagreen]
> 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:
|||Bill:
Thanks.
Good stuff!
Todd
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)
------
"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
"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...
>
>
|||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)
------
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:2DF6889A-A64A-483F-BE42-766155FC8AF7@.microsoft.com...[vbcol=seagreen]
> 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:
|||Bill:
Thanks.
Good stuff!
Todd
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 se
e
as a security risk. How can I stop this?
Any suggestions.
Thanks
--
Todd ChittendenYes, 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:
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 don
e
> if the applications are coded to use the shared memory provider (and bypas
s
> 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...
>
>|||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...gureMSDE.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)
----
---
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:2DF6889A-A64A-483F-BE42-766155FC8AF7@.microsoft.com...[vbcol=seagreen]
> 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:
>|||Bill:
Thanks.
Good stuff!
Todd
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 se
e
as a security risk. How can I stop this?
Any suggestions.
Thanks
--
Todd ChittendenYes, 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:
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 don
e
> if the applications are coded to use the shared memory provider (and bypas
s
> 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...
>
>|||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...gureMSDE.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)
----
---
"Todd C" <ToddC@.discussions.microsoft.com> wrote in message
news:2DF6889A-A64A-483F-BE42-766155FC8AF7@.microsoft.com...[vbcol=seagreen]
> 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:
>|||Bill:
Thanks.
Good stuff!
Todd
Subscribe to:
Posts (Atom)