Re: Defautl Hidden Shares
- From: "Roger Abell [MVP]" <mvpNoSpam@xxxxxxx>
- Date: Wed, 12 Apr 2006 04:07:24 -0700
The risks from the administrative shares are minimal if normal sane
practices are in use. Those only allow access by an admin account.
There is a risk of someone attempting login via the authentication
mechanisms that protect the administrative shares, using it as a way
to try to find username/password pairs. However, if only allowed
locations with supposedly trusted people have access to the needed
ports on those IPs, perhaps people that already have accounts, there
is little, if any, added risk.
Somewhat similarly for the IPC$ share you have mentioned, which
does not require an admin account.
"lwmccksg" <lwmccksg@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:85B9C50B-ABC8-4309-A8C2-BAD5EA9F3DA6@xxxxxxxxxxxxxxxx
I noted that during Windows 2000 Server setup, these hidden shares Admin$,
C$, D$ and IPC$ are created.
Most of the best practices from books mentioned to remove the hidden
shares.
What are the risks if these hidden shares are not remove?
Can i say that these hidden shares consist of
1) Admin$ - for administering the server which contains of Windows
system
utilities.
2) C$ & D$ - for may consist of application and data.
.
- Prev by Date: 802.1x Wired Config - automated method needed
- Next by Date: what permissions does a windows service need to execute another process? System.Diagnostics.Process process = System.Diagnostics.Process.Start(info); just local administrator? any specific permitions?
- Previous by thread: 802.1x Wired Config - automated method needed
- Next by thread: Re: Defautl Hidden Shares
- Index(es):
Relevant Pages
|
|
